What CTRF is
The Common Test Report Format (CTRF) is an open JSON format for test results that is meant to look the same whatever the language or framework. A report holds results.tool, a results.summary with counts and start and stop times, and results.tests, one object per test. The specification is still before version 1.0, and its JSON schema is the normative definition.
What the viewer reads
| CTRF field | Shown as |
|---|---|
status: passed, failed | Passed, failed |
status: skipped, pending, other | Skipped |
duration (integer milliseconds) | Time, in seconds or minutes |
suite (an array of names, outermost first) | The suite, joined with › |
message, trace | The failure message and stack trace |
retries, flaky | Retry count and the flaky marker |
summary.tests, summary.failed and the rest | Compared with the tests in the file |
The specification calls a test flaky when it passed after failed attempts. The viewer shows the flaky flag the reporter set, and the flaky test finder can compare several CTRF files to find tests that change result between runs.
Mixing CTRF with other formats
CTRF exists so that results from different stacks can sit side by side. The viewer takes that further: drop a CTRF file from a Jest suite next to a JUnit file from pytest or a TRX file from .NET and it merges them into one view, with a table of the files and their totals.
Sources
Testland for teams
In developmentAutomated test reports, manual test runs and regression tracking in one workspace. A separate product, built on the same skills.
One email when it opens, nothing else. Privacy policy