E2e

This is a structured debugging protocol for end-to-end test failures. It forces you to classify every failure into one of three buckets (flaky infrastructure, outdated test, or actual bug) before you touch any code, which prevents the common mistake of patching tests when the app is wrong or vice versa. The workflow is opinionated about boundaries: it won't let you change source code without a spec to back it up, and it requires unit tests before marking bug fixes complete. The taxonomy is sharp enough that you can actually apply it during a test run without overthinking. If you work on a codebase where e2e tests fail often and nobody's sure whether to trust them, this gives you a repeatable way to triage and fix without making things worse.

skills.sh installs: 126
GitHub stars: 48
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add 0xbigboss/claude-code --skill e2e --agent claude-code

Installs into .claude/skills of the current project.

Files

E2E Testing

Failure Taxonomy

Every e2e failure is exactly one of:

A. Flaky (test infrastructure issue)

Race conditions, timing-dependent assertions, stale selectors, missing waits
Symptom: passes on retry, fails intermittently

B. Outdated (test no longer matches implementation)

Test asserts old behavior that was intentionally changed; selectors reference removed elements
Symptom: consistent failure, app works correctly

C. Bug (implementation doesn't match spec)

Test correctly asserts spec'd behavior, code is wrong
Only classify as bug when a spec exists to validate against
If no spec exists, classify as "unverified failure" and report to the user

Fix Rules by Category

Flaky fixes:

Replace waitForTimeout with auto-waiting locators
Replace brittle CSS selectors with getByRole/getByLabel/getByTestId
Fix race conditions with expect() web-first assertions
Fix mock/route setup ordering (before navigation)
Never add arbitrary delays - fix the underlying wait
Never add retry loops around assertions - use the framework's built-in retry