What′s New in dotCover

This page guides you through updates in recent dotCover versions. Highlights include more options for code coverage highlighting, continuous testing for a lot faster unit test feedback, support for Visual Studio / JetBrains Rider and .NET Core.


Free 30-day trial

Coverage filters in JetBrains Rider 2020.1

Now, you can apply both runtime and coverage results filters in JetBrains Rider.

Support for Unity

Support for Unity on Windows, macOS, and Linux 2019.3

dotCover 2019.3 provides support for Unity 2018.3 and later on all operating systems. To perform coverage analysis of Unity tests, you must use JetBrains Rider.

Various improvements 2019.3

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.
Support for Mono on Windows, macOS, and Linux

Support for Mono on Windows, macOS, and Linux 2019.2

dotCover 2019.2 gets support for Mono 5.10 and later on Windows, macOS, and Linux. To perform coverage analysis on these operating systems, you must use JetBrains Rider or dotCover console runner.

Console runner on Linux and macOS 2019.2

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.

Support for .NET Core on macOS and Linux

Support for .NET Core on macOS and Linux 2019.1

dotCover 2019.1 provides full support for .NET Core 2.0 – 3.0 projects not only on Windows, but on macOS and Linux as well. To perform coverage analysis on these operating systems, you must use JetBrains Rider or dotCover console runner.

Improved coverage filters 2018.3

Now, there are two groups of filters in the dotCover options: runtime filters (applied during a coverage session) and results filters (applied to coverage results after the session is over).

Coverage results filters get an additional filter by file name.

Multiple target frameworks

Support for multiple target frameworks 2018.3

Now, if a project targets multiple frameworks, the Coverage Tree will show results separately for each framework (each framework will be shown as a separate node in the tree). Code highlighting also depends on context selected in the editor.

Support for Visual Studio 2019 Preview 1

Visual Studio 2019 Preview 1 support 2018.3

dotCover 2018.3, along with other products of the ReSharper Ultimate family, can now be installed into Visual Studio 2019 Preview 1.

dotCover integrated into Rider

JetBrains Rider integration 2018.2

In addition to Visual Studio, now dotCover is a part of the JetBrains Rider IDE on Windows. In this release, there are two main features supported: code coverage analysis of unit tests and continuous testing.

To learn more, see Unit test coverage and continuous testing. Now in Rider!

Support for dotnet

Support for the dotnet console tool 2018.2

Now, dotCover command-line runner can be used as an extension to .NET command-line tools (dotnet.exe). For example, you can run coverage analysis of unit tests by running:
dotnet dotcover test

Moreover, the "classic" dotCover.exe console runner also gets improved. Now, you should not choose between the analyze and cover commands: always use cover. The coverage result will depend only on the --ReportType argument: if it is specified, you'll get a report of a certain type; if not, a regular coverage snapshot will be saved.

To learn more, see > dotnet dot—Āover test

Continuous testing in any session

Continuous testing in any session 2018.1

No more separate continuous testing session! Continuous testing mode can be turned on for any unit test session. In dotCover 2017.3 and earlier, your continuous testing scope was limited by a single continuous testing session. Now, you can have as many scopes for continuous testing as you need.

Moreover, in dotCover 2017.3, you had no alternatives on how tests were auto-started during continuous testing. After you build or save your solution, dotCover started tests under coverage. In 2018.1, coverage is no longer necessary: you can tell dotCover to simply run new and outdated tests (without covering them). This could be a great time saver if you already have an up-to-date coverage snapshot.

To learn more, see Better continuous testing and more!

Unit Test Coverage window

Unit Test Coverage window 2018.1

Coverage information is now shown in a separate Unit Test Coverage window instead of a per-session Coverage tab. The positive effect of this decision is the ability to see aggregated coverage data for all unit test sessions in one place.

To learn more, see Better continuous testing and more!

Improved console runner tool

Improved console runner tool 2018.1

dotCover console runner gets the ability to cover arbitrary managed processes and services (analyze-everything, analyze-service) and send the get coverage snapshot command to the running instance of the console tool. This dramatically eases getting coverage of web apps running on IIS/IIS Express.

To learn more, see Analyzing code coverage of web apps.


Free 30-day trial