To start the test,

  • click Run on the Workflow Tree toolbar (a).


  • click Run and Monitor Test (b) on the Workflow Tree.

If you wish to change the test profile to execute, select a new test profile from the Profile dropdown (c). 

Optionally enter a Test Run Name (d) and a Test Run Description (e) for the current test run. By default, the Name will be the current Test Profile Name, and the Description will be the Test Profile Description.

Info: Test Run Name and a Test Run Description appear on the test reports and help to identify past test runs. If starting the test from the command line, the Test Run NAme and Test Run Description can be specified as command-line arguments

To run the test in debug mode, check the Debug mode box (f) and then click Run Test (g).

While running a test in debug mode, all replayed sessions will be displayed in the session grid, and response bodies will not be purged for more accessible diagnostics.

Note: Debug mode requires more hardware resources on the test machine and should be used only for test troubleshooting. It is not recommended to debug tests with many VUs. It is not available during distributed tests.

The Test Mix group (h) will show a table with all test cases (or test case groups) and the corresponding mix weights (i) and VU distribution (j). The Mix Weight column may be modified to change the number of VUs that each test case will execute. 

Note: If you are running a distributed test, then the VU distribution group (h) will look different, as described here.

Distributed test

If running a distributed test, the remote load agents must be initialized before the test starts. The load agent initialization grid will display the initialization progress for every load agent.

Agent (a)The agent name
Status (b)The current initialization status, such as copying a file or loading the test script
Progress (c)The initialization progress

Press the Stop button (d) to abort the agent initialization progress and cancel the test.


Starting from v5.8, the load agents in a distributed test are initialized in parallel. This speeds up the start time of a test, especially ones with multiple load agents.

  • No labels