Clover.NET is a Visual Studio extension from Cenqua that provides code coverage information.
I tried this product about a year ago and I was happy with the results. This is interesting to see if your code is being fully executed during your Unit Tests. It made me appreciate much more the art of testing a product.
The reality about code coverage is that you can never hit 100% of the code, but anything above 85% is pretty good already. This is one of those 80/20 rules. Which means to get the last 20% of code coverage you will need 4X more work than to hit the first 80% of the code.
Clover.NET is the only product that I ever used to do code coverage, so I can't really compare it to my previous experiences, but my thoughts are:
Integration w/ VS 2005: Pretty well done. The code is highlighted inline!
Installation: Bad. You need to *read* the instructions before installing, copy files, argh...
Reports: Pretty decent, easy to read and export.
Build/Run: If you have a simple project this will be easy. On the case of Sampa, were we had Post-build batch, there was a lot of things that I had to do for Clover.NET to work.
Missing: Why they don't have a profiler I don't understand. They already instrument every single line of code, why not collect that stats?
If you know another good Code Coverage tool, please, let me know. I'm also looking for a good C# profiler.
Subscribe to this Site
is a Visual Studio extension from 
Comments for "Code Coverage for Visual Stu...
October, 2007