Automatically select first broken test in NCrunch Tests Window

usually when I'm TDDing, I will create a failing test and then make it pass. It'd be uberhelpful if the NCrunch Tests window would select the first failing test so the details of the failure are shown as soon as it fails. Or at least make it an option.

If it's already there, I'm too thick to find it, and if someone could enlighten me, that'd be wonderful.

Dankedanke.

Hi, thanks for posting!

This feature has been requested a few times and is pending in the backlog for the next release (1.41b). If all goes well, you should see it soon :)


Cheers,

Remco

I didn't see it in the forums. Sorry for the duplicate request.

And thanks... NCrunch has made life geometrically easier.

For anyone interested, 1.41b has just been released including the above feature.

Maybe I'm blind, but I can't find the option to enable this. I see you added the "select most relevant node, but it doesn't seem to be working with mine. I've included a short video to demonstrate: http://screencast.com/t/Z18R2qE1m7

Thanks so much for any help.

Hi, thanks for posting!

The auto node selection happens when no existing nodes are selected in the list, and the list is then updated by NCrunch. The main use case would be if you had an empty list of tests/projects, then made a change that caused one of them to fail and appear in the list. You'll probably never see this if you have the 'Show passing tests' option turned on, as you'll end up always having something selected.

It would be great if you could share some more details about whether you see a more intuitive way to handle this. It's a new feature, so I'll accept that it may need some fine tuning.


Cheers,

Remco

Ahh.. gotcha. I turned off the passing tests and it worked as expected. Thanks...

I do actually have a suggestion for "choosing" which broken test to display. If there are two failing tests, would it be possible to display the one that is in the current context (i.e. the one that I'm editing). Or maybe the one that was most recently changed? Lots of times, I'll make a change and tons of stuff will blow up, then I'll start working on either the test or the production code until it works, but it's the last test I modified that is the one I'm interested in.

This makes good sense. It's a bit trickier to do (as it involves a bit more bouncing around with the VS integration), but I can see the benefit. Thanks for the suggestion.