Skip to main content

About the Summary report

The Summary report is the single document that brings together the outcome of a verification run. Each time you run one or more tests, Test Services produces a Summary report that states the overall result and links to the individual report for each test. It is the artifact you keep as evidence that a deployment was verified at a point in time.

What the Summary report contains​

Every Summary report opens with a header that identifies the run: the host name, the user who ran the tests, the date and time, and the overall result. When tests run under separate credentials, the header also names the submitting and executing users.

Below the header, the report lists each test in the run with its name, description, result, and execution time, and links to that test's individual report. A table of contents and a test summary grid let a reviewer see the whole run at a glance before reading any single test.

How the overall result is decided​

The overall result summarizes the entire run in one value:

  • Passed. Every test produced a passing result.
  • Failed. At least one test failed.
  • Not available. No tests have run yet.
  • Aborted. A user stopped the run before it finished. The report names the user who aborted it.

The result is deliberately conservative: a single failed or setup-failed test makes the whole run Failed rather than Passed, so a passing Summary report is a strong statement about the deployment. For the meaning of each individual test result, see Test result statuses.

Where the Summary report fits​

Test Services stores the Summary report, alongside each test's report, in the OpenLab storage backend. You can download it from the reports panel on the home page and from the execution history. All Test Services reports share a common header and footer and are produced in the language of the machine, so reports from different tests and locales read consistently.

The Summary report is the successor to the single report that earlier versions of the product generated for one end-to-end run; today it aggregates the results of an entire suite of independent tests.

See also​