Get Help

XLSX

One Excel sheet, one row per test, formatted as a table with filters — the format every plan writes.

When to use it

For people: business users, analysts, a developer who wants to sort and filter the failures of last night’s run without writing a line of code. It is also the one output the Starter and Professional plans write, so it is where a trial starts. It is not for automation — the file is a rendering of the results, not a data feed; take JSON for that.

How to set it 

Output: xlsx

writes TestResults/cat-test-results-{timestamp}.xlsx next to the project file. For one file that is overwritten on every run:

Format
xlsx
File
LatestTestResults.xlsx
Output:
- Format: xlsx
  File: LatestTestResults.xlsx

See Settings.

What it looks like

One worksheet, Test Results, a header row and one row per test; the range is an Excel table (TestResults, style Medium 2, filter buttons on every column, columns sized to their content). The sample run, first columns:

 Test Full Name                                        Test Result  Duration          Description                                      Expectation       Message                                          …
 [Smoke tests].[Airline dimension matches the source]  Passed       00:00:00.0755756  Every airline in the source must land in the …   sets match        The sets match.                                  …
 [Data quality].[No booking without a passenger]       Failed       00:00:00.1389169  A booking must reference an existing passenger.  set is empty      No row was expected, but at least 1 row exists…  …
 [Smoke tests].[Flights table is loaded]               Error        00:00:06.2492205                                                   set is not empty  Error when executing the test: Invalid object …  …

Multi-line messages keep their line breaks inside the cell.

Details

The 28 columns, in order: Test Full Name · Test Result · Duration · Description · Expectation · Message · Exception · Started On · Finished On · Test Suite · Test Case · Test Name · Tags · Project · First Data Source · First Query · Second Data Source · Second Query · Key · Metadata · Test Order · Timeout · Maximum Errors Logged · Number Of Errors · Log Number Of Errors · Thread Number · Test Definition Guid · Execution Guid. Friendly columns first, technical columns last; the header row is frozen so it stays visible while you scroll. The set is fixed — there is no way to add or drop columns; a database output is the configurable one. Every header is a name Properties uses, with two exceptions: Message holds the raw message (the verdict and the sample of rows, without description and queries), and Duration is a human convenience, not a property.

Changed in 3.0: five columns were renamed to match the properties page — Exception Message → Exception, Start Time → Started On, End Time → Finished On, Order → Test Order, ThreadNumber → Thread Number — and six columns were added: Key, Metadata, Timeout, Maximum Errors Logged, Number Of Errors, Log Number Of Errors. A saved filter, pivot or query over the old column letters or the old ThreadNumber/Order/Exception Message names needs updating.

Written once, after the run. A file that is open in Excel cannot be overwritten — close it before the next run, or use {timestamp} in the name.

  • JSON — the same results for programs.
  • Properties — what the columns hold.
← YAML
JUnit →