test-manager
latest
false
Test Manager user guide
- Getting started
- Project management
- 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
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Interpreting failed results
Interpret failed performance test results in Test Manager, including SLO violations and HTTP response time spikes.
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.