Use the Transaction operation to mark the beginning of a user-defined transaction.
|Number of occurrences:||Unlimited.|
|Parent operations:||Any other operation. If the scenario editor displays pages and connections, the operations cannot be placed between connections.|
|Child operations:||The operation cannot have child operations.|
The Think Time edit box at the top of the editor specifies the number of milliseconds the operation will wait for the run. See Setting Delays Between Operations.
The SLA edit box at the top of the editor specifies the maximum acceptable duration of the operation, in milliseconds. For transactions, it indicates the time it takes to execute a transaction completely.
This page provides summary information on the operation like the number of found errors, the list of variables used, and so on. Information on the page is read-only.
You can find information on issues in operation properties in the Summary page. Also, information about the erroneous settings is displayed in the editor’s header area.
Transaction is a paired operation: every Transaction operation must be followed by a matching End of Transaction operation.
The matching pairs of the Transaction and End of Transaction operations must be in the same scenario. You can use these operations in complex scenarios, but you cannot place the Transaction operation in one subscenario and the matching End of Transaction operation in another subscenario.
Transactions may overlap or contain one another.