Setting up Coverage Filters

Sometimes, you do not need to know code coverage data solution-wide.
For example, you may not be interested in coverage statistics for code marked with
ObsoleteAttribute
or a specific legacy project.
In this case, you can set coverage filters based on namespace, project, type, type member, or attribute.

By default, dotCover provides built-in filters for system assemblies.
You cannot view or edit these filters.
However, if you need to disable these filters, clear the
Filter out system and auxiliary assemblies
check box on the
Environment | General
page of dotCover options.

Coverage filters are saved in the dotCover settings.
If you reset all settings, all coverage filters will be removed.
For more information about dotCover settings, see
Managing and Sharing dotCover Settings.

Adding new coverage filters

To add a new coverage filter

Analyze code in
- to include the specified code item into code coverage analysis
and exclude all other code items.

Do not analyze code in
- to exclude the specified code item from code coverage analysis.

Do not analyze code marked with attribute
- to exclude code items with the specified
attribute from code coverage analysis.

If you have chosen one of the first two options, specify an assembly, a class, and/or a method to
be included or excluded in the coverage analysis.
Code items are filtered independently on one another.
For example, if you specify a method and leave asterisks (*) for assembly and class
to exclude methods with the specified name from all assemblies and all classes.

You can use asterisk wildcards when specifying code item names in a filter:
'*' (asterisk) represents zero or more characters.
For example, you can use the
*.Tests
wildcard that will exclude all test projects from code analysis.

If you have chosen the last option, specify the name of the attribute that will be used to exclude
symbols from the coverage analysis.
Optionally, specify the assembly name where this attribute is declared.

In the
Apply filter to
section, specify the scope of the filter:
All solutions or Current solution.

Click
OK
to finish adding the filter.

In the
Coverage Filters
dialog,
click
Save
to save and apply your modifications.

Be careful when adding exclude filters.
If sme combination of filters excludes everything from the snapshot, this snapshot appears empty.

Sharing coverage filters

Solution-wide filters are saved in the
Solution team-shared
settings layer and,
therefore, can be shared within other developers who work on this solution.

In fact, all you need to do to share solution-wide filters
is to put the
[SolutionName].sln.DotSettings
file in your solution
folder under a version control system (VCS). As soon as other team members get this file from VCS
the filters will be applied on their computers as well.

Note that other JetBrains products that integrate into Visual Studio
may store their solution-wide team-shared settings in the same file.
Therefore, if you put this file under VCS, bear in mind that other product's settings
may be shared as well.
For more information, see
Managing and Sharing dotCover Settings.

Other ways of filtering and searching coverage results

Besides setting up coverage filters in the
Coverage Filters
dialog box,
dotCover provides the following ways of filtering and searching coverage results;