!3 Setting up a '''Suite''' page.
You can run all the test pages in a sub-wiki by setting the "Suite" attribute of a page (see [[Page Attributes][MarkupPageAttributes]]).  That page will then include a "Suite" button that will execute all the test pages in that hierarchy.

!3 !-SetUp-! and !-TearDown-!
Sometimes you will need to delete a test database at the end of each test in a suite, or create an empty database at the beginning of each test.  Operations like this can be performed by writing special fixtures that perform these functions in their constructors.  These fixtures can then be invoked in the '''!-SetUp-!''' and '''!-TearDown-!''' pages of the suite.  See [[!-SetUp and TearDown-!][.FitNesse.SuiteAcceptanceTests.SuiteWikiPageResponderTests.TestSetUpAndTearDown]].

To perform operations at the beginning or end of an entire suite, rather than for each test, define the operations on pages named '''!-SuiteSetUp-!''' and '''!-SuiteTearDown-!'''.

!3 Test lists. 

Sub wikis are convenient for creating a structure to your tests.  You can put test pages below subsystems and/or features.  You can put !path and !fixture statements in the parent pages.  The sub-wiki hierarchy can be very convenient as a packaging structure for tests.  

However, sometimes you want to compose a test suite from test pages that are in many different modules, subsystems, or features.  For example you might want a test suite that lists all the test pages for the current iteration, or you might want a test suite that lists all the currently passing tests, or you may want to create a test suite for all the quickly executing tests, and another for all the slow tests.

To do this you can use the [['''!-!see-!'''][MarkupCrossReference]] command in a test suite.  Any test pages referenced by '''!-!see-!''' on a suite page will be executed as part of that suite.
