Screen size changes automatically while running the test cases !

[Gaurav]

Hi Team,

I had been using Telerik for UI automation but never faced this type of issue earlier. So the problem is while recording the test the screen doesn't changes but while running or testing the same test case screen size changes unexpectedly which results in failed step as after the screen changes the location of the elements also changes.

PFA - Actual Image & Expected Image.

[Plamen Mitrev]

Hi Gaurav, I am sorry to hear about the issue with test automation. I have some follow up questions to help me understand the misbehavior better, so I can advise you. 

It looks like there is a navigation panel on the left side, which can be collapsed or expanded. What would cause this panel to collapse in the middle of the test? Maybe a mouse click in the wrong position or against the wrong element could be doing that during the test execution. That would explain the incorrect coordinates for the rest of the elements in that area of the application and we need to understand which actions might be doing that and fix it.

Please enable the annotations for quick execution and run the test again. Observe the mouse and annotations a few times and let me know if you noticed something unexpected or different than what you would do manually. If you can record a short video and provide a sample Web test (.tstest, .resx and .imgstore files of the test) that would be helpful. 

Thank you!

[Gaurav]

Hi Plamen Mitrev,

It is not possible to share the test file as the test file contains confidential data, however I am adding the recorded video of the problem along with " annotations for quick execution " option enabled.

In the video the screen gets shifted to the left as we try to click on "Attribute Bases Data Management" Button. If you need to look into live execution of the test we can have meet session for that.

Link to the video - https://drive.google.com/file/d/1px4-NqGE_EKfjnMysE_HJJqsI_zT_dXc/view?usp=sharing.

Thank you!

[Plamen Mitrev]

Hello Gaurav,

I watched the video during test execution, but unfortunately I only see the failing moments without the steps before that. It is possible that the desktop mouse click did not happen as expected and it caused this misbehavior. Can you record a more extended video of the whole test or at least several steps before the issue?

In the end, the test runner did click on the "Attribute Bases Data Management", but the whole middle section of the application was shifted to the left. My suggestion is to disable the "SimulateRealClick" on the step that clicks on the "Attribute Bases Data Management" button. As a result, Test Studio will not try to scroll and should not move the elements.

If the above suggestion works, this is not a permanent solution, but part of the troubleshooting process. Unfortunately, in order to provide more details and resolve this issue, I will need access to the application under test or a demo page that reproduces the same behavior.

I am looking forward to your reply and details about the outcome from the suggestion.

Regards,
Plamen Mitrev
Progress Telerik

[Gaurav]

Hi Plamen Mitrev,

I am not getting the option to disable "Simulaterealclick" on that step. I have attached the image of options that is visible on

that particular steps.

Link to the full execution video - https://drive.google.com/file/d/1IGt23BgG-XQfhE6jVp8gAm7T_BcAJZFa/view?usp=sharing.

I think it would be better if we can get on a call (google meet or zoom call) and look into the issue ?

Just let me know if it is possible for you to get on a call today ?

[Plamen Mitrev]

Hi Gaurav, 

I did not realize that the recorded steps are actually desktop left click actions. In this case, you can disable the "Focus" option and run the test again to see if there is a difference in the behavior.

It would be better if you submit a private technical support ticket, where we can continue our discussion. It seems that the issue is specific to the application under test and how it behaves when there is "Scroll To Visible" action in particular. You can provide additional details in the private ticket, which will help me understand why this happens. Once we have explore the misbehavior further, we can plan our next steps or a call later on.