What′s New in dotCover

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.

Now, you can refine what projects should be built when a continuous testing session is triggered. This lets you speed up continuous testing sessions. The feature works in both Visual Studio and Rider.

Now, the Unit Tests Coverage window in both Visual Studio and Rider lets you filter coverage results by target framework.

Before 2020.3, methods with outdated coverage info were highlighted only with a marker in the gutter. Now, in Visual Studio, methods with outdated coverage info are also highlighted in the Unit Tests Coverage window.

Now, you can use the Rider’s solution highlight level options to turn code coverage highlighting on and off.

The dotCover console runner for Linux (Debian and Ubuntu) lets you perform coverage analysis on ARM64 systems.

The new release brings several useful new features to the dotCover plugin in Rider:

• The Unit Tests Coverage window now lets you export coverage reports.
• The Unit Tests Coverage window now has a quick search feature.
• You can now navigate from a character in the code to that character in the coverage tree (Navigate to | Coverage Tree).

• Summary report type. The --reportype=SummaryXml parameter lets you create a new report type which includes data on how many classes, methods, and statements are covered in total.
• Now the runner can generate reports for several types at once.

dotCover 2019.3 gets a couple more improvements:

• Support for Microsoft Fakes.
• Ability to group coverage results by nested namespaces in Rider, Visual Studio, and in reports generated by the dotCover console tool.

Now, you can use dotCover console runner not only on Windows but on macOS and Linux as well. To be more convenient on new platforms, the tool accepts command arguments in Unix-style syntax. For example, now, both /TargetExecutable=MyApp.exe and -⁠-⁠targetexecutable:MyApp.exe are valid.

In addition, the console runner gets two new commands to simplify coverage analysis of .NET Core and Mono applications and unit tests: cover-dotnet and cover-mono.