NCover

Hi Peter,



It would be great if you may provide some kind of a NCover roadmap on this website.



Some approx. dates when the next Beta would be expected and which
features might be realized would be excellent. Furthermore a known bug
list would be helpful to avoid peoble running into the same pitfals.



Ciao

ThomasD

Hey



You need to tell ncover which assemblies to profile.



For example ...



//a DllBeingProfiled

It's not necessary to specify the assemblies to profile.

However, you're using the command-line syntax from the 1.3.x versions.  For the version you have, you'll want drop the /c, and just run:

@NCover.Console <font>"C:\Program Files\NUnit-Net-2.0 2.2.5\bin\nunit-console.exe</font>" "<font>C:\DTA\CustomApps\BigDaddyDev\ZZZ.ClientServerTests\bin\Debug\ZZZ.ClientServerTests.dll</font>"

Montana,

Somehow I missed responding to this earlier - my apologies. I would hope you have this sorted by now!

If not (or if someone else is reading and wondering the answer is you need to customise ccnet.exe.config. Its not very intuitive to look there but thats the way it is. You will see a list of stylesheets that are applied to impact the appearance of the email. Add the NCoverExplorer one to the list and you should be fine.

The other thing to keep in mind is making sure your email publisher is AFTER the merge publisher in your ccnet.config file - obviously the coverage results have to be merged in before the transformations taking place in the email publisher will work...

I havent yet upgraded at work to the 1.3.6.15 build of NCoverExplorer.Extras (still using 1.3.6.14) but absolutely that build fails when unit tests fail. It is possible of course that I broke this in 1.3.6.15 but it would be fairly unlikely - the changes I made for that build were just for NCover registration.

I would suggest you turn on verbose logging and have a look at the nunit-console output etc - is it actually showing failed tests etc?

Did some more testing and I don't think this is directly an NCover/NCoverExplorer.Extras issue.

What version of NUnit do you use?

I tried with earlier versions of NCover/NCoverExplorer.Extras and still got the problem.  So then I tried reverting to earlier versions of NUnit.

With NUnit 2.2.9 my test task (via <ncover>) does seem to fail in the face of unit test failures.

However, with NUnit 2.4/2.4.1 it does not.

Unfortunately, I don't really want to revert to 2.2.9 because that causes other failures as I'm taking advantage of some other NUnit 2.4 stuff.

But I imagine you would be using 2.4, so maybe my problem is something else?

Thanks

Martin

Hi Martin,

I am using nunit 2.4 - although to be honest with the number of issues I have had with it I rather wish I wasn't always so keen to upgrade all our tool versions in this particular case. Not using any specific features as yet - the new test syntax option just doesn't grab me personally for a number of reasons. Performance with the nunit GUI is poor (not that I use it that often as using TD.Net), nunit 2.4.1 allegedly fixes a big problem we had with app domain unloaded exceptions, but we still get some unexplainable failures from time to time that make me pull my hair out where the return code from nunit is 1 (so the build fails) but there are no failed tests. Very frustrating - should have stuck with 2.2.9 which was working much more consistently.

As for your issue - the one problem I havent seen is test failures not being reported. The NCoverExplorer NAnt tasks are just very simple inherited versions of an exec task basically - the converting of return codes into a nant task failure etc is done by the NAnt base class, not my task code. I double checked 1.3.6.15 and it reported a failure as expected for me so that shouldnt be the cause. Without seeing your NAnt output personally I would be turning on verbose logging and monitoring exactly the output from nunit-console to see what it is saying as the culprit is more likely that than NAnt imho.

I've had this same problem for a while with NUnit, I had the problem with 2.3 betas and still have it with 2.4.1. I need 2.4 because I need to have seperate config files for each assembly where 2.2 doesn't allow this.

I'd really like to work out why it doesn't work too because my CI builds will pass if a unit test fails, which isn't nice. I might be doing something wrong, but nothing that I can see.

Just letting you know your not alone with this problem

Jono

Edit: I'm using the NAnt exec task

I just tried using NUnit without NCover and I can't even get my NAnt build to fail with NUnit 2.4. I made a failure test and I can see in the output that it failed. That is really strange because there are heaps of people using NUnit with NAnt, I would also assume the same problem happens with MSBuild.

Jono

It is now fixed with the NUnit 2.4.2 version

hi,

how to send NCover Coverage on my mail Using ccnat.config??

indradev

indradevpandey,

place these files:
NCoverExplorer.xsl
NCoverExplorer-Legacy.xsl
NCoverExplorerSummary.xsl
NCoverExplorerSummary-Legacy.xsl

in the server\xsl subdirectory of your cc.net install and add an email publisher to the "publishers" section of the CruiseControl config file. Instructions for that are here:
http://confluence.public.thoughtworks.org/display/CCNET/Configuring+the+Server

Stephen