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
- Creating automated tests
- Step 1: Complete prerequisites for performance scenarios
- Step 2: Add performance scenarios
- Step 3: Add test cases to load groups
- Step 4: Configure load group settings
- Executing performance scenarios
- Known limitations for performance testing
- Best practices for performance testing
- Troubleshooting performance testing
- 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
Step 4: Configure load group settings
Load group configuration parameters in Test Manager performance scenarios, covering execution scale, user behavior modeling, and performance thresholds.
When configuring a load group, you define how the selected test case is executed at scale. Each parameter models realistic user behavior and enforces performance expectations.
Steps
- Log in to Test Manager.
- Go to Performance Scenarios, open a scenario, and expand a load group.
- Under Virtual users, specify the number of concurrent simulated users assigned to the test case. Each group can support up to 500 virtual users, with a total of 2,000 across a scenario. Check the number of VU units and machines consumed after a Dry Run, based on your selection — if you ran Capacity Planner during that dry run (see On-premises robot system requirements), its recommended virtual-user count is a good starting point here, rather than an estimate based on the resource ratios alone.
- Define performance expectations. Breaching these thresholds highlights warnings or errors in the results dashboard, which helps you identify unstable scenarios.
- In the Max. response time threshold field, specify the upper time limit (in ms) that responses should not exceed (for example, 5,000 ms for Group 1).
- In the Average error rate threshold, specify the acceptable failure rate (%) across all executions (for example, 1%).
- In the Data source field, link a Data Fabric entity (also known as a Data Service entity) as the data source to feed parameterized inputs such as user credentials or account details. This ensures that each virtual user can run with unique data, avoiding collisions and making execution closer to real-world usage.
Tip:
To use Data Fabric for Performance Testing, ensure that your test case supports test data consumption from Data Fabric. For information on using Data Fabric test data in your tests, refer to Data-driven testing. When this test case is included in a Load Group, you can configure a specific data source at the group level. This allows you to define and use a dedicated Data Fabric source for your performance test executions.
- Decide whether you want to keep Studio parameters as is or override them. To override Studio parameters, under Parameters, select Override. In the Override parameters dialog, perform the required action.
- To override Studio parameters individually, toggle Override. For String types, enter a new value. For Boolean types, select True or False. When finished, select Save.
- To override all Studio parameters, select Override all. Enter or select the new values. When finished, select Save.
- To remove all Studio parameter overrides, select Remove overrides, and then select Save.
- Specify how the load is applied over time. Together, these settings let you model realistic traffic patterns such as gradual adoption, steady-state usage, and controlled shutdown.
- The Delay field shows the wait time before the load group starts execution (for example, 0 minutes).
- The Ramp up field shows the period over which the number of concurrent users is gradually increased until the maximum number of users is reached (for example, 2 minutes).
- The Peak field shows the duration during which the maximum number of users remain active (for example, 26 minutes).
- The Ramp down field shows the period over which the number of users gradually decreases to zero (for example, 2 minutes).
Result
The load group settings are saved. The scenario is configured with the defined virtual users, performance thresholds, data sources, and load profile. You can proceed to run a dry run or full execution.