e2e-browser-testlisted
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