Diagnose and fix failing or flaky Playwright tests using a four-category taxonomy.
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill fix-rohithdgrr
Please help me install this Agent Skill. Skill: fix Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/fix Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill fix-rohithdgrr
High-intent search queries and answers about installing and using this skill.
First reproduce it with npx playwright test --repeat-each=10, then capture a trace with --trace=on. Categorize the failure as timing, isolation, environment, or infrastructure, apply the matching fix, and verify with 10 consecutive passing runs.
This indicates an environment category failure. Compare CI versus local screenshots and traces, match viewport sizes, account for font rendering differences, and run tests in Docker locally to replicate the CI environment.
This is a test isolation problem caused by shared mutable state or leaked database data between tests. Fix it by creating per-test data via fixtures, using unique identifiers, and removing shared state.
Replace waitForTimeout with web-first assertions like toBeVisible() before interacting with elements, and wait for specific network responses before asserting. This eliminates timing-dependent flakiness.
The fixed test must pass 10 consecutive runs using npx playwright test --repeat-each=10. If any run fails, return to the categorization step and re-diagnose the root cause.
teocraftersAutomate reusable Playwright fixtures with test.extend() for end-to-end testing.
MoxyWolfLLCGuide Playwright end-to-end tests with user-facing selectors and web-first assertions.
CatalinPoataInspect Playwright trace files from the command line to debug test failures.
JaiminVadadoriyaMigrate test suites between frameworks with incremental adoption and parallel running.
