Fitnesse Plugin

Hudson
Home
Downloads
Mailing lists and IRC
Source code
Reporting Bugs
Documents
Meet Hudson
Use Hudson
Extend Hudson
Plugins
SCMs
Triggers
Build Tools
Build Wrappers
Notifiers
Reporters
Slave Launchers and Controllers
Uploaders
Other Post-build Actions
Ext. Site Integration
UI Plugins
Page Decorators
Authentication and User Management
Cluster Management and Distributed Build
CLI Extensions
Maven
Misc
Others
Container-specific Notes
Site Map

Plugin Information

Plugin ID fitnesse
Latest Release 1.4
Latest Release Date Apr 25, 2010
Sources Subversion
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

This plugin can be used to both execute and report on Fitnesse tests so that they can be integrated into a Hudson build.

Downloads

Settings

  • Project settings in build step
    • For existing fitnesse instance: host/port
    • For new fitnesse instance: jvm args / Java working directory / path to fitnesse.jar / path to FitNesseRoot / port
    • Http timeout
    • Target page, results file name
  • Project settings in post-build step
    • Results file name
  • No global settings

Change Log

  • 1.4
    • Added ability to specify path to fitnesse.jar and path to FitNesseRoot relative to the workspace
  • 1.3.1
    • Fixed bug where counts with X right and Y ignores were being treated as ignored not right
  • 1.3
    • Added ability to specify http timeout (default: 60,000 ms)
    • Added ability to specify java working directory (default: location of fitnesse.jar)
    • Added page or suite name to build page summary link
  • 1.2
    • Added prettier tabular format for results
    • Results file without path will be written to / read from workspace
    • Log incremental console output as fitnesse results are coming in over HTTP
    • Fixed: Unable to unpack fitnesse.jar
    • Fixed: Build hangs when http get stalls
    • Fixed: Unexpected EOF while reading http bytes catch IOException
  • 1.1
    • Fixed: unable to parse xml with BOM: error "content is not allowed in prolog"
  • 1.0
    • Brand new

Todo...

  • Run fitnesse tests using "-c" option when starting new fitnesse instance
  • Add more control over fitnesse start-up params
  • Using glob to collect (potentially) multiple results.xml files
  • Get plugin out of the "misc" list in the plugin manager on the admin page
  • Add ProjectAction so that history graph appears on project's front page
  • Nest Sub-suites and tests-within-suites within the uber-parent FitnesseResults instance
  • Allow direct URL access to sub-suites and tests-within-suites so that every level can have its history graph
  • Run multiple test suites from one project configuration
  • ? Parse HTML output directly (since XML output gives so little useful info)
  • Check plugin in distributed and maven builds

Labels:

plugin-report plugin-report Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Comments (14)

 

  1. Mar 30, 2010

    Carsten Pfeiffer says:

    Thanks a lot for the fitnesse plugin! Would it be possible to add support fo...

    Thanks a lot for the fitnesse plugin! Would it be possible to add support for more than one fitnesse result file? Currently, it is only possible to specify a path to one result file. The other plugins for displaying testresults typically accept an ant path specification, e.g. something like testresults/**/fitnesse-*.xml.

    Thanks,
    Carsten

    1. Apr 21, 2010

      timbacon says:

      That would certainly be possible - I'm also curious as to where the multiple XML...

      That would certainly be possible - I'm also curious as to where the multiple XML files are coming from, can you help me to understand the scenario a bit more?

      Tim

      1. Apr 21, 2010

        Carsten Pfeiffer says:

        Cool, looking forward to that! The scenario is simply that we have multiple test...

        Cool, looking forward to that! The scenario is simply that we have multiple test suites that each produce their own results file. In other cases we are testing different variants and each variant results in one results file.

        Thanks,
        Carsten

  2. Apr 16, 2010

    Paul Rulli says:

    How about a option where I can run FitNesse myself and have the plug-in only dea...

    How about a option where I can run FitNesse myself and have the plug-in only deal with the post build reporting stuff?

    thanks for the work!

    Paul

    1. Apr 21, 2010

      timbacon says:

      You can already do that - at the bottom of the project configuration page under ...

      You can already do that - at the bottom of the project configuration page under "Post-build options" select "Publish Fitnesse results report" and just point to the fitnesse XML results.

      HTH

  3. Apr 21, 2010

    Kevin Vranken says:

    I was wondering whether it was possible to edit the FitNesse startup parameters ...

    I was wondering whether it was possible to edit the FitNesse startup parameters ? You don't seem to have much control over them the way it is now, aside from the directory and the suite . Could a feature like that be added in the future.

    Thanks

  4. May 11, 2010

    Børge Haugsdal says:

    I really like the idea of a Hudson plugin rather using the maven fitnesse plugin...

    I really like the idea of a Hudson plugin rather using the maven fitnesse plugin, that we are using now in our project.
    But I have some suggestions for improvements, since we have a lot of test suites.
    What about making it easier to add new test suites running in the same environment (Host, port, and all are suites) ?
    Instead of having to add new build steps for each suite running in the same environment, could it be possible to add a list of tests to run within the same buildstep?
    The list of build steps can be quite long, and hard to edit.
    And as I can see it is only possible to view a single result file.

    I tried to specify the same result file for each suite hoping that each step should append to the same file, but is seems like each build step overwrites each other.
    What about letting the plugin decide the result file name for each test, and letting the Hudson plugin display all of them?

    Thanks
    Børge

    1. May 11, 2010

      timbacon says:

      Added to the backlog!

      Added to the backlog!

  5. Jul 26, 2010

    JP Erkelens says:

    How about the ability to use Hudson variables in the Suite name. This is a major...

    How about the ability to use Hudson variables in the Suite name. This is a major issue for me as I'd like to run a configuration matrix with different suites as an axis. However, since I cannot do this I have to manually call fitnesse -c and then parse the results myself.

  6. Aug 04, 2010

    Thang says:

    I'd like to second the idea of FitNesse startup parameters like "-e 0" or "-o" a...

    I'd like to second the idea of FitNesse startup parameters like "-e 0" or "-o" as we don't need to retain older versions or update from fitnesse server.

  7. Oct 13, 2010

    Michael Grant says:

    Having had a play with this plugin, I mostly like what I see with it, but there ...

    Having had a play with this plugin, I mostly like what I see with it, but there does seem to be one bug which limits its usefulness to me at present:  The test suite build only fails if there are failures in FitNesse; exceptions thrown in FitNesse do not cause the build to fail.

    1. Oct 13, 2010

      Michael Grant says:

      FWIW, I achieved the above result by adding the following to FitnesseResults.jav...

      FWIW, I achieved the above result by adding the following to FitnesseResults.java:

        public Result getBuildResult() {
           if (getFailCount() > 0 || getExceptionCount() > 0)
              return Result.FAILURE;
           else
              return null;
        }

  8. Dec 14, 2010

    Matthew Huang says:

    Hi, Dear Fitnesse plugin team. I really appreciate the cool thing you did. It'...

    Hi, Dear Fitnesse plugin team. I really appreciate the cool thing you did.

    It's easy to get this plugin work. I found one issue however, it's in the final report. There is link that links back to the Fitnesse test page. I have a Fitnesse page callsed "TestAutobuild" and therefore, I have a page like:
    __________________________________________________________________________________________
    0 failures
    1 tests
    Took 0 ms.
    add description
    Right: 1
    Name Right Wrong Ignored Exceptions
    TestAutobuilds.TestAutobuild 7 0 0 0
    __________________________________________________________________________________________

    where if I hove over the link for "TestAutobuilds.TestAutobuild" I see

    http//esbgftestrepo:8080/:8081/TestAutobuilds.TestAutobuild

    There are two problems in this link.

    First, there is no ":" symbol after http;

    Second, seems like the fitnesse plugin simply attached the port "8081" (since "8080" has been used by other app in my case) I specified portion after the existing hostname:port string with a forward slash in between.

    I am not sure if this is because I didn't configure the plugin correctly or a bug.

    Can you help?

    Thanks much,
    Matthew

    1. Jun 16, 2011

      sebastien girard says:

      I have the same problem, have you find something?

      I have the same problem, have you find something?