What′s New in dotCover

This page guides you through updates in dotCover versions 10, 2016.1 and 2016.2. Highlights include out-of-the-box xUnit support, improved TeamCity integration, Continuous Testing for a lot faster unit test feedback, support for latest versions of ReSharper as well as for Visual Studio 2015.

Free 30-day trial
dotCover supports xUnit.net out of the box

Out-of-the-box xUnit support

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

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

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

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

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

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