TeamCity supports JaCoCo, a Java Code Coverage tool allowing you to measure a wide set of coverage metrics and code complexity.
On this page:
Enabling JaCoco coverage
TeamCity supports the java agent coverage mode allowing you to collect coverage without modifying build scripts or binaries. No additional build steps needed - just choose JaCoCo coverage in a build step which runs tests:
- In the Code Coverage section, select JaCoCo as a coverage tool in the Choose coverage runner drop-down.
- Set up the coverage options - refer to the description of the available options below.
Classfile directories or jars
Newline-delimited set of path patterns in the form of +|-:[path] relative to the checkout directory to scan for classfiles to be analyzed. Libraries and test classfiles don't have to be listed unless their coverage is wanted.
Classes to instrument
Newline-delimited set of classname patterns in the form of
The code coverage results can be viewed on the Overview tab of the Build Results page; detailed report is displayed on the dedicated Code Coverage tab.
Importing JaCoCo coverage data to TeamCity
TeamCity can parse JaCoCo coverage data and generate a report using a service message of the following format:
Space-delimited set of paths relative to the checkout directory to read the jacoco data file
Space-delimited set of classname include patterns
Space-delimited set of classname exclude patterns
Space-delimited set of paths relative to the checkout directory to read sources from. Does not need to be listed by default.
Space-delimited set of path patterns in the form of
Path to the directory to store temporary files. The report will be generated as coverage.zip under this directory. Check that there is no existing directory with the same name.
A random directory under Agent's temp directory
An example of a complete service message: