Here is a brief summary of things you should watch out for in your tests, and ideas on how to fix them. Use this page as a check list to see whether it is time to do some housekeeping on your FitNesse pages.
Repetitive values in table cells, especially if the whole column is the same. See Replace repetitive values with arguments.
Lot of similar tests with minor differences in workflow. See Don't test workflow, get to business rules.
Test pages containing complex tables that are not really important for the particular test (often just used to set up the stage for the test, and copied from an different test page). See Remove irrelevant information.
Tests that don't belong to a test suite but have the same setup as other tests. See Group related tests into test suites.
Parts of test pages or even complete pages used as setup for other tests. Tests that are extensions of other tests. See Beware of test extensions.
Fixtures implementing a business interface or providing setters and getters to properties of a complex business object. See Don't reimplement business interfaces.
Tests that reflect the way code was written (you can spot them by looking if tables are too detailed or step-oriented when they should really be focused on higher-level activities). See Think about the intention, not the implementation.
Test suites with a mix of quick and slow tests. See Don't mix quick and slow tests.
Tests that fail intermittently even though you haven't changed the code (especially those that depend on external systems, or on the order of execution). See Beware of unstable tests.
Fixture methods that mostly deal with conversion from table content into business types. See Avoid conversions by supporting custom data types.
