run-android-maestro-flows 0.1.3

[chloe-vilain]

What to do if the build fails?

At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.

New Pull Request Checklist

Please mark the points which you did / accept.

• I will not move an already shared step version's tag to another commit
• I read the Step Development Guideline
• I have a test for my Step, which can be run with bitrise run test (in the step's repository)
• I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
• I read and accept the Abandoned Step policy

Note -
I noted from the Step Development Guide that installing external dependencies within a step is not preferred. Unfortunately, per the maestro documentation, there isn't an existing apt-get packaging for the maestro cli. I judged it more maintainable to use curl (the approach suggested by the maestro documentation) to pull & install the dependency, rather than manually copying down all the pertinent files at the current version and including them in my step. This is consistent with the approach taken by the iOS test runner community step: https://github.com/fepersembe/bitrise-step-maestro-ios-test-run

New Step
Thank you for the new Step share! The CI check might will fail due to our extended validation engine. Nothing to worry about yet, we will get back to you shortly.

[bitrise-coresteps-bot]

Don't forget to follow semantic versioning! Breaking changes (including step inputs) should be in major versions only.

step.yml changes compared to previous version:

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ofalvai]

Thank you @chloe-vilain for the contribution, this is a solid step! 🚀
Just a note about macOS: at the moment, Android emulators don't run on macOS machines because of a limitation in nested virtualization. But we expect this to be resolved in the future, so I'm okay with this step handling both macOS and Linux dependencies, I think it's the future-proof way!

[ofalvai]

Oh, one for thing before I can merge: the CLI signature is missing, or maybe you signed it with another email address than what the git commit contains.

[lpusok]

@chloe-vilain can you proceed with the CLI signature or should we close this?