I have the following step: Wait for element 'Div' 'is not' visiable.
Running the test it waits 30 seconds and then fails because the element is still visible. So, I increase the timeout time to 60000ms by enabling UseStepWaitOnElement property. However, the test continues to fail because it is still waiting 30 seconds. I tired running the test in a Test List and using the global ElementWaitTimeout setting with no success.
I can't seem to figure out why this step continues to wait 30 seconds even when changing the WaitOnElementsTimeout or the global ElementWaitTimeout setting.
Could this be because the element is a Div? If that is the case, could you recommend a possible work around?
Thanks in advance.
3 Answers, 1 is accepted
I'm sorry but there seems to be some confusion on how a timeout works in a wait for versus the wait on element timeout. These are actually 2 separate timeouts that work together in the test steps. The wait on element timeout is actually waiting for the element to exist in the underline browsers DOM. This timeout is controlled by the global settings as well as the use step weight on element property.
The other timeout, wait for element is not visible or any other test step, does not have a global setting. It does have a timeout property which you can find in the test step settings as shown in the attached screenshot.
I hope that clarifies how this is designed to work.
Regards,
Cody
Telerik
Rank 1
Cody,
Thank you for clarifying that up for me. I made the correct change in the timeout field in the test step settings. The step now executes properly.
Cheers!
Excellent! Thank you for the update.
Regards,
Cody
Telerik