UiPath Documentation
test-manager
latest
false
Test Manager user guide

Step 4: Configure load group settings

Load group configuration parameters in Test Manager performance scenarios, covering execution scale, user behavior modeling, and performance thresholds.

When configuring a load group, you define how the selected test case is executed at scale. Each parameter models realistic user behavior and enforces performance expectations.

Steps​

  1. Log in to Test Manager.
  2. Go to Performance Scenarios, open a scenario, and expand a load group.
  3. Under Virtual users, specify the number of concurrent simulated users assigned to the test case. Each group can support up to 500 virtual users, with a total of 2,000 across a scenario. Check the number of VU units and machines consumed after a Dry Run, based on your selection — if you ran Capacity Planner during that dry run (see On-premises robot system requirements), its recommended virtual-user count is a good starting point here, rather than an estimate based on the resource ratios alone.
  4. Define performance expectations. Breaching these thresholds highlights warnings or errors in the results dashboard, which helps you identify unstable scenarios.
    • In the Max. response time threshold field, specify the upper time limit (in ms) that responses should not exceed (for example, 5,000 ms for Group 1).
    • In the Average error rate threshold, specify the acceptable failure rate (%) across all executions (for example, 1%).
  5. In the Data source field, link a Data Fabric entity (also known as a Data Service entity) as the data source to feed parameterized inputs such as user credentials or account details. This ensures that each virtual user can run with unique data, avoiding collisions and making execution closer to real-world usage.
    Tip:

    To use Data Fabric for Performance Testing, define an In argument in the test case for each entity column you use. Each argument must have the same name and type as its column. For the full setup, refer to Use a Data Fabric entity as test data in performance scenarios.

  6. Decide whether you want to keep Studio parameters as is or override them. To override Studio parameters, under Parameters, select Override. In the Override parameters dialog, perform the required action.
    • To override Studio parameters individually, toggle Override. For String types, enter a new value. For Boolean types, select True or False. When finished, select Save.
    • To override all Studio parameters, select Override all. Enter or select the new values. When finished, select Save.
    • To remove all Studio parameter overrides, select Remove overrides, and then select Save.
  7. Change the application type of the load group from Desktop to Browser (optional). Complete this step after your first dry run, using the dry run report. For details, refer to Executing performance scenarios.
    Note:

    You can change the application type only from Desktop to Browser, and only after a dry run has completed. The change applies to the load group that you edit. For example, an automation that fetches data from Excel can be detected as Desktop even though it runs in a browser.

  8. Specify how the load is applied over time. Together, these settings let you model realistic traffic patterns such as gradual adoption, steady-state usage, and controlled shutdown.
    • The Delay field shows the wait time before the load group starts execution (for example, 0 minutes).
    • The Ramp up field shows the period over which the number of concurrent users is gradually increased until the maximum number of users is reached (for example, 2 minutes).
    • The Peak field shows the duration during which the maximum number of users remain active (for example, 26 minutes).
    • The Ramp down field shows the period over which the number of users gradually decreases to zero (for example, 2 minutes).

Result​

The load group settings are saved. The scenario is configured with the defined virtual users, performance thresholds, data sources, and load profile. You can proceed to run a dry run or full execution.

  • Steps​
  • Result​

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated