How do I get NUnit xml output?

Hi,

We're running TeamCity v7.1.

I have an NUnit build step that runs my tests, I'd like to get the output xml to feed into another step, but I can't find it and I can't see anyway to specify an output path.

Thanks

Ceri

4 comments
Comment actions Permalink

I think I have to conclude that this just isn't possible which is really annoying.

I'd like to get the XML so that I can display it in my own way. We are writing acceptance tests designed to be viewed by non-devs. The team city test display just isn't clear enough.

I've ended up using the nunit console runner instead of the built in NUnit build step.

0
Comment actions Permalink

Ceri,


> The team city test display just isn't clear enough.

Could you pelase elaborate more on this?


> I've ended up using the nunit console runner instead of the built in NUnit build step.


Yes, if you want to get cutom data you would need to run NUnit from your build script with all your settings. Still, reporting the results to TeamCity is recommended as othervise you will lose many test-related features of TeamCity. See available options for the integration.

0
Comment actions Permalink

> > The team city test display just isn't clear enough.

> Could you pelase elaborate more on this?



The display isn't clear enough for non-developers. Product Owners struggle to work out what is being tested. Descriptive test names were too long and wrapped on the screen. We tried using namespaces to create a tree instead - this works very well in the NUnit/Resharper test runners where you get a nice tree display, but teamcity's display is just a flat list.

> > I've ended up using the nunit console runner instead of the built in NUnit build step.


> Yes, if you want to get cutom data you would need to run NUnit from your build script with all your settings. Still, reporting the results to TeamCity is recommended as othervise you will lose many test-related features of TeamCity.
> See available options for the integration.



We have kept the team city display - we just need something more for product owners. However I'm not allowed to install NUnit on our build agents so this means I have to check in the NUnit binaries (yuk).

What I would really like is for team city to run my NUnit tests and expose the generated xml as an artifact I can use in a later build step.
0
Comment actions Permalink

Ceri,

Thank you for the detals.

TeamCity indeed does not support grouping by namespaces, we group by assemblies instead (and also by test clasees).
Related feature request in our tracker is http://youtrack.jetbrains.com/issue/TW-4609

0

Please sign in to leave a comment.