playwright-debugginglisted

# Playwright Debugging ## Flaky Test Diagnosis and Repair ## Overview Use this skill when a Playwright test fails intermittently, behaves differently in CI, or passes locally but not in a repeatable way. The goal is to identify the specific cause of the failure before changing the test. Use this skill as the first stop for failures. It is not a rewrite guide and it is not a replacement for `playwright-core` when the test still needs normal authoring discipline. This skill focuses on four common failure classes: timing and readiness issues, state bleed between tests, hydration or rendering gaps in SPA frameworks, and flakiness that only appears under CI's specific constraints. Do not use this skill to redesign a test from scratch unless the current test is beyond repair or the user explicitly asks for a rewrite. ## When to Use - When a test fails only in CI or only on some runs. - When a click, assertion, or navigation happens before the UI is ready. - When a test depends on data, cookies, or local storage left behind by another test. - When the app renders before it becomes interactive. ## When Not to Use - When you are writing a new test from scratch. - When the current test is already stable and the task is just to add new coverage. - When the app behavior itself needs redesign rather than a narrow test repair. ## Diagnostic Workflow Start with evidence. Use the failing error, the trace viewer, or the exact step that failed before choosing a fix. 1. Capture the