Repository navigation
Maestro CLI execution issues #3570
Unanswered
s473989541-prog
asked this question in
Q&A
Replies: 3 comments 1 reply
0 replies
|
I'm not yet convinced that the additional complexity in Maestro is warranted. Have you considered accessibility labels for those buttons that would make them addressable? Or perhaps relational selectors would work for you? |
0 replies
|
All of this has been considered, but it relies on the development team, and not all developers are willing to configure it. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When our company uses Maestro for app automation, many buttons are implemented using images, lacking unique XPath expressions. Given this, I manually wrote a Maestro executor to parse steps in the YAML file. It executes each step individually, but this initializes the Maestro process for each step, resulting in very slow execution. Should we consider initializing the Maestro CLI only once, so that subsequent Maestro tests executing YAML files reuse the existing Maestro process?
All reactions