ExpectedConditions class in Selenium Java - Build an Automation Script

Wait for a button to be clickable and then click it

Preconditions (1)

Step 1: Open the web page URL

Step 2: Wait until the button with id 'submitBtn' is clickable using ExpectedConditions

Step 3: Click the button

Step 4: Verify that the button click leads to the URL 'https://example.com/nextpage'

✅ Expected Result: The button is clicked only after it becomes clickable, and the browser navigates to 'https://example.com/nextpage'

Automation Requirements - Selenium WebDriver with Java

Assertions Needed:

Verify the button is clickable before clicking

Verify the current URL after clicking the button is 'https://example.com/nextpage'

Best Practices:

Use WebDriverWait with ExpectedConditions for waiting

Use By.id locator for the button

Avoid Thread.sleep; use explicit waits

Use try-catch to handle possible exceptions

Close the browser after test

Automated Solution

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 java.time.Duration;

public class ExpectedConditionsTest {
    public static void main(String[] args) {
        System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");
        WebDriver driver = new ChromeDriver();
        try {
            driver.get("https://example.com/startpage");

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

            submitButton.click();

            wait.until(ExpectedConditions.urlToBe("https://example.com/nextpage"));

            String currentUrl = driver.getCurrentUrl();
            if (!currentUrl.equals("https://example.com/nextpage")) {
                throw new AssertionError("URL after click is not as expected. Found: " + currentUrl);
            }

            System.out.println("Test Passed: Button clicked after becoming clickable and URL verified.");
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            driver.quit();
        }
    }
}

This code uses Selenium WebDriver with Java to automate the test case.

First, it opens the browser and navigates to the start page.

Then, it creates a WebDriverWait object with a 10-second timeout.

It waits explicitly for the button with id submitBtn to become clickable using ExpectedConditions.elementToBeClickable.

Once clickable, it clicks the button.

After clicking, it waits until the URL changes to the expected next page URL using ExpectedConditions.urlToBe.

It then asserts that the current URL matches the expected URL.

If all steps pass, it prints a success message.

The try-finally block ensures the browser closes even if an error occurs.

Common Mistakes - 4 Pitfalls

Using Thread.sleep() instead of WebDriverWait with ExpectedConditions

Using incorrect locator like XPath with absolute path for the button

Clicking the button without waiting for it to be clickable

Not closing the browser after test execution

Bonus Challenge

Now add data-driven testing to wait for and click buttons with ids 'submitBtn1', 'submitBtn2', and 'submitBtn3' on the same page, verifying navigation after each click.

Show Hint

Practice

1. What is the main purpose of the ExpectedConditions class in Selenium WebDriver?

easy

A. To perform browser navigation actions

B. To locate web elements on the page

C. To wait for certain conditions or states of web elements before proceeding

D. To execute JavaScript code on the page

Solution

1. Step 1: Understand the role of ExpectedConditions

   The ExpectedConditions class provides predefined conditions to wait for, such as visibility or clickability of elements.

2. Step 2: Compare with other Selenium functions

   Locating elements, navigation, and JavaScript execution are handled by other classes or methods, not ExpectedConditions.

3. Final Answer:

   To wait for certain conditions or states of web elements before proceeding -> Option C

4. Quick Check:

   ExpectedConditions = wait for element states [OK]

Hint: ExpectedConditions waits for element states before actions [OK]

Common Mistakes:

• Confusing ExpectedConditions with element locators
• Thinking it performs actions like clicking
• Assuming it runs JavaScript

2. Which of the following is the correct syntax to wait until an element located by By.id("submit") is clickable using ExpectedConditions and WebDriverWait?

easy

A. WebDriverWait(driver, 10).wait(ExpectedConditions.elementToBeClickable(By.id("submit")));

B. new WebDriverWait(driver, 10).until(ExpectedConditions.elementToBeClickable(By.id("submit")));

C. new WebDriverWait(driver, 10).waitFor(ExpectedConditions.elementToBeClickable(By.id("submit")));

D. WebDriverWait(driver, 10).until(ExpectedConditions.elementIsClickable(By.id("submit")));

Solution

1. Step 1: Identify correct WebDriverWait constructor and method

   The correct way is to create a new WebDriverWait object and call the until method.

2. Step 2: Check ExpectedConditions method name

   The method is elementToBeClickable, not elementIsClickable, and the locator is passed correctly.

3. Final Answer:

   new WebDriverWait(driver, 10).until(ExpectedConditions.elementToBeClickable(By.id("submit"))); -> Option B

4. Quick Check:

   Use new WebDriverWait + until + elementToBeClickable [OK]

Hint: Use new WebDriverWait(driver, time).until(condition) [OK]

Common Mistakes:

• Using wait() instead of until()
• Wrong method name like elementIsClickable
• Not creating new WebDriverWait instance

3. Consider the following code snippet:

WebDriverWait wait = new WebDriverWait(driver, 5);
WebElement element = wait.until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector(".login-button")));
element.click();

What happens if the element with class login-button is not visible within 5 seconds?

medium

A. The test passes without clicking the element

B. The code clicks on the element anyway

C. The wait silently ignores and continues without clicking

D. A TimeoutException is thrown and the test fails

Solution

1. Step 1: Understand behavior of WebDriverWait with ExpectedConditions

   If the condition is not met within the timeout, WebDriverWait throws a TimeoutException.

2. Step 2: Analyze the code flow

   Since the element is not visible within 5 seconds, wait.until throws an exception, so element.click() is not executed.

3. Final Answer:

   A TimeoutException is thrown and the test fails -> Option D

4. Quick Check:

   TimeoutException if condition unmet in wait [OK]

Hint: Wait throws TimeoutException if condition unmet [OK]

Common Mistakes:

• Assuming click happens even if element not visible
• Thinking wait ignores failure silently
• Believing test passes without clicking

4. Identify the error in the following code snippet:

WebDriverWait wait = new WebDriverWait(driver, 10);
wait.until(ExpectedConditions.presenceOfElementLocated("#username"));

medium

A. The locator should be a By object, not a String

B. The timeout value should be in milliseconds

C. ExpectedConditions.presenceOfElementLocated does not exist

D. WebDriverWait cannot be used with ExpectedConditions

Solution

1. Step 1: Check the argument type for presenceOfElementLocated

   This method requires a By locator, not a plain string.

2. Step 2: Verify the locator usage

   Instead of passing "#username", it should be By.cssSelector("#username") or another By method.

3. Final Answer:

   The locator should be a By object, not a String -> Option A

4. Quick Check:

   presenceOfElementLocated needs By locator [OK]

Hint: Use By locators, not strings, with ExpectedConditions [OK]

Common Mistakes:

• Passing string selector instead of By object
• Confusing timeout units (seconds vs milliseconds)
• Thinking ExpectedConditions methods don't exist

5. You want to wait until either an element with id loading disappears or a maximum of 15 seconds passes before clicking a button with id continue. Which code snippet correctly uses ExpectedConditions to achieve this?

hard

A. new WebDriverWait(driver, 15).until(ExpectedConditions.invisibilityOfElementLocated(By.id("loading")));
driver.findElement(By.id("continue")).click();

B. new WebDriverWait(driver, 15).until(ExpectedConditions.visibilityOfElementLocated(By.id("loading")));
driver.findElement(By.id("continue")).click();

C. new WebDriverWait(driver, 15).until(ExpectedConditions.elementToBeClickable(By.id("loading")));
driver.findElement(By.id("continue")).click();

D. new WebDriverWait(driver, 15).until(ExpectedConditions.presenceOfElementLocated(By.id("continue")));
driver.findElement(By.id("loading")).click();

Solution

1. Step 1: Identify the condition to wait for

   The requirement is to wait until the element with id "loading" disappears, which matches invisibilityOfElementLocated.

2. Step 2: Confirm the action after wait

   After waiting, the code clicks the button with id "continue" as required.

3. Final Answer:

   new WebDriverWait(driver, 15).until(ExpectedConditions.invisibilityOfElementLocated(By.id("loading"))); driver.findElement(By.id("continue")).click(); -> Option A

4. Quick Check:

   Wait for invisibility, then click continue [OK]

Hint: Wait for invisibilityOfElementLocated before clicking [OK]

Common Mistakes:

• Waiting for visibility instead of invisibility
• Clicking wrong element after wait
• Using presenceOfElementLocated for disappearance