Here we point you to pages that describe each of the styles of FitNesse test table, and the fixture code used to interpret and run them as tests.
The Most Common Table/Fixture Styles
|This is the style you may end up using most: rows of data represent inputs and expected outputs.
|This is good for testing queries that should return an exact set of values (order-independently).
|This style allows you write a script that emulates a series of events (such as controls manipulated on a user interface).
|Sometimes you want a tabular comment that is not executed as a test.
Less Frequently-Used Table/Fixture Styles
|Row Entry Fixture
|A special case of Column Fixture for processing rows of data.
|A fixture style that lets you create completely custom test table formats, and process them however you like.
|A fixture that generates a report of all the tests on a page.
Some Table and Fixture Examples
|An example using Column Fixture
Some extra things about Fit Tables that vary from port to port.
|Symbols In Test Tables
|Some ports of FIT allow symbols to be passed in Column and Row fixtures. This is very inconsistent amongst the different FIT ports.
|Keywords In Test Tables
|Some ports of FIT allow keywords blank, null, and error. This is very inconsistent between FIT ports.
|Comparison Expressions In Fixtures
|You can put comparison expressions in the cells of your test tables.
|Parameters In Fixtures
|Allows you to pass arguments into a fixture.
|Data Types In Fixtures
|Which data types FitNesse and Fit can handle in test tables.
|Trouble Shooting Acceptance Tests
|How to investigate problems when running test tables.
Writing Fit Tables
|Writing Fit Tables
|How to write tests.