What′s New in dotCover

This page guides you through updates in recent dotCover versions. Highlights include xUnit support, improved code coverage highlighting, continuous testing for a lot faster unit test feedback, and support for Visual Studio 2017 RC.

Free 30-day trial
Support for Visual Studio 2017 RC

Visual Studio 2017 RC initial support 2016.3

dotCover 2016.3, along with other products of the ReSharper Ultimate family, can now be installed into Visual Studio 2017 RC. Note that new .NET Core unit testing in Visual Studio 2017 RC is not yet supported by ReSharper Ultimate 2016.3. This means that currently dotCover is not able to provide coverage of .NET Core tests in Visual Studio 2017 RC.

Improved code coverage highlighting. Showing test results

Improved code coverage highlighting 2016.3

A new highlighting engine in dotCover 2016.3 reveals both coverage status and unit test status. A marker in the text editor shows red if any tests related to the current statement are failing, green if all tests are passing, and grey if there are no tests covering this statement.

Extremely helpful when used with continuous testing!

dotCover supports xUnit.net out of the box

Out-of-the-box xUnit support 2016.1

While dotCover has had support for xUnit.net for many years, it has always required installing a separate extension. Starting with version 2016.1, it provides support for xUnit.net directly in the product. This means dotCover will discover your xUnit.net tests and allow you to run, debug, and analyze their coverage without requiring any extra extensions. You can also run Continuous Testing sessions containing xUnit.net based unit tests.

Improved TeamCity integration 2016.1

TeamCity can now understand the output of dotCover console runner and highlight its errors and warnings in the build log.

Continuous testing with dotCover

Continuous testing 10

dotCover has recently introduced continuous testing: a modern unit testing workflow whereby dotCover figures out on-the-fly which unit tests are affected by your latest code changes, and automatically re-runs the affected tests for you.

Based on your preferences, dotCover can detect and/or run affected tests on saving a file, on building your solution or soon as you explicitly tell dotCover to do so.

You can use continuous testing with all your unit tests, or specify exactly which tests you want to run continuously and which to run in a traditional way.

dotCover as part of ReSharper Ultimate

Support for latest ReSharper and Visual Studio 10

dotCover 10 and later continues to refine integration with Visual Studio 2015 while keeping compatibility with Visual Studio 2010, 2012 and 2013 intact as well.

As to ReSharper compatibility, recent versions of dotCover and ReSharper use a single ReSharper Ultimate installer, and share common binaries to keep Visual Studio memory footprint low. In addition, compatible ReSharper and dotCover releases are now always using the same version number to avoid ambiguity.

Excluding auto-properties 10

If you want to exclude auto-properties from coverage analysis, dotCover 2016.2 now provides the Hide auto-properties option to let you do just that.

Filtering processes from console runner 10

When you work with dotCover console runner, you can now exclude child processes that are irrelevant to coverage analysis. To enable a process filter, use the /ProcessFilters parameter.

Free 30-day trial