skills.rest
mthines
mthinesCOMMUNITY
Explore all skills by this author →
GitHub

playwright-trace-analyzer

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

7|2|Updated Apr 23, 2026
Search Tags:#automation#performance#debugging#trace#playwright#test-flakiness
One-click install
npx skills add https://github.com/mthines/agent-skills --skill playwright-trace-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-trace-analyzer
Source: https://github.com/mthines/agent-skills/tree/main/skills/playwright-trace-analyzer
Command: npx skills add https://github.com/mthines/agent-skills --skill playwright-trace-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers diagnose and analyze Playwright E2E trace files to uncover performance issues and flaky test causes.

Core Features & Use Cases

  • Trace Analysis: Processes Playwright trace.zip archives to detect slow actions, network bottlenecks, and console errors.
  • Root Cause Diagnosis: Maps hotspots to code locations, providing insights into flaky behaviors or failures.
  • Use Case: When a test times out or fails intermittently, this Skill allows quick identification of underlying race conditions, network delays, or app errors.

Quick Start

Use the playwright trace analyzer to process an unpacked trace directory or a trace.zip file to generate a detailed analysis report.

Frequently Asked Questions about playwright-trace-analyzer

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

FAQPage Schema
How do I find the root cause of flaky Playwright tests?▼

Playwright trace analysis identifies flaky test root causes by processing trace.zip archives or raw JSONL streams. It detects slow actions, network bottlenecks, and console errors, mapping hotspots to code locations for test stabilization.

What is the best way to debug Playwright trace files in a CI/CD pipeline?▼

Debugging Playwright trace files in a CI/CD pipeline involves analyzing trace.zip archives or unpacked trace directories to generate detailed reports. This facilitates rapid issue resolution for intermittent failures and race conditions.

Does Playwright trace analysis work with raw JSONL streams or only trace.zip archives?▼

Playwright trace analysis works with trace.zip archives, directories of unpacked trace data, and raw JSONL streams. This flexibility allows you to process various trace formats to uncover performance issues and flaky behaviors.

How do I identify performance bottlenecks from Playwright E2E traces?▼

You identify performance bottlenecks from Playwright E2E traces by processing trace data to detect slow actions and network delays. The analysis maps these hotspots to specific code locations, providing actionable insights for test stabilization.

Why do my Playwright E2E tests time out intermittently?▼

Playwright E2E tests time out intermittently due to underlying race conditions, network delays, or application errors. Analyzing trace files helps quickly identify these specific issues causing flaky behaviors or failures.

When do I need to analyze a trace.zip file for test flakiness?▼

You need to analyze a trace.zip file for test flakiness when a test fails intermittently or times out. This analysis uncovers network bottlenecks and console errors to diagnose the underlying causes efficiently.

Related Skills

Explore More Software Engineering Skills→
hotyanovichahotyanovicha

test

Run Playwright tests with file, browser, and debug options.

Community
Basic
skyasu2skyasu2
2

playwright-triage

Analyze Playwright test-results to classify E2E failures and generate Markdown diagnosis reports.

Community
Advanced
act70255act70255

gitlab-ci-patterns

Automate GitLab CI/CD pipeline configuration with multi-stage workflows and caching.

Community
Advanced
rysweetrysweet
1

session-replay

Analyze claude-trace JSONL files for session health, token usage, and error patterns.

Community
Intermediate