...
You can run load tests on a remote machine from the command line by starting the remote instance of Load Test in Agent server mode and running a project with the local instance of Load Test that is configured to run the tests on the remote Agentserver.
Starting Load Test in
...
Server Mode
Use the -agentloadtestserver flag and specify the port number to enable the Load Test to run remotely. The port number is the local machine's port on which the Agent server is listening. If no port is specified, the default port of 8189 is used.
| Code Block | ||
|---|---|---|
| ||
lt -agentloadtestserver [PORT] |
| Code Block | ||
|---|---|---|
| ||
./loadtest -agentloadtestserver [PORT] |
Configuring a Remote Project
...
The machine that runs in GUI mode and provides the interface for controlling the load test is the Load Test controller machine. The controller can communicate with a Load Test agent server machine located on a different network network if the network equipment that bridges these networks allows communication on the port that the Load Test agent server machine is listening on.
For example, if you run your Load Test controller on network A and your Load Test agent server is started on port 10095 by an lt -agent loadtestserver 10095 command on network B, the communication on port 10095 between networks A and B must not restricted by your network equipment. Allow any TCP traffic exchange for that port. Talk to your system or network administrator about the network configuration issues.
...
The following commands allow you to start the Load Test agent Server and run load tests:
Load Test Command Line Options
...
| Option | Description | ||||
|---|---|---|---|---|---|
-cmd | Starts Load Test in command line mode. Required to run Load Test locally. | ||||
-run | Specifies the Load Test script to run. Required to run Load Test locally. | ||||
-help | Shows help information. Does not run testing. | ||||
-agent [PORT] | Starts the Load Test Agent on the default port 8189 unless another port is specified. To start the Load Test Agent on port 8999, for example, you would specify the port number in the command line argument such as:
| licenseServer <BASE_URL> | Specifies the base URL for the Parasoft License Server. By default, Load Test requests a license from the server | -licenseServer <BASE_URL> | Specifies the base URL for the Parasoft License Server. By default, Load Test requests a license from the server configured in the GUI, but this option enables you to dynamically request a license. Optional. |
-licenseUsername <USERNAME> | Specifies the username associated with the license on the Parasoft License Server. If this argument is not specified, no authentication is used. Optional. | ||||
-licensePassword <PASSWORD/ENCODED_PASSWORD> | Specifies the password or encoded password associated with the license on the Parasoft License Server. Passwords may be encrypted with AES 256-bit encryption using the soatestcli -encodepass command line option. If this argument is not specified, an empty password is used for authentication. Optional.used for authentication. Optional. | ||||
-licenseVus <VALUE> | Specifies the number of virtual users allowed by the license requested from the server specified with the -licenseServer option. You can specify an integer value or unlimited for unlimited virtual users' licenses. | ||||
| Starts the Load Test Server on the default port 8189 unless another port is specified. To start the Load Test Server on port 8999, for example, you would specify the port number in the command line argument such as:
| -licenseVus <VALUE> | Specifies the number of virtual users allowed by the license requested from the server specified with the -licenseServer option. You can specify an integer value or unlimited for unlimited virtual users' licenses. | ||
-password <LONG_PASSWORD_STRING> | Specifies a node-locked license to pass to Load Test. | ||||
-reserialize | Specifies a file path to Load Test assets that you want to reserialize into a different file format. See Reserializing Assets for more information. | ||||
-J<JVM_OPTION> | Specifies additional JVM options to pass to the Load Test JVM. (Note that there is no space between the Examples:
|
...
- Open a SOAtest workspace that has the project file format you want to reserialize your assets to. The project file format of the workspace isdefined in the workspace's Misc preferences.
- Close SOAtest.
- Run Load Test from the command line with the
-reserializeoption, specifying the directories directory containing the assets you want to reserialize.
The -reserialize option is used to specify a list of directories directory containing Load Test assets to reserialize. It will automatically use the project file format of the SOAtest workspace most recently opened. This option takes a single argument with a list of file system paths. To specify multiple paths, use the default path-separator character for your OS (semicolon for Windows or colon for Linux/Mac). The paths you specify do a file system path. The path you specify does not have to be in the SOAtest workspace providing the project file format, but matching files will be reserialized to that workspace's default format.
...
| Code Block |
|---|
lt.exe -cmd -reserialize <PATH_TO_ASSETS_FOLDER_1>;<PATH_TO_ASSETS_FOLDER_2>FOLDER> // Windows ./loadtest -cmd -reserialize <PATH_TO_ASSETS_FOLDER_1>:<PATH_TO_ASSETS_FOLDER_2>FOLDER> // Linux and macOS |
This option will reserialize .lt, .ltp, .metric, .ms, and .rpt files. However, .rpt files are always serialized as binary, not to the configured project file format.