Best practices | Project | Folders
We're big fans of folders. A good folder structure makes things easy to find, easy to classify, and easy to scale—especially in a team environment. Make sure you organize your test artifacts into a logical, sustainable structure, so your project can grow and evolve, without you having to reorganize all the time.
This topic explains folder considerations for the main sections of Tosca:
-
Modules, where you create and manage the building blocks of your tests.
-
TestCases, where you design your test sequences and actions.
-
Execution, where you organize your test runs and check their results.
Modules section
Modules are the building blocks of your tests. For your Modules section, keep these things in mind:
-
Create a structure that's logical for everyone. We recommend that your Module folders follow the structure of your application:
application name and acronym > areas or functionality > individual parts or processes
-
Avoid folders that have overlapping or competing categories. You don't want your fellow testers to wonder whether a Module belongs in folder A or folder B.
-
Use intuitive, human-readable folder names. Try to keep them on the short side, so they're easy to read in search results.
Yes! A logical folder structure is easy to navigate and easy to maintain.
TestCases section
A TestCase is a series of steps that Tosca should do in your application under test.
-
If you use Requirements and/or TestCase-Design, create the same folder structure in the TestCases section.
To do this quickly and easily, open your Requirements or TestCase-Design folders in the Details view. Select all, right-click, and select Copy table to clipboard from the context menu. Then right-click a TestCase folder and select
Create folder structure from the mini toolbar.
-
If you don't use Requirements or TestCase-Design, we recommend this folder structure:
application name and acronym > business process > sub-processes
Good folder structure for TestCases
Execution section
The Execution section is where you prepare and trigger your test runs and check their results. We recommend that you also create folders within your ExecutionLists folders to keep track of your test results:
-
Smoke tests for your high priority test cases.
-
Regression tests for your regression suite.
-
Archive for everything that clutters up the other folders, but that you want to keep.
If you test more than one application, create a separate parent folder for each application, and then add the suggested folders as sub-folders.
Folder structure for two applications in the Execution section
What's next
If you haven't yet, check out our other best practices articles.