Explicit wait (WebDriverWait) in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this explicit wait code snippet?

Consider the following Selenium Java code using WebDriverWait. What will be the result printed?

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
WebElement element = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("submitBtn")));
System.out.println(element.isDisplayed());

A true

B false

C TimeoutException

D NoSuchElementException

💡 Hint

The wait waits until the element is visible or timeout occurs.

The WebDriverWait waits up to 10 seconds for the element with id 'submitBtn' to be visible. If found, element.isDisplayed() returns true and prints 'true'.

❓ assertion

intermediate

Which assertion correctly verifies the element is clickable using explicit wait?

You want to assert that a button with id 'loginBtn' is clickable before clicking it. Which assertion is correct?

A assertNull(wait.until(ExpectedConditions.elementToBeClickable(By.id("loginBtn"))));

B assertFalse(wait.until(ExpectedConditions.elementToBeClickable(By.id("loginBtn"))).isDisplayed());

C assertTrue(wait.until(ExpectedConditions.elementToBeClickable(By.id("loginBtn"))).isEnabled());

D assertEquals(wait.until(ExpectedConditions.elementToBeClickable(By.id("loginBtn"))), null);

💡 Hint

Clickable means the element is enabled and visible.

Option C waits until the element is clickable and asserts it is enabled, which is correct. Other options either assert false, null, or equality to null which are incorrect.

🔧 Debug

advanced

Why does this explicit wait code throw TimeoutException?

Analyze the code below. Why does it throw TimeoutException even though the element exists?

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
WebElement element = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("dynamicElement")));
// The element appears after 7 seconds on the page

A The wait time is less than the element's appearance delay, so it times out.

B The locator By.id("dynamicElement") is incorrect and cannot find the element.

C The element is present but not clickable, causing TimeoutException.

D The driver is not initialized, causing the wait to fail.

💡 Hint

Check the wait duration vs element appearance time.

The wait is set to 5 seconds but the element appears after 7 seconds, so the wait times out before the element is visible, causing TimeoutException.

🧠 Conceptual

advanced

What is the main difference between implicit wait and explicit wait in Selenium?

Choose the correct statement that explains the key difference between implicit and explicit waits.

A Implicit wait is deprecated; explicit wait is the only recommended wait method.

B Implicit wait waits for a specific condition; explicit wait sets a default wait time for all elements.

C Implicit wait only works with JavaScript alerts; explicit wait only works with page loads.

D Implicit wait sets a default wait time for all element searches; explicit wait waits for a specific condition for a particular element.

💡 Hint

Think about scope and usage of each wait type.

Implicit wait applies globally to all element searches, waiting a fixed time if elements are not immediately found. Explicit wait waits for a specific condition on a specific element before proceeding.

❓ framework

expert

Which code snippet correctly implements a fluent wait with polling and ignoring exceptions?

Select the code that creates a FluentWait in Selenium Java that polls every 2 seconds, waits up to 15 seconds, and ignores NoSuchElementException.

A

Wait<WebDriver> wait = new FluentWait<>(driver)
  .withTimeout(Duration.ofSeconds(15))
  .ignoring(NoSuchElementException.class)
  .pollingEvery(Duration.ofSeconds(2));

B

Wait<WebDriver> wait = new FluentWait<>(driver)
  .withTimeout(Duration.ofSeconds(15))
  .pollingEvery(Duration.ofSeconds(2))
  .ignoring(NoSuchElementException.class);

C

Wait<WebDriver> wait = new FluentWait<>(driver)
  .pollingEvery(Duration.ofSeconds(15))
  .withTimeout(Duration.ofSeconds(2))
  .ignoring(NoSuchElementException.class);

D

Wait<WebDriver> wait = new FluentWait<>(driver)
  .withTimeout(Duration.ofSeconds(2))
  .pollingEvery(Duration.ofSeconds(15))
  .ignoring(NoSuchElementException.class);

💡 Hint

Check the order and values of timeout and polling intervals.

Option B correctly sets timeout to 15 seconds, polling every 2 seconds, and ignores NoSuchElementException. Option B has correct methods but order does not affect behavior; however, best practice is to chain as in A. Options B and D have polling and timeout values swapped causing incorrect wait behavior.