← ClaudeAtlas

e2e-heallisted

Find, debug, and fix failing Playwright E2E tests
event4u-app/agent-config · ★ 7 · AI & Automation · score 83
Install: claude install-skill event4u-app/agent-config
# e2e-heal > **Mobile scope:** this command targets Playwright (browser/web) tests only. For Detox / Maestro / Appium / XCUITest / Espresso failures, use the `mobile-e2e-strategy` skill plus the framework's own diagnostic tooling — the Playwright-specific steps below do not apply to native mobile. ## Instructions ### 1. Identify failing tests - Ask the user: > 1. Run all E2E tests and fix whatever fails > 2. Fix a specific test file — which one? > 3. Fix tests that failed in CI — provide the CI run URL or error output - Read the Playwright guideline: `../../docs/guidelines/e2e/playwright.md` ### 2. Run failing tests - Execute the test(s) to see current errors: ```bash npx playwright test [file] --reporter=list 2>&1 | tail -30 ``` - If all tests pass → report success and stop. - List all failing tests with their error messages. ### 3. Debug each failure (one at a time) For each failing test: 1. **Read the error** — understand what's expected vs. actual. 2. **Classify the failure**: | Type | Symptom | Action | |---|---|---| | Selector changed | Element not found | Update locator (prefer semantic) | | Timing issue | Timeout | Add proper waits or `waitForResponse` | | Assertion mismatch | Expected ≠ Actual | Update expected value or test logic | | App bug | Test is correct, app is broken | Mark `test.fixme()` | | Data dependency | Missing test data | Fix seed/setup | | Environment issue | Works locally, fails in CI | Check config, viewport, baseURL | 3. **Fix t