2009/4/1 Peter Niederwieser <[email protected]> > > > Tom Eyckmans wrote: > > > >> - I would expect that I could use multiple test frameworks (e.g. JUnit > >> and > >> TestNG), and Gradle would still run all of my tests. Will this be > >> supported? > > This will be possible but not with autodetection, you'd have to create 2 > > test tasks and specify which test framework should be used and mention > > junit > > in the first and testng in the second. Using one task would cause > problems > > with the different test framework options that available for > junit/testng. > > (This at the moment a problem with the autodetection, I have to look at > > because the test framework is not known yet at build evaluation, mh > tricky > > -> no testframework detection only test class finding?) > > > Just to make it clear, my motivation for adding automatic test detection to > Spock was to make it unnecessary to follow (and configure) a naming > convention for test classes.
This is exactly what we want to do. > This kind of detection should work equally well > for multiple test frameworks. We want to support this for both JUnit and TestNG at the moment. > Maybe you are doing something different? As Adam commented, when we would also select the test framework based on the detection it is possible that depending on which classes get processed first a different test framework could be selected. So this may cause problems regarding reproducability of the build and that is something that is not acceptable. > > I'm using the test detection both in Spock's Maven build (via Spock's Maven > plugin) and in its Gradle (0.4) build. The Gradle build script is here: > > http://code.google.com/p/spock/source/browse/trunk/spock-specks/build.gradle > > > > Tom Eyckmans wrote: > > > >> I chose the same ASM version that Groovy uses, even though it's not the > >> latest one. > > interesting, keeping the amount of dependencies low is indeed important. > > > The limitation is that if people are using groovy-all.jar, ASM will be > downloaded anyway. Nevertheless I thought it was the safest bet to go with > the same version that Groovy uses. I think that is the best way of doing things. > > > Cheers, > Peter > > -- > View this message in context: > http://www.nabble.com/Native-test-framework-integration-tp22815266p22834743.html > Sent from the gradle-dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
