Keep what the test was meant to prove.
Use your existing flow as the starting specification. Review launch state, text entry, scrolling, and assertions separately, then validate the equivalent journey on a prepared device.
Use the same build and expected outcome.
Document prerequisites, test data, and the final assertion. Recreate the case in AuraCheck, review the generated automation, and run against a controlled environment. Compare the evidence and the effort required to understand a failure.
Before you switch
There is no claimed one-click Maestro YAML importer. Review each behavior explicitly.
Move ownership, not just execution.
Agree who reviews the case, maintains the environment, and triages failures. Keep the old release gate until the pilot has demonstrated repeatable outcomes. Expand one feature at a time, retaining existing unit and API coverage.
Prepare your first AuraCheck project