Levi, On Mon, 2009-10-05 at 07:16 +0200, Levi Hoogenberg wrote: > In that case, the JUnit equivalent of failOnError could still help to > continue the build. The other part could be trickier. > > My idea was to check for test failures for one of your subprojects at > the end of your build (or the end of your CI task). For TestNG, you > could check for the existence of testng-failed.xml. Maybe with JUnit > there's something similar? Then, when you discover test failures, you > could fail the build. I'm not sure what's the best way to do that, > though - throwing an exception would certainly work :) > Thanks for the ideas. I'll take Hans' advice (see next email) on first though and see if that works.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
