playwright-trace

Analyze Playwright trace files to diagnose web automation script issues.

Updated May 24, 2025
One-click install
npx skills add https://github.com/layxew/revolution --skill playwright-trace-layxew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-trace
Source: https://github.com/layxew/revolution/tree/main/api.varietyproxys.com/yeniceri.varietyshop.com.tr/bin/Debug/net10.0/.playwright/package/lib/tools/trace
Command: npx skills add https://github.com/layxew/revolution --skill playwright-trace-layxew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a command-line interface to inspect Playwright trace files, simplifying the process of debugging web automation scripts.

Core Features & Use Cases

  • Trace File Analysis: List actions, view requests, console logs, errors, and screenshots from trace files.
  • Action Details: Dive into specific actions to see parameters, logs, source location, and available snapshots.
  • Request and Console Inspection: Filter and view network requests and console messages for debugging purposes.
  • Snapshots and Screenshots: Take screenshots or DOM snapshots of actions for visual debugging.
  • Use Case: When you encounter unexpected behavior in your Playwright automation scripts, use this Skill to inspect the trace files and identify the root cause.

Quick Start

Use the playwright-trace skill to open a trace file with the command 'playwright trace open my-trace.zip'.

Frequently Asked Questions about playwright-trace

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

FAQPage Schema
How do I debug Playwright automation scripts using trace files?

To debug Playwright automation scripts, you can analyze trace files to view detailed action logs, network requests, and console messages, which simplifies identifying the root cause of unexpected behavior during web automation testing.

How do I view network requests and console logs in a Playwright trace file?

You can view network requests and console logs within a Playwright trace file by using trace analysis tools to filter and inspect specific actions, enabling you to pinpoint errors and debug script issues effectively.

Can I take screenshots or DOM snapshots from a Playwright trace file?

Yes, you can take screenshots and capture DOM snapshots directly from Playwright trace files, providing visual debugging capabilities to inspect the state of web elements during specific automation actions.

What is the best way to inspect Playwright trace files for web automation errors?

The best way to inspect Playwright trace files is using a command-line interface to dive into specific actions, allowing you to examine parameters, source locations, and available snapshots to diagnose script issues.

Do I need Playwright installed to analyze trace files?

Yes, you need Playwright and its associated trace analysis tools installed in your environment to properly open, inspect, and analyze trace files for diagnosing web automation script issues.

Why are my Playwright web automation scripts failing unexpectedly?

Your Playwright web automation scripts may be failing due to unexpected behavior that can be diagnosed by inspecting trace files, which offer detailed action logs, request data, and error snapshots to identify the root cause.