Can I use this to create new tests?

No, this skill is specifically optimized for debugging existing failures. For creating new tests, use a dedicated test generator skill.

Does it support Playwright Traces?

Yes, it can analyze Playwright trace files, screenshots, and execution logs to understand the exact state of the browser at the moment of failure.

Can it debug tests that only fail in CI?

Yes, it specializes in resolving environmental differences between local and CI setups, such as viewport variations, network speeds, and resource constraints.

How does this skill help with flaky tests?

It identifies race conditions, suggests robust wait states, and analyzes network activity to ensure tests are stable across different execution environments.

Playwright Test Debugger

Name: Playwright Test Debugger
Author: joel611

byjoel611

Security & Testing

Debugs and resolves failing Playwright end-to-end tests by analyzing error logs, trace files, and screenshots.

About

The Playwright Test Debugger skill is a specialized utility designed to identify and fix failures in Playwright E2E test suites. It systematically analyzes error messages, stack traces, and visual artifacts like screenshots or Playwright traces to pinpoint root causes such as timing issues, brittle selectors, or complex race conditions. By providing actionable code fixes and prevention strategies, it helps developers stabilize flaky tests and ensure consistent test passes in both local and CI environments, optionally utilizing Playwright MCP for live state inspection.

Key Features

Automated analysis of Playwright error logs and stack traces
0 GitHub stars
Actionable code snippets for immediate test fixes and prevention
Troubleshooting for common failure types including timeouts and selector issues
Identification and resolution of intermittent race conditions and flakiness
Support for live browser state inspection via Playwright MCP

Use Cases

Fixing failing E2E tests in a CI/CD pipeline
Debugging flaky tests that pass locally but fail intermittently
Resolving complex element selector and navigation issues

About

Key Features

Automated analysis of Playwright error logs and stack traces
0 GitHub stars
Actionable code snippets for immediate test fixes and prevention
Troubleshooting for common failure types including timeouts and selector issues
Identification and resolution of intermittent race conditions and flakiness
Support for live browser state inspection via Playwright MCP

Use Cases

Fixing failing E2E tests in a CI/CD pipeline
Debugging flaky tests that pass locally but fail intermittently
Resolving complex element selector and navigation issues