What problem does it solve? Writing browser tests that pass locally but flake in CI wastes engineering time. This Skill provides a structured playbook for building stable Playwright E2E suites — from selector strategy and fixtures to trace-based debugging and network mocking — so tests fail only when the app is actually broken. ## Core Features & Use Cases - Selector Strategy: Enforces a stability-first locator priority (getByRole, getByLabel, getByTestId) over brittle CSS/XPath selectors. - Fixtures & Auth Reuse: Patterns for extending base tests, sharing authenticated state via storageState, and per-test resets. - Trace Debugging & Mocking: Diagnose CI failures with trace.zip artifacts, and stub backend APIs with page.route to isolate the UI under test. - Use Case: A checkout flow breaks intermittently in CI. Use this Skill to replace waitForTimeout calls with auto-waiting assertions, mock the payment API, and capture a trace on retry to pinpoint the failing locator. ## Quick Start Ask the AI to write a Playwright test for your login flow using role-based selectors, an authenticated fixture, and trace-on-first-retry configuration.