Java Doc for JUnitTask.java in  » Build » ANT » org » apache » tools » ant » taskdefs » optional » junit » Java Source Code / Java DocumentationJava Source Code and Java Documentation

JUnit is a framework to create unit tests. It has been initially created by Erich Gamma and Kent Beck. JUnit can be found at http://www.junit.org.

JUnitTask can run a single specific JUnitTest using the test element.

 <target name="test-int-chars" depends="jar-test">
 <echo message="testing international characters"/>
 <junit printsummary="no" haltonfailure="yes" fork="false">
 <classpath refid="classpath"/>
 <formatter type="plain" usefile="false" />
 <test name="org.apache.ecs.InternationalCharTest" />
 </junit>
 </target>
 

runs a single junit test (org.apache.ecs.InternationalCharTest) in the current VM using the path with id classpath as classpath and presents the results formatted using the standard plain formatter on the command line.

This task can also run batches of tests. The batchtest element creates a BatchTest based on a fileset. This allows, for example, all classes found in directory to be run as testcases.

For example,

 <target name="run-tests" depends="dump-info,compile-tests" if="junit.present">
 <junit printsummary="no" haltonfailure="yes" fork="${junit.fork}">
 <jvmarg value="-classic"/>
 <classpath refid="tests-classpath"/>
 <sysproperty key="build.tests" value="${build.tests}"/>
 <formatter type="brief" usefile="false" />
 <batchtest>
 <fileset dir="${tests.dir}">
 <include name="**/*Test*" />
 </fileset>
 </batchtest>
 </junit>
 </target>
 

this target finds any classes with a test directory anywhere in their path (under the top ${tests.dir}, of course) and creates JUnitTest's for each one.

Of course, <junit> and <batch> elements can be combined for more complex tests. For an example, see the ant build.xml target run-tests (the second example is an edited version).

To spawn a new Java VM to prevent interferences between different testcases, you need to enable fork. A number of attributes and elements allow you to set up how this JVM runs.
since:
   Ant 1.2
See Also:   JUnitTest
See Also:   BatchTest

It avoids interference between testcases and possibly avoids hanging the build.

Possible values are "once", "perTest" and "perBatch".

Output will always be passed to the formatters and not by shown by default.

If the test is running for more than this value, the test will be canceled.

Doesn't work for archives in JDK 1.1 as the URL returned by getResource doesn't contain the name of the archive.

Will be ignored if we are not forking a new VM.

Doesn't have any effect unless fork is true.

This property is applied on all BatchTest (batchtest) and JUnitTest (test), however, it can possibly be overriden by their own properties.

This property is applied on all BatchTest (batchtest) and JUnitTest (test), however, it can possibly be overriden by their own properties.

This property is applied on all BatchTest (batchtest) and JUnitTest (test) however it can possibly be overridden by their own properties.

It avoids interference between testcases and possibly avoids hanging the build. this property is applied on all BatchTest (batchtest) and JUnitTest (test) however it can possibly be overridden by their own properties.

Possible values are "once", "perTest" and "perBatch". If set to "once", only a single Java VM will be forked for all tests, with "perTest" (the default) each test will run in a fresh Java VM and "perBatch" will run all tests from the same <batchtest> in the same Java VM.

This attribute will be ignored if tests run in the same VM as Ant.

Only tests with the same configuration of haltonerror, haltonfailure, errorproperty, failureproperty and filtertrace can share a forked Java VM, so even if you set the value to "once", Ant may need to fork mutliple VMs.

Will be ignored if we are not forking a new VM.

Output will always be passed to the formatters and not by shown by default. This option should for example be set for tests that are interactive and prompt the user to do something.

If the test is running for more than this value, the test will be canceled. (works only when in 'fork' mode).