...
- Add the machine to the Machines area of the Load Tests tab.
- Configure one or more scenarios to run tests on remote machine.
- Start the remote machine as a Load Test ServerAgent.
After you have performed all these steps, Load Test will run tests on the remote machine whenever it executes a load test scenario that is configured to involve that machine.
...
- Refresh: Click to find all Load Test Windows service installations on the local network. A table displays the attributes of each remote machine installation and is sortable by column title. The following is displayed in the table:
- Host: Displays the name of the remote machine.
- Process State: Displays whether the Load Test Server Agent process is running or not running.
- Process Port: Displays the port number on which the Load Test Server Agent is listening.
- Check Process State: Click to view the process state of the selected machine.
- Start: Click to start the Load Test Server Agent process on the selected remote host.
- Stop: Click to stop the Load Test Server Agent process on the selected remote host.
...
A Load Test controller machine (the one that runs in the GUI mode and from which you control the load test) can use a Load Test server Agent machine located on a different network if the network equipment that bridges these networks allows communication on the port that the Load Test server Agent machine is listening on.
For example, if you run your Load Test controller on network A and your Load Test server Agent is started on port 10095 by a “lt -loadtestserver agent 10095” command on network B, you need to make sure that the communication on port 10095 between the networks A and B is not restricted by your network equipment.
...
- Allow the TCP traffic exchange associated with the port on which the Load Test server Agent is listening between networks A and B ("open the port").
- Lift, remove, or disable any protocol filters that may prevent the TCP communication associated with that port between networks A and B.
...
If your Load Test controller (master) is running on a machine with a Japanese or Chinese locale and you have remote machines in your Load Test configuration, the remote machines must have the same locale as the master machinecontroller machine. This is required to enable Load Test to properly process local resources after they have been transferred to a remote machine and vice versa.
...
| Code Block |
|---|
./loadtest -J-Duser.language=ja -J-Duser.region=JP -loadtestserveragent |
On Windows:
| Code Block |
|---|
./lt -J-Duser.language=ja -J-Duser.region=JP -loadtestserveragent |
Running the Test from the GUI
Starting the Load Test
...
Agent
The remote machines must be running the Load Test Server Agent whenever you want to execute load tests on these machines.
To start the Load Test Server Agent from the GUI (Windows only):
- Go to Start > Programs > Parasoft > Load Test > Load Test ServerAgent.
Running Load Tests
After you have started the test machines in Load Test server Agent mode, you can start your test by clicking Load Test in the client machine’s toolbar.
...