Get Help

Settings

The Output key of the project file: the short form, the list form and every key an output item takes.

Outputs are requested in the project file under the root key Output (also Outputs). The key is a root setting like Threads — at the very beginning of the line, not inside a test or a data source. It takes one of two forms.

Short form — formats only

A string: one or more format tokens, separated by commas. Each becomes a file with the default name in the default directory.

Output: xlsx, json, junit

Tokens: xlsx · json · yaml · trx · junit. Any other token fails the open with Unknown format of output file: ….

List form — one item per output

A list of items. Each item is either a file (Format, optionally File) or a database (Database plus Table or Procedure). The two kinds mix in one list; a project may have any number of items.

Output:
- Format: xlsx
  File: LatestTestResults.xlsx

- Format: json
  File: "Z:\\TestResults\\SmokeTests-{timestamp}.json"

- Database: DWH
  Table: dbo.CatTestResult
Key Applies to Meaning
Format file The format token: xlsx · json · yaml · trx · junit. Required for a file output.
File file Path of the file to write. Relative paths are resolved against the directory of the project file; a directory that does not exist is created. Default: TestResults/cat-test-results-{timestamp} with the format’s extension (.xlsx, .json, .yaml, .trx, .xml for JUnit).
Path file Older name for File; File wins when both are given. Still accepted, may go in a future major version.
Database database Name of a data source definition in the project. Its provider must be SqlServer@1, SqlServer@2, Postgres@1 or Oracle@1; a data source that is not defined, or uses another provider, fails the open.
Table database Table to insert into, schema-qualified. One of Table and Procedure is required.
Procedure database Stored procedure to call instead of inserting (on Oracle: the package that holds the procedure). See Database outputs.

The timestamp

{timestamp} anywhere in File is replaced when the file is written — after the last test — with the local date and time in ISO 8601 form, colons replaced by dashes so it is a valid file name: 2026-08-21T09-06-44.7333889. Without it, every run overwrites the same file, which is what a “latest results” file wants.

Where the setting is read

CAT reads the outputs when it opens the project, not when it writes them — a bad data source name, an unknown format or a plan that does not allow the format all fail the open, before any test runs. The Starter and Professional plans write MS Excel only: every other Format, and every Database item, is refused on those plans with a message that says what the Team plan adds.