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

Using Maestro programmatically accept a yaml file as argument #94

Closed
BenedictP opened this issue Aug 29, 2022 · 2 comments
Closed

Using Maestro programmatically accept a yaml file as argument #94

BenedictP opened this issue Aug 29, 2022 · 2 comments

Comments

@BenedictP
Copy link

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.

@dmitry-zaitsev
Copy link
Contributor

Maestro does in fact work on Linux (as it is written in Kotlin) and can be installed via Homebrew (that also works on Linux, with few tweaks). I have update our documentation with steps on how to install it: https://maestro.mobile.dev/getting-started/installing-maestro#cli

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.

Copy link

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!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants