FluentWait with polling in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is FluentWait in Selenium?

FluentWait is a Selenium wait that lets you wait for a condition with a custom timeout and polling interval. It checks repeatedly until the condition is true or timeout happens.

beginner

How does polling interval affect FluentWait?

Polling interval is how often FluentWait checks the condition. Smaller intervals check more often but use more resources; larger intervals check less often and may delay detection.

intermediate

Show a simple example of FluentWait with polling in Java Selenium.

FluentWait<WebDriver> wait = new FluentWait<>(driver) .withTimeout(Duration.ofSeconds(10)) .pollingEvery(Duration.ofMillis(500)) .ignoring(NoSuchElementException.class); WebElement element = wait.until(driver -> driver.findElement(By.id("myElement")));

beginner

Why use FluentWait instead of Thread.sleep()?

FluentWait waits only as long as needed and checks repeatedly, so tests run faster and more reliably. Thread.sleep() waits a fixed time no matter what, wasting time or causing flakiness.

intermediate

What exceptions can FluentWait ignore during polling?

FluentWait can ignore exceptions like NoSuchElementException or ElementNotVisibleException while waiting. This means it won't fail immediately if the element is not found yet.

What does the polling interval in FluentWait control?

A The maximum number of retries

B The total wait time before timeout

C The type of exception to ignore

D How often the condition is checked

Polling interval controls how often FluentWait checks the condition during the wait period.

Which exception is commonly ignored in FluentWait to avoid early failure?

A NoSuchElementException

B NullPointerException

C ArithmeticException

D IOException

NoSuchElementException is often ignored because the element may not be present yet during waiting.

What happens if the condition is met before the timeout in FluentWait?

A An exception is thrown

B Wait continues until timeout anyway

C Wait stops immediately and returns the result

D Polling interval is reset

FluentWait stops waiting as soon as the condition is true and returns the result.

Why is FluentWait preferred over Thread.sleep()?

A It waits only as long as needed and checks repeatedly

B It uses less memory

C It runs tests in parallel

D It automatically fixes bugs

FluentWait is smarter because it waits dynamically and polls, unlike fixed Thread.sleep().

Which method sets the polling interval in FluentWait?

A withTimeout()

B pollingEvery()

C ignoring()

D until()

pollingEvery() sets how often FluentWait checks the condition.

Explain how FluentWait works with polling in Selenium.

Think about waiting for an element to appear but checking every half second.

Describe the advantages of using FluentWait with polling over fixed waits like Thread.sleep().

Compare waiting dynamically vs waiting blindly.

Practice

1. What is the main purpose of using FluentWait in Selenium Java?

easy

A. To throw an exception as soon as an element is not found

B. To wait for an element with a custom timeout and polling interval

C. To immediately find an element without waiting

D. To perform actions on elements without any wait

Solution

1. Step 1: Understand FluentWait functionality

   FluentWait allows waiting for a condition with a custom timeout and polling frequency.

2. Step 2: Compare options with FluentWait purpose

   Only To wait for an element with a custom timeout and polling interval describes waiting with custom timeout and polling, which matches FluentWait's use.

3. Final Answer:

   To wait for an element with a custom timeout and polling interval -> Option B

4. Quick Check:

   FluentWait = custom wait with polling [OK]

Hint: FluentWait customizes wait time and checks repeatedly [OK]

Common Mistakes:

• Confusing FluentWait with immediate findElement
• Thinking FluentWait throws exception immediately
• Assuming FluentWait skips polling

2. Which of the following is the correct way to create a FluentWait object with polling every 500 milliseconds?

easy

A. new FluentWait(driver).pollingEvery(Duration.ofMillis(500))

B. new FluentWait(driver).pollingEvery(500, TimeUnit.MILLISECONDS)

C. new FluentWait(driver).pollingEvery(500)

D. new FluentWait(driver).pollingEvery(Duration.ofSeconds(500))

Solution

1. Step 1: Check correct Duration usage for pollingEvery

   pollingEvery expects a Duration object, so Duration.ofMillis(500) is correct for 500 ms.

2. Step 2: Analyze other options for syntax errors

   new FluentWait(driver).pollingEvery(Duration.ofSeconds(500)) uses seconds instead of milliseconds; B uses deprecated TimeUnit syntax; C uses int without Duration.

3. Final Answer:

   new FluentWait(driver).pollingEvery(Duration.ofMillis(500)) -> Option A

4. Quick Check:

   pollingEvery needs Duration.ofMillis for milliseconds [OK]

Hint: Use Duration.ofMillis for polling intervals in FluentWait [OK]

Common Mistakes:

• Using Duration.ofSeconds instead of ofMillis for milliseconds
• Passing int directly without Duration
• Using deprecated TimeUnit with pollingEvery

3. What will happen when the following FluentWait code runs if the element appears after 3 seconds?

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

WebElement element = wait.until(d -> d.findElement(By.id("dynamicElement")));
System.out.println(element.getText());

medium

A. The code waits full 5 seconds then throws TimeoutException

B. The code throws NoSuchElementException immediately

C. The element is found and its text is printed after about 3 seconds

D. The code prints null because element is not found

Solution

1. Step 1: Understand FluentWait behavior with polling and timeout

   The wait polls every 1 second up to 5 seconds, ignoring NoSuchElementException until element appears.

2. Step 2: Analyze timing and result

   Since element appears after 3 seconds, wait finds it before timeout and prints its text.

3. Final Answer:

   The element is found and its text is printed after about 3 seconds -> Option C

4. Quick Check:

   FluentWait polls until element found or timeout [OK]

Hint: FluentWait polls repeatedly until element found or timeout [OK]

Common Mistakes:

• Expecting immediate exception on missing element
• Assuming wait always waits full timeout
• Thinking element text prints null if not found

4. Identify the error in this FluentWait code snippet:

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

WebElement element = wait.until(d -> d.findElement(By.id("test")));

medium

A. pollingEvery should use Duration, not int

B. withTimeout should be in milliseconds, not seconds

C. Ignoring NoSuchElementException is not allowed

D. FluentWait cannot be used with WebDriver

Solution

1. Step 1: Check pollingEvery parameter type

   pollingEvery expects a Duration object, but 500 (int) is passed, causing a compile error.

2. Step 2: Verify other method usages

   withTimeout(Duration.ofSeconds(10)) is correct; ignoring NoSuchElementException is valid; FluentWait works with WebDriver.

3. Final Answer:

   pollingEvery should use Duration, not int -> Option A

4. Quick Check:

   pollingEvery requires Duration parameter [OK]

Hint: pollingEvery needs Duration, not plain int [OK]

Common Mistakes:

• Passing int directly to pollingEvery
• Confusing withTimeout units
• Thinking ignoring exceptions is invalid

5. You want to wait up to 10 seconds for an element with id "submitBtn" to appear, checking every 2 seconds, and ignoring both NoSuchElementException and ElementNotVisibleException. Which FluentWait code snippet correctly implements this?

hard

A. new FluentWait<>(driver)
.withTimeout(Duration.ofSeconds(10))
.pollingEvery(Duration.ofSeconds(2))
.ignoring(NoSuchElementException.class)
.until(d -> d.findElement(By.id("submitBtn")));

B. new FluentWait<>(driver)
.withTimeout(Duration.ofSeconds(10))
.pollingEvery(Duration.ofSeconds(2))
.ignoring(NoSuchElementException.class ElementNotVisibleException.class)
.until(d -> d.findElement(By.id("submitBtn")));

C. new FluentWait<>(driver)
.withTimeout(10)
.pollingEvery(2)
.ignoring(NoSuchElementException.class)
.ignoring(ElementNotVisibleException.class)
.until(d -> d.findElement(By.id("submitBtn")));

D. new FluentWait<>(driver)
.withTimeout(Duration.ofSeconds(10))
.pollingEvery(Duration.ofSeconds(2))
.ignoring(NoSuchElementException.class)
.ignoring(ElementNotVisibleException.class)
.until(d -> d.findElement(By.id("submitBtn")));

Solution

1. Step 1: Check timeout and polling interval syntax

   withTimeout and pollingEvery correctly use Duration.ofSeconds(10) and Duration.ofSeconds(2) in new FluentWait<>(driver) .withTimeout(Duration.ofSeconds(10)) .pollingEvery(Duration.ofSeconds(2)) .ignoring(NoSuchElementException.class) .ignoring(ElementNotVisibleException.class) .until(d -> d.findElement(By.id("submitBtn")));.

2. Step 2: Verify ignoring multiple exceptions

   new FluentWait<>(driver) .withTimeout(Duration.ofSeconds(10)) .pollingEvery(Duration.ofSeconds(2)) .ignoring(NoSuchElementException.class) .ignoring(ElementNotVisibleException.class) .until(d -> d.findElement(By.id("submitBtn"))); chains .ignoring() calls for each exception, which is valid. new FluentWait<>(driver) .withTimeout(Duration.ofSeconds(10)) .pollingEvery(Duration.ofSeconds(2)) .ignoring(NoSuchElementException.class, ElementNotVisibleException.class) .until(d -> d.findElement(By.id("submitBtn"))); tries to pass two exceptions in one call, which is invalid.

3. Step 3: Confirm other options

   new FluentWait<>(driver) .withTimeout(10) .pollingEvery(2) .ignoring(NoSuchElementException.class) .ignoring(ElementNotVisibleException.class) .until(d -> d.findElement(By.id("submitBtn"))); uses int instead of Duration, causing errors. new FluentWait<>(driver) .withTimeout(Duration.ofSeconds(10)) .pollingEvery(Duration.ofSeconds(2)) .ignoring(NoSuchElementException.class) .until(d -> d.findElement(By.id("submitBtn"))); ignores only one exception, missing ElementNotVisibleException.

4. Final Answer:

   new FluentWait<>(driver) .withTimeout(Duration.ofSeconds(10)) .pollingEvery(Duration.ofSeconds(2)) .ignoring(NoSuchElementException.class) .ignoring(ElementNotVisibleException.class) .until(d -> d.findElement(By.id("submitBtn"))); -> Option D

5. Quick Check:

   Chain ignoring() for multiple exceptions with Duration times [OK]

Hint: Chain ignoring() for each exception; use Duration for times [OK]

Common Mistakes:

• Passing multiple exceptions in one ignoring() call
• Using int instead of Duration for time values
• Ignoring only one exception when multiple needed