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. PartCover

PartCover

Last modified: 20 April 2023

TeamCity supports code coverage with PartCover (2.2 and 2.3) for NUnit tests run via TeamCity NUnit test runner, which can be configured in one of the following ways: web UI, TeamCity NUnit Test Launcher, NUnit for MSBuild, NUnit for MSBuild, NUnit for NAnt Build Runner.

tip

Important Notes

  • In order to launch coverage, PartCover should be installed on an agent where coverage build will run.

  • You don't need to make any modifications to your build script to enable coverage.

  • You don't need to explicitly pass any of the PartCover arguments to the TeamCity NUnit test runner.

  • PartCover supports .NET Framework 2.0 and 3.5 started under x86 platform. Make sure you have configured your NUnit tests to run on the .NET Framework version 2.0 or 3.5 and under x86.

To configure PartCover:

  1. While creating/editing Build Configuration, go to the Build Runner page.

  2. Select PartCover (2.2 or 2.3) as a .NET coverage tool.

  3. Set up the PartCover options - find the description of the available options below.

Option

Description

Path to PartCover

Specify the path to PartCover installed on a build agent, or corresponding Configuring Build Parameters, if configured.

Additional PartCover Arguments

Specify additional PartCover arguments, except the ones that can be specified using web UI. Moreover, do not specify here the output path for the generated reports, because TeamCity configures it automatically.

Include Assemblies

Explisitly specify the assemblies to profile, or use [*]* to include all assemblies.

Exclude Assemblies

Explicitly specify the assemblies to be excluded from coverage statistics. If you have specified [*]* to profile all assemblies, type [JetBrains*]* here to exclude TeamCity NUnit test runner sources.

Report XSLT

Write xslt transformation rules in the following format (one per line): file.xslt=>generatedFileName.html. As file.xslt you can use the default PartCover xslt, or your own. Xslt files path is relative to build's checkout directory.

tip

Note, that default xslt files bundled with PartCover 2.3 are broken and you need to write your own xslt files to be able to generate reports.

Reporting PartCover Results Manually



if .NET code coverage is collected by the build script and need to be reported inside TeamCity (for example, Rake, or if you run tests via test launcher other than TeamCity NUnit Test Launcher), there is a way to let TeamCity know about the coverage data. Please read more at Manually Configuring Reporting Coverage.