Fitnesse tests are written in Fit format (http://fit.c2.com ). This format is very simple. The page can contain any text at all. Any tables that exist on the page will be interpreted by Fit.
A Fit table begins with a row that contains the classname of the test fixture that will interpret the rest of the table. Usually you write these test fixtures. There are a number of test fixture base classes that make writing these fixtures very simple.
The rest of the rows in a Fit table have formats that are determined by the fixture.
Fixtures and Examples |
|
| Table Fixture | A simple fixture for dealing with static tables of data. |
| Column Fixture | Each row loads a data structure and then invokes functions upon it. |
| Row Entry Fixture | A special case of Column Fixture for processing rows of data. |
| Row Fixture | Allows you to match all the rows from a simple query, independent of order. |
| Action Fixture | A fixture that allows you write a script that emulates a user interface. |
| . | |
| Parameters In Fixtures | Allows you to pass arguments into any Fixture. |
| Symbols In Test Tables | Allows you to store outputs fromm one fixture and use them as inputs to another. |
| Keywords In Test Tables | There are certain keywords that can be used in fixtures. I.e. null and blank |
| Data Types In Fixtures | There are several data types that can be used in fixtures. |
| Graceful Names | Managing the names of fixtures, packages, and variables |
| Comment Tables | Sometimes you want a table in a test, that is not part of the test, but is just a comment |
| . | |
| ^ Bowling Game Project | A simple example of some custom acceptance tests. |