Test Mobile and Web UI with Maestro

Author, validate, execute, and diagnose E2E tests with Maestro across iOS Simulators (macOS host or Maestro Cloud), Android emulators or physical devices (Linux, macOS, Windows), and Web (Chromium, Beta). This skill owns declarative YAML flow authoring, single interactive actions through Maestro's MCP server, offline syntax checks, local and cloud/SSH execution, artifact retrieval, failure diagnosis, and growing a reusable suite over time. It does not own building the app binary, Maestro Cloud billing, or backend test fixtures.

Facts here were verified against the Maestro 2.11.0 source (latest release, 2026-09-29) and docs.maestro.dev. If maestro --version differs, re-check the version-sensitive rules.

When to use this skill

• Writing Maestro YAML flows for iOS Simulators, Android emulators/devices, or Web
• Driving a live device one clean action at a time through the Maestro MCP server (maestro mcp) from Claude Code, Cursor, Codex, or Gemini CLI
• Choosing where tests can run: Linux (Android and Web locally; iOS only via Maestro Cloud or a Mac) versus macOS (everything)
• Building reusable subflows, hooks, tags, and suites, and promoting exploratory steps into permanent tests
• Debugging failing selectors with maestro hierarchy or MCP inspect_screen
• Validating flow syntax offline with maestro check-syntax (or automatically inside MCP run)
• Collecting and reading JUnit reports, logs, and failure screenshots

Do NOT use this skill when