- 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
- Performance Testing Virtual Users Bundle
- Performance testing - usage example
- Platform Units and infrastructure costs
- Additional licenses
- Creating automated tests
- 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
Performance testing - usage example
Virtual User unit consumption model for performance tests, showing how VU units are drawn from the license pool at runtime and released after completion.
VU units are pulled from the license server at runtime and released back to the license pool after your performance tests are finished. The execution of performance tests will be allowed by the system if there are sufficient unused VU units on the license server. The execution of performance tests will be blocked by the system if there aren’t sufficient VU units available on the license server.
Example 1 - Execution of performance tests is allowed
In the following example, a customer who owns 1 bundle (2,500 VU units) creates 2 testing scenarios.
-
Test Scenario 1
- 1 Web UI test case with 100 virtual users = 1,000 VU units
- 1 API test case with 500 virtual users = 500 VU units
- Total: 1,500 VU units
-
Test Scenario 2
- 1 Desktop test case with 10 virtual users = 1,000 VU units
- Total: 1,000 VU units
Combined, the 2 testing scenarios can be executed within the provisioned license limit.
Scenario 1 + Scenario 2 = 2,500 VU units
Example 2 - Execution of performance tests is blocked
In the following example, a customer who owns 1 bundle (2,500 VU units) creates 2 testing scenarios.
-
Test Scenario 1
- 1 Web UI test case with 100 virtual users = 1,000 VU units
- 1 API test case with 500 virtual users = 500 VU units
- Total: 1,500 VU units
-
Test Scenario 2
- 2 Desktop test cases with 10 virtual users = 2,000 VU units
- Total: 2,000 VU units
Combined, the 2 testing scenarios exceed the provisioned license limit. For this example, only Test Scenario 1 is run. However, when Test Scenario 1 (or another test worth at least 1,000 VU units) is completed, users can trigger the execution of Test Scenario 2.
After a scenario execution completes, the used VU units are released back to the license server and they become available again. Users can, at this point, run the scenarios that may have previously exceeded the available VU unit capacity.
Scenario 1 + Scenario 2 = 3,500 VU units