Testing coverage across many UnitTest dlls ?

Testing coverage across many UnitTest dlls ?

We have 15 or so unit test dlls, and we would like to run them all and then see coverage numbers for the code, but we can only figure out how to get coverage numbers from each one. 

Suggestions, or is this impossible?

Thanks,

Ted


Re: Testing coverage across many UnitTest dlls ?

1. You can pass multiple test fixture dll's to NUnit in the command line.

2. Alternatively use a .nunit project

3. Alternatively run them all individually and merge the results using NCoverExplorer (either using the GUI or the command line version).


Re: 1.5.4 exclusion bug

What command-line parameters are you using?

Can you give me an example of the code structure you are using?


Re: 1.5.4 exclusion bug

I can send zip with code that reproduces this case.


Re: 1.5.4 exclusion bug

Great.  Send me a private email with the zip attached. 


Re: 1.5.4 exclusion bug

For everyone else's benefit.  This bug has been reproduced and fixed.  The fix will be included in the next release.  If you need it before then, email me and I'll send you a patch.


Re: 1.5.4 exclusion bug

How can I excluded code tat is generated by visual studio? I am talking about the partial designer classes. I think that when I add the ignore attribute, Vs will remove it, when it regenartes this class.

 

 


Re: 1.5.4 exclusion bug

Hi Peter,

can you please send me the patch???

Ciao
ThomasD


Re: Cannot get the analysis output

Do not put the extension on the assemblies used with /a


Re: Cannot get the analysis output

Thank you very much!!

That fixed my problem.

Regards,

goraperas


Re: NDoc2 NAnt Task - Issue with output directory

Hi Sam,

I'm pretty much at the whim of what NDoc does with the input - my NAnt task doesnt do anything but pass through that xml.

What I do in my scripts is set a fully qualified path in that OutputDirectory variable and that seems to work ok for me.


Re: Ignoring parts of a partial class

Absolutely it is possible to add attributes to methods in that class file so they will be excluded from coverage - the trick is whether the generation of that partial class is under your control or not to be able to add the attribute to those methods. By that I mean if you are using CodeSmith or some other code generator tool then clearly that is not a problem.

See question 9 in the FAQ, a copy of which is here:

http://www.kiwidude.com/dotnet/NCoverFAQ.html