Hi, thanks for posting.

Is it possible that these tests have inconsistent execution times, depending upon their execution sequence?

If the tests take a longer time to execute than the engine expects (for example, they may depend on some static state to be initialised at the start of their run), this could cause them to be lumped together as the engine thinks they are fast executing when they're actually not.

The easiest way to check this is to look at the test tasks inside your Processing Queue. Make sure you have both the 'Expected Processing Time' and 'Actual Processing Time' columns turned on. If these differ significantly from each other, you're likely to see poor optimisation of your test pipeline like this.

I note by the test names that these are all using selenium. Do they have a shared dependency on the UI, or anything in the system that might cause them to run through a bottleneck?

You could try marking the test fixtures with NCrunch.Framework.IsolatedAttribute if you want to force them into their own group and their own process.

I've just checked through the reports we give from the console tool and confirmed that we don't provide the expected processing time for the tasks, unfortunately.
However, the behaviour for your pipeline should be very similar when using the VS client. I would recommend checking the results from a normal run through in your VS client to see if there is an issue.



It's possible to apply this attribute at assembly level. When you do this, all fixtures in the test project are marked as isolated and the engine will always separate them into their own tasks.