make timeout for attaching to browser configurable

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 03 Jul 2014 08:06 by ADMIN

David

Created on: 22 May 2013 18:42

Type: Bug Report

make timeout for attaching to browser configurable

We occasionally (and sometimes not so occasionally) run into failure before the test even begins - browser fails to launch.  I understand that there is a default / hard coded value for how long test studio waits before giving up attaching to a browser.  It would be very helpful if that value were configurable - not all environments are equal, for example some VM's might run slower than usual depending on the host server load.

10 comments

ADMIN

Daniel Djambov

Posted on: 03 Jul 2014 08:06

Telerik: we have implemented the options to customize and apply ClientReadyTimeout (from Test View or Test List Setting) for all browsers (including Internet Explorer). This might potentially fix the random failures that happen during long or many executions. The fix will be available in our next internal product release planned in the beginning of July 2014.

David

Posted on: 01 Jul 2014 12:16

Yes, thanks Konstantin.  This feedback thread was from a while ago - my recollection is the symptom is the same, but the cause seems to be different.  I think with this item it was clear that some timeout threshold had been exceeded, the ticket you reference that isn't the case.

When I saw that this item was marked done, I assumed that meant a setting had been added somewhere and I wanted to try that to see if it helped ticket 827296.  That was the reason for my recent comment.

I'm fine with closing this feedback item out and if we (or somebody else notices) then open a fresh ticket.

ADMIN

Konstantin Petkov

Posted on: 01 Jul 2014 11:35

Is ticket Ticket ID: 827296 good to handle that? I just noticed you reported the same exception there.

ADMIN

Konstantin Petkov

Posted on: 01 Jul 2014 11:25

Hi David,

Do you mind if we switch to the support ticketing system? The feedback portal is not so useful for such kind of communication regarding specific issue like this.

Please submit a ticket with this trace and point to item here, I will make sure to handle it today.

Thank you!

David

Posted on: 30 Jun 2014 17:13

Sorry for the delay - see attached from trace file.  On the same server I can see 4 failures out of test 990 executions or about 1 out of every 10 times our tests were submitted.

Attached Files:

failtolaunch.log.invalid

ADMIN

Iliyan Panchev

Posted on: 25 Jun 2014 14:05

The client ready timeout applies to the initial launch of the browser. You can test it by setting it to 100msec - The test will fail immediately after started. But anyway, while we are trying to figure out which is this 10 seconds timeout, by any chance do you have the stack trace of the failure.
Thanks,
Iliyan

David

Posted on: 25 Jun 2014 13:51

Thanks for the response Iliyan.

A couple of things...

I don't think the client ready timeout applies to art of test runner attaching to the initial launch of the browser.  We see this fail at almost exactly 10 seconds and we adjust the client ready timeout to a much larger value, something like 3 minutes.

The issue is sporadic, we might run hundreds of tests without an issue and then on occasion we get a failure to launch IE.  Doesn't appear to be the same test each time and also not the same virtual machine.  My suspicion is this is related some how to the load of the underlying physical server.

I don't know that extending the timeout would help, but if that timeout was exposed as an option, the natural next step would be to double it and see if the problem gets better.

I was not able to go back and find the original support ticket, so I am working off memory that the timeout in question is hard coded to 10 seconds.

Any other suggestions would be much appreciated.

ADMIN

Iliyan Panchev

Posted on: 25 Jun 2014 13:15

Hi, The Client Ready Timeout in the Debugger and test list options determines how long Test Studio waits for the browser to be launched and ready for execution. So this should be the option that you are asking for. But I am curious when you communicated with the support did they got to the bottom of the failure. I fear that even increasing some kind of timeout may not solve your case. Why are you so sure that the failure is because of the timeout and increasing it will fix it?

David

Posted on: 25 Jun 2014 12:43

Sorry for the late response Konstantin!

I don't think the client ready timeout will help, the issue I am talking about is on launch of IE - the test never begins.  In the past we have opened tickets on this and the response was this timeout was hard coded.

I noticed that this is marked as "done" - does that mean I can configure it now somewhere?  We are hitting this again, more often now and would like to extend the timeout.

ADMIN

Konstantin Petkov

Posted on: 09 Jul 2013 11:41

Have you tried the ClientReadyTimeout setting? In Test Studio it is available as a TestList as well as a QuickExecution setting (the last item in the list at the Quick Execution Options dialog).

Does that help?