...

This is a different approach from the traditional way of organising Tests in flat lists by using Test Sets.

Similar to traditional operating systems (e.g. Windows, OSX, Linux), Tests may only be part of one folder.

Key concepts

Within the Test Repository screen you can see some meta-folders that provide you quick ways to see or filter some relevant Tests. These folders are read-only and will be used mainly as basis to select the proper Tests before adding them to folders within the Test Repository itself.

• All: all Test issues within the current project (independently if they're organised or not)
• Orphans: all non-organised Test issues (i.e. Tests that are not part of the Test Repository), in the context of the current project
  

T

• Test Repository: the actual Test Repository, composed of multiple folders and sub-folders along with Tests, in the context of the current project. It corresponds to the root folder.

Within the Test Repository root folder, multiple folders can be created and Tests can added to them. 

Similar to traditional operating systems (e.g. Windows, OSX, Linux), Tests may only be part of one folder.

Recommendations

• Avoid putting semantic related with the execution phase in the Test Repository or else your Test Repository will end messed up

...