playwright-debugging

Diagnose flaky Playwright tests with structured debugging steps.

5|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill playwright-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-debugging
Source: https://github.com/ed3dai/ed3d-plugins-testing/tree/main/plugins/ed3d-playwright/skills/playwright-debugging
Command: npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill playwright-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to diagnosing and fixing flaky Playwright browser automation tests, reducing debugging time and increasing test reliability.

Core Features & Use Cases

  • Systematic debugging workflow for locator failures, timeouts, and intermittent browser behavior.
  • Guided troubleshooting steps including visibility checks, waits management, and trace analysis.
  • Use Case: When a test intermittently fails in CI, apply this skill to reproduce, isolate, and stabilize the failing scenario.

Quick Start

Run the Playwright debugging workflow on a failing test using the UI and inspector-driven steps to identify root causes. Example: start with evaluating element visibility, then enable tracing and step through the test to capture a failure trace.

Frequently Asked Questions about playwright-debugging

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

FAQPage Schema
How do I debug flaky Playwright tests that intermittently fail in CI?

To debug flaky Playwright tests, apply a structured workflow to reproduce, isolate, and stabilize the failing scenario. Evaluate element visibility, enable tracing, and step through the test using the UI inspector to capture and analyze the failure trace.

What is the best way to troubleshoot Playwright locator failures and timeouts?

The best way to troubleshoot Playwright locator failures and timeouts is using guided diagnostic checks. Manage wait strategies effectively and verify element visibility through the Playwright inspector to identify the root cause of the failing selectors.

How does Playwright trace analysis work for unstable browser automation tests?

Playwright trace analysis works by capturing a detailed execution log of your browser automation tests. You enable tracing, step through the test to record the failure trace, and inspect the logs to understand intermittent browser behaviors and unstable test actions.

Can I use the Playwright inspector to fix failing selectors in local and CI environments?

Yes, you can use the Playwright inspector to fix failing selectors across local and CI environments. The inspector provides UI-driven debugging options to step through test execution, helping you evaluate visibility and isolate selector failures systematically.

Why does my Playwright test fail intermittently and how do wait strategies help?

Your Playwright test fails intermittently due to unstable timing and browser behaviors. Wait strategies help by ensuring elements are fully loaded and visible before interaction, reducing flakiness and stabilizing the test execution flow.