Can this skill fix timeout errors?

Yes, it analyzes whether timeouts are caused by slow loading, incorrect selectors, or environment differences and provides optimized waiting strategies to resolve them.

Do I need Playwright MCP to use this skill?

No, the skill works effectively with provided error logs and trace files, but Playwright MCP enhances debugging by allowing Claude to inspect and interact with the live browser state directly.

How does this skill help with flaky tests?

It identifies common causes of flakiness like race conditions or missing network idle states and suggests robust patterns like waitForLoadState or specific API response listeners to ensure tests are stable.

Does it support debugging failures in CI environments?

Yes, it is designed to analyze CI logs and artifacts to identify why tests might pass locally but fail in automated pipelines, such as viewport differences or network latency.

Is this skill used for creating new tests?

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

Playwright Test Debugger

Name: Playwright Test Debugger
Author: joel611

byjoel611

•

セキュリティとテスト

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.

主な機能

Live browser state inspection using Playwright MCP tools
Automated analysis of Playwright error logs and stack traces
Visual debugging via screenshots and trace file interpretation
1 GitHub stars
Step-by-step guidance for implementing and verifying test fixes
Diagnostic workflows for timeouts, selector conflicts, and race conditions

ユースケース

Fixing intermittent 'flaky' tests that fail in CI but pass locally
Optimizing test performance by identifying unnecessary waits and timeouts
Resolving 'Element not found' or 'Target closed' errors in complex SPAs

概要

主な機能

Live browser state inspection using Playwright MCP tools
Automated analysis of Playwright error logs and stack traces
Visual debugging via screenshots and trace file interpretation
1 GitHub stars
Step-by-step guidance for implementing and verifying test fixes
Diagnostic workflows for timeouts, selector conflicts, and race conditions

ユースケース

Fixing intermittent 'flaky' tests that fail in CI but pass locally
Optimizing test performance by identifying unnecessary waits and timeouts
Resolving 'Element not found' or 'Target closed' errors in complex SPAs