ReportGenerator - New release with risk hotspots analysis
ReportGenerator 3.1 has just been released. The new version ships with a new risk hotspot analysis and several other improvements.
Daniel Palme
Softwareentwickler aus Augsburg/München
.NET / Web / Azure
ReportGenerator 3.1 has just been released. The new version ships with a new risk hotspot analysis and several other improvements.
ReportGenerator 2.5 has just been released. This latest version has some enhancements in the HTML report and and some other improvements.
ReportGenerator 2.1 has just been published as a beta release. This blog post will explain the new feature trend/history charts and some other improvements.
ReportGenerator 2.0 has just been released. The new version contains some new features and improvements. This blog post will give a brief overview of the most important changes.
Since my last blog post about ReportGenerator a couple of features have been added. In this post I will describe the most important changes.
Some time ago somebody on Stackoverflow asked how to integrate OpenCover results into CruiseControl .NET. After being asked again, I decided to write a tutorial to show how CC.NET has to be configured.
I created a demo project that uses NUnit, OpenCover and ReportGenerator to generate HTML coverage reports that are integrated into CC.NET.
ReportGenerator 1.3.0.0 has just been published. The new release offers some new features which I want do describe in this post.
Just some days ago, a new code coverage tool was released for the first time. It's called OpenCover. Shaun Wilde created this tool, since PartCover 4 has some issues that are difficult to resolve with the current code base. He describes some of them on his blog.
In this post I will do a comparison between OpenCover and PartCover and show how these tools can be used to get the coverage of unit tests.
A few weeks ago I blogged about a problem concerning coverage of unexecuted code in PartCover. The problem was that the report generated by PartCover does not contain any coverage information about uncovered methods. That implicated, that my tool ReportGenerator calculated a wrong coverage quota, since the lines of unexecuted method were considered to be 'not visitable'.
I claimed that it would not be easy to create a workaround for the problem, but actually it isn't that difficult, if you use the right tools.
During the last weeks I received several emails pointing me to a potential issue in my tool ReportGenerator. The problem is that methods that have not been executed during a test run using PartCover, are marked as 'not visitable'.
I decided to take a closer look at the problem. In this post I will explain how ReportGenerator works and why it is not easy to create a workaround for the deficiency of PartCover.
IoC Container Benchmark - Performance comparison
ASP.NET MVC 4 - Blog engine based on Twitter Bootstrap
Reflection vs. compiled expressions vs. delegates - Performance comparison
ASP.NET MVC - Generic filtering based on expressions
ASP.NET MVC - Authentication (Two-Factor, MembershipProvider, SimpleMembership)