9

Resolved

Test runner - add a node for each Theory data item

description

I first felt over this while using the R# runner. So I've tried the Gui runner and noticed that he also dose not add an item for each specific data item in a theory test. With this node it would be possible to debug in specific date item.

Without that feature it is really hard to see which data item fails and its much harder to to debug the failed item.

comments

LOBOMINATOR wrote Apr 26, 2012 at 5:28 AM

That's a vote from me! I really like xunit but this is one major advantage of nunit over xunit regarding R# integration.

justinc wrote May 1, 2012 at 9:10 PM

I like it the way it is. If any item fails the whole test shows as a failure, if you look in the log for that test it tells you exactly which data item failed. Seems perfect to me.

lanwin wrote May 2, 2012 at 9:11 AM

@justinc: And how do you debug exactly this specific data item if you have 500 of them?

justinc wrote May 2, 2012 at 12:59 PM

Well that's a good point but you could probably add a breakpoint + condition to get to the one you wanted. Do you really want 500 nodes in your UI though?

lanwin wrote May 2, 2012 at 2:02 PM

That is problematic when the test run raises an exception, so it will break on all 500. And not in all cases you can set a condition.

Why not. I heard there are projects with 2000 unit tests out there. But that debugging point also was annoying for me with having 30 tests.

NicolasRaoul wrote Nov 15, 2012 at 3:04 AM

In Extreme Programming we write tests before writing code.
Unfortunately a unit test stays red until ALL Theory data items are perfectly implemented.
That makes it impossible to judge progress at a glance, which is the least you can ask from a unit testing framework.
A tree in the xunit.net Test Runner would be great.

BradWilson wrote May 5, 2013 at 1:09 AM

This is fixed in v2 runner for VS2012.

There are no plans for a GUI runner for v2.