adding the option to not halt after a test failure; it will still report failure at the end. This makes sense for Bamboo so we know all the tests that fail, not just the first. It is also useful for checking what tests are affected by a change.

You can tell ant not to halt with: 'ant -Dhalt=no' (yes is the default)

git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@2240 348d0f76-0448-11de-a6fe-93d51630548a
This commit is contained in:
aaron 2009-12-03 06:19:39 +00:00
parent a88202c3f6
commit d27d56ea0c
1 changed files with 5 additions and 2 deletions

View File

@ -7,6 +7,9 @@
<property name="single" value="*Test" />
<property name="singleintegration" value="*IntegrationTest" />
<!-- do we want to halt on failure of a junit test? default to yes (Bamboo uses 'no') -->
<property name="halt" value="yes" />
<!-- should our junit test output go to a file or the screen?
false means it goes to the screen (default) true to file -->
<property name="usefile" value="false" />
@ -257,7 +260,7 @@
<target name="test" depends="test.compile,agent" description="Run unit tests">
<mkdir dir="${report}"/>
<echo message="Sting: Running test cases!"/>
<junit printsummary="yes" showoutput="yes" clonevm="yes" haltonfailure="yes" failureProperty="test.failure">
<junit printsummary="yes" showoutput="yes" clonevm="yes" haltonfailure="${halt}" failureProperty="test.failure">
<jvmarg value="-javaagent:build/TestAgent.jar"/>
<formatter type="${testOutput}" usefile="${usefile}" />
<classpath>
@ -282,7 +285,7 @@
description="Run the long integration unit tests">
<mkdir dir="${report}"/>
<echo message="Sting: Running integration test cases!"/>
<junit printsummary="yes" showoutput="yes" clonevm="yes" haltonfailure="yes" failureProperty="test.failure">
<junit printsummary="yes" showoutput="yes" clonevm="yes" haltonfailure="${halt}" failureProperty="test.failure">
<formatter type="${testOutput}" usefile="${usefile}" />
<classpath>
<path refid="runtime.dependencies"/>