For those of you that didn't follow this ticket:
Chrome minimizes and reopens every on screen action | SmartBear Community
When Chome v139 came out TC stopped working with Chome (and edge).
This was fixed in TC v15.77.6.
Now Chrome updated again to v140, Testcomplete v15.77.6 does not work with Chome again.
If you updated Chome already i recommend downgrading Chrome back to v138 or v139.
Having the same problem where the "Keys" operation does not properly interact with textbox fields. Was able to work around the issue by utilizing the "Set Text" operation instead. It appears that TestComplete is sending the key inputs to the "Tab Groups" button beneath the "Go back" button on the Chrome window. I am using the hotfixed version of 15.76 on my local machine and the latest version in a pipeline on Azure Dev Ops and the issue is happening on both versions of the software. If you're not able to downgrade your Chrome then you just have to wait for SmartBear. I would recommend that everyone having this issue make a ticket with Smart Bear and attach your log files. The more information we can get to them, the more pressure they will face to fix this. I'm hoping that they can start getting ahead of some of these chrome updates so we don't have to deal with everything being broken every single time that Chrome updates.
To downgrade Chrome I followed these steps:
https://support.google.com/chrome/a/answer/6350036
https://stackoverflow.com/questions/18483087/how-to-disable-google-chrome-auto-update
If it still updates chrome after, delete chrome again, install preffered version and try this step
To get an old Chrome version I found this GitHub page:
https://github.com/Bush2021/chrome_installer/releases
Its unofficial so download at your own risk!
Champion Level 3I've just updated both to Edge Version 140.0.3485.54 (Official build) (64-bit) and Chrome Version 140.0.7339.81 (Official Build) (64-bit), and I'm not able to reproduce the issue with TestComplete v15.77.6.7 x64
I did not test edge but Chrome 140 is broken for me.
It does seem to be a different issue.
The issue seems random. Sometimes the objects are detected properly in the object browser, sometimes not. For example, an angular component using the tag "app-root", sometimes it's detected as AppRoot(0), sometimes as Panel(0)...
We also have Problems with TestComplete and Chrome 140.
In our test that worked with Chrome 139 and did not work with Chrome 140,
we address a field and want to enter some data, but this does not work with Chrome 140.
It seems that either the object can not be found or the field can not be filled.
But at our tests it does not appear in general, only at some fields.
I have the same problem, but for me its on the login page on our webapp.
this makes all tests fail since I can't login.
You can potentially work around this issue by using the "Set Text" operation instead of the "Keys" operation if that's how your filling the text fields. However, this hasn't worked in every case for me... I'd recommend making a support ticket with your test logs if you haven't already
In our test it is the field "Username" on an internal webpage that can not be adressed/filled, so that all test fail.
When i start the test as loged in user, it looks like the other teststeps are working
Champion Level 3Chrome is only supported up to version 138 right now
https://support.smartbear.com/testcomplete/docs/app-testing/web/general/supported-browsers-and-technologies.html
Hi !
I think many of us know this. But in my case, browser updates are managed by the company and I have no way to downgrade them.
Champion Level 3End-users need to understand, that TestComplete typically supports Chrome and Edge versions that are 2–3 versions behind the latest release due to the following reasons:
In short, this delay is intentional to ensure reliability and consistency across different environments.
Many organisations use locked or controlled browser versions in their environments to ensure consistency and compliance. TestComplete’s support for slightly older browser versions aligns with these enterprise practices, ensuring stable, predictable testing across teams. However, it seems like many organisations do not implement to this rule!
In my case, the organisation pushes every updates... for "security reasons"... and unfortunately, it's not negotiable. (even for one computer...)
So, I have no choice to deal with "unstable" versions.
Champion Level 3It's the same with me, as I work in a corporate environment and our equipment is maintained by the IT department, updates are done automatically which I have no control of.
