Report exports
Download any run report as a PDF, a self-contained HTML page, JSON, or JUnit XML
Report exports
Every finished run has a full report: the pass-or-fail result, each step with its expected and actual outcome, screenshots, performance metrics, and any issues found. You can download that report as a file in four formats, from the Export Report card in the run's sidebar (or the Export menu in the top bar). Single runs and multi-step pipelines both export.
Formats
| Format | Best for | What you get |
|---|---|---|
| Sharing, tickets, audits | The full report in one document: result, steps, screenshots embedded inline, metrics, issues, and a branded footer with page numbers. | |
| HTML | Opening anywhere | The same report as a single self-contained web page. Screenshots and styling are baked in, with no account or network needed. |
| JSON | Your own tooling | The structured result: every step, status, metric, and issue as data. |
| JUnit XML | CI | The format CI systems understand. Import it into GitHub Actions, GitLab, Jenkins, or CircleCI to see the run in the native test-report view. |
PDF and HTML are generated in your browser, so the run data goes straight into the file. JSON and JUnit are the machine-readable views of the same result.
Pipelines
A multi-step pipeline exports as a single file. PDF and HTML lay out one page (or section) per step, in order, so the whole journey is one document instead of one link per step.
When to use which
- Hand a result to someone who will not log in: PDF or HTML.
- Keep a dated artifact for an audit or release sign-off: PDF.
- Feed results into a dashboard or script: JSON.
- Surface a browser run next to your unit tests in CI: JUnit XML.