E2e Testing Automation

This helps Claude write E2E tests that actually simulate user behavior across your full stack. You get working examples for Playwright, Cypress, and Selenium with proper patterns like Page Object Model, stable selectors using data-testid attributes, and explicit waits instead of sleeps. Use it when you need to test critical flows like checkout or signup, validate multi-step workflows, or catch regressions from UI changes. The practical advice on what not to do is honestly more valuable than most E2E guides: skip brittle selectors, don't share state between tests, and stop trying to E2E test every edge case when unit tests would work fine.