Hi Tanya,
I have experienced a similar issue to what other users in this thread have expressed.
I am running TC 10.40 on Windows 7 Professional 64-bit, and updated Chrome from 37 to 38 on the stable channel last week. (After the update, I ensured the extension was still enabled, and it was.) Immediately after updating from 37 to 38, Test Complete was unable to find any objects. (It navigated to the correct pages just fine, but it was unable to find objects on the page to perform any actions.)
Yesterday, I worked with Rick. We were able to get my tests to execute successfully again by changing my system DPI settings from 125% (default) to 100%. Please bear in mind that I have never changed the DPI setting on my machine in the two years I have owned it, nor do I ever touch the zoom level for Chrome, either. This issue strictly arose from the 37 to 38 Chrome update.
After further reading on other forums, I can see that this is not a rare issue, and the DPI settings with Chrome are a known problem. Here are some examples:
http://www.reddit.com/r/chrome/comments/2inzjv/ Although this is clearly an issue with Chrome, I believe it may warrant extra investigation by the Smart Bear team to help other Test Complete users who may encounter this problem.
By following the advice in the above forums, the DPI scaling is fixed by changing the path to include " /high-dpi-support=1 /force-device-scale-factor=1". However, after doing so, Test Complete can no longer find the path to the Chrome browser, and I have not yet found a solution to tell Test Complete to find it with this modified path. Thus, I still have to run my system DPI at 100% to get my tests to execute properly, when previously they were fine with 125% on previous versions of Chrome.
Again, I think extra investigation into this, and an alternate solution to changing the system DPI settings, would be appreciated by your TC customers.
