Load Balancing for Local Test Environments
With Katalon TestOps, your tests can be executed in parallel using load-balanced configurations.
To do so, Katalon TestOps distributes Test Executions over Agents to optimize Remote Execution efficiency.
Each Agent can be configured with a unique Threshold. Test Executions can then be setup to minimize Agent idleness.
You have at least one active Local Test Environment. See: Create a Local Test Environment with an Agent.
Configure an Agent's Threshold
An Agent's Threshold is the maximum number of sessions that an Agent can execute concurrently in a Local Test Environment.
You must configure the Threshold value to assign the number of jobs to an Agent.
By default, the Threshold value of all Agents is set as 1.
To configure an Agent's Threshold, follow these steps:
Sign in to Katalon TestOps and go to your Project.
Go to Configurations > Test Environments.
The Test Environments page appears.
Click on the Local Test Environment you want to configure the Agent's Threshold for (e.g., My Agent).
The Agent Details page appears as below.
Update the value in the Threshold section.
The maximum number of concurrent sessions that an Agent can execute is equal to the Threshold value you have configured.
You can check the sessions in the Test Environments page.
Assign an Agent to execute Test Runs
For a new Test Plan
You can create a new Test Runs Schedule to assign an Agent for Test Executions. See: Schedule Test Runs.
When creating a new Test Runs Schedule, you are asked to select Test Environments.
You can select an Agent here to assign it to your new Test Plan.
For an existing Test Plan
Go to your Project > Test Planning > Test Run Types.
Click on a Test Run Type (e.g., a Verify Match exact name).
The Test Run Type page appears as below (e.g., Test run type: a Verify Match exact name).
Scroll down to the Select Test Environment section.
In the Test Environments section, select a new Agent.
- You can reassign old Test Run Types or assign multiple new Test Run Types to any configured Agent.
To check the Test Execution process, go back to the Test Environments page.