On Tue, Jun 28, 2011 at 7:28 PM, Thomas Tuegel
I've been working on this new interface and a test runner for it, and I've made a discovery about this property of "exclusivity" (alternately, "concurrent safety") that I think I should share.
Exclusivity is not a property of individual tests, but of test groups. If you think carefully about the (admittedly pathological) case of a test suite with only one test case, you see that it doesn't matter whether it is marked as exclusive or not: it will be run both concurrently and sequentially with all the other tests. Exclusivity only exists when there is more than one test.
I don't think this is necessarily the case. If you put concurrentSafe on a test you'd then partition tests like so (safe, unsafe) = partition isConcurrentSafe tests and then run all of the safe tests (possibly in parallel) and then all the unsafe tests one by one. Johan