We have got Fitnesse testing integrated into a Jenkins Build Server contributed by BayCIX from Landshut, Germany. It can be viewed and run from http://fitnesse.idempiere.com.
The Jenkins server at http://jenkins.idempiere.com has a configuration to automatically take the Fitnesse module from ADempiere SourceForge.net's SVN/branches/fitnesse and copy it to the above location and then run it and place the results.xml in a specific location for easy access. Jenkins will run the tests each time the ADempiere361 experience a change in codebase.
The Fitnesse itself already has graphical display at a click under 'Test History'. The Fitnesse test suite itself is fully single based, meaning that all my tests i did before are now in a single folder and can be run either in a suite for all tests at one go or singularly one by one according to your selection.
The import and class-paths are also consolidated into the Frontpage header page.
Now you can either run this yourself by going to the link above or just access the results.xml when Jenkins runs it for us on regular or occasional whenever there is a change in the codebase. At the moment only the Adempiere Standard Testing and Pos Gui Testing is tested locally and activated for testing on the Jenkins. The rest are put on 'normal' mode until the modules such a Fixed Assets are properly integrated (some Romanian terms in the model).
Next on the roadmap will be to get the OSGi version of 361, which is iDempiere 1.0 pending to be tested with the same Fitnesse suite. This involves using fixtures that works within the OSGi container. After that it is the Web-based HTML or Ajax UI testing (using SAHI or ZTL(for ZK5)) and incorporate them into the Jenkins environment also.
I am now with Dominik of BayCIX in Landshut, 70km near Munich, Germany doing the Jenkins proofing together so i probably do the SAHI portion first as both that and the above suite is useful as a complete suite for both 361 and ADempiere 370 at SourceForge.net. I also will be studying another recent SAHI contribution from Michael McKay of Canada to see if they can work on this Jenkins.
At the Jenkins server, when you login as an Administrator and click on the 'FitnesseTests' row and then 'configure' you will see the following page:
The Repository URL is set to http://adempiere.svn.sourceforge.net/sv ... s/fitnesse where any change detected there (when i or someone else upload a new fixture or test script) it will fetch onto Jenkins.
The Fitnesse engine is already running in the Jenkins and will allow at that port 8070, which is conveniently set to http://fitnesse.idempiere.com.