Understanding Test Reports
Every Playrunner test run generates a full Playwright HTML report stored with a unique run ID. This tutorial shows you how to navigate the report, find failing tests, and access screenshots and traces.
Accessing a report
After a run completes, right-click any Playwright node on the canvas and choose View Report. The report opens in a new browser tab, served directly by the Playrunner file server.
Report structure
The HTML report is generated by Playwright itself and contains:
| Section | What it shows |
|---|---|
| Summary | Pass / fail / skip counts and total duration |
| Test list | Every spec file and individual test case |
| Test detail | Steps, duration, error message, and stack trace |
| Attachments | Screenshots, videos, and traces captured during the run |
Reading a failing test
- Click on a failed test in the list (marked with a red ✗).
- The detail pane shows the error message and the step that failed.
- If a screenshot was captured on failure, it appears under Attachments.
- Click Trace (if available) to open the Playwright Trace Viewer — an interactive timeline of every network request and DOM snapshot during the test.
Run history
Each run is stored under a unique UUID directory on the file server:
/outputs/<testId>/<nodeId>/
Previous reports are never overwritten, so you can compare runs across time. The editor's node context menu always links to the most recent run for that node.
Next steps
You've completed the core tutorials. Where to go from here:
- 🔐 Reuse browser sessions with Authentication Profiles — capture and attach an encrypted signed-in session to a Local or Playrunner Cloud runner workflow
- 📖 Development reference docs — integration development and deep dives into every service
- 🔧 Troubleshooting — common issues and fixes