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.
Transaction start and end are linked not only to a start step and end step, but to events you specify within the steps. Therefore, a transaction does not necessarily begin at the start of a step or end at the end of a step.
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.
Tip: When a transaction start or end is moved to another step because the start or end step is deleted, the start or end event is reset to the default.
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 TC.startTransaction (name) and TC.endTransaction(name, status).
You can add transactions for steps that are adjacent by using the transaction editor.
To access the Transaction Editor, click the button from the TruClient menu bar, or press Ctrl + Alt + F7.
User interface elements are described below:
Adds a new transaction.
Deletes the selected transaction.
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: . , : # / \ " < @ &.
The step and the event that marks the start and the end of the transaction.
An event can be one of the following: