Timeout error to connect with browser the first time

7 posts, 0 answers
  1. Juan
    Juan avatar
    18 posts
    Member since:
    Mar 2012

    Posted 09 Jul 2012 Link to this post

    Hi everyone,

    Just to report you that most of the time that we run a test, the first time we are getting a timeout error when the test is trying to connect with the browser (IE8, IE9, Chrome, Safari or Firefox). We need to cancel the test and run it again, and in the this second time the test runs correctly without timeout errors. 

    We are using VS and the Browsers extension are installed and enabled.
    Does anyone know what is happening this?

    Thanks in advance,
    Juan
  2. Anthony
    Admin
    Anthony avatar
    19 posts

    Posted 12 Jul 2012 Link to this post

    Hello Juan,

    We haven't experienced this issue on our side. Do the browsers launch quickly when opened manually? Is it possible the browser takes more time to load than the standard 20 second timeout?

    You can increase the timeout used to wait for a client to be ready after initial launch like this:

    Manager.Settings.ClientReadyTimeout = 60000;

    Alternatively you can catch the timeout exception and launch again:

    try
    {
        Manager.LaunchNewBrowser();
    }
    catch (System.TimeoutException)
    {
        Manager.LaunchNewBrowser();
    }


    All the best,
    Anthony
    the Telerik team
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
  3. Juan
    Juan avatar
    18 posts
    Member since:
    Mar 2012

    Posted 12 Jul 2012 Link to this post

    Hi Anthony,
    Thanks for your response!

    The browser is launching quickly manually, the problem is when Telerik tries to connect to the browser, most of the time the browser window only show the message: "Preparing browser for automation..."

    I've attached an example screenshot. But, let me try your suggestions and I'll let you know.

    Thanks,
    Juan
  4. Patrick
    Patrick avatar
    7 posts
    Member since:
    Oct 2010

    Posted 12 Jul 2012 Link to this post

    Have you tried running VS in Administrator Mode?
  5. Juan
    Juan avatar
    18 posts
    Member since:
    Mar 2012

    Posted 12 Jul 2012 Link to this post

    Hi Patrick,

    Yes, some of the machines that we use for the tests is with the Administrator user.
    I don't think that could be the problem, at least not all the problem.

    Thanks,
    Juan
  6. Patrick
    Patrick avatar
    7 posts
    Member since:
    Oct 2010

    Posted 12 Jul 2012 Link to this post

    If these are win vista/7 platforms you have to right click "run as Admin".  I say this because I was getting the same issue prior to doing a run as admin.

    Pat
  7. Juan
    Juan avatar
    18 posts
    Member since:
    Mar 2012

    Posted 12 Jul 2012 Link to this post

    Actually, your suggestion make sense.

    I'll let you know guys how it goes,
    Thanks for that!
Back to Top