dotCover 2019.1 Help

What's New in dotCover

dotCover 2019.1

  • Support for .NET Core unit tests on macOS and Linux. To perform code coverage analysis on these operating systems, you must use JetBrains Rider.

  • Remote coverage from Visual Studio is no longer available. The feature is removed from dotCover.

dotCover 2018.3

  • Improved coverage filters. Now, there are two groups of filters in the dotCover options: runtime filters (the ones that are applied during a coverage session) and results filters (the ones that are applied to coverage results). The latter are extended with a filter by file name.

  • Support for multiple target frameworks . 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.

dotCover 2018.2

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

  • Support for the dotnet console tool. 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

  • Now, when using the dotCover.exe console runner, you should always prefer the cover command over the analyze command. The coverage result depends 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.

dotCover 2018.1

dotCover 2017.3

  • .NET Core tests coverage support in the continuous testing mode for NUnit and xUnit.

  • Quick evaluation of coverage results.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. Clicking on the icon navigates you through the uncovered statements.

  • Improved ‘Show Covering Statements’. Now, after you use Show Covering Tests in the editor, the popup window tells you what exact part of your code is covered by these tests: a class, a method, or a particular statement.

dotCover 2017.2

  • .NET Core tests coverage support for MSTest.

  • Improved performance. Before 2017.2, working with continuous testing on large solutions was a real headache: while tests were executed really fast, it could take several minutes until the subsequent coverage session was finished. The problem no longer exists in dotCover 2017.2: due to the new snapshot format, dotCover provides much faster processing of coverage results.

  • Coverage results are now shown not only for specific tests, but also for test groups, projects, categories, etc.

  • Color-blind markers. Now, markers are able to indicate coverage and test results not only with color but also with their shape.

  • Add coverage data from snapshots. Now, when viewing coverage results of a particular unit test session,you can merge them with coverage data from a snapshot.

dotCover 2017.1

  • Highlighting using colored background. 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.

dotCover 2016.3

dotCover 2016.2

  • Execution log in the Unit Test Sessions window and in the Continuous Testing Session window.

  • Ability to exclude auto-properties from coverage analysis with Hide auto-properties option.

  • Ability to filter processes from console runner to reduce unnecessary overhead by excluding child processes that are irrelevant to the coverage analysis.

dotCover 2016.1

Last modified: 1 August 2019