Something is going seriously wrong in the test process when it tries to execute your tests.

If you can send through a bug report after you've had this happen, I should be able to advise further. If there's an error, this should show up in the logs. If you set your 'Log Verbosity' setting to 'Detailed', there should be more detailed information available about the run inside the test tasks in the Processing Queue Window.

Thanks for the report.

Something is going seriously haywire in the way that NUnit is reporting results here. Everything is being reported very badly out of sequence.

Are you using any NUnit plugins? Do you have any specially coded settings that might cause NUnit to try to implement concurrent or parallel execution?

You'll need to disable this attribute when working under NCrunch. For example:

#if !NCRUNCH
[assembly: Parallelizable(ParallelScope.Children)]
#endif

Tracking code coverage data is impossible when tests are being run concurrently in the same process, because there is no way to differentiate one test run from another. Code coverage tracking is heavily reliant on global state (think multi-threaded tests), so when you have multi-threaded state being updated by different tests at the same time, there's no way to know which test is actually responsible for touching the code.

Because NCrunch parallelises things at a much higher level, it's fairly useless to do this in-process anyway. For these reasons, NUnit parallelization cannot work with NCrunch and never will.

I've made a note to add an error when this attribute is detected under NCrunch, so that these problems are bit less cryptic.