Find Element Timeout?

[Steven Raybell]

Hey all,

I couldn't immediately figure this out, as it doesn't seem obvious, but what controls element lookup timeouts?  Which setting is it?  None of the Manager.Settings properties seems directly related to this particular action.  I have an idea that ExecuteCommandTimeout might, but ExecutionDelay could, too.

I'm extremely tired, so perhaps my observation skills leave something to be desired at the moment.  ;-)


Thanks,
Steven

[Kiran]

Hi Steven,

Can you please try this.
http://blogs.telerik.com/blogs/posts/10-06-24/silverlight_test_automation_changing_the_element_find_strategy_to_avoid_timeoutexecution-2578840260.aspx

Thanks
Kiran

[Missing User]

Hello,

Thanks for the post Kiran, and you can also try this link also and ActiveBrowser.WaitForElement().

All the best,
Nelson Sin
the Telerik team

[Kiran]

Hi Nelson,

Thanks for you reply.
Wai.Timeout =XXXXXXX is a good option. Nelson thanks for figuring out that.


Thanks
Kiran

[Steven Raybell]

When working with the Silverlight equivalent, does this propagate down to all the child element find strategies?  For instance:

this.Application.Find.Strategy = FindStrategy.AlwaysWaitForElementsVisible;
this.Application.Find.WaitOnElementsTimeout = 5000;
this.eventCategory = this.Application.Find.ByAutomationId<ComboBox>("CategoryComboBox");
var rootElement = this.Application.Find.ByName("CreationControl"); // does this use the same strategy and timeout as above?
this.nextButton = rootElement.Find.ByText("Next");

Thanks,
Steven

[Cody]

Hello Steven Raybell,

At the time your rootElement object is created, it should be getting a clone of the parent this.Application.Find. Thus it should propagate down. However once cloned they are treated separately. Thus changes to this.Application.Find won't automatically be reflected in rootElement.Find.

Greetings,
Cody
the Telerik team