Projektor can visualize code coverage stats in your codebase, helping identify areas that need further testing. Projektor supports code coverage reports in these formats:
| Format | Produced by |
|---|---|
| Jacoco XML | Jacoco, and Kover using the Jacoco engine |
| Clover XML | Jest (clover.xml) and other JavaScript coverage tools |
| Cobertura XML | Cobertura and the many tools that can write Cobertura-format reports |
| Go coverage profile | go test -coverprofile (Projektor server >=6.1.0) |
Projektor detects the format of each report automatically. If your code coverage tool can output a coverage report in one of those formats, you’re golden.
Example Projektor report with code coverage:
Instructions for enabling code coverage with each publisher:
Projektor reads Go’s native coverage profile format, the file written by go test -coverprofile:
go test -coverprofile=coverage.out ./...
Then publish the coverage profile along with your test results, for example with the Node script:
npx projektor-publish --serverUrl=<projektor_url> --coverage=coverage.out test-results/*.xml
Go’s test runner doesn’t write JUnit XML itself, so use a tool such as
gotestsum (gotestsum --junitfile test-results/results.xml)
to write test results Projektor can read.
On the test run summary page, Projektor can display the overall coverage stats for your project:

In Gradle multi-project builds, Projektor can break down the coverage stats for each sub-project:

View the code coverage over time in a given Git repository:

Repository code coverage timeline example
View the code coverage stats for repos across your Git organization to identify areas to focus on:
