Hi Albert,

Unfortunately, for NCrunch to meaningfully discover and report these steps is currently impossible.

NCrunch separates its test discovery and execution into two distinct steps. A test can only be created during test discovery, and can only be executed during its execution step. This is quite different to a number of other runners where the discovery of tests and their execution can often be mashed together. NCrunch relies on this different to support many of its features, particularly the dynamically controlled pipeline of tests.

Under xbehave, the steps inside the tests are non-deterministic. They cannot be identified during the discovery of the test and are only reported by the framework when the test is actually executed. This is a big problem for NCrunch, which cannot create new tests during their execution.

There is also the problem of the steps requiring a new dimension in the Project-Fixture-Test structure, which is not so simple to extend in NCrunch.

To deal with this, NCrunch groups the steps into their parent tests and provides an aggregate report.

As in .. breaking up the Tests Window output pane to section the results for each step?

I think at the moment the Tests Window output does introduce text markers separating the output between each step, though this certainly isn't very fancy.

Sorry, it looks like this isn't working the way it's expected to.

I'll see what I can do about adding some separation between the steps in the trace output.