Structure of a User Path

A User Path in NeoLoad is organized into three components: Init, Actions, and End containers. Each plays a specific role in the Virtual User's performance test scenario.

Init container

The Init container prepares the environment at the start of a session. This container only runs once at the start of the Virtual User's session. For example, when you log into an application, you see all the required web pages and interactions grouped in this container.

Actions container

The Actions container is central to the User Paths that holds repetitive actions performed during the Virtual User's session. These actions run repeatedly until the session ends.

You can control whether the browsing data, such as cookies and cache, resets after each iteration or is maintained between iterations with these Runtime parameters options:

• Yes: The browsing data always resets after each iteration.

• No: The browsing data is conserved between two iterations of the Actions container.

• Auto: The browsing data resets after each iteration if the Init container is empty.

Note: If the Init container is empty, NeoLoad automatically resets and simulates a new browser after each iteration, unless you've customized otherwise in the Runtime parameters.

End container

The End container wraps up the User Path by running the last steps necessary to end the session. For example, this runs to log out of an application where the associated web pages are grouped together.