Idea ID: 1683004

Add an option to restart a failed virtual user load during a run time

Status: Delivered

This option will allow users to achieve the desired virtual load even when some virtual users have failed.

If you were designing the solution, how would you do it?

Add a button to restart virtual users.

Parents
  •  , We have purchased a VUH license with LR Cloud.

    We are testing a SAP GUI application configured with Zscaler on on-premise load generators. We observed Zscaler going in idle state in machines after 10 min because of which tests which had ramp up time of all users greater than 10 min started having failed Vusers after 10 min duration. As a result, we have to abort the test which wastes VUH license. We have to keep accessing LG machines once in every 10 min duration throughout the ramp up period so that we don't get failed Vusers. Having the leverage to restart a Vuser would have avoided license wastage in such instances.

    The problem is also with Vusers distribution during test in LR Cloud. Vusers are assigned to first LG and when that limit is over, then next set of Vusers are assigned to next LG. Because of this, some LG's don't get covered in the initial 10 min of ramp up  stage and thus Zscaler in those machines goes in idle state and needs reauthentication and the moment a vuser is assigned in running stage to those machines, it fails.

    We can also configure the reauthentication timeout in Zscaler but vusers can fail due to n no. of reasons during ramp up.

    My last test was planned for 250 users but 25 failed in ramp up and just because I couldn't restart those failed vusers, I had to abort and there was a license wastage for the time test was executed.

Comment
  •  , We have purchased a VUH license with LR Cloud.

    We are testing a SAP GUI application configured with Zscaler on on-premise load generators. We observed Zscaler going in idle state in machines after 10 min because of which tests which had ramp up time of all users greater than 10 min started having failed Vusers after 10 min duration. As a result, we have to abort the test which wastes VUH license. We have to keep accessing LG machines once in every 10 min duration throughout the ramp up period so that we don't get failed Vusers. Having the leverage to restart a Vuser would have avoided license wastage in such instances.

    The problem is also with Vusers distribution during test in LR Cloud. Vusers are assigned to first LG and when that limit is over, then next set of Vusers are assigned to next LG. Because of this, some LG's don't get covered in the initial 10 min of ramp up  stage and thus Zscaler in those machines goes in idle state and needs reauthentication and the moment a vuser is assigned in running stage to those machines, it fails.

    We can also configure the reauthentication timeout in Zscaler but vusers can fail due to n no. of reasons during ramp up.

    My last test was planned for 250 users but 25 failed in ramp up and just because I couldn't restart those failed vusers, I had to abort and there was a license wastage for the time test was executed.

Children
No Data