This goal uses the fitnesse.runner.TestRunner class for calling a remote FitNesse web page and
executes the tests or suites locally into a forked JVM. It's possible to define several pages and/or
servers.
Mojo Attributes:
| Name | Type | Description |
|---|---|---|
| fitnesses | List |
This is the list of FitNesse server pages. A FitNesse tag is compose of the nested tags:
<fitnesses> |
| Name | Type | Description |
|---|---|---|
| cmdFitnesseHostName | String |
No description. |
| cmdFitnessePage | String |
No description. |
| cmdFitnessePort | int |
No description. |
| dateFormat | String |
Date format for FitNesse page timestamp. Default value is dd/MM/yyyy HH:mm. |
| failOnError | boolean |
Fail the build if fitnesse pages have error. Default value is false. |
No Description.
java.lang.StringNo${fitnesse.hostName}java.lang.StringNo${fitnesse.page}intNo${fitnesse.port}java.lang.StringNodd/MM/yyyy HH:mmbooleanNofalse
<fitnesses>
<fitnesse>
<pageName>This is the only required parameter, the name of
the FitNesse page</pageName>
<hostName>default is locahost</hostName>
<port>: default is 80;</port>
<serverId>ServerId defined in your settings.xml, this allows to use credentials
(basic athentification) for calling your FitNesse pages</serverId>
<type>Override the default type of the page (Suite or Test).;</type>
</fitnesse>
...
</fitnesses>:
java.util.ListYes