- 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 3: Add test cases to load groups
Add test cases to load groups within a performance scenario in Test Manager to define parallel workloads that simulate real-world application traffic patterns.
Populate a load group in a performance scenario with a test case, an Orchestrator folder, a robot type, and a package version. Combining several groups mixes API, web, and desktop workloads in one scenario.
Context
Load groups define the specific test cases that run in parallel at scale. Each group can represent a distinct workload (for example, login flow vs. transaction flow).
In real-world systems, application traffic rarely comes from a single type of user or follows one uniform pattern. By designing scenarios with varied test case types, load profiles, and execution timings, you simulate realistic usage conditions—making it more likely to uncover bottlenecks and validate that the application can handle true production-scale demands.
By combining multiple load groups within a scenario, you can:
-
Mix different automation types: Include API, Web UI, and Desktop test cases together to reflect the diversity of how users and systems interact with the application. For example, API calls may run in high volume while fewer desktop or web users perform more complex transactions.
-
Simulate realistic traffic patterns: Different load groups allow you to model varied timings, ramp-ups, and peak loads. Some users may log in continuously, while others generate activity in bursts or spikes, as shown in the screenshot where one group runs steadily while others ramp up and down at different times.
-
Detect interaction effects: Running different workloads in parallel highlights how one process may affect the performance of another. For instance, a surge in API requests may slow down web transactions, or heavy login activity could impact back-end processing times.
-
Stress the system holistically: Multiple groups together create a more authentic end-to-end workload, ensuring the system is validated against combined stress, not just isolated test cases. This improves confidence that performance in the test environment reflects production behavior.
Steps
-
Log in to Test Manager.
-
Go to Performance Scenarios and open a scenario.
-
Select Add Load Group or select the Test case field in an empty load group to open the selection dialog.
-
To set the execution context, under Default folder, select the Orchestrator folder where your user and robot are assigned.
-
Choose the test case you want to execute at scale.
-
Select the robot type.
-
Cloud serverless robots consume Platform Units and are recommended for Web and API testing.
-
On-premises robots consume runtimes (250 per Virtual Users Bundle), which must be configured in machine templates in Orchestrator.
-
Elastic Robot Pool generates load from your own Azure, AWS, or Google Cloud private capacity, scaling load injectors up and down as the test requires.
-
-
Select the package version of the automation you want to run. By default, the latest version is chosen automatically.
-
Confirm your selection.
Result
The test case is added to the load group and configured for execution at scale. The load group is ready for further configuration of virtual users, thresholds, and timing parameters.