playwright-testinglisted

# Playwright Testing Generate tests from evidence, not guesswork: inspect the product, name the claim, choose the smallest durable test structure, then harden until reruns are boring. **Playwright tests are checks** — automated pass/fail assertions. **Testing as investigation** — charters, heuristics, oracles under stress, edge-case discovery, perspective rotation — is upstream. Compose with `tester-mindset` when strategy, risk framing, or the shape of the unknown dominates. This skill tells you how to build durable checks; it does not replace the thinking that decides which checks to build. ## When To Use - writing, reviewing, or hardening Playwright E2E specs in a working harness for Node Playwright Test, Playwright Pytest, Playwright .NET, or Java Playwright test projects - debugging flaky specs, brittle locators, or tests that only pass on retry - exploring a running app with `playwright-cli`, UI Mode, or `codegen` - adding responsive, visual, or accessibility coverage against existing config - choosing between page objects, fixtures, parameterization, or route mocks ## Not For - first-time Playwright install, browser install, or runner config authoring in any ecosystem — route to `setup-playwright` - creating runner-level reusable-auth setup such as `auth.setup.ts`, setup-project wiring, or ecosystem equivalents — route to `setup-playwright` (using that wiring *in tests* belongs here) - test-strategy or edge-case discovery for a feature with no named clai