After the upgrade to latest version of test complete I'm getting the error -"The tested window (or control) has been deleted"
When I run any test it just opens the browser do the first action and closes the browser with above error.
Test Complete Version: 15.51.18.7 x64
Chrome Version 113.0.5672.93
i posted this on the Chrome 113 thread as well.
15.51.30.x has resolved the issue i was experiencing. i am no longer getting the "tested window (or control) has been deleted" error message and my web applications are running successfully as they did before the whole Chrome 113 issue reared its ugly head
I am having the exact same issue.
I have had this issue with both TestComplete 15.51.4.7 and 15.51.18.7. The version of Chrome does not seem to matter - we see the same issue with both Chrome 112 and 113.
TestComplete 15.50 does not have this issue. We have rolled back to 15.50 until this issue is resolved in TestComplete.
Just to reiterate / clarify, as there has been no movement on this issue yet:
TestComplete 15.50.3.7 x64 is working for us with Chrome 113.0.5672.127 (latest update to Chrome at the time of this post).
TestComplete 15.51.x.y is not working for us at all with any browser or browser version.
wanted to provide an update on recent developments. When I first opened up testcomplete this morning I got the notification that a new release/build was available so I downloaded and installed it. my web apps still did not work. At the suggestion of Alex Karras, I uninstalled testcomplete 15.51 and downloaded the install package for 15.49 and put it on my workstation. Now my web apps are working. My concern now is that, since I have also updated the testexecute apps on my VM’s to 15.51 will testcases I develop on my workstation with 15.49 be able to run? clearly something has changed about the newest releases of testcomplete that are causing this issue. when is smartbear going to address it?
joe_brooks wrote:TestComplete 15.51.x.y is not working for us at all with any browser or browser version.
What exactly do you mean when you say "not working at all"? TestComplete doesn't recognize anything in Chrome? Does it view Chrome as just a big red box in Object Browser?
Or, do you mean the "Control has been deleted" issue is not working at all?
mfoster711 When I say "not working at all", it is only a very slight exaggeration. Unlike the Chrome 113 issue, TC does recognize the browser window, but that's about it. It does not find most other objects. Every test we have errors out with the error message "The tested window (or control) has been deleted". We are unable to run any of the tests in our test suite of well over 100 tests successfully. TC 15.51 is entirely useless for us. That is what I mean by "not working for us at all".
mikef I have tried turning off hardware acceleration as you suggested, and it made no difference. I still see the same error message.
Problem is in last version of Chrome 113* (or in Testcomplete with last version Chrome).
A_Roskoshnyi No, it is not. We experience the same issue when running Chrome 112. The issue is entirely with TC 15.51.
Just to cross-reference that others also have this problem (which seems to be either not resolved yet, or be a regression): https://community.smartbear.com/t5/TestComplete-Questions/TestComplete-issues-with-Chrome-113/m-p/250823/highlight/true#M109336
Is their a URL to your app that we could see and try ourselves?
@ChrisPerth and @rpfaucher1 You may want to continue your discussion of your issues over on this thread, which I believe is more specific to the issue we are all having with TC 15.51, which is separate from the Chrome 113 issue.
mfoster711 Let me clarify one point, using the login test as an example (again, all our tests fail in this way on TC 15.51).
On TC 15.50, when we run our login test, we see the following behaviors. TC:
Running the same test on TC 15.51, we see the following behaviors. TC:
To reiterate, all tests on all pages behave this same way and fail with the same error message. It is not limited to the login page nor to the submit button on the login page. This is some type of system-wide TC 15.51 failure that does not occur in TC 15.50.
