dotCover Web Help

This topic provides several walkthroughs that would help you understand how to apply the Console Runner to your unit test projects. In the examples, it is supposed that dotCover is installed and the path to the Console Runner executable ([Program Files]\JetBrains\dotCover\[version]\bin\dotCover.exe) is added as a system path.

In this topic:

Basic scenario

The following procedure illustrates the simplest case of running coverage with the Console Runner.

To cover a single unit test project
  1. Build your unit test project.
  2. Type dotcover help analyse coverage.xml on the command line.
  3. Open the generated coverage.xml file and edit ti to specify the configuration parameters. For example, the configuration file can look as follows:

    <?xml version="1.0" encoding="utf-8"?>
      <TargetExecutable>D:\Program Files\NUnit 2.6\bin\nunit-console.exe</TargetExecutable>


    • TargetExecutable: Is the path to the unit testing framework runner
    • TargetArguments: Arguments passed to the runner - the compiled unit test assembly.
    • Output: Report file name.
    • ReportType: Type of the report (in this case, we generate an HTML report)
  4. Type dotcover analyse coverage.xml to run the coverage with the specified parameters.
  5. When the Console Runner exits, the AppCoverageReport.html file should appear next to the coverage.xml. Open this file to explore the coverage results in your web browser.

Applying filters

If the coverage report contains some information that you are not interested in, you can apply filters, which tell the Console Runner, what should be included or excluded from the coverage report.


Check out the Setting up Coverage Filters to learn how to configure filters in dotCover GUI. Note, that the filters configured in the GUI are not applied when you run coverage with the Console Runner.

You can specify include and exclude filters in any order. Independently of the order, Console Runner first applies include filters and then exclude filters.
If no include filters is specified explicitly, Console Runner first includes everything and then excludes what specified in exclude filters.
If there is some include filter, then Console Runner first excludes everything that does not match to include filter, and then applies explicit exclude filters, if any.

By default, whether you specify any exclude filters on not, Console Runner adds the following filters for system assemblies:

  • mscorlib
  • System
  • System.*
  • Microsoft.*

In the first steps of the previous procedure we have generated the configuration file with the dotcover help analyse coverage.xml command. In this file, there are two nodes commented out: Filters and AttributeFilters. You can use these nodes to apply filters.

To set up coverage filters
  • To exclude some items from the coverage report while keeping all others, add the corresponding entries to the ExcludeFilters node. For example, to exclude the IntegrationTests class, we can add the following to the coverage.xml configuration file:


  • Alternatively, to include only the desired items while excluding all others of the same kind, add the corresponding entries to the IncludeFilters node.
  • Another option, is to filter out classes and methods based on their attributes. For example, to filter out methods marked with the System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute attribute, we can add the following to the coverage.xml configuration file:


Covering multiple test projects

If there are several unit test projects in your solution, you can run coverage for all of them at once as described in the basic scenario. In this case, to avoid specifying full path to each assembly, you could use the TargetWorkingDir parameter when specifying test assemblies. E.g.:

<?xml version="1.0" encoding="utf-8"?>
  <TargetExecutable>D:\Program Files\NUnit 2.6\bin\nunit-console.exe</TargetExecutable>
  <TargetArguments>\AppTests.dll, AppTests2.dll, AppTests3.dll</TargetArguments>

However, sometimes this approach may not work. For example, when unit test projects use different unit testing frameworks. In such cases we can breakdown the coverage, merging and reporting into individual steps.

Let's suppose that we have two unit test projects, TestProject1 that uses MSTest and TestProject2 that uses NUnit. To run coverage on both projects and get a single report, we perform the following steps:


To run coverage for multiple projects in separate steps
  1. Create two configuration files for running the cover (c) command on each of the tests projects. testProject1.xml for the TestProject1 that uses MSTest:

    <?xml version="1.0" encoding="utf-8"?>
      <TargetExecutable>C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\MSTest.exe</TargetExecutable>

    and testProject2.xml for the TestProject2 that uses NUnit:

    <?xml version="1.0" encoding="utf-8"?>
      <TargetExecutable>D:\Program Files\NUnit 2.6\bin\nunit-console.exe</TargetExecutable>

  2. Run the cover (c) command on each of the tests projects using the prepared configuration files: dotcover c testProject1.xml and dotcover c testProject2.xml. As a result you'll get two coverage snapshots, Snapshot1.xml and Snapshot2.xml.
  3. Run the merge (m) command to merge both snapshots:
    dotcover m merge.xml
    where the merge.xml is the configuration file:

    <?xml version="1.0" encoding="utf-8"?>

  4. To build an HTML test report from the merged snapshots, run the report (r) command
    dotcover r report.xml
    where the report.xml is the configuration file:

    <?xml version="1.0" encoding="utf-8"?>