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...
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.
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).
on the latest version of TestComplete with the latest Chrome installed, TC was not recognizing the username textbox clearly visible in the image below
i decided to try your suggestion BreezerK and i rolled back my TC to 15.49.6.7. The project only has two test cases in it and when i ran it this time i got the same error on the first test case but, because it wasn't set up to kill chrome in between test cases the second testcase started up with the credentials box from the first test case still up on the screen and it worked. it was able to enter the username, password, click the Sign In button and go on about its way to a successful completion. When i modified my code so that it would kill Chrome between test cases then both failed to find the username textbox object. Very confusing. Not sure if i should go back to an even older version of TC (as some have suggested) or just wait for the fix that has been promised for "this week" now (instead of yesterday). is anyone else having issues with credentials boxes that popup over the webpage as opposed to being embedded in the page?
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?
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.
jordansweeneyr I just shared a table of my testing, but a moderator deleted it for some reason. I can confirm that 15.47 is working for me (chrome only).
Yes, I am still seeing the drop-down issue. Instead of selecting a specific item from the list it is scrolling all the way down and selecting the random items.