Structure of a User Path
A User Path is composed of three Containers: Init, Actions, and End.
Init Container
An Init Container groups together all the various web pages required to initialize the User Path. An Init Container is always executed once at the Virtual User start. A typical example of this type of Container is the set of web pages used to log the user in to the application.
Actions Container
An Actions Container groups together the elements that are repeatedly executed during a Virtual User runtime until the user stops.
By default, if both Init and End containers are empty, NeoLoad automatically resets the user session and simulates a new browser after each iteration. You can change this default behavior in the Runtime parameters when the Actions Container is selected in the User Path tree.
In Runtime parameters...
| Yes | browsing data (session, cookie values and Virtual User cache information) is always reinitialized after each iteration. |
| No | browsing data is conserved between two iterations of the Actions Container. |
| Auto | browsing data is reinitialized after each iteration only if both Init and End containers are empty. |
End Container
An End Container groups together the elements executed prior to a Virtual User execution end. An End Container is always executed once when the Virtual User execution stops. A typical example of this type of Container is the set of web pages used to log the user out of the application.