What problem does it solve? End-to-end test suites often become slow, flaky, and untrusted, causing teams to ignore failures or abandon the suite entirely. This Skill provides a disciplined workflow for building an E2E suite that stays green for the right reasons: stable selectors, owned test data, deliberate CI gating, and an enforced flake policy. ## Core Features & Use Cases - Tool routing with deep references: Routes web apps to Playwright (TypeScript) and Expo/React Native apps to Maestro (YAML flows), with Detox as an alternative, backed by detailed reference guides for each framework. - Suite architecture and data lifecycle: Enforces page-object patterns, user-visible selectors, per-test data ownership via API seeding, and explicit environment strategy (ephemeral, staging, or prod-dogfood). - CI gating and flake policy: Defines smoke vs full suite gates, parallel sharding, failure artifacts, and a quarantine policy with TTLs and a 2-3% flake-rate budget. - Use Case: A team shipping a checkout feature uses this Skill to automate the critical journeys from their test plan as Playwright tests, wire a smoke subset into the merge gate, and quarantine a flaky test with a named owner and fix deadline. ## Quick Start Use the e2e-automation skill to automate the critical user journeys from my test plan as a Playwright suite with CI smoke gating.
