Forum Discussion
Hi Dave,
Have you tried to execute this loop step-by-step under debugger in TestComplete and check whether the problem persists?
My current understanding is that:
-- There was IE browser running in the system;
-- The loop found it on the first pass and proceeded to .Close() statement;
-- The browser was commanded to close and TestComplete waited for 0.5 sec for the browser process to end;
-- 0.5 sec was not enough for the browser to close thus the second loop pass still found the process and proceeded to .Close() statement;
-- By the moment of actual execution of the .Close() method IE process has ended. This invalidated the reference to the browser process and caused the error.
As a quick fix attempt try to increase the parameter of the .Close() method from 500 to, say, 2500 and check if it helps.
Hi Alex
Thanks for your prompt reply. I will give it a try and report ASAP.
Dave
- royd8 years agoRegular Contributor
Just ran it, it got stuck the first time on line 19, did not make it to 21. See capture.
Thanks.
Dave
- tristaanogre8 years agoEsteemed Contributor
WaitBrowser is part of the Web licensing of TestComplete. If, for some reason, the machine you're on isn't licensed for web application testing then the problem may not be in the time outs or anything but on actually calling "WaitBrowser".
Couple of things to check:1) Go to File | Install Extensions and make sure that the Web option is checked with everything under neath it
2) In your text editor, type Sys. followed by CTRL-SPACE to get the code completion window and see if WaitBrowser shows in there.
- royd8 years agoRegular Contributor
Hi Robert
You hit the nail on the head! I have been working with TestComplete for over 6 months now. We have web and mobile license. Never had any problem!
I last night I spent hours to figure out what was going on! Finally I decided to create a new suite and start from scrach to see what happens. That is when TestComplete complained "The selected testing type requires the Web Testing plug-in, which is currently disabled. ..."!
There is no reason for me to disable it, neither I did so! Anyway, after enabling the plug-in, all is well now.
Dave
Related Content
Recent Discussions
- 4 days ago
- 4 days ago
- 7 days ago