Explicit wait (WebDriverWait) in Selenium Java - Test Execution Trace

Test Overview

This test opens a webpage, waits explicitly for a button to become clickable using WebDriverWait, clicks it, and verifies the expected result appears.

Test Code - JUnit with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertEquals;
import java.time.Duration;

public class ExplicitWaitTest {
    WebDriver driver;
    WebDriverWait wait;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        wait = new WebDriverWait(driver, Duration.ofSeconds(10));
    }

    @Test
    public void testButtonClickWithExplicitWait() {
        driver.get("https://example.com/wait-demo");

        // Wait until the button with id 'delayed-button' is clickable
        WebElement button = wait.until(ExpectedConditions.elementToBeClickable(By.id("delayed-button")));

        button.click();

        // Verify that clicking the button shows the message with id 'result-message'
        WebElement message = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("result-message")));
        String text = message.getText();
        assertEquals("Button clicked!", text);
    }

    @AfterEach
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts and Chrome browser opens	Chrome browser window is open and ready	—	PASS
2	Navigates to https://example.com/wait-demo	Page loads with a delayed button that appears after some time	—	PASS
3	Waits explicitly up to 10 seconds for the button with id 'delayed-button' to become clickable using WebDriverWait	Button becomes visible and clickable on the page	Checks that the button is clickable before proceeding	PASS
4	Clicks the 'delayed-button'	Button is clicked, triggering a message to appear	—	PASS
5	Finds the element with id 'result-message' and reads its text	Message 'Button clicked!' is displayed on the page	Verifies the message text equals 'Button clicked!'	PASS
6	Test ends and browser closes	Browser window is closed	—	PASS

Failure Scenario

Failing Condition: The button with id 'delayed-button' does not become clickable within 10 seconds

Execution Trace Quiz - 3 Questions

What does the WebDriverWait in this test do?

A Waits for the page to load completely

B Waits until the button is clickable before clicking it

C Waits for the browser to open

D Waits for the test to finish

Key Result

Using explicit waits like WebDriverWait helps tests wait only as long as needed for elements to be ready, making tests more reliable and faster than fixed delays.

Practice

1. What is the main purpose of using WebDriverWait in Selenium tests?

easy

A. To automatically retry failed tests

B. To speed up the test execution by skipping waits

C. To pause the test until a specific condition is met or timeout occurs

D. To capture screenshots during test execution

Solution

1. Step 1: Understand the role of waits in Selenium

   Waits help tests handle dynamic page content by pausing until elements are ready.

2. Step 2: Identify what WebDriverWait does

   WebDriverWait explicitly waits for a condition like element visibility or clickability before proceeding.

3. Final Answer:

   To pause the test until a specific condition is met or timeout occurs -> Option C

4. Quick Check:

   Explicit wait = pause until condition met [OK]

Hint: Waits pause tests until conditions, not speed up [OK]

Common Mistakes:

• Confusing explicit wait with implicit wait
• Thinking it speeds up tests by skipping steps
• Using it to retry tests automatically

2. Which of the following is the correct syntax to create a WebDriverWait object with a 10-second timeout in Java?

easy

A. WebDriverWait wait = new WebDriverWait(driver, 10);

B. WebDriverWait wait = new WebDriverWait(Duration.ofSeconds(10), driver);

C. WebDriverWait wait = new WebDriverWait(10, driver);

D. WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));

Solution

1. Step 1: Recall the constructor for WebDriverWait in Selenium 4+

   It requires the WebDriver instance and a Duration object for timeout.

2. Step 2: Match the correct syntax

   WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10)); uses Duration.ofSeconds(10) correctly with the driver as first argument.

3. Final Answer:

   WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10)); -> Option D

4. Quick Check:

   Use Duration for timeout in WebDriverWait [OK]

Hint: Use Duration.ofSeconds for timeout in WebDriverWait [OK]

Common Mistakes:

• Passing timeout as int instead of Duration
• Swapping driver and timeout arguments
• Using deprecated constructors

3. What will happen when the following code runs if the element with id "submitBtn" becomes clickable after 5 seconds?

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
WebElement button = wait.until(ExpectedConditions.elementToBeClickable(By.id("submitBtn")));
button.click();

medium

A. The test waits up to 10 seconds, finds the button when clickable, then clicks it

B. The test immediately throws a timeout exception

C. The test clicks the button immediately without waiting

D. The test waits 5 seconds then throws a stale element exception

Solution

1. Step 1: Understand the wait condition and timeout

   The wait will pause up to 10 seconds for the button to become clickable.

2. Step 2: Analyze the element state after 5 seconds

   The button becomes clickable after 5 seconds, so wait.until returns the element successfully.

3. Final Answer:

   The test waits up to 10 seconds, finds the button when clickable, then clicks it -> Option A

4. Quick Check:

   Waits up to timeout, proceeds when condition met [OK]

Hint: Waits up to timeout, proceeds once condition is true [OK]

Common Mistakes:

• Assuming immediate failure if element not ready
• Thinking wait always waits full timeout
• Confusing stale element with clickable condition

4. Identify the error in this code snippet using WebDriverWait:

WebDriverWait wait = new WebDriverWait(driver, 10);
wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("username")));

medium

A. ExpectedConditions is not imported

B. Timeout value should be wrapped in Duration.ofSeconds()

C. By.id() cannot be used with visibilityOfElementLocated

D. wait.until() should return a boolean, not void

Solution

1. Step 1: Check the WebDriverWait constructor usage

   Since Selenium 4, the timeout must be a Duration object, not an int.

2. Step 2: Confirm the correct way to specify timeout

   Use Duration.ofSeconds(10) to specify 10 seconds timeout.

3. Final Answer:

   Timeout value should be wrapped in Duration.ofSeconds() -> Option B

4. Quick Check:

   Timeout must be Duration, not int [OK]

Hint: Use Duration.ofSeconds for timeout, not plain int [OK]

Common Mistakes:

• Passing int instead of Duration causes compile error
• Ignoring import errors for ExpectedConditions
• Misunderstanding return type of wait.until()

5. You want to wait for a button with CSS class "submit-btn" to be clickable, but only wait up to 5 seconds. If it doesn't become clickable, you want to log a message and continue without failing the test. Which code snippet correctly implements this using WebDriverWait?

hard

A. try {
WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
WebElement btn = wait.until(ExpectedConditions.elementToBeClickable(By.cssSelector(".submit-btn")));
btn.click();
} catch (TimeoutException e) {
System.out.println("Button not clickable in time, continuing test.");
}

B. WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
WebElement btn = wait.until(ExpectedConditions.elementToBeClickable(By.cssSelector(".submit-btn")));
btn.click();
System.out.println("Button not clickable in time, continuing test.");

C. WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
if (wait.until(ExpectedConditions.elementToBeClickable(By.cssSelector(".submit-btn")))) {
driver.findElement(By.cssSelector(".submit-btn")).click();
} else {
System.out.println("Button not clickable in time, continuing test.");
}

D. WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
WebElement btn = wait.until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector(".submit-btn")));
btn.click();

Solution

1. Step 1: Use try-catch to handle timeout without failing test

   Wrap the wait in try block and catch TimeoutException to log and continue.

2. Step 2: Use elementToBeClickable with correct selector and timeout

   Create WebDriverWait with 5 seconds timeout and wait for clickable condition.

3. Step 3: Click the button if found, else log message

   If wait succeeds, click the button; if timeout occurs, catch block logs message and test continues.

4. Final Answer:

   Code with try-catch around wait and logging on timeout -> Option A

5. Quick Check:

   Handle timeout with try-catch to continue test [OK]

Hint: Use try-catch around wait to handle timeout gracefully [OK]

Common Mistakes:

• Not catching TimeoutException causing test failure
• Using visibility instead of clickable condition
• Logging message after wait without exception handling