Commands let you control performance testing behaviors and processes within sessions to better simulate business traffic. Available commands include data commands, data export commands, conditional jump commands, think time commands, and rendezvous point commands.
Commands
The following table describes the available Performance Testing Service (PTS) commands.
|
Command category |
Description |
|
Specifies a parameter from the global parameter file as the base column to maximize the use of all data in the parameter file. You can also specify a parameter in a secondary definition file, applicable only to the current session. |
|
|
Performs secondary processing on the output parameters of a preceding API before passing them to the succeeding API in the same session, such as concatenating strings or running encryption functions. Data commands can also further process parameters exported by data export commands. |
|
|
Exports data such as cookies, export parameters, and parameters defined by data commands from a session for use in other sessions, enabling global data sharing. |
|
|
Defines multiple conditions that determine which APIs to execute. |
|
|
Modifies the execution path of requests in a session based on the output parameters of an API. Supported actions include jumping to a different path, continuing along the current path, or ending the process. Conditions can be combined with AND relationships, where all conditions must be met to trigger an action. If no conditions are satisfied, the default action runs. You can also add conditions with OR relationships. |
|
|
Repeats API operations or commands a specified number of times to simulate real business traffic. |
|
|
Postpones the execution of a session for a specified duration. The countdown starts when the test begins, and the session runs after the specified period elapses. |
|
|
Simulates the time a user spends thinking and reacting between two actions during performance testing. Multiple modes are supported. |
|
|
Sets a rendezvous point where virtual users wait until the specified conditions are met before proceeding together. This is particularly useful for scenarios such as flash sales. You can configure the rendezvous point based on time or the number of virtual users. |