We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Hey,
this is a general message about TestComplete issues with Chrome 113
Please note that the current version of our product may experience issues when used with Google Chrome 113. We apologize for any inconvenience this may cause. Our team identified this is Chrome issue and we are working on a permanent fix. We appreciate your patience as we work through this issue.
The dev team on our side is already working to solve the problem. We expect the problem to be solved by the middle of next week.
More updates will be provided here in this thread.
Really appreciate your patience and sorry for inconveniences.
Best regards,
Pawel Mularczyk
Product Manager for TestComplete
OK, this is to the point of ridiculousness. If I didn't do MY job for what's been almost a week now, I wouldn't HAVE my job.
I (and others) have waited patiently (although we shouldn't have had to) through yesterday when a fix was promised mid-week. I am the testing manager for my organization and my ENTIRE TEAM has been unable to do their work because of this issue with the tool.
I initially recommended Ranorex instead of TestComplete and this tool was forced on us. Since then we had a previous issue - not being able to integrate with Zephyr and SmartBear tech support told us essentially - too bad. I feel like I am in that same situation again.
To recommend changing browser versions isn't only not possible in a managed organization - it is a TERRIBLE idea. Why would someone even waste time testing something other than what is being used throughout the organization? I try to be positive and patient but this is NOT my idea of customer service and I would NOT be comfortable recommending a license renewal.
PLEASE FIX THIS ISSUE - immediately and correctly. At the very least - COMMUNICATE about it so we all know what's going on and when we can get back to work.
the damage done by
* being surprised by the bug
* not fixing the bug in reasonable time
* terrible workarounds suggested
* horrible communication
is beyond imagination.
although we are rather locked in to TestComplete on the part we are still using it, we had already had to discuss how we can force replacing it even faster.
Hi Pawel,
what do you mean "over the past 2 days"? At least we found the issue on Wednesday last week (May 3rd).
Were these changes to the Chromium engine not included in the Chrome 113 beta versions?
I expect you to use them!
The Chrome stable channel has been updated to 113.0.5672.63 for Windows on April 26th according to https://chromereleases.googleblog.com/search?updated-max=2023-04-27T14:50:00-07:00&max-results=7&start=7&by-date=false
Joachim
Awesome. Last week we made changes to the scripts to allow us to test with Edge. As of this morning, we are getting the same issue with Edge that we were getting with Chrome last week. Edge Version 113.0.1774.35 (Edge updated this morning as well). We are now unable to do any testing and I have an entire team unable to function
Hey all, wanted to provide a quick update based on the work we've done over the past 2 days. We've identified the root cause of the Chrome and Edge 113 issues, and it appears that a few changes in the Chromium engine has impacted the way TC interacts with the browser. We should have a patch coming along very soon.
Due to the fact that Edge and Chrome are based on Chromium, with the release of Edge 113 there were problems here too.
Thanks for your patience!
Best regards,
Pawel Mularczyk
Product Manager for TestComplete
Hey,
we just released Test Complete version 15.51.30 which solve problems with testing Edge and Chrome for some users. This is minor release which has this only one fix related to Chrome and Edge. Thank you for your ongoing patience.
Best regards,
Pawel
15.51.30.x has resolved the issue i was experiencing. i am no longer getting the "tested window (or control) has been deleted" error message and my web applications are running successfully as they did before the whole Chrome 113 issue reared its ugly head
Thanks!
We have a tightly controled domain and we simply can't go around installing, rolling back etc, especially when it comes to browsers. Thats 2 internal support tickets, to rollback and to revert. 2 days lost for us. This has massively impacted our test shedules and ability to write new tests. We purchased this because of the excellent support and product capabilities which now seem to be in decline, as the price increases.
How did you miss this during testing? Dont you test against edge beta releases?
Hey all, Dev team has completed changes to TC to support Chrome 113, and will be releasing changes today. The changes were tested by the QA team and Chrome 113 will be fully supported.
Bet regards,
Pawel Mularczyk
Product Manager fot TestComplete
does "today" mean before close of business today or before midnight?
Hellow, PMularczyk
I have a question here on this. We did not install any new version of TestComplete or the corresponding extension this morning. We DID see a minor change in version number for Chrome 113 (it's still Chrome 113 but changed from .92 to .93). And now, suddenly, our automations are working again.
I'm VERY suspicious of magical fixes like this. Was it the chrome change that corrected things? Or are we still expecting code changes to come in TestComplete/TestExecute and the associated extensions?
Automation has started working but my tests on drop-down controls have also started acting weird on Chrome 113.0.5672.93 😞
Around when? We would like to plan for this as the team has already been idle for three days and we have a weekly deadline on a current project. Thanks.
Yesterday came and went, and there is no further communication. Did we make a mistake with choosing TestComplete? WebDrivers for Selenium are working without issue (there is even a beta release for chrome 114), and that is free to the public!
When is this update coming?
Hey, we know that some users have had problems testing Edge and Chrome on all versions of TC 15.51.
We have identified an issue that was blocking testing of TestComplete 15.51 on Google and Edge browsers.
Next week we will have a ready version available for customers. We’re always committed to delivering the highest quality tools to your team. Thank you for your ongoing patience and continued partnership.
Best regards,
Pawel
I found two sites that can help you obtain an older version of Chrome directly from Google's website. The first gives you a PowerShell script that you can run (if you have the appropriate permissions) to obtain links to various Chrome versions.
https://squirrelistic.com/blog/how_to_download_older_version_of_google_chrome
The second is a StackOverflow post from a user (Andrzej Jakuszyk) that used the script from the above link and obtained a number of links for different versions and posted those links.in his post.
https://stackoverflow.com/questions/54927496/how-to-download-older-versions-of-chrome-from-a-google-official-site
The StackOverflow post has links up to Chrome 110 but doesn't have links for later versions. You can use the script to obtain those if needed. I did that for Chrome 111 and 112, and obtained these links for those versions:
Chrome 111
https://urldefense.com/v3/__https:/www.google.com/dl/release2/chrome/e62jniza5yx3zn3jxfcif46dwu_111.0.5563.147/111.0.5563.147_chrome_installer.exe__;!!BzWKgdXLVQ!BBnJs2sd8DodETd1IreiLjOJ4QDmT7v81tH5rjmq8Y4LPRqanjIBjbzI4TpIrpasNW0OCyGX784joCTeggQ$
Chrome 112
https://urldefense.com/v3/__https:/www.google.com/dl/release2/chrome/dwyescrl2iyc6pdqgxpdlxncdu_112.0.5615.138/112.0.5615.138_chrome_installer.exe__;!!BzWKgdXLVQ!BBnJs2sd8DodETd1IreiLjOJ4QDmT7v81tH5rjmq8Y4LPRqanjIBjbzI4TpIrpasNW0OCyGX784j3j-bd10$