Skip to content
squallyDocs
Runs

Run report

A print-ready view of one run - filters, your title and notes, print or save as PDF, copy as Markdown.

Open it from a run’s menu with Export report…. It covers the whole run - every shard - and is available on every plan. Back to run #N returns to the run.

The page has two parts: the options on the left, and on the right the report itself, drawn as a paper page. Only the paper page is printed.

The paper page

Section titled “The paper page”

The page starts with the Squally logo and when the report was made, for example “Created Oct 17, 2026 · 09:40”. Below:

  • the project and the run, for example “Demo Shop · Run #24”, with “ · shard N only” while one shard is picked;
  • the title: the commit’s first line, or “Run #N” when the run has no commit message. The pencil next to it edits it;
  • the run’s line, the same as on the run page: status, number, the run page’s chips (Local, the job key, PR #n, Re-run of #N or Re-run: #M, the shard count), branch, commit, author, time and duration. It ends with View in CI where the run has a link to its CI run, and Check posted opens the GitHub check itself;
  • one sentence on what happened, for example “2 of 24 tests failed. 2 were flaky, 1 was skipped. Stability 82.6%.”;
  • while one shard is picked: “Lists below filtered to shard N · totals for the whole run”.

Then, in this order:

  • Notes, folded to Add notes while empty. Empty notes are not printed.
  • Summary: Stability, Total, Passed, Failed, Flaky and Skipped, and a table of the shards for a sharded run. Under Stability, “first-try passes · this run” says what it counts - this run only, so it can differ from the week’s figure in the email report. In the shards table, a shard a re-run did not re-run reads “passed in #N · not re-run”, without counts. While the run’s counts can still change, the summary says “Partial — these counts cover only part of the run.”, by the same rule as the run page: never for a finished, cancelled or settled incomplete run.
  • Errors in this run - the run’s errors, counted like the run page: each test by its final attempt across the whole run, “all passed on retry” or “N of M passed on retry” where a retry rescued its tests. The heading counts them, for example “2 errors in 3 tests”, each test once. Each category says how many tests it hit, for example “Assertion · 3 tests”, and each error lists its tests, with the project and, on a sharded run, the shard.
  • Failed tests - each failed test with its error and screenshot. At most 20 screenshots are shown; the rest are “+ N more screenshots in the app”.
  • All tests - every test, by spec file.

A test that ran under a named Playwright project carries it after its title, for example “applies a coupon code (chromium)”, so the same test in chromium and firefox reads as two tests - in every section and in the Markdown copy.

A footer names the run and the time zone the times are in.

Options

Section titled “Options”
  • Report: two starting points. Team summary, what the page opens with: errors, failed tests, and all tests while the run has at most 300 tests, with the first line of each error. Full record: every list on, whole error messages, no filter. Any other choice is shown as custom, and Reset to team summary goes back.
  • Screenshots: on or off.
  • Shard, for a sharded run: narrows the three lists to one shard. The summary and the totals always cover the whole run. Clicking a shard in the shards table picks it too.
  • Customize: turns Errors, Failed tests and All tests on or off. Under All tests, a status filter - All, Failed, Passed, Flaky, Skipped - narrows that list; while it is not All, the heading says so, for example “All tests · failed only”. Full error messages shows whole messages instead of their first line.

The choices are kept in the page’s address, so a copied link opens the same report.

Title and notes

Section titled “Title and notes”

Add notes under Summary, Next steps and Prepared by. Title and notes are kept in this browser only - they are not saved in Squally and nobody else sees them.

Section titled “Print or copy”
  • Print or save PDF uses your browser’s print dialog. The PDF is named after the project and the run, for example “Demo Shop — Run #24”.
  • Copy as Markdown copies the same sections and filters, with links back into Squally and without images - for an issue, a pull request or a chat. Its line about the run has the facts as words after the run number, for example “Failed · Run #24 · firefox · Re-run of #23 · 2 shards · branch main …”; the pull request is named separately, with its title. The line ends with [View in CI](…), the link to the CI run, when the run has one.

The weekly email about a whole project is something else: see Email reports.