If there are many steps in a sessions, it might be useful to consider them as separate steps, so that one can build and analyze them one at a time.
So, a step can be a click, a page, or a specific sequence of steps that logically belong to one single transaction, for example the login.
Multiple transactions can be combined sequentially to form more complex scenarios. They can also be used as a common step in different sessions. For example, in an application where login is required, that step can be re-used for all the different scenarios that need to be tested.
This format is also preserved when analyzing results. The overview page will provide metrics for the complete sequence, and tabs representing the individual steps, will provide similar metrics for that specific transaction.
CREATE MULTIPLE TRANSACTIONS
Multiple sequences of transactions are managed by the MULTI-SESSION manager.
Each transactions is just a regular session, that can be created using DiveTrace, DiveProxy or directly imported from Postman. In order to create a sequence of sessions, at least two sessions need to be already present in the account. A sequence of sessions is created by clicking on the SESSION button, located in the navigation bar of the page, and select the Multi Session submenu, as shown in the figure below.
For more information on how to create a Sequential Multisession, please check the Sequential Multisession help page.
The new combined session will show up in the Multi Session table. All the sub-sessions that are part of it are listed in chronological order, as shown in the image below.
Individual sessions can be then combined and re-used for different multisession, as shown in the example below, where the same logindc session used in the FullTestScenario above is now used for a different set of steps.
For more information on how to use Sequential Multisessions, how to create a test plan and analyze results, please check the Sequential Multisession help page.