playwright-trace

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

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/bsamiee/Rasm --skill playwright-trace-bsamiee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-trace
Source: https://github.com/bsamiee/Rasm/tree/main/.claude/plugins/playwright/skills/playwright-trace
Command: npx skills add https://github.com/bsamiee/Rasm --skill playwright-trace-bsamiee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve? Debugging failed Playwright tests normally requires opening the Trace Viewer in a browser, which is slow and impractical in headless CI environments or terminal-based workflows. This Skill lets you inspect .zip trace files entirely from the command line. ## Core Features & Use Cases - Action Inspection: List all test actions as a tree with IDs and timing, filter by title or errors, and drill into any action's parameters, logs, and source location. - Cross-Cutting Views: Review network requests, console messages, and errors across the whole trace with filters for failed requests, error messages, and URL patterns. - Snapshot Analysis: Load DOM snapshots for any action into a headless browser to run eval queries, capture screenshots, or extract the accessibility tree. - Use Case: A CI run reports a failed test with a trace.zip artifact. Open the trace, list failed actions, inspect the failing action's snapshot, and check failed network requests — all without leaving the terminal. ## Quick Start Ask the AI to open the Playwright trace file from your failed test results and show the failing actions along with their console errors.

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 the Playwright trace CLI commands to open the trace.zip file and inspect it from the terminal. Run trace open to extract metadata, then trace actions, trace requests, or trace console to explore the recorded test execution.

How to find failed actions in a Playwright trace?▼

Run trace actions with the --errors-only flag to list only failed actions. You can then use trace action with the action ID to see parameters, logs, source location, and available snapshots for that failure.

Can I inspect network requests from a Playwright trace?▼

Yes, the trace requests command lists every network request 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 above.

Does the Playwright trace CLI support DOM snapshots?▼

Yes, trace snapshot loads an action's DOM snapshot into a headless browser and returns the accessibility tree by default. You can also run eval commands against elements or capture screenshots of the frozen snapshot.

What are the limitations of running commands on a trace snapshot?▼

Only three browser commands work on a frozen snapshot: snapshot, eval, and screenshot. Interactive commands like click or navigation are not useful because the snapshot is a static recording of the page state.