...

Using the Test Repository

...

 The Test Repository organization follows an hierarchical, tree like way, of organizing Tests within folders. Since a Test can only be part of one folder within the Test Repository, you have to think in an hierarchical way "What is most important? Usualy, how do I look for the Tests to schedule executions?"

• create top-level folders for the things that are most important (e.g. "performance", "security", "smoke tests")
• create the hierarchy from the things that are most relevant and them decompose each one; thus, if your concerning are the "components" of the system, you can create a top-level "components" folder and sub-folders for each sub-component
• avoid mixing executing or planning related aspects in the Test Repository or you'll reach a no way out solution
• don't organize the Tests based on things that are volatile and that can rapidly change