Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 [VIS-4480] Get maestro working on android api level 24 and above and build and deploy to github releases #1

Conversation

testifyqa
Copy link

VIS-4480

Problem

We want to use Maestro as a black-box test framework that we can use with device farm in CI. Official Maestro does not support API 25 and below.

Solution

I have made a PR in the Open Source repo here -> mobile-dev-inc#1527. It is actually going to be merged soon apparently but until then, I have forked the repo here and made the same fix to support older Android versions and also build and deploy the maestro-cli binary to our own GitHub releases so that Bitrise workflows can later grab the maestro-cli tool and use it for testing against real devices in CI

Screenshots / videos

N/A

Prevention

N/A

Manual QA testing notes

Areas affected that need attention from QA:
N/A

Checklist

I have:

  • considered documenting breaking changes for public module APIs in RELEASE_NOTES.md
  • considered testing UI changes on A80
  • tested all important logic with unit tests, except mentioned above
  • done a self-review and believe the PR follows our best practices

@testifyqa testifyqa force-pushed the task/VIS-4480-build-maestro-from-fork-and-deploy-binary-for-use-by-bitrise branch from e35b109 to db3a1b3 Compare November 28, 2023 15:27
@testifyqa testifyqa merged commit b5261b7 into main Nov 28, 2023
3 checks passed
@testifyqa testifyqa deleted the task/VIS-4480-build-maestro-from-fork-and-deploy-binary-for-use-by-bitrise branch November 28, 2023 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants