skills.rest
kirillshilin
kirillshilinCOMMUNITY
Explore all skills by this author →
GitHub

debug-e2e-test

Diagnose and fix flaky Playwright E2E tests by classifying failures from traces.

Updated Aug 23, 2026
Search Tags:#debugging#tracing#playwright#e2e-testing#test-flakiness#locator-inspection#ci-differences
One-click install
npx skills add https://github.com/kirillshilin/instructions --skill debug-e2e-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-e2e-test
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/claude/skills/debug-e2e-test
Command: npx skills add https://github.com/kirillshilin/instructions --skill debug-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flaky or failing Playwright E2E tests disrupt CI and slow delivery; this Skill provides a repeatable, step-by-step approach to identify root causes such as timeouts, locator issues, and CI environment differences, and to guide fixes.

Core Features & Use Cases

  • Classify failure types from test output and traces.
  • Guide enabling tracing, reproducing in headed mode, and inspecting locators.
  • Standardize a reproducible diagnostic workflow across CI and local runs.

Quick Start

Run the diagnostic workflow on your failing Playwright test using this Skill to collect traces, reproduce in headed mode, and apply fixes.

Frequently Asked Questions about debug-e2e-test

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

FAQPage Schema
How do I debug flaky Playwright E2E tests failing in CI?▼

To fix flaky Playwright E2E tests, follow a diagnostic workflow: collect traces, reproduce failures in headed mode, and inspect locators. This identifies root causes like timeouts, locator issues, or CI environment differences to ensure stability.

What causes test flakiness and how does trace collection help diagnose it?▼

Test flakiness is caused by timeouts, locator issues, and CI environment differences. Trace collection helps diagnose it by providing detailed execution logs that classify failure types and identify network timing differences across runs.

Why does my Playwright test pass locally but fail in CI?▼

Playwright tests pass locally but fail in CI due to network timing differences and environment variations. Analyzing failures across both environments using traces helps identify these root causes and standardize a reproducible diagnostic workflow.

How do I inspect Playwright locators to fix E2E test failures?▼

To inspect Playwright locators and fix E2E test failures, reproduce the test in headed mode and analyze the collected traces. This guides locator inspection to pinpoint element resolution issues causing timeouts or test flakiness.

What is the best way to reproduce and verify fixes for flaky E2E tests?▼

The best way to reproduce and verify fixes for flaky E2E tests is following a standardized workflow: collect traces, reproduce in headed mode, apply fixes, and verify stability across multiple CI and local runs.

Related Skills

Explore More Software Engineering Skills→
tonone-aitonone-ai
69

vigil-incident

Diagnose production incidents by analyzing logs, metrics, and traces to identify root cause.

Official
Advanced
BurburtonBurburton

flaky-test-diagnosis

Diagnose flaky tests by analyzing failure patterns and root causes.

Community
Advanced
JaiminVadadoriyaJaiminVadadoriya
1

test-reliability

Diagnose and repair flaky Playwright tests with confidence-scored auto-repair.

Community
Advanced
ynotradioynotradio

e2e-debugging-workflow

Debug Playwright E2E test failures with local execution and debugging flags.

Official
Advanced