Question

I am using VS2010 + C# + .Net 4.0. I want to do code coverage for unit tests. I have two choices after investigating, my question is, I want to know the pros and cons of such two tools/choices.

1. Using non-VS built-in tools, like ncover;
2. Using VSTS built-in tool, for example,

http://msdn.microsoft.com/en-us/library/dd299398%28VS.90%29.aspx

http://msdn.microsoft.com/en-us/library/ms379625%28VS.80%29.aspx#vstsunittesting_topic7

Answer 1

Having used both tools, they both work pretty much the same way. You run your tests and then you view the report. Both tools provide code highlighting to show, which lines of code have coverage and which ones do not. MsTest does not provide much more in terms of information, but NCover provides lots of HTML reports and can trend code coverage over time. These sorts of things can be helpful.

Now for the differences. The MsTest coverage tools really only work with MsTest unit tests. It cannot easily cover tests written using NUnit (or other testing frameworks) from the IDE. It can be done, but takes some time and requires invoking the coverage tools from the command line and instrumenting your assemblies manually. Again, it can be done, but not very easily, especially for a beginner. NCover is more flexile and can be run with most testing frameworks. Also, I have found that it is easier to run NCover with an automated build server. I never had much luck automating MsTest coverage in CruiseControl, but I am guessing MS makes it work in Team Foundation Server.