test-manager
latest
false
- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manual test cases
- Importing manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- 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
- Accessibility testing for Test Cloud
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Last updated May 6, 2026
Note:
Feature availability depends on the cloud platform you use. For details, refer to the Test Manager feature availability page.
You can execute test cases without adding them to a test set.
Note:
This capability is available only in Test Manager delivered via Test Cloud.
Considerations
When you execute test cases without a test set, the following limitations apply:
- Automated executions always use the latest version of the associated automation.
- For automated executions, the project's default Orchestrator folder is used as the execution context. If no default folder is set, you can only execute tests manually.
- You must automate test cases by selecting an automation linked to an Orchestrator package. Test cases automated through direct Studio binding are not supported. Additionally, the selected Orchestrator package must be deployed either to the default folder feed or the tenant feed.
Limitations
When you execute test cases without test sets, the following capabilities are not available:
- Selecting a robot account when configuring an execution folder
- Overriding parameters
- Re-executing test executions
- Activity coverage
Prerequisites
To execute test cases without a test set, your Test Manager role must have the following permissions and task permissions:
- Permission: Test case - Read
- Task permissions: Depending on the type of test cases you want to run individually:
- Manual execution
- Automated execution
Steps
To execute test cases without a test set, follow these steps:
- Open your Test Manager project.
- Go to Test cases.
- Choose how many test cases to execute:
- To execute a single test case:
- For the test case you want to run, select More Options.
- Depending on the test case type, select one of the following:
- Execute Manually
- Execute Automated
- To execute multiple test cases:
- Select the checkboxes next to the test cases you want to run.
- Select Execute, then choose
- Execute Manually
- Execute Automated
- To execute a single test case:
Result: Each run creates a test execution that is not linked to a test set.