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
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.
- Same here. I had to vigorously motive the financial expense - seeing as their prices have skyrocketed. Now I'm sitting with pie on my face.
We'll also be discussing a move. jsc, jordansweeneyr, goda_zu, breezerK, LRuoc
Google rolled back their change and we tested internally to find that TestComplete does work with Chrome v113. Are you not seeing the same? Or are you referring specifically to the dropdown issue? Just want to clarify to ensure we're on the same page.
I am running Chrome 113.0.5672.93 & Edge 113.0.1174.35 (all updates managed by IT, of course, as it should be. I can't downgrade the browsers). Current version of TestComplete on my machine is 15.51.4.7.
With this version of TestComplete, basic xpath identification is not working in my test cases. Sure the browser is detected now, but that is not useful if xpath elements are not detected on the screen.
Funny enough, I had one of my team members install an older version of TestComplete (15.49.6.7) and they are having no issues on Chrome 113.0.5672.93. I am going to downgrade TestComplete on my machine to that version and test it out as well (for those of you interested here).Interesting. I have a member using 15.48 and they are seeing the issue. Find it confusing as no one else is on this version, just the latest one.
My version of Chrome is Version 113.0.5672.93 (Official Build) (64-bit). I tested this morning and TestComplete still almost immediately gives the error we have been seeing since this issue started - the tested window or control has been deleted.
Am I to understand that SmartBear is saying Google rolled back their changes so SmartBear is no longer planning to release an update to resolve this issue?
prashantmohan wrote:jsc, jordansweeneyr, goda_zu, breezerK, LRuoc
Google rolled back their change and we tested internally to find that TestComplete does work with Chrome v113. Are you not seeing the same? Or are you referring specifically to the dropdown issue? Just want to clarify to ensure we're on the same page.
yeah sure I see this and our tests are running again. But I am not sure that the same thing can happen again with the next chrome version ...
TestComplete 15.4 works, with Chrome but not Edge. 15.4 isn't the latest version so should we avoid updates and for how long? Also, we haven't run ALL our tests, just a preliminary check.
