I guess you could hook in a test listener and throw an exception yourself. See: http://gradle.org/1.0-milestone-1/docs/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:afterTest(groovy.lang.Closure)
Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleware CEO, Gradleware - Gradle Training, Support, Consulting http://www.gradleware.com On Thu, Mar 17, 2011 at 6:38 AM, Adam Murdoch <[email protected]>wrote: > > On 17/03/2011, at 1:20 AM, c_maker wrote: > > Hello, > > I have some long running integration tests and I would like these tests to > make the build fail 'fast'. Currently, if I have a failure, the test task > still attempts to execute the remaining tests. Only after all of them > executed, I get the build failure. > > How can I make it so when I have a failure, everything stops there and the > build is flagged failed right after the first failure? > > > There's no way to do this yet. Could you add a jira issue? > > > -- > Adam Murdoch > Gradle Developer > http://www.gradle.org > Co-Founder and VP of Engineering, Gradleware Inc. - Gradle Training, > Support, Consulting > http://www.gradleware.com > >
