This repository was archived by the owner on Nov 29, 2018. It is now read-only.
This repository was archived by the owner on Nov 29, 2018. It is now read-only.
WebDriverWait uses Implicit wait duration instead #4471
Closed
Description
Originally reported on Google Code with ID 4471
What steps will reproduce the problem?
1. Run the attached program
2. View the console output
What is the expected output? What do you see instead?
Expected output is something like:
Implicit wait: Find element took 3.148129654 s
Explicit wait: Find element took 3.160037161 s
Explicit and implicit wait: Find element took 3.136456231 s
Instead it is more like:
Implicit wait: Find element took 3.148129654 s
Explicit wait: Find element took 3.160037161 s
Explicit and implicit wait: Find element took 6.136456231 s
Selenium version: 2.25.0
OS: Windows 7
Browser: Program uses Firefox but browser is irrelevant to behavior
Browser version: 14.0.1
Please provide any additional information below.
The attachment is a simple program that displays three cases: a WebDriver with an implicit
wait set, a WebDriver without an implicit wait being used by a WebDriverWait, and a
WebDriver with an implicit wait and being used by a WebDriverWait. In the last case,
the implicit wait is *higher* than the duration set on the WebDriverWait. In each case,
the WebDriver will go to google and try to find an element that is not present, so
it will trigger whichever form of waiting is active. In the third case though, the
longer implicit wait is used, meaning the duration set in the constructor of the WebDriverWait
is essentially meaningless.
If the implicit wait is lower than the WebDriverWait's duration, then the behavior
is as expected, it's when the implicit wait is higher that it becomes a problem.
Reported by smith.6606
on 2012-08-27 17:50:59
- _Attachment: [ImplicitWaitTest.java](https://storage.googleapis.com/google-code-attachments/selenium/issue-4471/comment-0/ImplicitWaitTest.java)_