Skip to main content
Every run produces a report: the pass-rate donut, the failures grouped by root cause, an AI-written summary, and a copy-paste fix prompt for your coding agent. Read it in the portal for triage, or download the PDF — a cover page, executive summary, and per-failure detail — to hand to a PM, to leadership, or to attach to a release record.
The Test Report page — stat cards, the pass/fail/blocked donut, and the Detailed Test Report button

​
Where to Find It

The report opens from a run’s page: click View Report on a run in Test Runs. It reflects the run you opened it from.
View Report on a run's page, which opens that run's report
The report is generated from an AI analysis pass that runs automatically when a run finishes. While it’s still working, the page shows “Analyzing your results” — refresh or wait a moment and the full report renders.

​
Reading the Report Page

The report is built around outcomes and coverage — pass/fail/blocked counts and how many features and cases were tested — rather than timing. For when a run happened and how recent it is, use the Test Runs history (each run is timestamped); the downloadable PDF also prints a “Saved By TestSprite” time estimate on its cover.

​
The AI Fix Prompt

The Fix prompt for your coding agent card holds a ready-to-paste prompt that enumerates every concrete problem the run found and what to change. Click Copy prompt and paste it into Claude Code, Cursor, or any LLM agent pointed at your repo.
The Fix prompt for your coding agent card — a Copy Prompt button and the generated repo-oriented prompt
The prompt is generated by the same analysis that writes the summary, so it reflects the actual failures in this run. When there are no actionable issues, the card is empty.
The same copy-a-fix-prompt idea appears in two other places: the Triage Queue on Insights, and (for one failing test at a time) the Step-by-Step failure detail.

​
Downloading the PDF

The PDF is a fuller, print-ready rendering of the same execution — with a cover, a table of contents, coverage tables, and per-failure detail including source code. It’s produced through your browser’s print dialog rather than as a server file, so the export step matters.
1

Click Detailed Test Report

On the report page, click Detailed Test Report. A new tab opens and assembles the full report.
The Detailed Test Report button on the Test Report page
2

Let it finish generating

The page shows a Generating spinner while it lays out every section. Wait for it to settle before printing.
3

Print to PDF with the right settings

When the print dialog opens, choose Save as PDF as the destination and match these settings so the report renders correctly:Save. You now have a self-contained PDF to share or archive.
The PDF is generated client-side by your browser’s print-to-PDF. There is no separately-stored PDF file on the server — regenerate it any time from the same button.

​
What’s in the PDF

The failure-detail section covers failed and blocked tests only — passing tests aren’t itemized. That keeps the report focused on what needs attention and makes it a natural artifact to attach to a bug review or release sign-off.

​
Who it’s for

  • PMs and leadership — the cover tiles and executive summary give the run’s outcome and headline findings without reading test code.
  • Release records — attach the PDF to a release or sign-off so there’s a durable, self-contained record of what was tested and what passed.
  • Engineers — the per-failure detail (error, cause, fix, source) is enough to start debugging straight from the document.

​
Generation & Retention

  • Generated automatically when a run completes — the analysis pass runs on completion, and the report/PDF render on demand from the stored result. No manual “generate report” step.
  • No fixed expiry on the report itself: it lives with the execution record and re-renders whenever you open it. The time-limited pieces are the embedded media links — screenshots are signed for roughly a week — so download the PDF if you need a permanent copy with images intact.

​
Where to Go Next

Watching a Run Live

See results build up before the run finishes

Insights

The triage queue and quality trends across runs

Step-by-Step

Localize a single UI failure action by action

Test Detail

The full page behind a single test