- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Automate test cases
- Configuring test cases for execution
- Linking test cases in Studio to Test Manager
- Assigning test cases to requirements
- Document test cases with Task Capture
- Importing manual test cases
- Cloning test cases
- Exporting test cases
- Manual test cases
- Parameters
- Delete test cases
- Applying filters and views
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Configure individual test case execution in Test Manager by selecting an execution folder, runtime type, robot account, machine template, and automation package.
You can execute test cases individually or as part of a test set. The current topic details how you can configure test cases for individual execution. For information on how to execute test cases as part of a test set, refer to Configuring test sets for specific execution folders and robots.
You can automatically execute test cases from the folder or folders where the automation is published. You can further specify a machine and a robot for your execution run.
Configuring a test case for execution
- Navigate to Test Cases and identify the test case you want to run.
- Go to the end of the test case row and expand the vertical three-dot menu.
- From the context menu, select Execute Automated.
- Select an Orchestrator execution folder.
- Under Runtime type, select one of the options, depending on your license type. Testing is the default option.
- Under Robot account, select a robot account. The default value is Any User/Robot account, which lets you execute the test case using any robot available in the selected folder.
- Under Machine template, select Any machine template or a specific machine template.
- Under Automation packages, review the preselected package and version. To change them, select different values from the dropdowns.
- Select Save to confirm the selection.
Result
The test case is queued for automated execution using the selected folder, robot account, machine template, and package configuration.