Looks like the problem might be the engine settings; divide by 0 will throw an error in strict mode (lenient=false)
So if tests use a mix of modes, it's possible that the wrong mode will be left around. The JEXL engine is not immutable, and is shared between some tests, so this can easily happen. On 31 May 2013 16:36, Jörg Schaible <joerg.schai...@scalaris.com> wrote: > Gary Gregory wrote: > >> Yes, please see >> https://garygregory.wordpress.com/2013/01/23/understanding-junit-method-order-execution-updated-for-version-4-11/ > > ... and ... > > http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#runOrder > > Personally I use always random order in my tests. Otherwise you might not be > able to run individual fixtures r.g. in Eclipse or parallel execution is > also not possible. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
