Migrate
Maestro
Convert Maestro YAML flows to Autonomy mobile test cases. Turn declarative commands into natural-language steps.
Maestro flows are already declarative and close to Autonomy's step vocabulary, so this migration is mostly mechanical. Autonomy can also export a recorded case as Maestro YAML, which makes side-by-side comparison easy.
Prompt
Paste this into a coding agent connected to the Autonomy MCP server from inside the repository:
Migrate the Maestro tests in this repository to Autonomy.
For each test: read it, then create one Autonomy Test Case with autonomy_test_case_create named after the test title.
Convert selectors into plain-language descriptions of the control. Keep every asserted value exactly as written.
Replace hard-coded credentials with agent-chosen fill values and configuration with environment values.
Map tapOn -> Tap/Click, inputText -> Type, assertVisible -> Assert, launchApp -> a Precondition, and runFlow -> inline the sub-flow. Drop waits, retries, and framework fixtures. List existing Test Cases first and skip any that already cover the journey.
Report a table of source test -> created Test Case ID when done.Mapping notes
launchAppwithclearStatebecomes a Precondition (clear app state).tapOn: { id: ... }/tapOn: "text"become Tap/Click on the described control.assertVisible/assertNotVisiblebecome Assert.runFlowsub-flows are inlined;repeatloops are unrolled or dropped if they only wait.envvariables become{{env.VAR}}Environment values.
See the migration overview for the full construct-by-construct mapping.