What′s New in dotCover

We've reworked the continuous testing workflow to improve usability:

Previously, each unit test session could be converted into a continuous testing session, which could lead to confusion when multiple sessions are running.

Now, there is a single, separate continuous testing session. This change makes it easier to manage and understand your testing workflow.

Now, you can perform coverage analysis of unit tests and applications based on the MAUI framework. Currently, dotCover supports only WinUI desktop applications targeting .NET 7.0+ on Windows. This applies to dotCover standalone and dotCover in ReSharper and Rider.

dotCover in Rider and ReSharper gets improved code highlighting: new background colors, a new gutter icon for partially covered code lines, and other minor changes.

dotCover command-line tools are now provided as a cross-platform framework-dependent .NET tool.

This tool acts as a default solution for CI/CD scenarios and replaces the previous one.

Now, it's possible to trigger Continuous Testing directly by applying a shortcut. Previously, you could do this only indirectly by building or saving your project. This feature works in both Visual Studio with ReSharper and JetBrains Rider.

We’ve added the Show Covering Tests action to the dotCover context menus in both the code editor and Unit Test Coverage window. This action shows a popup with all covering tests together in the same place. The popup also lets you create a new coverage session.

You can now quickly view coverage results for the file you have open using the shield icon. Clicking on the icon navigates you through the uncovered statements.

You can now use comments to exclude certain lines or blocks of code from coverage analysis. Several options are available for this:

// dotcover disable
var i = 1;
var j = 10;
// dotcover enable

/* dotcover disable */ var i = 1; /* dotcover enable */

var i = 1; // dotCover disable this line

// dotcover disable next line
var j = 100;

For any of these options to work, you must reference the JetBrains.dotCover.MSBuild NuGet package. This is a development-only dependency that won't be included as a run-time dependency in your project.

A new Code Vision metric has been added to dotCover in Rider. For each type member included in a set of tests, dotCover shows the number of successful and failed tests. You can also use a Code Vision notification to run, cover, and debug the tests.

The dotCover console runner is able to collect coverage information for individual tests and show it in the generated reports. Currently, only the following test runners are supported: dotnet test, dotnet vstest, vstest.console.exe. For example: dotCover.exe dotnet --output=AppCoverageReport.xml --reportType=XML --IncludePerTestInfo=Method -- test "C:\MyProject\MainTests.csproj"

• Now, dotCover can run coverage analysis of test classes in parallel within one assembly. In certain scenarios this can result in faster coverage analysis.
• Unit test runners can now be preloaded for .NET Core and .NET projects (this allows coverage analysis to start quicker, as the unit test runners are already loaded in memory).

• We’ve improved support for C# 8.0 and C# 9.0 in the coverage tree (showing default interface implementations, and more).
• Now, dotCover will offer to restart Unity Editor when coverage filters are changed.

You can now configure coverage filters in Visual Studio with ReSharper in the same way as in JetBrains Rider.

You can install the dotCover console runner as a dotnet global tool: dotnet tool install --global JetBrains.dotCover.GlobalTools --version 2021.1.0

Use it to analyze coverage in your .NET Core projects and unit tests.