When waiting for element to exist in code, Test Studio doesn't respect the timeout set in the coded step.

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 04 Apr 2013 07:38 by ADMIN

ADMIN

Plamen

Created on: 21 Mar 2013 16:13

Type: Bug Report

When waiting for element to exist in code, Test Studio doesn't respect the timeout set in the coded step.

When waiting for element to exist in code, Test Studio doesn't respect the timeout set in the coded step. Instead it uses the global "Wait on elements timeout" from the Quick Execution options.

For example, if we have the following code: 
Pages.ASPNETComboBoxDemo.ListItem.Wait.ForExists(10000);
and "Wait on elements timeout" is set to 30000, Test Studio will wait for 30 seconds insted of 10.

1 comment

ADMIN

Konstantin Petkov

Posted on: 28 Mar 2013 12:24

Yes, that is expected. When you call Page.Element (ListItem in this case) you obviously haven't reached the ForExists method yet, where you pass the timeout argument. Please use Browser.WaitForElement() code like this instead:

ActiveBrowser.WaitForElement(Pages.ASPNETComboBoxDemo.ListItem, 30000, false);