Test Properties

Property	Optional?	Description
maven.junit.fork	Yes	When using Java 1.4, it may be necessary to fork the JUnit tests to prevent XML parser issues. The default value is `no`.
maven.junit.format	Yes	Specifies the formatter to use for output to the console. Defaults to `brief`
maven.junit.dir	Yes	The directory to invoke the VM in. (ignored if fork is disabled). The default value is `${basedir}`.
maven.junit.usefile	Yes	If this value is set to false, JUnit test run details will appear on the console as the tests are executed. If not, they are stored in a file in the `test-reports` directory. The default value is `true`.
maven.junit.printSummary	Yes	If this value is set to false, JUnit test run details will not include test summary information for a suite. Default value is `true`. This parameter corresponds to the JUnit Ant task `printSummary` attribute.
maven.junit.jvm	Yes	If this property is set it is used as the JVM for the junit tests to run in. This is passed to the Ant junit task in the jvm property. If maven.junit.fork is not true, this is ignored.
maven.test.dest	Yes	Specifies the unit test classes directory. This is the location where the java classes for the test source code will be generated to. The default value is `${maven.build.dir}/test-classes`.
maven.test.skip	Yes	Set this to 'true' to bypass unit tests entirely. Its use is NOT RECOMMENDED, but quite convenient on occasion.
maven.test.failure.ignore	Yes	Set this to `true` to ignore a failure during testing. Its use is NOT RECOMMENDED, but quite convenient on occasion.
maven.test.source	Yes	Provide source compatibility with a specific release Corresponds to the `source` attribute for the ant javac task.
maven.iutest.dest	Yes	Specifies the integration unit test classes directory. This is the location where the java classes for the integration unit test source code will be generated to. The default value is `${maven.build.dir}/iutest-classes`.
maven.iutest.dir	Yes	Specifies the integration unit test source directory. This property should never be overridden as the value is determined directly from the project descriptor. The default value is `${maven.integrationUnitTestSourceDirectory}`.
maven.out.test.dir	Yes	Specifies the directory where the integration unit testing is run. The default value is `${build.dir}/iutest`.
maven.webapp.dir	Yes	Specifies the directory of the web application used to perform integration unit testing. The default value is `${iutest.dir}/testapp`.
maven.conf.test.dir	Yes	Specifies the configuration directory used to build the web application used for integration unit testing. The default value is `${iutest.dir}/cactus`.
maven.tomcat.home	Yes	Specifies your local Tomcat installation directory. The default value is `${tdk.home}`. If `${tdk.home}` is not specified in your `${user.home}/build.properties`, you should set this property. This is used for the integration unit testing.
maven.test.port	Yes	Specifies the port that Tomcat will use for integration unit testing. The default value is `8192`.
maven.junit.jvmargs	Yes	If fork is enabled, additional parameters may be passed to the new VM. You can specify some args separated by a space. Sample :
maven.junit.envvars	Yes	If fork is enabled, additional environment variables may be passed to the new VM. You can specify some variable separated by a space. Each variable is describe in sub properties. Sample :
maven.junit.sysproperties	Yes	Use this property elements to specify system properties required by the class. These properties will be made available to the VM during the execution of the test (either Maven's VM or the forked VM, if fork is enabled). You can specify system properties separate by space. Each properties is describe in sub properties. Sample :
maven.test.search.classdir	Yes	Use this property to specify that JUnit should search the test classes directory rather than the source directory. This allows for test cases to be written in other languages such as Groovy which generate bytecode that can then be used by this plugin. Sample :