- Getting Started
- Studio
- Orchestrator
- Testing robots
- Test Manager
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.
- Using Static Assignment - select the test cases manually.
- Using Dynamic Assignment - input the label of the test cases that you want to assign.
- Open the test set for which you want to enable activity coverage.
- Go to the Configuration tab.
- Select Enable RPA activity coverage calculation.
- Select More Options for the Test Set that you want to duplicate, and select Clone.
- Rename the Test Set and choose the information you want to clone, such as:
- Documents
- Labels
Test Cases assigned to the original Test Set (both statically and dynamically) are automatically linked to the clone. Custom field definitions, and custom field values are also cloned if they exist.
- Select Confirm to start the cloning process. The clone is created in the background.
You can link your test sets from Orchestrator and execute them in Test Manager.