Luke Daley wrote: > > I'd consider moving this optional tests out into another module. >
Alternatively you could add a separate test task that runs the optional tests and doesn't get executed as part of the regular build. tog wrote: > > It is not really tests that are not critical it is rather that we have > a function that is being implemented 2 ways (for example one > implemented on CPU the other in GPU) - the whole software can work if > one only is available > "Only one is available" is not the same as "only one works". Maybe what you are really looking for is to execute some of the tests only in certain environments? Spock has @IgnoreIf for this, and you could do something similar in JUnit (for example with a custom @Rule). Or you could make Gradle exclude some of the tests based on the current environment. -- 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/Ignoring-some-JUnit-tests-tp4290076p4290281.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
