playwright-trace

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

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/CatalinPoata/SistemPortalDMS --skill playwright-trace-catalinpoata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-trace
Source: https://github.com/CatalinPoata/SistemPortalDMS/tree/main/API-DMS-TESTS/bin/Debug/net9.0/.playwright/package/lib/tools/skills/playwright-trace
Command: npx skills add https://github.com/CatalinPoata/SistemPortalDMS --skill playwright-trace-catalinpoata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve? Debugging failed Playwright tests usually requires opening a browser-based trace viewer, which slows down headless and CI workflows. This Skill lets you inspect .zip trace files entirely from the command line to find failing actions, network errors, and console output. ## 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 filters for failed requests or error-only output. - DOM Snapshots: Load before/after DOM snapshots for any action, run eval queries against them, and capture screenshots without a live browser. - Use Case: A CI pipeline reports a failed end-to-end test. Open the uploaded trace.zip, list failed actions, inspect the failing action's snapshot, and check for failed API requests to identify the root cause in minutes. ## Quick Start Open the trace.zip file from my failed Playwright test and show me which action failed and what the page looked like at that moment.

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. Follow with trace actions, trace requests, or trace errors to inspect the contents without launching the trace viewer UI.

How to find which action failed in a Playwright 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 the DOM at the moment a Playwright test failed?▼

Yes, use npx playwright trace snapshot <action-id> to load the DOM snapshot for that action. You can get an accessibility snapshot, run eval queries against elements, or capture a screenshot of the frozen page state.

How do I check network requests in a Playwright trace?▼

Run npx playwright trace requests to list all network requests with method, status, URL, and duration. Filter with --grep for URL patterns, --method for HTTP verbs, or --failed to show only requests with status 400 or higher.

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 snapshot because there is no live page.