FitNesse is an acceptance testing framework and wiki.
| [top] |
This plugin allows to run fitnesse during your build (remotly or locally) and creates a report into your site.
| [top] |
If you have a fitnesse server, say http://fitnesseSrv:80, when you call the goal fitnesse:run
goal you will request the Fitnesse page content (only the Fit test definition) from fitnesseSrv,
then you will execute your tests locally (where fitnesse is running).
When you call fitnesse:remotecall you will execute
your Fitnesse Test or Suite on fitnesseSrv, then the plugin will copy the page result locally. In
this case it's exactly similar to the execution of fitnesse with its GUI, when you click on the button Test ou Suite.
| [top] |
It depend of what you want :-).
If your are a developer that built new code on your desktop and if you want to confront this brand new code with a Fitnesse test,
goal fitnesse:run is exactlly what you need. You will be able to test your code without having to upload it
onto the FitNesse server. This is especially interesting when your connection between your desktop and the FitNesse server is
not at the top or if you doesn't want to publish this a code for the moment.
If your want to aggregate the FitNesse result (with a Maven report) to your build in the same manner that your should run FitNesse with
Test ou Suite button, you should use the fitnesse:remotecall goal.
If you want to aggregate FitNesse test into your code coverage report, your should execute the FitNesse tests on the same server than your
unit-test (the localhost). In this case the goal fitnesse:run goal seems to be the good one, except if the FitNesse
server and the build server are the same (then both are good).
| [top] |
We provide a Clover exemple. You can use the same mecanism with other framework (clover has the advantage
to automatically install its instrumented jars with a '-clover' extension in your local repository).
Your should use the goal fitnesse:run goal for that.
More information can be found at Atlassian Clover 2 Maven 2 plugin.
Note that the Apache Clover 1 Maven 2 plugin is now deprecated.
| [top] |
First, your may consider to migrate your build to Maven2, its the better build tool :-).
Otherwise your may use this plugin without having a full Maven2 build. In fact you only need to have a very simple pom.xml for running it,
this pom can be obtain with the minimalist example.
This use may resolve what I call the FitNesse paradoxe: FitNesse has a centralized repository for tests (the server local folders)
when development is a decentralized activity (each developer onto his own desktop). If (and I consider that as a good practice) you decide to
promote only well test code to your centralized repository, your can't check this code without boring and dangerous manipulations: manual copy of the
FitNesse working files.
See goal fitnesse:run for more information about this usage and configuration,
specially the classpath modification.
| [top] |
The plugin never run the tests in the same Jvm than FitNesse. It could be a remote one (case of the remote ) or another Jvm on the same computer (). You can specifed your local Jvm with this option and pass argument to it with this one.
| [top] |
