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 1 shows the status Failed because the configured
service level objective (SLO) for response time was violated.
- HTTP response time: The chart shows multiple spikes above the defined threshold of 1,000 ms, with peaks reaching over 5,000 ms. These consistent threshold violations triggered the failed status.
- HTTP errors and automation errors: Both remained at 0%, so the failure was not due to request errors or automation breakdowns, but purely due to performance degradation.
- Automation step duration: Execution times for steps fluctuated heavily, with some activities taking significantly longer than expected, further indicating instability in application response.
- Infrastructure metrics: Robot CPU and memory usage stayed within acceptable ranges, showing that the issue was not related to insufficient infrastructure capacity, but rather to the performance of the system under test itself.
Because response times repeatedly exceeded the threshold, the system flagged the group as Failed. This result highlights that while functional execution was correct, the application did not meet the expected performance levels under the applied load.