- Getting started
- Project management
- Documents
- 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
- Manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- 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
- Accessibility testing for Test Cloud
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Software and system prerequisites for performance testing in Test Manager, covering Studio version requirements, cloud robot, and on-premises robot configuration.
Before you create and execute performance testing scenarios in Test Manager, make sure your organization and tenant meet the required infrastructure, robot, and test automation prerequisites. The configuration depends on the type of robot used to execute the load with: cloud robots or App Testing robots (unattended), on-premises robots.
Studio requirements
Performance testing reuses your existing automated functional test cases. Make sure that you create your Studio tests based on the following conditions:
- Use a UiPath Studio version equal to or higher than 2025.10.3.
- Use a Test Automation project type.
- Using the latest activity package versions:
System.Activitiesversion 25.4.2 or higherTesting.Activitiesversion 25.10.0 or higherUIAutomation.Activitiesversion 25.10.2 or higherWebAPI.Activitiesversion 2.1.0 or higher
Workflow Analyzer runs as part of every dry run and confirms that the Studio, UIAutomation.Activities, and Testing.Activities package versions used by each test case meet the requirements above. A test case built on an older version may run fine in a regular test set but fail once it hits the dry run — Workflow Analyzer surfaces exactly which version or activity is the problem, before you spend time on a run that can't succeed.
Robot requirements
Configure the robot types you need.
- Serverless cloud robots consume Platform Units and are best suited for Web and API testing. They scale automatically in Test Cloud, but do not support desktop automations.
- On-premises robots consume 250 runtimes per Virtual Users Bundle and are required for desktop performance tests. These runtimes must be assigned within machine templates in Orchestrator. Refer to the system requirements for on-premises robots.
Network requirements
Firewall-safe HTTP metrics: If port 5671 (AMQP to Azure Event Hub) is blocked, Performance Testing automatically falls back to WebSocket-based communication over port 443, and if that also fails, to API-based metric delivery. You don't need to request a new firewall rule to get metrics flowing — the fallback is automatic. Refer to Troubleshooting performance testing for the port 5671 diagnostic, still the right first check if metrics aren't showing up.
Data sources (Data Fabric entities)
Performance scenarios often require dynamic test data at scale. Test Manager can connect to Data Fabric entities, which serve as the source of parameterized test data during scenario execution. This ensures realistic and varied input for concurrent virtual users.