I would more readily expect that the dependency is due to the random 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.
The surefire parameter just controls what order the *classes* run in AFAICT: http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#runOrder On Sat, Jun 8, 2013 at 7:40 AM, Dawid Weiss <[email protected]> wrote: > In fact the core of it is that people assume method order will be that of > declaration within the class and this is not guaranteed anywhere. Java7 > returns methods from reflection api in an undefined order and this > propagates to junit. I believe surefire can be configured to use a junit > runner that guarantees sorted method order. This said it is usually a bug > to have method interdependencies. > > Dawid >>
