You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How I would like to use Maestro:
Developers can write tests with the Maestro CLI locally and add them to a folder in our app repository.
For running them on the CI, I would use the programmatic approach and create a small script to get all files from this folder and run them one by one with the programmatic approach.
Why? Our CI system runs on Linux, so I can not install the Maestro CLI with brew.
The text was updated successfully, but these errors were encountered:
Programmatic usage of Maestro is also possible, albeit I would not recommend it for your use case. If you would still like to try, add Maestro as a Gradle/Maven dependency , read commands by using YamlCommandReader, create a Maestro instance (i.e. Maestro.android()), and pass it all to Orchestra class.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue.
Thank you for helping keep us our issue tracker clean!
How I would like to use Maestro:
Developers can write tests with the Maestro CLI locally and add them to a folder in our app repository.
For running them on the CI, I would use the programmatic approach and create a small script to get all files from this folder and run them one by one with the programmatic approach.
Why? Our CI system runs on Linux, so I can not install the Maestro CLI with brew.
The text was updated successfully, but these errors were encountered: