Marco Hunsicker wrote: > > I have a class IntegrationTest.java with two test methods test01(), > test02(), both tagged with the JUnit @Test annotation. Running either > method directly, i.e. only one test at a time, works fine. But when I > try to run all tests, the second test fails with spurious ClassLoader > errors (again). >
Never heard about such a problem before. Did you submit an issue? Can you provide a self-contained example that demonstrates the problem? Marco Hunsicker wrote: > > When looking for ways to overcome this problem, I've found the "forkEvery" > property. [...] > I guess the granularity of that property only applies to classes, not > methods? > Yes. Marco Hunsicker wrote: > > The final workaround was to move each method into its own class > Are you sure there isn't something wrong with your test? What platform? Can you show the code and the stack trace? -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Running-JUnit-tests-in-isolation-tp4386838p4387340.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
