e2e-testing-mobilelisted

Plans, generates, runs, and heals end-to-end tests for Expo and React Native mobile apps using Maestro (the 2026 standard for RN E2E, adopted by Meta, Microsoft, and DoorDash, and integrated with Expo via EAS Workflows). Drives a spec-first YAML-flow loop, proposes `testID` source diffs (never `accessibilityLabel` reuse), runs Maestro Cloud as an EAS job, and stays token-aware via `--shards`, `--retries`, and failure-only healing. Use for native flows in Expo / RN apps. Triggers on "test this RN flow", "add mobile e2e", "maestro flow", "expo e2e", "e2e for react native", "test the native app", "/e2e-testing-mobile". Defer to [`e2e-testing`](../e2e-testing/SKILL.md) for web flows and the WebView portion of hybrid apps.
mthines/agent-skills · ★ 5 · Testing & QA · score 83

Install: claude install-skill mthines/agent-skills

# E2E Testing — Mobile (Expo / React Native) Drive native mobile end-to-end tests through Maestro and Maestro MCP. The user writes (or approves) a Markdown feature spec; an agent emits a Maestro YAML flow, runs it against a simulator or Maestro Cloud, and self-heals when locators drift. This is the **mobile** counterpart to [`e2e-testing`](../e2e-testing/SKILL.md). Anything orthogonal to native (web flows, WebViews inside a hybrid app) defers to that skill. The two skills compose; they do not overlap. > **This `SKILL.md` is a thin index.** > Decision rules live in [`rules/*.md`](./rules) and load on demand. > Worked references (Maestro CLI surface, MCP tool catalog, EAS Workflow > wiring, Detox legacy notes, mobile pyramid math) live in > [`references/*.md`](./references). > Literal boilerplate the skill emits lives in > [`templates/*.md`](./templates). > Do not preload everything — load only what the current phase asks for. --- ## When to use Reach for this skill when any of the following is true: - An Expo or React Native app needs E2E coverage of a native user flow. - A bug only repros across native navigation, deep links, push, permissions prompts, or a real device sensor. - A flake needs a Maestro heal pass instead of a manual locator hunt. - The repo has no `.maestro/` flows or EAS E2E build profile yet and needs Phase 0 setup. Do **not** reach for this skill when: - A unit or component test would catch the same bug — defer to [`tdd`](../tdd/SKILL.md) and