Diagnoses and fixes failing Playwright E2E tests by analyzing logs, traces, and live browser states.
This skill provides an expert-level diagnostic workflow for troubleshooting failing or flaky Playwright end-to-end tests. It guides Claude through a systematic analysis of error messages, stack traces, and visual artifacts like screenshots and traces to identify root causes such as race conditions, selector issues, and timeout errors. By optionally integrating with Playwright MCP, it allows for real-time inspection of browser states, enabling developers to quickly implement verified fixes for complex automation failures and improve suite reliability.
Key Features
01Live browser state inspection using Playwright MCP tools
02Automated analysis of Playwright error logs and stack traces
03Visual debugging via screenshots and trace file interpretation
041 GitHub stars
05Step-by-step guidance for implementing and verifying test fixes
06Diagnostic workflows for timeouts, selector conflicts, and race conditions
Use Cases
01Fixing intermittent 'flaky' tests that fail in CI but pass locally
02Optimizing test performance by identifying unnecessary waits and timeouts
03Resolving 'Element not found' or 'Target closed' errors in complex SPAs
