test-report
Open and analyze Playwright HTML test reports. Use when user asks to see test results, check test report, view test output, or analyze test failures.
When & Why to Use This Skill
This Claude skill streamlines the software testing lifecycle by providing automated access and intelligent analysis of Playwright HTML test reports. It enables developers and QA engineers to instantly visualize test results, diagnose failures through screenshots and traces, and generate comprehensive summaries of test suite performance, significantly reducing the time spent on manual debugging and quality assessment.
Use Cases
- Post-test execution analysis: Automatically open and interpret Playwright HTML reports immediately after running a test suite to identify regressions.
- Root cause diagnosis: Analyze failed test cases by extracting specific error messages, viewing embedded screenshots, and accessing the Playwright Trace Viewer for step-by-step debugging.
- Quality reporting: Generate a high-level summary of test health, including pass/fail ratios and common failure patterns, to share with the development team.
- Environment troubleshooting: Verify the existence of report files and troubleshoot missing outputs by triggering fresh test runs directly through the agent.
| name | test-report |
|---|---|
| description | Open and analyze Playwright HTML test reports. Use when user asks to see test results, check test report, view test output, or analyze test failures. |
| allowed-tools | Bash(npx:*), Bash(open:*), Bash(xdg-open:*), Read, Grep, Glob |
Test Report Viewer
Instructions
1. Open HTML Report
# Open Playwright HTML report
npx playwright show-report
The report will open in the default browser showing:
- Test results summary
- Failed test details
- Screenshots and videos
- Test traces
2. Analyze Report Files (if needed)
Check for report existence:
ls -la playwright-report/
Check recent test results:
# List recent test runs
ls -lt playwright-report/ | head -10
# Check for failures
grep -r "failed" playwright-report/ 2>/dev/null || echo "No failures found"
3. Provide Summary
If analyzing results, provide:
- Total tests: passed/failed/skipped
- Failed test names
- Common failure patterns
- Screenshots/traces available
4. Troubleshooting
If report doesn't exist:
# Run tests first
npx playwright test
# Then show report
npx playwright show-report
Alternative: Direct file access
# Open report HTML directly (macOS)
open playwright-report/index.html
# Linux
xdg-open playwright-report/index.html
Tips
- The report includes interactive filtering by status, browser, file
- Click on failed tests to see detailed error messages and traces
- Screenshots are embedded for visual verification
- Trace viewer allows step-by-step debugging