Practical QA guide · 12 min
Maestro Mobile Testing Guide
Learn the fundamentals of Maestro mobile UI testing: YAML flows, visible-text and accessibility selectors, test IDs, assertions, reusable flows, and stable mobile QA automation.
Written and reviewed by ShiftQA Labs QA Education Team · Updated October 6, 2026
Browse Lessons modules
Think in short user flows
A Maestro flow is easiest to maintain when it proves one coherent outcome such as signing in, adding an item, or saving a preference. Keep setup predictable and use reusable subflows for repeated navigation or authentication where appropriate.
Readable YAML is an advantage, but the same test-design principles still apply: clear preconditions, stable data, and an expected result that matters to the user.
Choose selectors the app can support
Visible text works well when labels are stable and unique. Accessibility identifiers or test IDs are stronger when text changes, is localized, or multiple controls share a label. Coordinate taps should be a last resort because layout and device differences make them brittle.
Automation friction can expose product accessibility gaps. If a control has no useful semantic identity, adding one can improve both testability and accessibility.
Design for devices and timing
Mobile flows contend with keyboards, permissions, animations, network latency, system dialogs, and different screen sizes. Assertions should wait for meaningful state rather than depending on fixed pauses.
Run important flows across representative devices and OS versions according to product risk. Parallel execution can shorten feedback, but shared accounts and backend data must be isolated to avoid tests interfering with one another.
Worked example
A basic login flow
A native app exposes email and password fields with stable labels or accessibility IDs.
- 1Launch or reset the app into a known signed-out state.
- 2Tap the email field and enter a dedicated test account.
- 3Enter the password and tap the Login control by visible text or stable identifier.
- 4Assert that a unique signed-in element such as the account heading or home navigation is visible.
- 5Add a separate negative flow for invalid credentials rather than mixing both outcomes into one test.
Frequently asked questions
Questions testers ask
Does Maestro require accessibility IDs?
No. It can locate elements in several ways, including visible text, but stable accessibility identifiers or test IDs can make automation more reliable when text is ambiguous or dynamic.
Can Maestro run tests on multiple devices?
Maestro can be used in workflows that execute across multiple simulators, emulators, or cloud devices. Test data and accounts should be isolated so parallel flows do not interfere with each other.
Is Maestro a replacement for unit testing?
No. Maestro is primarily useful for user-facing mobile flows. Unit and integration tests remain important for fast feedback on lower-level logic and service behavior.