Why does the "Stop Virtual User" logical action disappear from version 4.1?

In NeoLoad 5.5, designing complex test cases is quick and easy. All User Paths contain now the Init/Actions/End immutable Containers allowing easy design for long scenarios. All elements inserted in the Actions Container are repeated until the User Path stops at which point End container actions are executed before finishing the scenario.

With this User Path structure, the former Stop Virtual User logical action has been replaced by the logical action Go to next iteration. This action interrupts the Virtual User runtime and makes it go to the next iteration which is almost similar to the former Stop Virtual User logical action. The way the Go to next iteration action behaves depends on where it is placed within the User Path:

• In an Init Container, the User Path interrupts its initialization and starts its first iteration by running the Actions Container.
• In an Actions Container, the User Path interrupts its current iteration and runs (depending on the load policy):
  • a new iteration by running the Actions Container,
  • its End Container.
• In an End Container, there is no interruption. The User Path continues to run its End Container and an error message is written to the log files.

The Go to next iteration logical action can be particularly useful in combination with an If ... Then ... Else or Try...Catch action. For example, this makes it possible to:

• avoid running the Init Container for a Virtual User that is already logged on to the application
• restart a User Path iteration if an error occurs

As a result, the Go to next iteration logical action is almost similar to the former Stop Virtual User one. The only difference is that when the User Path restarts an iteration, the container Init is not executed. When in the User Path, with the Go to next iteration, to have the Virtual User log out and log in again, it is necessary to:

• insert the login process at the beginning of the Actions container to have the same behavior as until version 3.2, or
• insert the logout/login process before going to next iteration (using a shared Container to avoid duplicating action).

Home