Hi, this looks normal, although I agree it isn't intuitive. I'll explain what's happening here.

NCrunch breaks your tests up into batches that are each represented in the processing queue. You'll find that the batches are carefully sized so that longer running tests set to sit in small batches, with faster tests being grouped together. ExclusivelyUsesAttribute also has a role in how the tests are batched, as tests that use this attribute cannot be grouped with other tests that don't make use of it (or use a different resource).

When NCrunch runs your tests, it calls into the test runner once for each batch, executing all tests within the batch then returning the results. NCrunch does not display results for batches that are mid-way through execution. This is done for performance reasons as it is much harder to produce an engine that can interpret all results in real-time without slowing down the overall execution or consuming extra CPU.

In the case of your scenario above, these tests are all in the same batch and are being run in sequence inside the same test runner process. NCrunch has marked them all as 'executing' through the status of their batch, even though it's only possible for one test to be executing within the batch at any one time. As soon as the entire batch has finished, they will be marked as succeeded/failed at the same time.