Hey, this is a general message about TestComplete issues with Chrome 113Please 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.

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=falseJoachim

does "today" mean before close of business today or before midnight?

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 MularczykProduct Manager for TestComplete

Deef

Forum Discussion

Recent Discussions

Failed to upload the report data - An exception occurred

Unable to access popup menu from MFC Ribbon Dropdown button

How to compare local variables with a reusable script in TestComplete?

Related Content

TestComplete - Interact with the Chrome download bar.

TestComplete Test Adapter (v15.53.9) issues running tests in DevOps

TestComplete Trial Chrome not recording