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 2017 and .NET Core.

Free 30-day trial
Support for .NET Core MSTest unit tests

Support for NUnit and xUnit in .NET Core 2017.3

Now, NUnit and xUnit unit tests targeting .NET Core are fully supported in the continuous testing mode.

Quick evaluation of coverage results

Quick evaluation of coverage results 2017.3

The "shield" icon in the right gutter of the Visual Studio editor allows you to quickly view total coverage percentage and the number of failed tests for code in the currently opened file. Clicking on the icon navigates you through the uncovered statements.

Improved 'Show Covering Tests'

Improved 'Show Covering Tests' 2017.3

Before 2017.3, after you used Show Covering Tests (Ctrl+Alt+K T) in the editor, the popup window showed you a list of covering tests but contained no info about what exact part of your code is covered by these tests: a class, a method, or a particular statement. Now, the popup tells this explicitly and even highlights covered statements in the editor.

Support for .NET Core MSTest unit tests

Support for .NET Core MSTest unit tests 2017.2

dotCover 2017.2 provides full coverage support for MSTest unit tests in projects targeting .NET Core, including:

  • Coverage and highlighting of test results,
  • Merging coverage data,
  • Showing tests that cover a particular location in code.
Code coverage improvements

Code coverage improvements 2017.2

dotCover 2017.2 introduces multiple improvements in terms of code coverage:

  • Improved performance. Before 2017.2, working with continuous testing on large solutions was a real pain: while test execution was fast, subsequent coverage analysis could take up to several minutes. The problem is addressed in dotCover 2017.2: due to a new snapshot format, dotCover can now process coverage results much faster.
  • Coverage results are now shown not only for specific tests, but also for test groups, projects, categories, etc.
  • When viewing coverage results of a particular unit test session, you can now merge them with coverage data from a snapshot.
Color-blind markers

Shaped markers (color-blind mode) 2017.2

dotCover's highlighting markers can now indicate coverage and test results not only with color but also with their shape.

Support for Visual Studio 2017

Visual Studio 2017 support 2017.1

dotCover 2017.1, along with other products of the ReSharper Ultimate family, can now be installed into Visual Studio 2017.

Colored background highlighting

Highlighting using colored background 2017.1

Old-style highlighting is back again and it's better than before!

Since the new highlighting style (using markers) may not be a good fit for all use cases, we've added an option to switch between markers and colored background or to display both. The old highlighting style also supports the updated logic and displays both tests coverage and test results.

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.

Free 30-day trial