Highlight Elements loses focus when trying to mouse to Quick Steps/JavaScripts Events/Mouse Action/Scroll Actions

Hello Barry,

This seems to be an issue related to your specific application. Would it be possible to provide us access to the tested page so that we could reproduce the issue in our source code debugging environment? If this would not be suitable I would like to ask you to capture Fiddler trace against the problem page and provide it along with the script itself. We have about 75% success rate using Fiddler trace to simulate your web server and reproduce the faulty behavior. 

Here is what you need to do to get this trace. 
1) Start Fiddler - note no browser should be open
2) Click Clear Cache
3) If your site uses HTTPS click Decrypt HTTPS traffic
4) Start Capture
5) Launch a browser
6) Navigate to the problem page and pop up.
7) Stop Capture
8) Save Capture
9) Put the .SAZ file into a .zip file and attach that to this support ticket

Thanks in advance for the cooperation. I hope to hear from you soon. 

Regards,
Elena Tsvetkova
Telerik by Progress

Thank you for responding. Based on a different response i have removed all Test Studio Chrome plug-in and reinstalled only the three approved by Chrome. The issue still exists. I found a public site where this is happening when I have Highlight Elements enabled. www.cabelas.com. I have attached a simple TS test script i recorded where the sub menus for the Highlight Elements disappear. It happens starting at step 8 of the script. Hover over the image for Big Game (pants) or Scent Control until the element popup is displayed. Then try to navigate to Quick Steps. About the time the Quick Steps flyout starts to display the whole pop up disappears. 
After this happens you will notice the red box used to select an element no longer appears. Click off into a blank space of the web page and the red box will start appearing again. I have attached the .resx & .tstest files for reference.

Thank you,

Barry

Additional configuration info. My PC is running Windows 8.1 pro 64 bit. I am testing with Chrome 32 bit and Firefox 32 bit. 

Hi Barry,

Thank you for the script.

Unfortunately, I couldn't reproduce this issue. Please, make a short video (using Jing) - how to reproduce and share its link.

This problem could be due to your DPI settings. Check and adjust it according the documentation, please.

I hope to hear from you soon.

Regards,
Nikolay Petrov
Telerik by Progress

Did anyone find a solution I am having same issue I am using TestStudio 2017 and running it in Ie against our servicenow application

Hi Radha,

Did you try to adjust the DPI settings as it is described in this article?

What type of monitor do you use? Is it Ultra High Definition one?

Regards,
Nikolay Petrov
Telerik by Progress

I was never able to get this to work in Chrome. As a work around I can get it to work in Firefox 43. Our application uses Angular.

Hi Barry,

I could not reproduce the problem using the provided test script and product version 2017.1.207. I suppose that the application is changed during the time. Would you record and provide new test that could reproduce this problem with the latest product version? 

Thank you for your cooperation.

Regards,
Nikolay Petrov
Telerik by Progress

I encountered the same issue. Test Studio does not execute any actions or activities from the Fly out menu. any help??

Thanks,

Phanel

Hello Phanel,

Thanks for reaching us out. 

In regards the Fly Out menu I guess it appears only when you hover over the mouse. Please double check if you have inserted Hover Over steps where necessary to ensure the menu is visible when you want to select anything from it. Hover over step is available in the Step Builder under Mouse actions section. 

For the links you mentioned are not being executed I suspect the find logic of the target elements might not be correct - please verify if it is necessary to edit the find expression. Please also use the execution log to better understand what is going wrong and why the test fail to click on any of the links. 

You could also perform the execution with annotations turned on (please see point 5. in this article) to better evaluate what could be possibly wrong. If the element could be found on page you might need to enable simulate real click. 

I hope the above information will be useful for you. Thanks for your cooperation! 

Regards,
Elena Tsvetkova
Progress Telerik