MXUnitAntTask - Version: 1.0.7
Description
Runs MXUnit tests and saves the output to the directory specified by the outputdir parameter.
This version uses HTTP to connect to the MXUnit test runner running on a CFML serv (Adobe ColdFusion, Railo, Blue Dragon).
This supports the following HTTP authentication mechanisms - BASIC, DIGEST, and NTLM.
The default testrunner (/mxunit/runner/HttpAntRunner.cfc) accepts either individual test cases or directories of tests to run. This runner returns only JUnitReport formated XML. These XML filesmay optionally be used by the JUnitReport Ant task to generate nice HTML reports. Example usage:
Note that the mxunit-ant.jar must be in Ant's class path. This can be done by specifying the taskdef tag like this:
and then coding the rest of the MXunit Ant task ...
In theory, one should be able to run multiple tests across multiple domains, as long as those tests are accessible via Http.
Parameters
| Attribute | Description | Required | Default | ||
| protocol | The HTTP protocol to use. Valid values are 'http' or 'https' | no | http | ||
| server | The Http server name where MXUnit is located. | Yes | |||
| port | The port the Http server is listening on. | No | 80 | ||
| outputdir | A directory in which to save JUnit XML test results. | No | |||
| haltonerror | Instructs the task to stop executing when an ERROR is detected. This occurs after all the tests in the DIRECTORY or TESTCASE task have been run. |
No | false | ||
| haltonfailure | Instructs the task to stop executing when a FAILURE is detected. This occurs after all the tests in the DIRECTORY or TESTCASE task have been run. |
No | false | ||
| errorproperty | The name of a property to set in the event of an error. | No | |||
| failureproperty | The name of a property to set in the event of a failure (errors are considered failures as well). | No | |||
| defaultrunner |
The testrunner responsible for accepting requests.
|
No | /mxunit/runner/HttpAntRunner.cfc | ||
| verbose | Flag to indicate to output additional information. | No | false | ||
| testResultsSummary | Name of the properties file the task creates. This file is a Java Properties file that records a summary of all the tests the task has executed and is saved to the location specified in the ${outputdir} attribute. This can be useful in automated deployments, for example, if you wish inspect the results of all the tests run prior to deployment. This offers a deeper level of granularity than the haltonerror or haltonfailure offers. The task generates the following properties that can be read by Ant using the following syntax: <br><property file="${outputdir}/testresults.properties" /><br>testresults.properties looks something like:#Sat Mar 01 22:20:25 EST 2008 success.ratio=.99 total.failures=2 failure.ratio=.01 total.errors=0 error.ratio=.00 total.time=8016 total.runs=151 error.ratio is the number of errors to the total number of tests runs. failure.ratio is the number of failures to the total number of tests runs. success.ratio is the total number of tests run to the total number of errors and failures combined. |
No | testresults.properties | ||
| authmethod | The method of authentication to use. Options are basic, digest, ntlm | No | |||
| username | The username, if authmethod is set | No | |||
| password | The username, if authmethod is set | No |
Parameters specified as nested elements
directory
<directory ... >s are used to specify groups of tests to run.
| Attribute | Description | Required | Default |
| path | Directory of tests to run. | Yes | |
| componentPath | A prefix to the components being tested. This is a performance attribute. If specified, directory tests will run faster. Otherwise, the framework will discover the componentPath using built in Adobe ColdFusion functions. Example: componentPath="mxunit.tests.framework". MXUnit will correctly prepend this to all the tests in the specified directory. |
No |
Optionallity is deprecated. Future release will require this attribute to be specified. | |
| runner | The ColdFusion component runner responsible for running the tests, | No | /mxunit/runner/HttpAntRunner.cfc |
| remoteMethod | The remote method in the ColdFusion component that will be called. | No | run |
| packageName | The name used by the JUnitReport task to print the main and child packages in the test result report. | No | mxunit.testresult |
| recurse | Flag to indicate to run all tests in sub directories. | No | false |
| excludes | Comma-delimitted list of files not to include in the test suite. | No | none |
testcase
A <testcase> allows you to specify one or more individual test cases to run.
| Attribute | Description | Required | Default |
| name | The fully qualified ColdFusion component name (com.foo.bar.MyCFC) | Yes | |
| runner | The ColdFusion component runner responsible for running the tests, | No | /mxunit/runner/HttpAntRunner.cfc" |
| remoteMethod | The remote method in the ColdFusion component that will be called. | No | run |
| packageName | The name used by the JUnitReport task to print the main and child packages in the test result report. | No | mxunit.testresult |
Examples
This example illustrates a minimal amount of code required to run one directory of tests. Note that this example does not save any results. This may be useful for automated deployments.
This example runs both directories of and individual tests, saves the output to ${output.dir}, generates a JUnit report, and opens a web browser with the JUnit report.