- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
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.
- Test sets linked from Orchestrator to Test Manager include only the test cases from
Orchestrator.
Important: For any tenant, test management capabilities have been moved to Test Manager. As a result, test schedules are no longer available in Orchestrator, and you cannot execute test cases and test sets directly from Orchestrator anymore. However, you can continue executing test cases and test sets through Orchestrator APIs for Test automation, or using the native Test Manager - CI/CD integration.
- You can run test sets from either a default or a specified execution folder. This allows you to exclusively execute test cases that are part of that particular folder. Moreover, you also have the option to specify particular packages and their versions from which the test cases will be exclusively run.
