E2E Playwright Diagnosis
Diagnoses and resolves End-to-End (E2E) test failures in Playwright using a systematic, tool-driven workflow.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Orchestrates browser automation (Playwright) and developer tools (Chrome DevTools) for in-browser test reproduction.
- Systematic analysis of test failures, from initial error message to specific test identification.
- Includes a detailed troubleshooting checklist for common Playwright issues like timeouts and selector failures.
- Delegates code corrections to specialized agents, focusing solely on diagnosis and validation.
- Manages environment preparation, including build cache clearing and project rebuilds.
Use cases
- Performing root cause analysis for specific Playwright test errors.
- Debugging test failures by reproducing them in a live browser session for visual inspection.
- Investigating and resolving failures in an E2E test suite.
FAQ
What does the E2E Playwright Diagnosis skill do?
This skill automates the diagnosis of failing End-to-End (E2E) tests in Playwright. It follows a systematic workflow to identify the root cause of a failure, from analyzing the error message to reproducing the issue in a live browser environment.
Does this skill write code to fix the tests?
No, this skill's primary role is diagnosis. It identifies the root cause and collects all necessary context, then delegates the actual code or test modification to a specialized agent like a frontend developer to ensure the fix is handled correctly.
What key capabilities does it provide?
It provides a complete diagnostic toolkit, including automated environment preparation (clearing build cache), in-browser test reproduction, deep log analysis, and a comprehensive troubleshooting checklist for common issues like timeouts and selector failures.
When should I use this skill?
Use this skill whenever you encounter E2E test failures in your CI/CD pipeline or local development. It's ideal for analyzing cryptic error messages, debugging tests that fail intermittently, and understanding why a test is not behaving as expected.
How does this skill improve my workflow?
It saves significant debugging time by automating browser reproduction with Playwright and Chrome DevTools. By focusing solely on diagnosis and delegating code fixes to specialized agents, it ensures a clear, structured, and efficient resolution process.
Related skills
UI Testing
Guides the development of robust UI tests using Cypress and Testing Library, covering component tests, end-to-end flows, and accessibility.
Security Testing1012 ptsEnd-to-End Playwright Testing
Creates robust end-to-end Playwright tests that simulate real user behavior through a structured, three-phase workflow.
Security Testing19212 ptsWeb Application Testing
Builds and debugs web application features through a structured, iterative testing process using Playwright.
Security Testing6912 pts