I’ve recently started using Fitnesse, an acceptance testing framework. There really isn’t much around on how to get it working on the mac with ruby, so I decided to get it working and put up my findings…
Installing the Fit Ruby Gem
First of all, you’ll need to download the Fitnesse ruby gem. It isn’t complete by any stretch of the imagination, but it does the job. To get it, run the following command, entering your administrator password when prompted:
sudo gem install fit
You should see the following as a result:
Successfully installed fit-1.1
Installing the Fitnesse Server
Now, you’ll need to download Fitness… Click here, and select the most recent version (20070619 at time of writing). I downloaded the fitnesse20070619.zip version.
Unzip the file, and copy the resulting fitnesse folder to the Applications folder (there’s where I put it… if you do the same, it’ll be easy to follow along with this post).
Allowing Fitnesse to run
We now have to set the correct unix file permissions to allow the Fitnesse server to run. Back to the terminal, this time entering the following commands:
cd /Applications/fitnesse/
chmod +x run.sh
That sets the “I can be executed” flag on the file, allowing us to run the server. Not very Mac-like, but it has to be done.
Setting up the Ruby Fixture Code
We’ll now prepare the ruby fixture code (ie: the test) that we’ll eventually be executing. Having this in place before we create the Fitnesse page gives us the ability to test everything we do whilst trying to get it all to work – it’s a painful process, anything to make it easier is a good thing).
I created the following file…
/Users/nat/Development/Projects/Ruby/WatirFitFramework/lib/Framework/Testcase.rb
…with the following contents…
require 'rubygems'
require 'fit/column_fixture'
module Framework
class Testcase < Fit::ColumnFixture
attr_accessor :numerator
attr_accessor :denominator
def quotient
@numerator.to_f / @denominator.to_f
end
end
end
Make sure that the the case used for the name is consistent. I advise using a filename beginning with a capital letter, followed by only lowercase letters.
Setting up the Fitnesse Test Page
We first of all need to start the fitnesse server. Back to the terminal…
cd /Applications/fitnesse/
./run.sh -p 8080
The “-p 8080″ means that the fitnesse server will be running on port 8080. Ports lower than 1024 will cause errors.
Now open Safari (or any other web browser – I’m using safari for this post) and navigate to http://127.0.0.1:8080. If you see the “Welcome to Fitnesse!” page, all is good.
Due to the way that test suites work in fitnesse, I decided to put the config stuff in a parent page, and the test itself in a child page. I haven’t got the space/time/energy to explain that concept – see the fitnesse documentation for that.
I created the “NatTest” page by going to http://127.0.0.1:8080/NatTest and clicking on the “create this page” link that is displayed as a result.
In the page (click the ‘Edit’ link in the navigation column) I added the following:
!define COMMAND_PATTERN {ruby -I %p /Library/Ruby/Gems/1.8/gems/fit-1.1/bin/FitServer.rb}
!path /Users/nat/Development/Projects/Ruby/WatirFitFramework/lib
The first line tells fitnesse how to run ruby, and the second line tells fitnesse where our ruby fixture code is.
Next, I created the actual fitnesse test by navigating to http://127.0.0.1:8080/NatTest.TheTest, again clicking on the “create this page” link. In it, I pasted the following ColumnFixture table:
|Framework.Testcase|
|numerator|denominator|quotient?|
|10|2|5|
|12.6|3|4.2|
|100|4|24|
Last thing now… we need to make our “TheTest” page an actual test so that fitnesse can execute it. To do that, click on the “Properties” link in the navigation column, check the “Test” check button and then click “Save properties”.
Run the test
In the navigation column there should now be a “Test” button. Click it…
If all has gone well, you should see some test results. From here on, you’re by yourself.