> number generators. Where a test depends on a particular sequence, and > somewhere an RNG doesn't use the "RandomUtils" trick, it may have a > different state if other tests ran before.
I have a different solution for this in randomizedtesting framework (a Random instance cannot be shared from test to test, it will throw an exception if you do share it). This doesn't solve all the possible problems but proved quite effective at catching test dependencies. > The surefire parameter just controls what order the *classes* run in AFAICT: > http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#runOrder Yeah, I was on the train when I wrote that e-mail. The trick I remembered is in fact inside JUnit 4.11 and onwards -- https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#test-execution-order D.
