What problem does it solve? Manually verifying mobile app behavior on emulators is slow and error-prone, and in-process testing tools cannot exercise real OS-level flows like deep links and OAuth redirects. This Skill automates end-to-end UI testing of built iOS/Android apps through Maestro CLI, driving taps, swipes, input, assertions, and screenshots against what the user actually sees. ## Core Features & Use Cases - YAML Flow Automation: Write declarative test flows covering navigation, taps, gestures (swipe, long press), text input, assertions, waits, and screenshots, then run them with maestro test. - Deep Linking & OAuth Testing: Simulate OAuth callbacks and push-notification links via openLink, which routes through the real OS router — something in-process test frameworks cannot do. - Native OS Boundary Handling: Guidance for surfaces Maestro cannot touch (photo pickers, native alerts, biometrics), with a service_role data-injection pattern via GraalJS runScript scripts and [Manual] fallback steps. - Use Case: During a feature review, convert each verification checklist item into a .maestro/<feature>-<scenario>.yaml flow, run it against a dedicated E2E Supabase project, and report pass/fail per checkbox with screenshots. ## Quick Start Ask the assistant to write a Maestro flow that launches the app, logs in with the test account, asserts the welcome screen appears, and captures a screenshot.
