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 Apr 27, 2026
In this example, Load Group 2 has the status Passed because all configured service
level objectives (SLOs) were met.
- User metrics (upper charts) show that HTTP response times remained well below the threshold of 1,000 ms throughout the run, with an average response time of 51 ms and a maximum of only 830 ms.
- HTTP errors and automation errors both remained at 0%, confirming that no requests failed and the automation executed consistently.
- The automation step duration chart indicates stable performance, with execution times showing some variation but without exceeding expected tolerances.
- Infrastructure metrics (CPU and memory usage of executing robots) stayed within safe ranges, demonstrating that robot resources were not overloaded during the execution.
Because both application performance and infrastructure usage were healthy, this load group is marked Successful.