dotCover(英語版) の新機能

What's New in dotCover

What's new in dotCover 3.1?

  • Remote Code Coverage - Now you can run coverage analysis of unit tests on a remote machine and save resources on your local computer.
  • Custom Coverage Scope - dotCover provides you with ability to include uncovered solution assemblies into the coverage results.
  • Updated Coverage Controller - New controller provides you with two snapshot getting options: to record or not coverage results right after taking the snapshot.

What's new in dotCover 2.x

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

What’s new in dotCover V1.2?

  • Added support for latest ReSharper versions, enabling easy unit test coverage analysis

What’s new in dotCover V1.1.1?

  • Integration with ReSharper 6 - dotCover integrates with the latest version of ReSharper 6, allowing a smooth user experience. ReSharper 5.x continues to be supported also.
  • Per-snapshot Settings - Snapshot settings, including node exclusion and inclusion are now saved in a file alongside the snapshot (*.settings).
  • Improved presentation of class members - When you browse coverage results with dotCover 1.1.1, 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 1.1.1 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 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 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.