Problems with TestComplete 15 and Chrome 113
Test Complete Version: 15.51.4.7 x64 Chrome Version: 113.0.5672.63 Hello, we are having problems running tests after updating Chrome from 112.0.5615.138 to 113.0.5672.63. No more elements ar...
Forum Discussion
So I have also discovered this issue after a recent system upgrade. Chrome version 113 is not compatible with the SmartBear extension.
I have tried downloading and installing Chrome version 105 and disabling updates by using information from
https://www.chromium.org/administrators/turning-off-auto-updates/
and
I added the two new reg keys suggested (one by each article) with no success. Chrome still updates automatically to version 113. I am not connected to a workplace network so the ADM group policy option doesn't apply to me.
Does anyone know of any other methods for preventing Chrome from auto-updating?
Otherwise Chrome cannot be currently used with TestComplete and will be useless until there is a patch.
Hi,
> Does anyone know of any other methods for preventing Chrome from auto-updating?
Try to:
-- Stop and disable all Chrome/Google-related services; and
-- Delete the 'Update' folder under Chrome folder in Program Files and, maybe, your local user profile folder.
> it is probably a simple licensing issue.
Well... I will not argue against line of code you are talking about, but, considering the fact that all problems with TestComplete we are talking about here started in past March, my personal opinion is that the real reason is a little bit different...
AlexKaras wrote:problems with TestComplete we are talking about here started in past March, my personal opinion is that the real reason is a little bit different...
Many of the issues started in early 2022. Prior to that, I felt like support from Smartbear was OK.
AlexKaras just curious, is this issue affecting your testing? Do you perform WEB testing? If it is not an issue for you, how do you manage TestComplete and Chrome to avoid this?
In my opinion, any automated testing tool for WEB must always support the latest version of Chrome the day any update is released. Chrome is the most widely used browser and everybody gets automated updates so we must test our software on the latest version.
What am I supposed to say to my management when they ask "does TestComplete support the latest version of Chrome"? There is no reason I could ever give them that would justify NOT supporting the latest version. As an IT company, we must insure our software works on the latest version and so should Smartbear.
Well... Major part of TestComplete efforts for my current project are for Desktop. And we do not have a requirement to support latest Chrome. Maybe because this project is oriented on controlled environment with planned updates. So we are lucky here. But yes, I also had to rollback TestComplete to version 15.49.
As for immediate support for the latest browsers... Well, my personal opinion is that I never understood and accepted these forced software updates introduced by Google and that a lot of other companies followed later. To my opinion, all software updates must be scheduled and controlled. I hate to imagine the situation when I come to a meeting to present my project, turn on my notebook and appear in the situation that some software updates start with not predictable result. I also don't think that the necessity to keep notebook turned on in advance in order just to make sure that all software started is a good and acceptable approach.
So for me, those who allow automatic volatile software updates do this on their own risk and must not expect that everything after such software updates will work as before it.
On the other hand, previously TestComplete almost always provided support for latest browsers within several days after browser release. This was confirmed policy of the company and they stated that they need these days for final testing on released official version of the browser. This was not a showstopper for the majority of our Community, worked quite well, and I do not remember problems like those reported recently for .WaitAliasChild().
So my personal opinion is that SmartBear must pay extreme attention to these things. Maybe even at the cost of delays for other functionality like BitBar and Visual testing support.
