DPI settings different from 100% in Windows 7 cause Chrome execution to misclick Desktop clicks

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 22 Jul 2019 09:58 by ADMIN

Lisa

Created on: 22 Mar 2019 16:08

Type: Bug Report

DPI settings different from 100% in Windows 7 cause Chrome execution to misclick Desktop clicks

Changing the DPI settings to 125%, for example, on Windows 7 causes troubles with the Desktop clicks when running tests against Chrome. The click is below or above the target element. Highlighting in record mode may also be affected.

Workaround: As a workaround the Desktop clicks (MouseClick() method) can be replaced with the Click() method, which works as expected. The alternative in a non-coded solution is to disable the 'SimulateRealClick' option for the click steps.

3 comments

ADMIN

Elena

Posted on: 26 Mar 2019 08:51

Hello Lisa,

Let me, please, share some additional details to better describe the situation and what options there are to use Test Studio with different DPI settings. In the past it was a requirement to set the scaling to 100% as no other settings were supported. However, last year in our 2018 R3 release (release notes here) we managed to implement changes, which allows using different DPI settings and Test Studio is no longer affected by this limitation.

Having that said, the current reported issue is related to Windows 7 and Chrome specifically - the rest of the browsers for Windows 7 and all browsers for Windows 10 work as expected despite the applied DPI settings for the display. The issue needs to be analyzed by the development team and this is the item, which you can follow for further news on the progress of investigation.

Thank you for your understanding in advance!

Regards,
Elena Tsvetkova
Progress Telerik

The New Release of Telerik Test Studio Is Here! Download, install,
and send us your feedback!

Lisa

Posted on: 22 Mar 2019 16:21

You response is not helpful. Many people use the app at higher DPI settings than 100%. Not being able to run tests at higher DPI values makes your automation inferior to other products.

Also, your response doesn't answer the issue at all. I never said there was a problem at 100% I said there was a problem at 125%.

Are you trying to say that Telerik has no interest in supporting higher DPI settings? Because Selenium works at higher DPI settings.

ttsts

Posted on: 22 Mar 2019 16:17

If the DPI settings is set to 100%, any tests will work as expected against Chrome