Implicit Waits

Set a global timeout for findElement calls to handle basic timing issues

Concept

An implicit wait tells Selenium to wait a specified amount of time when trying to find an element if it's not immediately available.

Once set, it applies to all findElement and findElements calls for the lifetime of the WebDriver instance.

What it does

Sets a global wait time for findElement calls.

If an element isn't found immediately, Selenium will keep trying until:

The element appears → returns it
Timeout is reached → throws NoSuchElementException

driver.manage().timeouts()
  .implicitlyWait(
    Duration.ofSeconds(10)
  );

When to use it

For simple apps where timing issues are small and consistent
As a basic safety net across your test suite
When you don't need fine-grained control over specific waits

Important

Default is 0 seconds (no waiting). You must set it explicitly if you want implicit waiting behavior.

Best Practice Notes

⚠Do NOT mix large implicit waits with explicit waits – it can lead to weird combined timeouts
→Prefer explicit waits for anything dynamic or unpredictable
✓Use small values (3-5 seconds) as a fallback, not as your primary wait strategy

Interactive Practice

Imagine a page where elements load with a slight delay. This demo shows how implicit wait keeps retrying:

Implicit Wait Simulator

Click the button to start simulation...

Click the button to see how Selenium retries finding an element with implicit wait enabled!

How it works

You call driver.findElement(By.id("btn"))
Selenium checks if the element exists in the DOM
If not found, Selenium waits ~500ms and tries again
This retry loop continues until either:
- Element is found → returns WebElement
- Timeout reached (10s) → throws exception

Java Code Example

ImplicitWaitExample.java

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
WebDriver driver = new ChromeDriver();

// Set implicit wait to 10 seconds - applies globally
driver.manage().timeouts()
      .implicitlyWait(Duration.ofSeconds(10));

// Navigate to the page
driver.get("https://example.com/dynamic-page");

// This will wait up to 10 seconds for the element to appear
WebElement delayedButton = driver.findElement(By.id("delayed-button"));
delayedButton.click();

// All subsequent findElement calls also use the 10s timeout
WebElement anotherElement = driver.findElement(By.className("content"));

driver.quit();

Code Breakdown

driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));: Sets a global implicit wait of 10 seconds. This applies to ALL subsequent findElement calls in this WebDriver session.
driver.get("https://example.com/dynamic-page");: Navigates to a page that may have dynamically loading elements.
driver.findElement(By.id("delayed-button"));: Tries to find the button. If it's not immediately available, Selenium will retry for up to 10 seconds (because of the implicit wait we set). If found within 10s, returns the element. If not, throws NoSuchElementException.
driver.findElement(By.className("content"));: Any other findElement call also benefits from the 10-second implicit wait. You don't need to set it again.
driver.quit();: Closes the browser and ends the WebDriver session.

Pro Tip

Set Once, Applies Everywhere

Implicit wait is set once at the start of your test and applies to every findElement call. You don't need to repeat it.

Keep Timeouts Small

Use short timeouts (3-5 seconds) for implicit waits. Long timeouts slow down failing tests significantly, since Selenium will always wait the full duration before throwing an exception.

Explicit Waits Are Better

For modern, dynamic web apps, prefer explicit waits. They're more precise, readable, and let you specify different conditions (visibility, clickability, text changes).