Using the following schema will help you keep your tests and suites well organized:
Keep all your Story Tests in the StoryTests branch. Each of the containers in the StoryTests branch are related to sections of the application - typically one for each tab, high-level logical section, etc.. If a feature is accessed from multiple sections, use your best judgment as to where it belongs in the hierarchy.
The TestComponents branch is used to organize component pages that are assembled into tests by test pages in the StoryTests branch. Component pages are included using the !include widget.
SprintTests organize the test by sprint. For each sprint, we create a tagsuite page for every story in the sprint. We tag the tests in the StoryTests section with the story name and the sprint section name (e.g. !tag ShowNewItems SprintSeven). The story tagsuite page gathers all the acceptance tests for the story (e.g. !tagsuite ShowNewItems ) and the AllTests tagsuite page gathers all the story tests for the sprint (e.g. !tagsuite .StoryTests SprintSeven).
IntegrationTests is a tagsuite that gathers tests to be run in continuous integration. We tag tests with !tag Integration and the IntegrationTests page simply consists of !tagsuite .StoryTests Integration.
SmokeTests is a tagsuite that contains a few tests that can be run quickly to "smoke test" the system (!tag Smoke on tests to be used and !tagsuite .StoryTests Smoke on the SmokeTests page).
Note: The tree renders with alphabetical ordering.
IntegrationTests SmokeTests SprintTests SprintSeven ShowNewItems FrontPageHasDate SprintEight UserCanChangePassword StoryTests NewsSection SortByDate RecentItemsList BlogFeature UserPreferences DisplayName SummaryPage TestComponents SiteSecurity LoginTestUser LogoutTestUser NewsSection SortByDate SortAscending SortDescending BlogFeature