test-manager
latest
false
- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Creating automated tests
- Executing performance scenarios
- Known limitations for performance testing
- Best practices for performance testing
- Troubleshooting performance testing
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Last updated Feb 18, 2026
Cloud, serverless robots can run for a maximum of 60 minutes per test. On-premises robots can exceed this limit.
Up to 2,000 virtual users per scenario and 500 virtual users per load group are supported.
Performance testing is currently limited to Browser, API (
HTTP
WebRequest), and Desktop automations. For example, Integration Service or Coded
automations are not yet supported.
- Infrastructure gaps:
ACR-VMsupport and elastic provisioning are not yet available, so automatic scaling of resources is currently not possible. - API access: Direct programmatic access to raw performance test data is not yet supported.
- Historical comparison: Test results from different historical runs cannot yet be compared.
- Autopilot and agentic support: Autopilot and agentic support are not available in the current release.
- Recordings displayed in the detail: Recording can be activated and viewd only in Orchestrator.
