Safari, Chrome fail to run test

[Lee]

I have recorded a test using IE9 and it successfully replays in IE9 and Firefox 5. The same tests fails in both Chrome 12 and Safari 5 at the same point. In each case these other browsers are launched and show the app's login page.

The test is to click in the user name window, type the user name, tab to the pw window and type in the pw. The first step of the test is to navigate to the app at localhost:port#/index.html  which it does in all browsers. The point of failure is step 2 labelled: "radmaskedtextbox: click with '1' offset action" where it is to click in the user name window. It apparently times out? To ensure the environment is copacetic I ran the test in IE at the beginning and end of trying to run the others, and of course it succeeded both times.

I have installed as per directions the add-ins for Safari but don't know if Chrome needs one.

Lee

[Anthony]

Hi Lee,

Please provide the Step Failure Details for the step that fails in Safari and Chrome. The easiest option is to "Export Result to File" and attach the zip file this thread.

As part of best practices, we typically recommend not including Tab key presses and steps that click into fields. Often the step that inputs the text is enough on its own. What happens when you disable the problematic step(s)?

All the best,
Anthony
the Telerik team

[Lee]

Hey Anthony,

I disabled the click and tab steps and reran it. It runs fine in IE9 but fails as usual in Safari. I have attached the step failure detail file.

[Anthony]

Hello Lee,

This appears to be a simple timeout issue. Extracted from the log:

"Timeout trying to connect to Silverlight App."

The simplest thing to do is increase the Silverlight Connect Timeout in Project Settings > Recording Options. For more in-depth troubleshooting please review this article in our Troubleshooting Guide.

Kind regards,
Anthony
the Telerik team

[Lee]

I agree that's what appears to be the problem but when I run it at the standard 30000 ms timing it fails in 22 sec: 413 msec. When I ramp the timeout up to 100000 ms it fails in 22 sec: 377 msec. So I don't think the setting is getting set, or else something is failing before the timeout time, and is erroneously reporting it's a timeout.

What do you want me to try next?

Lee

PS
I looked into the link for troubleshooting and tried the ideas there to no avail. I did see in Fiddler2 that the xap file is sending over x-silverlight-app in the header...

[Anthony]

Hi Lee,

Let's increase the Global "Wait on elements timeout" as seen at points 5 and 6 on this page. It seems your SL app is already connected to, so Test Studio is no longer looking at the SL timeout in Project Settings. It is failing on an input action on a TextBox. Every step has a built-in "wait on elements" and I suspect these two browsers are simply taking longer to load that element.

I actually just tested this on a SL demo page with Safari and encountered the same error. After I increased the W.O.E. timeout in Quick Execution Options, it worked.

Regards,
Anthony
the Telerik team

[Lee]

Okay, I did that. And I also tried the UseStepWaitOnElement checkbox in the test step itself. In the Quick Execution Options dialog I set the Wait on Elements to 100000 and the Client ready to 60000 and fail just as before. 

I am intrigued that the failure times in the log file are always within spitting distance of themselves no matter what I set the wait times to. They are always just at 22 seconds and change. Why is that? 

Lee

[Anthony]

Hello Lee,

That's a great question. I actually saw the same behavior testing this site with Chrome. The page is navigated to successfully, however step 2 (that clicks on a TreeView item) always fails in Chrome. The other three browsers work. I get the same error: "Timeout trying to connect to Silverlight App" and the timeout is always after 22 - 23 seconds. I'll run this by a developer and see why this could be.

The UseStepWaitOnElementsTimeout will ignore the Global Timeout you set in Quick Execution Options and instead use that step's WaitOnElementsTimeout. So if you set that to True for specific steps, be sure to change the accompanying property.

Greetings,
Anthony
the Telerik team