| 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.forkmode | Yes | NOTE: Ignored in maven < 1.1. Controls how many Java Virtual Machines get created if you want to fork some tests. Possible values are "perTest" (the default), and "once". "once" creates only a single Java VM for all tests while "perTest" creates a new VM for each TestCase class. Note that only tests with the same settings of filtertrace, haltonerror, haltonfailure, errorproperty and failureproperty can share a VM, so even if you set forkmode to "once", Ant may have to create more than a single Java VM. This attribute is ignored for tests that don't get forked into a new Java VM. |
| 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 |
| 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 :
|
| maven.test.excludeXmlApis | Yes |
If set to yes, the XML APIs will not be added to the list of libraries used for your test cases
when forked. This should be used when you provide your own XML APIs library. By default, it is
no.
|
| testmatchpattern | Yes (required in test:match) | List of ant patterns (spared by commas) used in test:match goal to specify the tests that should run |
| testnotmatchpattern | Yes | List of ant patterns (spared by commas) used in test:match goal to specify the tests that shouldn't run |