CTRF

CTRF, or Common Test Report Format, is a JSON-based standard for representing test execution results. It was created to address the inconsistencies and limitations of older formats like JUnit XML by providing a strict, well-documented schema that all test reporters can target uniformly.

How CTRF Differs from JUnit XML

While JUnit XML has been the industry default for decades, it suffers from a lack of a formal specification. Different test runners produce subtly different XML, and consumers must handle numerous edge cases. CTRF solves this by defining a single, versioned JSON schema. Every compliant reporter produces output with the same structure, field names, and data types, eliminating the parsing ambiguity that plagues XML-based reports.

CTRF also includes fields that JUnit XML lacks out of the box, such as retry information, environment metadata, and a summary object with aggregate counts. This makes it a better fit for modern CI workflows where retries, parallelism, and multi-environment testing are common.

Adoption and Ecosystem

CTRF reporters are available for popular frameworks including Jest, Playwright, Cypress, pytest, and many others. CI platforms and test analytics tools are increasingly adding native CTRF support alongside their existing JUnit XML ingestion. Because the format is JSON, it integrates naturally with JavaScript-based toolchains and REST APIs.

Why CTRF Matters for Test Monitoring

When a test monitoring platform like TestGlance ingests results, data consistency is critical. Inconsistent field names or missing attributes force brittle parsing logic and degrade analytics quality. CTRF's strict schema means the platform can trust the shape of incoming data, enabling more reliable trend tracking, flakiness detection, and duration analysis.

For teams starting a new project or re-evaluating their test reporting pipeline, CTRF offers a cleaner, more future-proof alternative to JUnit XML while maintaining the simplicity that makes adoption straightforward.