To effectively simulate business traffic, you can use commands to change and manage the performance testing behaviors and processes in sessions. The commands include data commands, data export commands, conditional jump commands, think time commands, and rendezvous point commands.
Commands
The following table describes the Performance Testing Service (PTS) commands.
Command category | Description |
Allows you to specify a parameter from the global parameter file as the base column to maximize the use of all available data in the parameter file. You can also specify a parameter in a secondary definition file, which is applicable only to the current session. | |
Before you provide the output parameters of a preceding API to the succeeding API in the same session, you can execute one or more data commands to perform secondary processing on the output parameters of the preceding API, such as concatenating strings or executing encryption functions. Data commands can also be used to further process parameters exported by using data export commands. | |
Exports data such as cookies, export parameters, and parameters defined by data commands from a session for use in other sessions, which facilitates global data sharing. | |
Allows you to define multiple conditions that determine which APIs to execute. | |
Modifies the execution path of the requests of 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. You can combine conditions by using AND relationships. All specified conditions must be met to trigger an action. If none of the defined conditions are satisfied, the default action is executed. You can add additional conditions by using OR relationships with existing conditions. | |
Calls API operations or runs commands a specified number of times to simulate real business traffic. | |
Postpones the execution of a session for a specified period of time. The countdown begins at the time when the testing begins. The session is executed after the specified period ends. | |
Simulates the time that a user spends on thinking and reacting between two actions in the performance testing process, and supports various modes. | |
Specifies a rendezvous point at which virtual users wait until the conditions are met before they all proceed together. This is particularly useful in scenarios like flash sales. You can configure the rendezvous point based on time or the number of virtual users. |