Forum Discussion

erikgt's avatar
erikgt
Contributor
2 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 iss...
jsc's avatar
jsc
Regular Contributor
15 days 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
    15 days 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. 


    • jsc's avatar
      jsc
      Regular Contributor
      15 days ago

      thank you. For sure I start with this approach.

      But in my experience chrome always finds a way to update itself...