Test Report

A test report is the structured record of a test suite execution. It captures which tests passed, which failed (with error messages and stack traces), which were skipped, and how long each test took. Reports can be generated in various formats — JUnit XML, CTRF JSON, HTML, or proprietary formats — depending on the test framework and the tools consuming the results.

What a Test Report Contains

A typical test report includes a summary with total counts of passed, failed, skipped, and errored tests. Below the summary, individual test results are listed with their names, durations, and any failure details. Rich reports may also include screenshots (for E2E tests), console output, and links to the source code or CI build that produced the report.

Why Test Reports Matter

Without test reports, CI results are a binary pass/fail signal. Reports add the context needed to act on failures quickly. An engineer reviewing a failed build can immediately see which specific tests broke, read the error messages, and begin debugging — without re-running the suite locally.

Over time, archived test reports become a historical record. Analyzing reports across multiple builds reveals trends: tests that are gradually slowing down, tests that fail every Monday (pointing to an environment issue), or tests that consistently fail on a particular branch.

Test Reports in the CI Workflow

Most CI systems archive test report artifacts and render them in the build UI. GitHub Actions, for example, can display JUnit XML results as annotations on a pull request. Third-party tools ingest these reports to provide richer analytics — dashboards, trend charts, flakiness detection, and alerting.

Best Practices

Generate reports in a standard format like JUnit XML or CTRF so they are portable across tools. Include timing data for every test case to enable duration analysis. Archive reports as CI artifacts so they remain accessible after the build environment is cleaned up. Ensure failure messages are descriptive enough to diagnose issues without reproducing them locally.