does webdriverwait override implicitlywait when both are used?

  • Last Update :
  • Techknowledgy :

To further explain (pseudo C# code):

WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(20));
wait.Until(w => {
         return w.FindElement(By.Id("something")).Displayed;

It will hit:

return w.FindElement(By.Id("something")).Displayed;

Suggestion : 2

TestNG 28 May 2020 , 3 June 2020 at 1:43 AM , 1. What is TestNG and How to install it 27 May 2020

Implicit Wait

So do I need to use Implicitly Wait? Answer is really NO..

Dis-advantages of Implicitly Wait:

  • undocumented and practically undefined behaviour.
  • runs in the remote part of selenium (the part controlling the browser).
  • only works on find element(s) methods.
  • returns either element found or (after timeout) not found.
  • if checking for absence of element must always wait until timeout.
  • cannot be customised other than global timeout.

This list is gathered from observations and reading bug reports and cursory reading of selenium source code.

Let me tell you one thing : <Always use explicit wait. Forget that implicit wait exists>   --Naveen Khunteta

package com.example.automation;

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import java.time.Duration;
import java.util.function.Function;

 * @author Mandeep Kaur
 * @Date 2 May,2020
public class SeleniumConfig {
    public static void main(String[] args) {
        String path = System.getProperty("user.dir");
        System.setProperty("", "true");
        System.setProperty("", path + "/chromedriver");
        WebDriver driver = new ChromeDriver();
        // Create object of WebDriverWait class

        Wait wait = new FluentWait(driver)
                //Wait for the condition
                //checking for its presenceonce every 5 seconds.
                //Which will ignore the Exception

        WebElement element = wait.until(new Function<WebDriver, WebElement>() {
            public WebElement apply(WebDriver driver) {
                return driver.findElement("lastname"));


Suggestion : 3

To overcome the problem of race conditions between the browser and your WebDriver script, most Selenium clients ship with a wait package. When employing a wait, you are using what is commonly referred to as an explicit wait.,There is a second type of wait that is distinct from explicit wait called implicit wait. By implicitly waiting, WebDriver polls the DOM for a certain duration when trying to find any element. This can be useful when certain elements on the webpage are not available immediately and need some time to load.,The conditions available in the different language bindings vary, but this is a non-exhaustive list of a few:,With this knowledge, and because the wait utility ignores no such element errors by default, we can refactor our instructions to be more concise:

<!doctype html>
<meta charset=utf-8>
<title>Race Condition Example</title>

  var initialised = false;
  window.addEventListener("load", function() {
    var newElement = document.createElement("p");
    newElement.textContent = "Hello from JavaScript!";
    initialised = true;
WebElement element = driver.findElement(By.tagName("p"));
assertEquals(element.getText(), "Hello from JavaScript!");
el = driver.find_element(By.TAG_NAME, "p")
assert el.text == "Hello from JavaScript!"
IWebElement element = driver.FindElement(By.TagName("p"));
assertEquals(element.Text, "Hello from JavaScript!");
require 'selenium-webdriver'
driver = Selenium::WebDriver.for: firefox
# Navigate to URL
driver.get 'file:///race_condition.html'

# Get and store Paragraph Text
search_form = driver.find_element(: css, 'p').text

"Hello from JavaScript!".eql ? search_form
await driver.get('file:///race_condition.html');
const element = driver.findElement(By.css('p'));
assert.strictEqual(await element.getText(), 'Hello from JavaScript!');