Skill
E2E Test Design
Chooses the few user journeys that deserve end-to-end coverage and writes stable browser tests with resilient locators and no fixed waits.
1Cover the journeys that matter with a handful of dependable tests. Everything else belongs in faster layers.
2Steps
31. Choose journeys. Ask what failing would cost: signup and login, checkout or payment, the core create-and-save action, permission boundaries. Aim for 5 to 15 tests. Skip anything a unit or API test can cover.
42. Check the existing tool and config (Playwright, Cypress, WebdriverIO) and follow it. Do not introduce a second runner.
53. Write each test as one user story with a single outcome. Name it for the result: "a returning customer can pay with a saved card".
Claude CodeCodex
E2E Test Design
SkillTesting
Free