playwright-trace

Inspect Playwright trace files from the command line to debug test failures.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill playwright-trace-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-trace
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/playwright-trace
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill playwright-trace-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging failed Playwright tests normally requires opening a browser-based trace viewer, which is slow and impractical in headless or CI environments. This Skill lets you inspect trace.zip files entirely from the command line. ## Core Features & Use Cases - Action Inspection: List all test actions as a tree, filter by title or errors, and drill into individual actions for parameters, logs, and source locations. - Cross-Cutting Views: Review network requests, console messages, and errors across the entire trace with filtering by URL, HTTP method, or failure status. - Snapshot Analysis: Load DOM snapshots for any action into a headless browser to run eval queries, capture screenshots, or extract accessibility trees. - Use Case: A CI pipeline reports a failed Playwright test. Open the uploaded trace.zip, list failed actions, inspect the failing action's snapshot, and query the DOM for the error message — all without leaving the terminal. ## Quick Start Open the Playwright trace file at test-results/my-test/trace.zip and show me which actions failed and why.

Frequently Asked Questions about playwright-trace

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

FAQPage Schema
How do I view a Playwright trace file without opening a browser?

Use npx playwright trace open <trace.zip> to extract the trace and view its metadata from the command line. Then run commands like trace actions, trace requests, or trace errors to inspect the recording without launching the trace viewer UI.

How to find which Playwright action failed in a trace?

Run npx playwright trace actions --errors-only to list only failed actions with their IDs. Then use npx playwright trace action <action-id> to see the action's parameters, logs, source location, and available snapshots.

Can I inspect network requests from a Playwright trace?

Yes, run npx playwright trace requests to see all requests with method, status, URL, duration, and size. Filter with --grep for URL patterns, --method for HTTP verbs, or --failed for requests with status 400 or higher.

How do I get the DOM state at a specific point in a Playwright trace?

Use npx playwright trace snapshot <action-id> to load the DOM snapshot into a headless browser and get an accessibility tree. You can also run eval queries against the DOM or capture a screenshot of the frozen snapshot.

What are the limitations of Playwright trace snapshots?

Snapshots are frozen DOM states, so only three browser commands work on them: snapshot, eval, and screenshot. Interactive commands like click or navigation cannot run against a recorded snapshot.