As we've seen, every FitNesse
test table begins with a row that contains the classname of the FixtureCode
that will interpret the rest of the table. The rest of the rows in a test table depend on which style of table and fixture we are using (each style of test table has its own style of FixtureCode
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 tablular comment that is not executed as a test.
Less Frequently-Used Table/Fixture Styles
||A special case of ColumnFixture 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
Some extra things about Fit Tables that vary from port to port.
||Some ports of FIT allow symbols to be passed in Column and Row fixtures. This is very inconsistent amongst the different FIT ports.
||Some ports of FIT allow keywords blank, null, and error. This is very inconsistent between FIT ports.
||You can put comparison expressions in the cells of your test tables.
||Allows you to pass arguments into a fixture.
||Which data types FitNesse and Fit can handle in test tables.
||How to investigate problems when running test tables.
Rick Mugridge's FitLibrary
This is Rick's writeup on DoFixture and all the other fixtures in his library.
Quick overview of FitDecorators
||A quick overview with examples
Writing Fit Tables