Transactions

In this section you will learn how to split a journey into named transactions, timed separately when it runs in Mugnsoft.

What a transaction is

A journey such as search a product, add it to the basket, pay is made of stages that do not take the same time and do not fail for the same reasons. A transaction names one stage: the steps between a start transaction and the matching stop transaction.

When the test runs as an EUM monitor in Mugnsoft, each transaction is timed and graded on its own thresholds, so a report tells you which stage is slow, not only that the journey is. In Pulse, transactions structure the test: the command list draws a bracket around each one, and Collapse All Transactions in the step menu folds them to show the outline of the journey.

Add a transaction

1. Select the first step of the stage, right-click it and choose Insert Command.
2. Set Command to start transaction, Target to the transaction name, for example addToBasket, and Value to its thresholds and description.
3. After the last step of the stage, add a stop transaction step with the same name as Target.

The Value of start transaction holds the major threshold, the critical threshold and a description, separated by commas, the description between single quotes:

3.0,5.0,'add the product to the basket'

The first number is the major threshold, the second the critical threshold. When they are left out, the deployed script uses 1.2 and 1.5, and the transaction name as description.

Rules

• Every start transaction needs a stop transaction with the same name.
• Close a transaction before starting another one with the same name.
• Give each transaction a name that is unique in the test and stable over time: the name is what Mugnsoft charts the transaction under.

See also

• Deploy to Mugnsoft — run the test as an EUM monitor
• Thresholds — thresholds on the whole test in Pulse
• EUM Monitor — how Mugnsoft runs and reports the test

Translations

• fr: Transactions