Chrome browser.Window.Exists == null

3 posts, 0 answers
  1. uteotw
    uteotw avatar
    4 posts
    Member since:
    Nov 2010

    Posted 06 Apr 2014 Link to this post


    While (true)
        using (Manager manager = new Manager(false)
            manager.LaunchNewBrowser(BrowserType.Chrome, true);

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

    This does not repro with IE nor with FF.
  2. Cody
    Cody avatar
    3360 posts

    Posted 09 Apr 2014 Link to this post


    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.

    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  3. uteotw
    uteotw avatar
    4 posts
    Member since:
    Nov 2010

    Posted 17 Apr 2014 in reply to Cody Link to this post

    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

Back to Top