- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- 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
Known limitations for performance testing
Known constraints for performance testing in Test Manager, including robot runtime limits and maximum concurrent jobs.
Execution duration limits
Cloud, serverless robots can run for a maximum of 60 minutes per test. On-premises robots can exceed this limit.
Concurrency limits
-
Maximum concurrent jobs: Up to 500 jobs can run concurrently using serverless robots.
-
Impact on virtual users (VUs) — serverless: The number of achievable virtual users depends on multiplexing (multiple VUs per job). For example, with a multiplexing factor of 4, a scenario can scale up to 2,000 concurrent virtual users.
- This factor is automatically detected during the dry run and reported in the application logs. It cannot be manually overridden for serverless robots.
-
Impact on virtual users (VUs) — on-premises: On-premises robots are not capped at 2,000 VUs. With sufficient licensing, the dry run can compute a higher achievable virtual-user count, up to a hard maximum of 10,000 concurrent virtual users. Unlike serverless robots, the multiplexing factor here can be manually overridden.
-
VPN constraints: When using a VPN, the effective concurrency depends on the VPN or gateway capacity.
- Default limit: ~250 concurrent jobs
- The actual limit may vary based on the gateway SKU and infrastructure capacity.
- If higher concurrency is required, customers should contact UiPath support or their account team to discuss VPN scaling options.
-
Execution duration: Serverless robots are limited to 60 minutes per execution
Application type override
You can change the application type of a load group only from Desktop to Browser. The override applies to a single load group.
Supported automation types
Performance testing is currently limited to Browser, API (HTTP WebRequest), and Desktop automations. For example, Integration Service or coded automations are not yet supported.
Within these supported automation types, Workflow Analyzer now flags specific unsupported activities automatically during dry run — see Creating automated tests for the current list.
Additional limitations
Performance Testing measures only the following:
- Load
- Response time
- Error rate
- Throughput
It does not collect application- or system-level monitoring metrics (CPU, memory, database, infrastructure). Existing APM/observability tooling covers that data instead.
Programmatic access to performance test data is available at the scenario level: the API can return execution metrics for a specific scenario ID, which you can use to build your own historical tracking (for example, exporting results after each run for later comparison).
No API exists for comparing execution metrics across two or more scenario runs, or for retrieving an aggregated historical summary across runs. Within the product itself, the Comparing performance results view supports this.