RE: Fluent Wait not working as expected

I observed fluent wait not identifying an element even though page is loaded completely and element is visible on the screen. For an example, I have an application with say page A and Page B. On clicking continue button on page A, user navigates to Page B where I am trying to identify a button Webelement by waiting 60 secs. Even though page is loaded completely and button is present on Page B, I see webdriver keep on polling to identify webelement and fails at the end with NoSuchElementException. If I add a sleep for 5 secs and perform same action, script is working fine. is anybody facing same problem and found a solution to deal with such problem. Any help in this matter would be greatly appreciated.

rockygarg11 Default Asked on February 16, 2016 in Selenium WebDriver.


Total wait time = 60 seconds
Polling time = ??

Are you adding Sleep Additional to the polling time?
If possible share code snippet.

on February 17, 2016.
Add Comment
1 Answers

I have seen a similar problem recently but it was my code only. We had to switch to an Iframe before waiting. Anyway that might not be true in your case. Can you share your code and also if its possible to share the test site?


Professor Answered on February 16, 2016.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.