I have a set of tests where each test usually takes 5-20 seconds to run. They normally run in parallel and everything is fine.
However, occasionally I'll code a bug so they immediately fail, spend some time fixing it, then when the issue is fixed, ncrunch has decided these tests always finish immediately, so it runs them as one job.
Normal behaviour
https://github.com/danze...ur/blob/master/good.png
bad behaviour (after a bunch of quick fails)
https://github.com/danze...our/blob/master/bad.png
repo for reproducing
https://github.com/danzel/ncrunchbadbehaviour
Open it, run the tests to confirm the good behaviour.
Uncomment the exception so they fail immediately.
edit the Console.WriteLine text a few times so ncrunch thinks these tests are quick.
Comment out the exception.
Test will now run all in one job.
Any advice on avoiding this?
I think I could maybe catch a quick failure when running under ncrunch and sleep for a few seconds so they never finish quick, not an ideal hack though :)
Thanks!