TeamCity
 
7.0
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. Administrator's Guide
  3. Managing Projects and Build Configurations
  4. Creating and Editing Build Configurations
  5. Configuring Unit Testing and Code Coverage
  6. Configuring .NET Code Coverage
  7. JetBrains dotCover

JetBrains dotCover

Last modified: 20 April 2023

TeamCity comes bundled with console runner of JetBrains dotCover. Just by enabling configuration option you can collect code coverage for your .Net project and then view coverage statistics and detailed coverage report inside TeamCity web UI.

If you have a purchased dotCover installed on a developer machine, TeamCity-collected coverage results can be downloaded and viewed inside Visual Studio with the help of Visual Studio Addin.

dotCover Settings



Path to dotCover Home

Leave this field blank to use bundled dotCover. Alternatively, specify path to dotCover installed on a build agent.

Filters

Specify assemblies to profile one per line using following syntax: +:assembly=*;type=*;method=***. Use -:assembly to exclude an assembly from code coverage. Asterisk wildcard (*) is supported here.

Attribute Filters

Starting with TeamCity 7.1, if you don't want to know coverage data solution-wide, you can exclude from coverage statistics code marked with an attribute (for example, code marked with ObsoleteAttribute). You only need to specify these attribute filters here in a following format: filters should be a new-line separated list; use the -:attributeName or -:module=myassembly;attributeName syntax to exclude a code marked with attributes from code coverage. Use asterisk * as a wildcard if needed. Supported only for dotCover 2.0 or newer.

tip

Note, that dotCover coverage engine reports statement coverage instead of line coverage.