Downloading and Installing FitNesse

It really takes very little time and effort to get FitNesse running on your machine.

1. Go to http://fitnesse.org/FrontPage.FitNesseDevelopment.DownLoad and click on the most recent fitnesse.jar file.
• If this is a brand new installation, just put it in some convenient empty directory.
• If this is an update, then copy it on top of the old fitnesse.jar in your current installation.
2. Type java -jar fitnesse.jar
• It will ask you to be patient as it installs or updates.
• When it's done, it will ask you to reload fitnesse. Type java -jar fitnesse.jar again.
• If you have nothing running on port 80 on your machine, you should see a message similar to the following:
• Fitnesse (date code) Started...
• on port 80
• using path '.'
• using dir 'FitNesseRoot'
• Not logging.
• If you don't see this, you may have something running on port 80 already,
• So try the command java -jar fitnesse.jar -p 8080
• If you are still having trouble then check out FitNesseWontStart.

1. Start up a browser and go to http://localhost
• or if you had to edit run.bat in step 3 then go to http://localhost:8080.
2. The main FitNesse screen should come up. That's it. You're ready to start using FitNesse.

Learning More

If you have not yet done so, check out the TwoMinuteExample. To learn more about what FitNesse acceptance testing is all about, see AcceptanceTests. If you are ready to start creating FitNesse pages and test tables, check out EditingFitNessePages and CreatingTestTables.

Memory Issues.

With the 20090320 release, some operations in FitNesse take more than the default memory allocated to the JVM. This can cause tests to fail for out of heap space reasons. You can fix this by adding the -Xmx100M JVM argument to the java command line when you start FitNesse. java -Xmx100M -jar fitnesse.jar.

Memory issues and the build.

If you build FitNesse from source, the ant script may fail for out of heap space reasons. You can fix this by setting the ANT_OPTS environment variable to -Xmx100M.