This is a migrated thread and some comments may be shown as answers.

Chrome browser.Window.Exists == null

2 Answers 45 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
uteotw
Top achievements
Rank 1
uteotw asked on 06 Apr 2014, 12:49 PM
Hi

While (true)
{
    using (Manager manager = new Manager(false)
    {
        manager.Start();
        manager.LaunchNewBrowser(BrowserType.Chrome, true);
        manager.ActiveBrowser.WaitUntilReady();
        Console.WriteLine(manager.ActiveBrowser.Window.Exists);
        manager.ActiveBrowser.Close();
    }
}

Chrome browser.Window.Exists == null when starting for the second or third time.

This does not repro with IE nor with FF.

2 Answers, 1 is accepted

Sort by
0
Cody
Telerik team
answered on 09 Apr 2014, 10:03 PM
Hi,

While that may be a very minor bug in our framework, why are you trying to do this? What purpose does it server in your test automation? LaunchNewBrowser doesn't return until the browser is up and running and our framework has successfully connected to it. I see no value in the code you have written.

Also as a side note, ActiveBrowser.WaitUntilReady only needs to be used after doing some real action in the browser, such as a Navigate or a click that causes the page to change. That API monitors the browsers Ready flag meaning it's done downloading the HTML content and supporting ancillary files. It servers no purpose calling it immediately after LaunchNewBrowser.

Regards,
Cody
Telerik
 
Quickly become an expert in Test Studio, check out our new training sessions!
Test Studio Trainings
 
0
uteotw
Top achievements
Rank 1
answered on 17 Apr 2014, 06:37 AM
Hi Cody

My code was just a compact version for you guys to repro the problem.
This problem is now resolved in 2014.1.410

Thanks
Tags
General Discussions
Asked by
uteotw
Top achievements
Rank 1
Answers by
Cody
Telerik team
uteotw
Top achievements
Rank 1
Share this question
or