← ClaudeAtlas

e2e-browser-testlisted

Use when a ticket asks for end-to-end or browser coverage of a user journey — sign-up, checkout, a form submission, a dashboard flow — driven through the real UI with Playwright, Cypress, or the repo's browser harness. Invoke for "add an e2e test", "cover the flow in the browser", or when an acceptance criterion can only be shown by clicking through the app.
tmj-90/gaffer · ★ 1 · Testing & QA · score 70
Install: claude install-skill tmj-90/gaffer
# Write an end-to-end browser test An end-to-end test proves a user journey works through the real UI against a real (or faithfully stubbed) backend. It is the slowest and most flake-prone test in the suite — Google's data shows flakiness grows with test size and with WebDriver-style tooling — so it earns its place by covering a journey no cheaper test can, and by being deterministic: no sleeps, no order dependence, no data another test created. ## Procedure 1. **Find the harness.** Locate the repo's browser setup (`playwright.config.*`, `cypress/`, a `test:e2e` script). Use it exactly — its browsers, base URL, `webServer` block and CI command. Do not add a second framework. If none exists and the ticket does not ask for one, raise `request_decision` with the smallest viable setup. (Independent tester: never raise `request_decision`; follow `black-box-test` — scaffold a disposable rig in a test directory only with what the repo already has installed, run the spec once, and record `manual_note` rows.) 2. **Push coverage down first.** For each acceptance criterion ask whether a component or integration test proves it (the `frontend-testing` and `add-integration-test` skills). Only journeys that need the real browser, routing, cookies or the full stack belong here. 3. **Write the journey in plain words:** start state → user actions → what the user must observe. Map each AC to one observable outcome on screen or one persisted result. Name the t