JetBrains dotCover
TeamCity comes bundled with the console runner of JetBrains dotCover. In addition to the bundled version, you can install another version of JetBrains dotCover Command Line Tools.
After choosing the appropriate option in the .NET coverage section of a build step, you will be able to collect code coverage for your .NET project and then view the coverage statistics and detailed coverage report inside the TeamCity web UI.
If you have a license for dotCover and have it installed on a developer machine, TeamCity-collected coverage results can be downloaded and viewed inside Visual Studio with the help of the TeamCity Visual Studio Add-in.
dotCover Settings
Path to dotCover Home | Leave this field blank to use the default dotCover. Alternatively, specify the path to the dotCover installed on a build agent. |
Filters | Specify a new-line separated list of filters for code coverage. Use For example, to run coverage on all See also the related blog post. |
Attribute Filters | If you do not want to know the coverage data solution-wide, you can exclude the code marked with an attribute (for example, with |
Additional arguments | Provide a new-line separated list of additional commandline parameters to pass to |
Note that dotCover coverage engine reports statement coverage instead of line coverage.
Compile and Test in Different Builds
To build a consistent coverage report, dotCover has to be able to find source files under the build checkout directory which should be easy if you build binaries and collect coverage in the same build, or if you use different builds, but they use a snapshot dependency and the same agent as well as the same VCS settings.
If you need to build binaries in one build and collect code coverage in another one using different checkout settings, some additional properties are required. It is assumed that:
Build configuration A compiles code with debugging information and creates an artifact with assemblies and
.pdbfilesBuild configuration B runs tests with dotCover enabled and has a snapshot dependency on A.
To display the source code in the Code Coverage tab of build results of B, you need to point B to the same VCS root as A to get your source code in an appropriate location (the checkout root) and add an artifact dependency on build from the same chain of A (for dotCover to get the paths to the sources from the .pdb files).
You also need to tell TeamCity where to find the source code. To do this, perform the following:
Add the
teamcity.dotCover.sourceBaseconfiguration parameter with the value%teamcity.build.checkoutDir%to the compiling build configuration A.Add the configuration parameter
dotNetCoverage.dotCover.source.mappingto your test configuration B with the value%dep.btA.teamcity.dotCover.sourceBase%=>%teamcity.build.checkoutDir%, wherebtAis the actual ID of your configuration A.
Bundled dotCover Versions
TeamCity Version | dotCover Version |
|---|---|
2018.1 | 2018.1.2 |
2018.2 | 2018.1.4 |
2019.1 | 2019.1.1 |
2019.2 | 2019.2.3 |
2020.1 | 2019.2.3 |
2020.2 | 2020.2.4 |
2021.1 | 2021.1.2 |
2021.2 | 2021.2.2 |
You can view the installed versions of dotCover on the Server Administration | Tools page. The bundled version is set as default, you can install other versions and change the default settings.
Cross-platform dotCover
TeamCity allows collecting coverage for .NET Core projects on Linux and macOS by supporting cross-platform JetBrains dotCover, version 2019.2.3+. Thi
dotCover 2019.2.3 for Windows is bundled with TeamCity. If you need to collect code coverage under non-Windows platforms, install the cross-platform dotCover tool on a build engine and enable the dotCover coverage in the .NET build step. If you want to use cross-platform dotCover under Windows as well, make sure the agents have .NET Framework SDK 4.6.1+ installed.
You can also run dotCover code coverage analysis inside a Docker container, with the Docker Wrapper extension.