I have the latest test complete and the latest version of chrome that came out 3 days ago.Now running scripts that did pass, they now fail.I get a common error saying 'The window was destroyed during method execution'.The browser window is open and visible. Never had this before the latest updates. Any advice please as this has stopped all our scripts running

Just because it was working before and is not now does not necessarily mean your code isn't at least part of the issue. As mentioned xpath is not the best practice way for finding objects in Test Complete. Perhaps there was a change in your website that you are also now finding a native DOM object instead of a Test Complete object as mentioned by AlexKaras. The error message even indicates that whatever object you are trying to work with is destroyed between you finding a reference to it and then interacting with it. Even so, with new versions of anything, automation tools, browsers, SDKs, there is always a risk that something may change that could break the way you're approaching a solution. Have you tried any of the suggestions in this thread? You mentioned name mapping say that is time consuming and brittle, sure, it takes a while to set up, but when done properly it is absolutely NOT brittle. Automation by nature has an upfront time investment, but the goal is to make it rock solid and not have touch it again until your requirements change. Name mapping is a sure fire way to find your objects as fast and accurately as possible. It also has the added benefit that when an object or layout changes you have ONE spot to adjust, as opposed to every single place in your code that needs to use the object. Not saying it's impossible that there is a legitimate issue with TC 12.5 and Chrome 66, but if it were widespread we would be seeing A LOT of posts regarding this here in the forum. I would suggest at least trying some of the suggestions given here while you wait to hear back from SmartBear's support team. Automating tests is just like developing software, the end goal is a reliable solution, so it's not the end of the world if you need to take a slightly different approach.

Neither Marsha_R nor myself are SmartBear employees. SmartBear staff DO frequent these forums so they could still respond, however, any questions on time frame, specifics about what you perceive as "bugs", etc., for which you need a more rapid direct response should be addressed via the link I posted earlier as has already indicated. However, if you're having problems, it's entirely possible that they are NOT bugs but just items that need to be addressed in your automation to correct what might be timing issues and such that should be taken care of. The error message you described about the object being destroyed usually occurs when the handle to an object is destroyed before the action can be executed, usually meaning that there's insufficient code for waiting for page loads, object recognition, etc. If you can show us screenshots of your Keyword tests and/or copy the code that is generating the error, we would be happy to help you with it.

It still sounds like there is something with the way you are finding and / or interacting with objects. I am running Test Complete 12.5 and the latest version of Chrome as well with no issues like you have mentioned. This leads to believe you're hitting a condition where you are not properly waiting for an object before interacting with it like others have said. The fact that this appeared for you in 12.5 could be due to performance improvements in Test Complete hitting an action faster than it was previously. Have you tried the suggestion provided by Marsha_R? Can you provide example code, screen shots of your mapping, or screen shots of your Keyword Tests that this is happening in? The more information provided the more likely we can help isolate the issue.

Selenium and TestComplete approach the technology of UI automation differently. Therefore, it is not necessarily out of scope for one to have a solution before another. Feel free to change tools... honestly, no risk to me if you do. NO ONE in this thread to date is a SmartBear employee. If you have such a serious concern, then I would suggest you make your concerns known to SmartBear directly via your Customer Success representative or through the already posted link for contacting support. Good luck in your endeavors.

Hi Guys, I've talked with the TestComplete Customer Care Team Lead - we are not familiar about any specific issues with Chrome 66. If you face some problems, the best way to move forward is to contact our Support Team and explain in detail what is going on. You can reach out to them here: https://support.smartbear.com/message/?prod=TestComplete tristaanogre, thanks for letting me know!

Issues with new chrome | SmartBear Community

36 Replies

Marsha_R
Champion Level 3
6 years ago
It's helpful if you give your version numbers of TC and of Chrome.
- endorium
  Frequent Contributor
  6 years ago
  As above the latest versions.
  Test complete also crashes a lot on the newest version. Also issue with layouts and window sizing that were not there before.
  
  Chrome : Version 66.0.3359.139 (Official Build) (64-bit)
  Test Complete : Version: 12.50.4142.7 x64
  - tristaanogre
    Esteemed Contributor
    6 years ago
    Concerning TestComplete 12.50 with Chrome version 66, there's another thread up here that gave feedback from the actual customer service staff that, at this time, recommendation is to downgrade Chrome to version 65 as there are issues with v66 that need to be addressed. If you need to address this further, the best suggestion is to contact support directly at https://support.smartbear.com/message/?prod=TestComplete
    
    As for your other problems.... If you want us to try and answer them here on the forums, please create additional queries/posts for each with as much detail as possible and we'll do our best. We may end up, at the end, referencing you to support but we may still be able to give insight.
AdamUK
Occasional Contributor
6 years ago
I'm having issues with Chrome 66 and TC 12.5.

Tests originally recorded in older versions of Chrome no longer work (fail to recognise objects). If I try to record tests on our web application I get errors claiming that 'Chromium Embedded Content Detected'. I checked with a developer and we don't have this.
- tristaanogre
  Esteemed Contributor
  6 years ago
  TanyaYatskovska... There are several people now, in this thread and in others, that are reporting multiple problems using Chrome version 66 with TestComplete 12.50. The patches page for Chrome patches indicates that TestComplete 12.50 works "out of the box" with Chrome 66. Could you have the customer service folks take a closer look at this?
  - TanyaYatskovska
    SmartBear Alumni (Retired)
    6 years ago
    Hi Guys,
    
    I've talked with the TestComplete Customer Care Team Lead - we are not familiar about any specific issues with Chrome 66.
    
    If you face some problems, the best way to move forward is to contact our Support Team and explain in detail what is going on.
    
    You can reach out to them here:
    
    https://support.smartbear.com/message/?prod=TestComplete
    
    tristaanogre, thanks for letting me know!
AdamUK
Occasional Contributor
6 years ago
"Even so, with new versions of anything, automation tools, browsers, SDKs, there is always a risk that something may change that could break the way you're approaching a solution. "

That's a fair point but the main reason we chose TestComplete and other Smart Bear products was to minimize that risk.
- Marsha_R
  Champion Level 3
  6 years ago
  Certainly we all chose TestComplete for that reason too, but *everyone* has a unique testing setup and even SmartBear can't cover everything ahead of time. Contact Support at this link and get individual help with your issue:
  
  https://support.smartbear.com/testcomplete/
  - jjessop
    Occasional Contributor
    6 years ago
    UPDATE***
    
    I have tracked down what my issue is. FOR ANYONE seeing the Red rectangle of death on the full browser window:
    
    I was using remote desktop to work on a scripting box that I do ALL of my ui testing on, so it doesn't destroy my local things. 12.5 with chrome, will not function this way. If I access the machine directly and run the exact same test, no problems. All other browsers work through Remote Desktop Connection.. 12.42 worked just great this way as well with all browsers, including chrome. So my question for the devs is, what changed with how we interact with chrome and 12.5?

Forum Discussion

Issues with new chrome

36 Replies

Related Content

TestComplete issues with Chrome 113

Chrome updated, now TC can't find browser

TC14.2 \ Chrome 77 close browser \ process issue

Issue while launching the chrome browser with Run Options

Chrome Extension for Chrome version 111, TestComplete version 15.49

Recent Discussions

TestComplete14.72 is not recognizing WinUI-3 objects

Floating window bleep overlapping window takes longer time (~10 min) to click the button on it.

Test case randomly fails with "parent object was not found"

Does TC have a .within() method similar to Cypress.io?

SessionCreator /Timeout option not firing EventControl_OnTimeout