TestComplete issues with Chrome 113
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 apolog...
Forum Discussion
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 😞
I am also having exactly the same issue with Chrome Version 113.0.5672.93 (Official Build) (64-bit) 😞
Our tests are not selecting dropdowns correctly and they are all failing cos of it.So our team is also stagnant until this is resolved.
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.
PMularczyk The 114 beta release is available: Are you going to test against that as well? It may prevent this happening in the future.
You could likewise create a Beta TestComplete release, and I'd be willing to use it as part of our own testing of new browser versions with our products. This issue has highlighted our own lack of testing future browser testing.
jrsbr wrote:PMularczyk The 114 beta release is available: Are you going to test against that as well? It may prevent this happening in the future.
You could likewise create a Beta TestComplete release, and I'd be willing to use it as part of our own testing of new browser versions with our products. This issue has highlighted our own lack of testing future browser testing.
PMularczyk I agree wiht jrsbr that creating a beta release of TestComplete is an excellent idea. You could have a small set of customers run this beta release of TC along with beta version of Chrome. Give these customers priority access to Smartbear support personnel so any issues they find can be quickly addressed. Maybe you would even give these customers an extra license that can only be used on the beta version?
I would signup for this beta. I have a lab of 24 PCs that I use with testing and I could easily spare a couple PCs to run beta testing, especially if it helps ensure we don't ever run into this issue again.
