93 / 168 · 01 Agent Skills for Browser Automation · Reporting and Observability← prev⊞ allnext →☰ Read as one page
13.1What to Capture
Per-Test Artifacts
| Artifact | Format | Purpose |
|---|---|---|
| Commands executed | Text log | Reproducibility |
| Screenshots (each step) | PNG | Visual timeline |
| YAML snapshots (each step) | YAML | Agent-readable semantic state |
| Current URL (each step) | Text | Navigation tracking |
| Playwright trace (runner/healer sessions) | trace.zip | Full flight recorder — actions, before/after snapshots, console, HAR |
| Timing | JSON | Performance analysis |
| Pass/Fail result | JSON | CI gate |
| Error details | Text | Debugging |
Per-Suite Artifacts
| Artifact | Format | Purpose |
|---|---|---|
| Summary report | JSON + text | Quick overview |
| Failure screenshots | PNG directory | Human review |
| Agent reasoning log | Markdown | Understanding agent decisions |
| Performance metrics | JSON | Trend analysis |
A structural advantage of the disk-first CLI: most of this is already on disk. The .playwright-cli/ workspace accumulates snapshots and screenshots as a side effect of the agent working — observability is largely a matter of copying the workspace into your artifacts directory, not instrumenting anything.