Test Suites can be described as containers for your Test Cases that allow you to group those cases by domain or testing area. For our example of a Mobile game project, we will need to test the Background music, User Interface, Performance, and Save features, among many others. We will create an individual Test Suite for each of these domains.
Since the project is new and there aren’t any suites or cases, you’ll have to create your first suite by clicking on the “+Suite” or “Create New Suite” buttons:
Once you’ve clicked on either of those buttons, you’ll be greeted with a pop-up which will require you to update information pertaining to the suite itself.
Suite Name: give your Test Suite a descriptive name that allows you to unequivocally define which domain or area of development it will cover. Suite Name is the only mandatory field to create a Suite - other fields are optional and can be filled at a later stage or left empty.
Parent Suite: it is possible to have a multi-level hierarchy of Test Suites, so if a Suite you are configuring will be a part of a larger scope of testing scenarios, you can put it into a higher-level Parent Suite.
Description: provide additional details and context regarding which Test Cases should belong to a Test Suite.
Preconditions: describe the steps that should be completed before you can proceed with Test Cases from the newly created Suite.
After you have created a Test Suite or several of those, your Repository will now reflect how your Test Suites are structured and how they are related to each other:
If you hover your mouse over Test Suite while in Repository view, several controls will reveal itself:
Collapse / Expand: Clicking on the name of your test suite will either expand or collapse the suite:
Create Case / Create Suite: Clicking on the “+” icon opens up a menu with the options to “Create Suite” or “Create Case”:
Edit Suite: Clicking on the pencil icon allows you to edit the suite itself:
Clone Suite: Clicking on the two pages icon allows you to clone the suite. You also have the option to choose the project to which you would like the suite to be cloned to, the parent suite, the clone strategy, the prefix, and you can choose to clone the suite with its children (suites and cases)
Delete Suite: Clicking on the trash can icon will allow you to delete the suite. Once you’ve deleted the suite, you will no longer be able to restore the suite from the “Trash Bin”:
To navigate around your Suite structure easier, there are three Suite Tree layouts available, which you can toggle between using the “Views” dropdown in the top-right corner of the Repository:
Default layout also known as the “Nested Tree View” shows all of the Suites you currently have in your project; you can open up the Suite Tree sidebar to navigate from one suite to another:
The alternative “Folders view” layout shows only the Test Suite and Test Cases in focus, while to navigate to a different Suite, you need to select it from the sidebar. This layout proves to be a better solution for massive structures with complicated hierarchy:
Mind Map view (Beta): This view displays all the suites and test cases within a project in the form of a mind map. It also provides you the option to create quick cases or suites by clicking on the “+” icon. You can also alter the hierarchy of display by dragging the suite up or down. You can also move a test case from one suite to another. Additionally, clicking on the case will allow you to update its title.
Additionally, in both the Nested Tree view and the Folders view, you can click on the “...” menu icon to Edit, Close, Select and Unselect all, Create Suite, Create Case, and Delete.