For the longest time, I've been using NCover for coverage. It was free, gave good results and with NCoverExplorer and CI integration it was the perfect tool. Easy to use, easy to setup, and worth the typical hassle of new tools (setup, learning, configuration, etc.)
NCover has since gone commercial and the old versions won't run properly against 3.0/3.5 code. I'm ditching NCover support in TreeSurgeon because of this. TS nees to be friction free and something anyone can just grab and run and not have to deal with buying or obtaining licenses for products the generated code depends on. I looked at Clover.NET as an alternative (last time I checked it was free?) but it's $600 just for an "academic" version.
So what's with coverage and .NET these days? Are these the only options? Have all the open source/free tools gone the way of the Dodo for coverage and .NET 3.0 projects? My quick Google checks this freezing morning (it was minus 38 as I drove in this morning, that's -36 in Fahrenheit kids) don't show anything.
To be friction-free a code coverage tool needs to be:
- Command line driven (have to be able to integrate into continuous integration process)
- Xml report output (again, CI ready)
- Usable with any unit testing framework
- Support 3.0/3.5 .NET framework
- Somewhat stable (i.e. non-alpha/beta versions)
Nice to haves:
- Free (or relatively cheap)
- HTML or Text output
- Ability to set thresholds and get failures back (for example, break the build if the coverage falls below 80%)
Looking for some feedback on your experience here. Thanks!