Softpedia >Windows >Programming >Other Programming Files >dotCover >  Changelog

dotCover Changelog

What's new in dotCover 2023.2 Build 2023.2.0.65536

Aug 3, 2023
  • This release was dedicated to bug fixes and stability improvements.

New in dotCover 2023.1.1 Build 2023.1.1.65536 (Apr 30, 2023)

  • The Show Covering Tests context action in the coverage tree now works even if focus is lost (DCVR-11858).
  • The Coverage tree has excluded nodes notification now correctly appears when you choose Exclude from Coverage Results from the drop-down list of actions (DCVR-11570).

New in dotCover 2022.3.2 Build 2022.3.2.65536 (Jan 30, 2023)

  • Tracing, sampling, and line-by-line profiling modes work as expected even when there is a usage of a LibraryImport attribute in the system or user’s code (PROF-1321).

New in dotCover 2022.3 Build 2022.12.05.205404 (Dec 8, 2022)

  • You can use dotCover on ARM64 CPUs on Windows. This applies to all versions: dotCover standalone, dotCover in Rider, dotCover in Visual Studio, and the dotCover console runner.
  • Beginning with this release, restarting Unity is no longer required and test coverage in JetBrains Rider is supported out of the box.
  • You can now use the dotCover console runner on ARM32 CPUs on Linux.
  • We’ve added the Show Covering Tests action to the dotCover context menus in both the Rider code editor and the Unit Test Coverage window.
  • Now dotCover copies only the assemblies and symbol files required for continuous testing in both Visual Studio and JetBrains Rider.

New in dotCover 2022.2 Build 2022.2.0.65536 (Aug 4, 2022)

  • This release has improved the dotCover plugin in Rider. You can now quickly view coverage results for the file you have open by using the shield icon. Clicking on the icon navigates you through the uncovered statements.

New in dotCover 2021.3 Build 2021.3.0.65536 (Apr 19, 2022)

  • The dotCover command-line runner now supports Alpine versions 3.13–3.15.
  • You can now use comments to exclude certain lines or blocks of code from coverage analysis.
  • We’re adding new report types that include per-test coverage information.
  • We’ve improved the post-processing of coverage data.

New in dotCover 2021.3 (Dec 9, 2021)

  • The dotCover command-line runner now works on computers with Apple silicon processors. It can provide coverage analysis for .NET 6 applications (native mode) and .NET 5 applications (Rosetta 2 mode).
  • A new Code Vision metric has been added to dotCover in Rider. For each type member included in a set of tests, dotCover shows the number of successful and failed tests.
  • The dotCover .NET global tool now includes the merge and report commands.
  • Coverage analysis in the dotCover Command Line Tool is faster.

New in dotCover 2021.2 (Aug 3, 2021)

  • Coverage information for individual tests in the console runner:
  • The dotCover console runner is able to collect coverage information for individual tests and show it in the generated reports. Currently, only the following test runners are supported: dotnet test, dotnet vstest, vstest.console.exe. For example: dotCover.exe dotnet --output=AppCoverageReport.xml --reportType=XML --IncludePerTestInfo=Method -- test "C:MyProjectMainTests.csproj"
  • Improved coverage performance:
  • Now, dotCover can run coverage analysis of test classes in parallel within one assembly. In certain scenarios this can result in faster coverage analysis.
  • Unit test runners can now be preloaded for .NET Core and .NET projects (this allows coverage analysis to start quicker, as the unit test runners are already loaded in memory).
  • Updates to C# 8 and C# 9 support:
  • We’ve improved support for C# 8.0 and C# 9.0 in the coverage tree (showing default interface implementations, and more).
  • Now, dotCover will offer to restart Unity Editor when coverage filters are changed.

New in dotCover 2020.3 (Dec 14, 2020)

  • dotCover now lets you perform coverage analysis of applications targeting .NET 5.
  • You can now specify which projects should be built when a continuous testing session is triggered, which helps speed up continuous testing sessions.
  • The Unit Tests Coverage window in Visual Studio lets you filter coverage results by target framework.

New in dotCover 2019.1 (Apr 30, 2019)

  • Support for .NET Core on macOS and Linux:
  • 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 code coverage analysis on these operating systems, you must use JetBrains Rider.

New in dotCover 2018.2 (Aug 22, 2018)

  • JetBrains Rider integration:
  • 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.
  • 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
  • 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.

New in dotCover 2018.1 (Jul 27, 2018)

  • 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.
  • 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
  • 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..

New in dotCover 2018.1 (Jul 27, 2018)

  • Redesigned two of its vital features: continuous testing mode can be turned on for any unit test session instead of running a separate continuous testing session, and coverage information is now shown in a separate Unit Test Coverage window, instead of a per-session Coverage tab. dotCover console runner gets the ability to cover arbitrary managed processes and services and send the get coverage snapshot command to the running instance of the console tool. And last but not least, coverage analysis performance has been improved.

New in dotCover 2.7.0.662 (Mar 21, 2014)

  • dotCover 2.7 additionally introduces standalone test runner which can be most useful for running manual tests outside Visual Studio, as well as for analyzing coverage snapshots.

New in dotCover 2.5.574.60 (Sep 6, 2013)

  • dotCover now integrates with ReSharper 8. If you're using ReSharper's unit test runner, you should upgrade to dotCover 2.5 to be able to analyze unit test coverage.
  • This version introduces the Hot Spots view that helps identify the most risky methods in your solution, in terms of high cyclomatic complexity and low unit test coverage.
  • As a result of major internal improvements dotCover’s memory consumption has been significantly decreased.
  • dotCover 2.5 lets you merge coverage snapshots even if different filters are applied to them.

New in dotCover 2.2.515.8 (Dec 3, 2012)

  • Integration with the recently released ReSharper 7.1
  • Support for Windows Store Application Tests. Please note that with this version of dotCover you'll be able to get overall coverage statistics, without percentages per single test.

New in dotCover 2.0.425.12 (Jun 19, 2012)

  • A bundled unit test runner as an alternative to integration with JetBrains ReSharper's unit testing tools.
  • Statement-level code coverage analysis in .NET Framework and Silverlight applications.
  • Filtering out specific classes or assemblies from coverage analysis, as well as code marked with specific attributes.
  • Integration with Visual Studio 2012 Release Candidate, in addition to Visual Studio 2005, 2008, and 2010.
  • Support for multiple unit testing frameworks: MSTest, NUnit, xUnit, and MSpec.
  • Highlighting for covered and uncovered code.
  • Console utility to run code coverage analysis as part of Continuous Integration process. JetBrains TeamCity provides dotCover-based code coverage analysis out of the box.
  • Aggregating data from multiple coverage sessions, merging snapshots, and exporting coverage results to XML, HTML and JSON.

New in dotCover 2.0.418.9 Beta (Jun 9, 2012)

  • Integrated unit test runner:
  • dotCover has traditionally relied on ReSharper's unit test runner to analyze coverage of unit tests based on MSTest, NUnit, xUnit, or MSpec.
  • dotCover 2.0 breaks this dependency: from now on, even if you don't have ReSharper installed, you can still use dotCover to manage, run and analyze coverage of unit tests. In case you have both products installed, you can choose which unit test runner you want to use.
  • Locate in coverage tree:
  • dotCover 2.0 introduces a shortcut that takes you from a caret position in Visual Studio text editor to the matching node in dotCover's coverage tree.
  • Attribute filters:
  • In addition to applying traditional coverage filters based on method, type or assembly, dotCover 2.0 allows filtering out code marked with specific attributes. More than that, a single dialog is now used for managing coverage and attribute filters.
  • Filters are useful when you need to focus on production code, or exclude code that you're not interested in testing right now. As soon as you've done this, dotCover will recalculate percentages of covered and uncovered code.
  • Support for Visual Studio 2012 RC:
  • dotCover 2.0 is quick to support Visual Studio 2012 RC. Support for the RTM version of the new Microsoft IDE is expected as soon as it is available.
  • Previous versions of Visual Studio, including 2005, 2008, 2010, are also supported.

New in dotCover 1.2.384.4 (Jun 9, 2012)

  • Integration with ReSharper 6:
  • We are continuing to add support for latest ReSharper versions, enabling easy unit test coverage analysis. Specifically, dotCover 1.2 adds support for ReSharper 6.1.
  • Per-snapshot settings:
  • Node exclusion, inclusion, and other snapshot settings are now saved in a file alongside the snapshot (*.settings).
  • Improved presentation of class members:
  • When you browse coverage results, you can clearly see properties with getters and setters, as well as events with add and remove accessors. Anonymous delegates and lambdas are represented by nodes within containing methods denoting types that they receive and return.
  • HTML and JSON reports:
  • In addition to XML export available previously, dotCover now allows you to generate reports as HTML and JSON both from the console runner and from Visual Studio coverage UI.
  • Integration with NDepend:
  • dotCover 1.1.1 and above provides support for NDepend in the form of exporting coverage reports to XML for NDepend.
  • Predefined color schemes:
  • Some like it dark, some like it bright, so we figured, why not provide several color highlighting schemes by default? That said, you can still fine-tune coverage highlighting colors by tweaking dotCover display items via Tools | Options | Environment | Fonts and Colors.
  • Support for dynamic NUnit tests:
  • Full support for dynamic NUnit Test cases as well as Combinatorial, Sequential and other common NUnit attributes.
  • Filtering coverage tree on-the-fly:
  • You can now exclude a specific node, or all nodes except this node, from the coverage tree and have dotCover instantly recalculate percentages of covered and uncovered code.
  • Getting coverage analysis data from TeamCity:
  • You can now use TeamCity Visual Studio plug-in to connect to a TeamCity server and obtain data from a Continuous Integration coverage analysis run.
  • Incremental update of coverage info when tests are partially rerun:
  • Coverage information is calculated incrementally without requiring full profiling on new runs, making the whole process much faster.
  • Per-solution coverage settings:
  • Starting from dotCover 1.1.1, coverage filters are stored per-solution in projectName.dotCover files. In case you're covering a compiled application, i.e. you're not working with a solution per se, global settings are used.
  • On-demand license checking:
  • Previous dotCover versions executed their license checking routine right upon installing the product. In contrast, dotCover 1.1.1 and later versions don't check your license until you actually start using the product. A similar change has been implemented in dotTrace 4.5 Performance.