Free tools

CTRF Report Viewer: Common Test Report Format

View a Common Test Report Format (CTRF) JSON file from any framework: status counts, flaky tests, retries and suites.

Runs in your browserNothing is uploadedNo sign-up

Paste the file, or choose or drop one or more files. Reads JUnit XML, TRX (Visual Studio / dotnet test), NUnit 3 XML, Playwright JSON, CTRF JSON.

Or drop files on the box. Nothing is uploaded.

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 fieldShown as
status: passed, failedPassed, failed
status: skipped, pending, otherSkipped
duration (integer milliseconds)Time, in seconds or minutes
suite (an array of names, outermost first)The suite, joined with ›
message, traceThe failure message and stack trace
retries, flakyRetry count and the flaky marker
summary.tests, summary.failed and the restCompared 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

  • CTRF specification, accessed 2026-11-21 (statuses, millisecond durations, suite as an array and the flaky definition).
  • CTRF repository README, accessed 2026-11-21 (project status and the normative schema).

Testland for teams

In development

Automated 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