Thanks for the updates
I am killing the firefox browser process through the testcomplete script. Before starting any tests we use the following code in the script.
BrowserConfig.killProcess("iexplore");
BrowserConfig.killProcess("firefox");
BrowserConfig.killProcess("chrome");
What if you try to kill Firefox right after closing its window? (I.e. before the line of code that triggers the error in test log.)
Though my preference is to configure browser to not stay in memory when all its windows are closed.
It is the same thing. Before this error happened , we saw one more issues as can be seen in the report. Authentication pop up appear even after entering the correct username and password. Not sure why it happens ?
> Authentication pop up appear
Might it be because of your network configuration? I tried to navigate to the tested page, entered user name and some password and pressed Sign In button. No authentication popup was displayed. (Sure I got the message about incorrect password.)
> It is the same thing.
Did I get you right that your test code:
-- Closes Firefox (this records a message to the test log that FF process remained in the system);
-- Terminates FF process (as per my suggestion);
-- Tries to do something else and this triggers the 'window is disabled' error?
What is the test code line that triggers the error?
