- Getting Started with Test Suite
- Studio
- Orchestrator
- Testing robots
- Test Manager
- CI/CD Integrations
Test Sets
Test Sets are logical groups of test cases. The purpose of test sets is to define groups of tests that should be executed together within one run. For instance, a smoke test is a group of tests that only check for top-critical capabilities. Whenever any test case from a smoke test fails, there is a critical problem. Executing a smoke test should not take too long. They are executed for instance whenever a developer commits changes to the source code. By comparison, a regression test is a comprehensive test which should provide a detailed overview over the system under test. Execution often takes hours or even days. To define the set of tests to be executed for those purposes, test sets are created. A test case can be assigned to several test sets.
-
Test sets in Test Manager can include both manual and automated test cases, including automated test cases from multiple Studio projects. For more information, see Automated executions conditions.
- Test sets linked from Orchestrator to Test Manager include only the test cases from Orchestrator.
To assign test cases to a test set perform the following steps.
Navigation and Search
To quickly find your test sets, use the search function and the filters. Navigate within the page using and configuring the paginator. Alternatively, you can use the breadcrumb to navigate between the pages.
-
Filter - You have two filter tabs to choose from:
- Browse - to list all test sets.
- Updated by me (predefined) - to list only the test sets that have been updated by the current user, running the Test Manager instance.
-
Search - Use the search bar to find test sets by their key, name or labels (requires full search term match).
You can use the search bar at the top of the page to look for items across Test Manager (e.g., requirements, test cases).