Howdy, I'm still running into problems with my integration testing.
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).
When looking for ways to overcome this problem, I've found the "forkEvery" property. I was hoping that setting it to '1' should workaround the issue. But it does not make a difference. I guess the granularity of that property only applies to classes, not methods? To put it another way, as far as Gradle is concerned a test is a unit that might contain several test methods?
The final workaround was to move each method into its own class, but I would prefer to be not restricted in the way I structure my test cases. Thanks.
Cheers, Marco --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
