Forum Discussion

erikgt's avatar
erikgt
Contributor
3 months ago

Elements detected, clicked in wrong location with Chrome

Hi,

Since a few days, we've been noticing one of our TestExecute workers, running on v. 15.79.43.11 is detecting elements in the Chrome browser in the wrong location.

A collegue has similar issues on their desktop, running TestComplete v15.80.1.7.

Other TestExec workers and TestComplete instances running the same version (including the same version of the Chrome browser) do not experience this issue. 

Does anybody have an idea what might cause this?

We've checked the obvious things as screen resolution and Windows zoom level. 

The issue doesn't occur with our regular AUT, only during interaction with Chrome.

 

26 Replies

Show More
  • jsc's avatar
    jsc
    Regular Contributor
    1 month ago

    It's now  the same here with our tests.

    1/4 Test VMs still runs smoothly, 3/4 VMs locate the elements in Chrome in a different place and so the test cannot be run properly. 

    • the 4 VMs are completely identical
    • all 4 use the same chrome version (145.0.7632.117)
    • all 4 use the same TestExecute Version (15.80.1.11 x64)

    the problem started occurring this week only after updating to chrome 145.0.7632.117.

    there was no problem with chrome 145.0.7632.110.

     

    • MCH's avatar
      MCH
      Contributor
      1 month ago

      I fixed the Problem with downgrading chrome to 143 from https://google-chrome.en.uptodown.com/windows/versions
      Unfortunately the latest Supported Version for TC 15.80 according to docs is 138.
      If I create an issue as support case they tend to reply with saying which version is officially supported and suggest downgrading.
      But If a lot of people create cases asking for support of the latest chrome version, it may put pressure on SmartBear to release a fix soon. 


      • jkrolczy's avatar
        jkrolczy
        Super Contributor
        2 days ago

        Users are sometimes not able to down grade Chrome to an older version to company policy maintaining the latest version.

        I do wish TestComplete would keep up with issues from newer Chrome versions.

        Unfortunately, while I was typing this reply a newer version of Chrome could have just been released :)

  • rhu's avatar
    rhu
    Contributor
    1 month ago

    Hi we have same problems that Testcomplete clicks elements on wrong position, but had not time for deeper anaylse upt to now.
    But I found an article that may could help

    https://community.smartbear.com/discussions/testcomplete-questions/elements-detected-clicked-in-wrong-location-with-chrome/279220

  • MCH's avatar
    MCH
    Contributor
    1 month ago

    What helped me now was to remove Chrome and reinstall version 138 (latest officially supported version according to documentation). 
    It's strange that the issue occurred only couple weeks after updating to a newer version. 
    On other machines chrome still works flawless with version 143 or 145. 

  • MCH's avatar
    MCH
    Contributor
    1 month ago

    We seem to have the same problem since today on one machine. 
    Not sure what changed because TC Version and Chrome Version are still the same as it was before today. 

     

      • MCH's avatar
        MCH
        Contributor
        1 month ago

        I forgot to mention, that scaling is already set to 100%.
        It was the first thing we checked.
        The behavior seems to appear only when we run Chrome from TestComplete via Browsers.Item[btChrome].Run().
        If I start Chrome manually every is fine. 
        It also only happens on one machine. We are not able to reproduce it on other machines.