Home

This project assists in testing (SOAP) web services and web applications by providing an application to define and run tests. To this end it contains a baseline installation of Fitnesse (an acceptance testing wiki framework) and some FitNesse fixture (base) classes.

The fixtures provided aim to assist in testing (SOAP) web services and web applications (using Selenium) minimizing the amount of (custom) Java code needed to define tests.

Baseline installation features

The baseline Fitnesse installation offers the following features:

1. Ability to easily create a standalone (no JDK or Maven required) Fitnesse environment.
2. Run Fitnesse tests on a build server, reporting the results in both JUnit XML format and HTML.
3. Fitnesse installation for fixture developers containing:
   • the fixture base classes (and Selenium drivers for Chrome, Internet Explorer and PhantomJs),
   • Maven class path plugin (such that tests can use all dependencies from pom.xml),
   • HSAC’s fitnesse-plugin to add additional Wiki features (random values, calculating relative dates, Slim scenarios without need to specify all parameters, Slim scripts that take a screenshot after each step),
   • easy fixture debugging,

1. Create standalone Fitnesse installation

To create a standalone installation execute
mvn clean package -DskipTests

The standalone installation is present in the wiki directory and as ...-standalone.zip in the target directory. It can be distributed by just copying the wiki directory or by copying and extracting the zip file).
This standalone installation can be started using
java -jar fitnesse-standalone.jar
from the wiki directory (or directory where the ‘standalone.zip’ was extracted).

A zip file containing released versions of this project can be downloaded from the Releases or Maven Central.
A similar zip file containing the latest ‘snapshot’ (i.e. not released but based on the most recent code) version is published as part of the automated build of this project.

2. Run on build server

To run the tests on a build server have the build server checkout the project and execute
mvn clean test-compile failsafe:integration-test

The result in JUnit XML results can be found in: target/failsafe-reports (most build servers will pick these up automatically)
The HTML results can be found in: target/fitnesse-results/index.html

The Fitnesse suite to run can be specified by changing the value of the @Suite annotation’s value in nl.hsac.fitnesse.fixture.FixtureDebugTest,
or (preferably) by adding a system property, called fitnesseSuiteToRun, specifying the suite to run to the build server’s mvn execution.

The Selenium configuration (e.g. what browser on what platform) to use when testing websites can be overridden by using system properties. This allows different configurations on the build server to test with different browsers, without requiring different Wiki content, but only requiring a different build configuration.

Example reports for Windows using a Sauce Labs Selenium driver and Linux with PhantomJs are generated in the automated build process of this project.

3. Fixture developer installation

Import this project in your favorite Java IDE (with Maven support).

To start Fitnesse: have the IDE execute
mvn compile exec:exec
The port used by Fitnesse can be controlled by changing the fitnesse.port property’s value in pom.xml.
Fitnesse will be available at http://localhost:/

To debug a fixture used in a Fitnesse page: change @Suite annotation’s value to contain page name in nl.hsac.fitnesse.fixture.FixtureDebugTest, then just debug this test.

Making fixtures accessible

To ensure the fixtures (and all dependencies as specified in the project’s pom.xml) are available, add the following lines to the root Wiki page containing the tests.

!path fixtures
!path fixtures/*.jar
!pomFile ../pom.xml@compile

The first two will ensure all classes are accessible when working standalone, the last will be used by Java developers changing fixtures (with a Maven installation).