fix

Diagnose and repair flaky Playwright test suites through systematic reproduction and categorization.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill fix-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/pw/2.1.2/skills/fix
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill fix-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves the frustration of unreliable Playwright tests by providing a structured diagnostic framework to identify and eliminate the root causes of intermittent failures.

Core Features & Use Cases

  • Systematic Taxonomy: Categorizes failures into Timing/Async, Test Isolation, Environment, or Infrastructure issues.
  • Diagnostic Workflow: Guides you through reproduction, trace analysis, and verification steps to ensure stability.
  • Use Case: When a test suite passes locally but fails intermittently in CI, use this Skill to isolate the environment-specific race conditions or state leaks causing the instability.

Quick Start

Use the fix skill to diagnose the failing test named should redirect after login in the file e2e/login.spec.ts.

Frequently Asked Questions about fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky Playwright tests failing intermittently in CI?

Fix flaky Playwright tests by systematically reproducing the intermittent failures and categorizing them into Timing/Async, Test Isolation, Environment, or Infrastructure issues to isolate root causes.

What causes intermittent Playwright test failures when tests pass locally?

Intermittent Playwright test failures in CI are typically caused by environment-specific race conditions, timing issues, or state leaks. Categorizing these failures helps identify whether they stem from async timing, test isolation, environment differences, or infrastructure problems.

How to diagnose a failing Playwright test suite using trace analysis?

Diagnose a failing Playwright test suite by running trace analysis to capture execution details, reproducing the failure, and verifying the stability fix. This structured diagnostic framework guides you through reproduction, trace analysis, and verification steps.

Do I need the Playwright test runner to execute burn-in tests for flaky tests?

Yes, you need Playwright test runner capabilities to execute traces, run burn-in tests, and verify stability fixes. The Skill applies to end-to-end testing workflows where intermittent failures occur due to timing, isolation, environment, or infrastructure issues.

What is the best way to isolate race conditions in end-to-end testing workflows?

The best way to isolate race conditions in end-to-end testing is using a systematic taxonomy to categorize failures, followed by reproduction and trace analysis. This isolates environment-specific race conditions or state leaks causing intermittent instability.