What's New in dotCover 1.1

Read below or watch this screencast to learn what's new in dotCover 1.1.

Improved presentation of class members

When you browse coverage results with dotCover 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 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 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.


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, 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, the new dotCover 1.1 doesn't proceed to checking your license until you actually start using the product. A similar change has been implemented in dotTrace 4.5 Performance.