Home/ Questions/Q 7672415
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T16:16:48+00:00

The background is : I am trying to implement an automated integration test solution.

  • 0

The background is : I am trying to implement an automated integration test solution. I want to have a FitNesse server running which QA/Users can maintain the test cases. During our nightly build, we want to have the test run locally in the build machine. (In our build script, we are going to startup Jetty, and FitNesse test cases are invoking the RESTful APIs)

When I am looking into the fitnesse-maven-plugin (http://mojo.codehaus.org/fitnesse-maven-plugin/), in the description of goal fitnesse:run, it said that:

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

However, when I am using this plugin with FitNesse version 2009xxxx or 2008xxxx (with a special patch of this maven plugin), I found that the test is not running locally. Instead, I saw new test results created in the remote FitNesse wiki server.

May I know if it is due to change of behavior of FitNesse? (Coz the fitnesse maven plugin is depending on a much older version of FitNesse) Also, with the original Test Runner being deprecated, is it possible to have the behavior I am looking for? (Pages defined in remote server, but run locally in build machine)

Or, is such way of work no-longer a recommended approach to use FitNesse? (If so, I will need to change the approach of the automated test)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    One solution I’ve used is the wiki import option feature. This can import the latest changes from the remote wiki to your local build server.

    http://fitnesse.org/FitNesse.UserGuide.WikiImport

    You can also tell it to auto-update when running the tests rather than having to re-import manually whenever they change.

    Another possibility is to use a source control plugin to automatically commit changes by QA/Users from the remote wiki and pull them down as part of your build.

    • 0