Open the Report
On a test run, open the... menu beside Debug with AI and select Print / Export. The report opens in a new window with 2 panes:
The toolbar reads Report Preview with the run number, and holds the Print & PDF button.
What the Report Contains
Sections are numbered in the order they appear. Turning one off renumbers the rest, so the numbering always runs in sequence.
Area is the spec file the test case lives in. A test case that passed on a retry reads Passed (retry 2/2), never a plain pass. A test case that was interrupted counts as failed; one still running counts as in progress.
Failures are summarised rather than pasted. A reader sees a readable reason (
Assertion failed: toBeVisible, Timed out after 8s) with the expected and received values beside it. Playwright’s retry transcript never reaches the PDF, so request headers and session cookies stay out of the file.
Each test case name links to that test case inside the run. The link works for readers who are signed in to TestDino and has no effect for anyone else.
Turn Sections Off
The sidebar carries a checkbox for Test case overview, Test case details (with Steps, Screenshots, and Code around the failure under it), Defect summary, and Coverage by area. Report overview, executive summary, and results at a glance are always included.Choose Which Test Cases Appear
The report opens with every test case selected. The sidebar tree groups them by spec file, with a checkbox on each area and each test case. Ticking an area ticks everything under it.- The counter reads
n of N selected. - Select all shown and Clear shown act on what the filters currently show.
- Unticking a test case removes it from every section: the tables, the details, the summary sentence, the defect summary, and the coverage rows. The report never states a number that disagrees with what is in it.
Filter the Test Case List
Filters narrow the tree and set the selection to match, so what you filter is what prints.
In progress appears only while the run still has test cases running. Tags and error types list the values present in this run, so a filter you do not see is one the run has no values for.
Add Your Own Summary
4 fields in the sidebar are yours to write:
The text is remembered in your browser for this run, so a reload keeps it. It is not shared with teammates and does not travel with the run.
Save as PDF
Select Print & PDF, then choose Save as PDF as the destination in your browser’s print dialog. The preview is laid out at print width, so the PDF matches what you see. On a large run the toolbar counts the test cases still loading (Loading details 120/200). Print & PDF stays disabled until that finishes, so the file always carries every detail the report shows. Above 300 selected test cases the sidebar notes that the report is large.
A run that has not finished carries a banner reading that results are partial, with the time the report was taken. On a very large run, a banner names how many test cases the report covers.
Automated Evidence in a Manual Run Report
A manual run report shows the same failure detail for any test case linked to a Playwright test. Automated evidence is on by default in the manual run’s Sections menu: linked test cases then carry the result, steps, screenshots, and failure detail they would have in the automated report. Manual test cases and every count on the page are unchanged.Related
Test Runs
Read a test run: header actions, tabs, and shards
Run Errors
Failures grouped by the error they share
Manual Runs
Track manual and automated test cases in one run
Scheduled Reports
Email a recurring PDF summary on a schedule