Scenario Duration and Phase Ending Events

In LoadGen Load & Performance Testing we have several features to build your perfect load or performance test.

Scenario Duration

With the Scenario Duration you set the total run time of the test. The duration time count will start at the beginning of a test and will run for all users together or each individual user. If the duration time is due, the sessions can either be logged off or disconnected.

Scenario Duration supersedes the Phase Ending Events

A Scenario Duration supersedes the Phase Ending Events no matter how many events you would like to trigger.

Phase Ending Events

The Phase Ending Events can be used to control the end of a Phase. If you don't have any Phase Ending Events and no active Scenario Duration the test will stop directly after all users are initialized. In this case the test will stop immediately and sends a stop test command to all LoadGen Agents, resulting in a Disconnect of all your sessions. We offer the following Phase Ending Events:

  • OnUserConnected - Windows event, the user has connected
  • OnUserDisconnected - Windows event, the user has disconnected
  • OnUserLogonSuccessful - Windows event, the user has logged on
  • OnUserLogonFailed - Windows event, the user has not logged on
  • OnSendLogonSuccessful - LoadGen event, the user flow has triggered the logon successful event
  • OnSendLogonFailed - LoadGen event, the user flow has triggered the logon failed event
  • OnScriptSuccessful - LoadGen event, the user flow has successfully completed
  • OnScriptFailed - LoadGen event, the user flow has failed
  • OnErrorMessage - LoadGen event, an error from the user flow is triggered

The Phase Ending Events are collected for each user in the Phase. If all of the users receives on or more of the selected Events the Phase will signal a successful ending and will continue with the next Phase or ends the test. 

Be careful with Phase Ending Events and multiple Phases

If you have multiple Phases you must be aware that the default Phase Ending Events on a Phase can block the rest of your test Phases. Especially the OnScriptSuccessful event could take a long time to finish and therefor will take a long time to continue with the next Phase. 

Was this article helpful?
0 out of 0 found this helpful