search

Blazemeter / CitrixPlugin

A repository for the Citrix Plugin for JMeter
Apache License 2.0
11 stars 2 forks source link

Enhancement: asynchronous catch windows #62

Open XerOpsNL opened 1 year ago

XerOpsNL commented 1 year ago

Een Appl Under Test sometimes has asynchronous windows, for example: an error dialog for example witch apear without any perticulair user interaction. You cant "catch" these windows, a Citrix Interaction block met End Clause is useless, there is no predefined user interaction

3dgiordano commented 1 year ago

Thanks for the suggestion.

We will evaluate the possibility of incorporating a mechanism that allows us to react to this type of event.

Madeppa commented 1 year ago

Hi @3dgiordano,

Could you please us know any update on this to catch asynchronous windows or error dialog?

3dgiordano commented 1 year ago

Hi @Madeppa

The concept of asynchronous windows, are windows that appear at times when a script does not wait for those windows to appear.

Today the way to solve this is to incorporate defensive programming into the test plan.

Module Controller is usually incorporated to reference logic to be repeated for the detection of the window and its actuation, in general with an approach to resolve closing it in a controlled way so as not to affect the flow of the main script.

These problems happen in any type of functional script in any type of language and are not usually easy to solve, simply because a popup can appear just at the moment when an action is going to be carried out or when it is being carried out.

Not all applications have this type of behavior and in general those who use the plugin and need to solve it, by learning to perform detection tasks and actions, tend to solve it.

In the future, there are plans to incorporate actions to be carried out previously before carrying out any action, to make it easier to reference the detection and actions to help to try to solve it, so that flows can be run that resolve these difficulties.

Today the option you have is to use the Module Controller before each action or in those actions where an unexpected window prevents them from doing the action.

Currently this request is marked as an improvement suggestion that would be nice to have so that users have to define fewer elements in the test plan.

But currently there is no impediment for users to program their own control logic when a window appears, using the text or image detection mechanism to take action on them.