fix

Topics in the source

• Fix Failing or Flaky Tests
• Input
• Steps
• 1. Reproduce the Failure
• 2. Capture Trace
• 3. Categorize the Failure
• 4. Apply Targeted Fix
• 5. Verify the Fix

Diagnose and fix a Playwright test that fails or passes intermittently using a systematic taxonomy. $ARGUMENTS contains: A test file path: e2e/login.spec.ts A test name: ""should redirect after login" A description: "the checkout test fails in CI but passes locally" Run the test to capture the error: If the test passes, it's likely flaky. Run burn-in: If it still passes, try with parallel workers: Run with full tracing: Read the trace output. Use /debug to analyze trace files if available. Load flaky-taxonomy.md from this skill directory. Every failing test falls into one of four categories: | Category | Symptom | Diagnosis | |---|---|---| | Timing/Async | Fails intermittently everywhere | --repeat-each=20 reproduces locally | | Test Isolation | Fails in suite, passes alone | --workers=1 --grep "test name" passes | | Environment | Fails in CI, passes locally | Compare CI vs local screenshots/traces | | Infrastructure | Random, no pattern | Error references browser internals | Timing/Async: Replace waitForTimeout() with web-first assertions Add await to missing Playwright calls Wait for specific network responses before asserting Use toBeVisible() before interacting with elements Te

This is an excerpt. Refer to the complete source and its current requirements.