Test Complete Version: 15.51.4.7 x64Chrome 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 are detected in the test and the following error is logged:The window with the handle 0x000000 does not exist.Also no new elements can be mapped in the NameMapping. These are not recognized. The TestExtension in Chrome seems to work, because the test can navigate via URL in the browser.An update to the latest TestComplete version and also a reinstallation of the TestExtension plugin did not solve the problem. Is there any known incompatibility between TestComplete 15.51.4.7 and Chrome 113? Best regards

I have already submitted a support ticket, emailed my salesman and called Smartbear to yell at somebody. TestComplete must always support the latest version of Chrome, PERIOD! That is what our clients use, that is what we must test on. Google releases beta version of Chrome a month in advance and Smartbear should easily be prepared for any changes and have TestComplete ready. This issue very well might be the "straw that broke the camels back". I just spent the last 4 days coding around the issues in TC 15.51 to get our testing running again. I came to work today hoping to get back to the project I was working on only to discover we can't use TestComplete at all for WEB testing. While switching to a new tool is a nightmare that will take 6 months or more to complete, I am not sure I really have an alternative at this point. My company is trying to make some major advancements in our automated testing processes. I spent part of the past year convincing my upper management that TestComplete was the best option because of its ability to test Desktop and WEB. I am starting to look like a fool for that recommendation. Let's hope it doesn't cause me to lose my job.

For many users, it's difficult to downgrade to Chrome 112 - as it's controlled by IT, and it's not possible to get hold of previous version of Chrome from Google.

I made a feature request to support more recent browsershttps://community.smartbear.com/t5/TestComplete-Feature-Requests/Update-Testcomplete-to-support-more... Please give it some kudos so the developers will take note and hopefully give it a higher priority.

this is not realistic. Chrome gets updated automatically and we need to test the versions our customers use and not some old Chrome 105 that noone can still use.

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.

Problems with TestComplete 15 and Chrome 113

37 Replies

mfoster711
Regular Contributor
3 years ago
I have already submitted a support ticket, emailed my salesman and called Smartbear to yell at somebody.

TestComplete must always support the latest version of Chrome, PERIOD! That is what our clients use, that is what we must test on. Google releases beta version of Chrome a month in advance and Smartbear should easily be prepared for any changes and have TestComplete ready.

This issue very well might be the "straw that broke the camels back". I just spent the last 4 days coding around the issues in TC 15.51 to get our testing running again. I came to work today hoping to get back to the project I was working on only to discover we can't use TestComplete at all for WEB testing. While switching to a new tool is a nightmare that will take 6 months or more to complete, I am not sure I really have an alternative at this point.

My company is trying to make some major advancements in our automated testing processes. I spent part of the past year convincing my upper management that TestComplete was the best option because of its ability to test Desktop and WEB. I am starting to look like a fool for that recommendation. Let's hope it doesn't cause me to lose my job.
rraghvani
Champion Level 3
3 years ago
For many users, it's difficult to downgrade to Chrome 112 - as it's controlled by IT, and it's not possible to get hold of previous version of Chrome from Google.
- AlexKaras
  Community Hero
  3 years ago
  Disclaimer: All text below is my private opinion provided without any intention to lower the importance of latest browsers support.
  
  Nevertheless... I think that while private end-users may behave as they like and they are free to leave their computers open to uncontrolled volatile software updates, updates for computers that are used for testing purposes must be controlled and performed in a scheduled planned manner.
  
  Obviously, every company may have their own policy for this, but my primary reasons are like that:
  
  -- Test engineers must know what environment they are working on. If I need to check something on Chrome 112 and it suddenly becomes unavailable this will be a huge problem for me;
  
  -- I am not sure that all users may and can accept the concept of 'our web application is guaranteed to work on the latest version of the browser only'. If your company cannot afford to follow this concept, then you must have test environments with not latest version of the browser;
  
  -- Test environments must be updated incrementally in a controlled manner to ensure that tests and everything else still works. If we update all our test environments at once, we may find ourselves in a situation when our tests are just blocked. What is better: to be able to let management know how tested application behaves with the previous version of the browser or be not able to say anything?
  
  -- As an end-user I think that all these 'security-related' efforts became mostly marketing cover to force end-users to agree to update and to free browser provider from the obligation to support previous versions of the browser. (Microsoft, whatever is been said in its address was famous for its support of old applications in newest versions of Windows.) Two sub-notes: a) if security problem was revealed in the current version of the browser, is it really required to update the whole browser to the new version? Isn't a patch for some module is enough? And b) if security problems are revealed that often, I, as an end-user, may start thinking that browser provider just does not bother with proper design, implementation, validation and testing and just provides something that is 'good enough'. And finally, as an end-user, personally I use browser to read information and thus I am almost not interested in all this fancy stuff provided with the new version of the browser. And no, as an end-user I do not care about enhancements introduced for developers. Such stuff well can be made to be separate from the browser itself and be installed on demand only when/if needed.
  
  Uf-f-f... 🙂
MW_Didata
Super Contributor
3 years ago
I made a feature request to support more recent browsers
https://community.smartbear.com/t5/TestComplete-Feature-Requests/Update-Testcomplete-to-support-more...

Please give it some kudos so the developers will take note and hopefully give it a higher priority.
- Anton101
  New Contributor
  3 years ago
  I have the same issue with TC 15.4 and Google Chrome 113. Everything was fine with TC and Google Chrome 112 before the latest update for the last one.
  
  Is there any quick WA (work around)?
  
  I see that I can't roll back Google updates for its browser and I can't find the installer for CG 112.
  - MW_Didata
    Super Contributor
    3 years ago
    Anton101 Edge version 112 is still supported (for now) i recommend using edge untill SmartBear updates their web support.
    You can use third-party sites to download previous versions of chrome, and turn off auto-update
    But I would not recommend that for security reasons
automation_ph
Occasional Contributor
3 years ago
count me in. I'm having this issue as well
PMularczyk
Staff
3 years ago
Hey, this is Pawel - Product Manager for TestComplete. We are aware of this problem and the team is actively working on adapting TC to the new version of Chrome 113. This is our top priority and as soon as we make the changes we will release the patch.

As workaround, you can downgrade Chrome to 112. Please also remember to disable auto-updates in Chrome.

Thank you for your patience.

Best regards,

Pawel Mularczyk
- jsc
  Regular Contributor
  3 years ago
  for testing experts this is hilarious!
  
  We need to test with versions our customers use. Our customers use chrome and they use it (as every regular user) in the latest version. If they would mostly use netscape navigator we would test our application with netscape navigator and would select a tool that supports our testing.
  Testing is no self-purpose just to test with any browser or version the testing tool is working with. It's not our goal just to get the tests green.
  
  I expect that TestComplete supports a browser version the day it is released. That's why we pay for it.
  There are, as mentioned before, beta versions available that are released 4-6 weeks in advance. I really expect that TestComplete Dev uses this! (https://support.google.com/chrome/a/answer/9027636?hl=en)
- mfoster711
  Regular Contributor
  3 years ago
  PMularczyk wrote:
  Hey, this is Pawel - Product Manager for TestComplete. We are aware of this problem and the team is actively working on adapting TC to the new version of Chrome 113. This is our top priority and as soon as we make the changes we will release the patch.
  
  As workaround, you can downgrade Chrome to 112. Please also remember to disable auto-updates in Chrome.
  
  Thank you for your patience.
  
  Best regards,
  Pawel Mularczyk
  We need this fixed today. Not tomorrow, not next week, not "soon", TODAY.
bhcommunity1
Contributor
3 years ago
Issue has seemed to spread to Edge browser now.
Just started today.

TestComplete:15.51.4.7 x64
Edge: 113.0.1774.35 (Official build) (64-bit)

TestComplete fails to recognize it as a Browser Object. Test Complete "Object Browser" tab doesn't see it.
jrsbr
Contributor
3 years ago
Our IT people cannot rollback the Edge 113 browsers on our test platforms so we're totally dependent on the fix smartbear are pushing out soon.

Does anyone know when Microsoft will be issuing a fix?
rollosa
New Contributor
3 years ago
we are expierincing the same issue also our side, tests can't be executed after chrome upgrading to version 113.0.5672.63 . We have same problem on both TestComplete and TestExecution and the error we get is:

Unable to find the object ...
TommyTester
Occasional Contributor
3 years ago
Same issues for us as well.
rraghvani
Champion Level 3
3 years ago
Browser versions that are not listed in https://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/index.html, are not officially supported.
- jsc
  Regular Contributor
  3 years ago
  this is not realistic.
  
  Chrome gets updated automatically and we need to test the versions our customers use and not some old Chrome 105 that noone can still use.