Share this page
A transaction measures the time between two points in a business process. This topic describes how to use transactions in your scripts.
About using transactions
Add transactions so that you can analyze the time spent in different sections of the process after running the test.
For example, a transaction might start when sending credit card information and end when receiving authorization.
When you delete a step that contains a transaction start, the transaction start is moved to the next step. When you delete a step that contains a transaction end, the end is moved to the previous step. If a transaction starts and ends in the same step, the transaction is deleted when the step is deleted.
Transactions for steps are not sequential. You can use the same transaction name in different sections of the script to join the times of actions that are not one after another. To use the same name in different places, use TCA.startTransaction(name) and TCA.endTransaction(name, status).
You can add transactions for steps that are adjacent by using the Transaction editor.
Transaction editor
To access the Transaction editor, click Transactions editor in the TruClient Toolbar.
User interface elements are described below:
| UI Element |
Description
|
|---|---|
|
Adds a new transaction.
|
|
Deletes the selected transaction.
|
| Name |
Enables you to edit the name of the transaction.
Transaction names must be unique and may contain letters or numbers. Do not use the following characters: . , : # / \ " < @ &. |
| Start/End step
|
The steps that mark the start and the end of the transaction.
|
See also:
