skills.rest
guillempuche
guillempucheCOMMUNITY
Explore all skills by this author →
GitHub

playwright-trace

Analyze Playwright trace files to inspect actions, requests, and UI events.

6|1|Updated Apr 1, 2026
Search Tags:#testing#debugging#logs#cli#trace#playwright#snapshot
One-click install
npx skills add https://github.com/guillempuche/batuda --skill playwright-trace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-trace
Source: https://github.com/guillempuche/batuda/tree/main/docs/repos/playwright/packages/playwright-core/src/tools/trace
Command: npx skills add https://github.com/guillempuche/batuda --skill playwright-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect Playwright trace files to understand actions, requests, and UI events.

Core Features & Use Cases

  • View an action tree and timings to diagnose flaky tests and performance issues.
  • Inspect network requests, console output, errors, and DOM snapshots for precise debugging.
  • Navigate per-action details and artifacts (attachments and screenshots) and export results.

Quick Start

Open a trace with the CLI and begin inspecting actions, requests, console messages, errors, and snapshots to diagnose issues quickly.

Frequently Asked Questions about playwright-trace

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

FAQPage Schema
How do I inspect Playwright trace files from the CLI?▼

You can inspect Playwright trace files from the CLI by opening local files or archives to view action trees, network requests, console output, and DOM snapshots. This allows developers and QA engineers to diagnose flaky tests and verify end-to-end interactions quickly.

What is a Playwright trace used for when debugging end-to-end tests?▼

A Playwright trace is used to understand UI events, actions, and network requests during end-to-end tests. It helps diagnose flaky tests, verify interactions, and optimize trace-based debugging workflows across local and CI environments by presenting action trees and per-action details.

Can I view network requests and console errors in a Playwright trace without a browser?▼

Yes, you can view network requests, console output, and errors directly from the trace file without a browser. The Skill reads local files or archives and presents these details alongside DOM snapshots and attachments for precise debugging.

Does CLI trace debugging work for CI environment test failures?▼

Yes, CLI trace debugging works for CI environments by reading trace archives generated during CI runs. You can analyze action timings, network requests, and screenshots to diagnose flaky tests and performance issues locally after downloading the artifacts.

How do I export results from a Playwright trace analysis?▼

You can export results from Playwright trace analysis after inspecting per-action details and artifacts. The Skill supports exporting results to share findings from action trees, network logs, and DOM snapshots with your development team.

Related Skills

Explore More Software Engineering Skills→
mthinesmthines
7

playwright-trace-analyzer

Analyze Playwright E2E trace files to diagnose performance bottlenecks and flaky test causes.

Community
Intermediate
layxewlayxew

playwright-trace

Analyze Playwright trace files to diagnose web automation script issues.

Community
Intermediate
xxziikoxxziiko

playwright-e2e

Automate Playwright end-to-end test execution and debugging across projects.

Community
Intermediate
Zoppy-crmZoppy-crm

playwright-cli

Automate browser interactions and end-to-end testing via Playwright CLI.

Official
Intermediate