FluentWait with polling in Selenium Java - Framework Patterns

Framework Mode - FluentWait with polling

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── WaitUtils.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown for browser control.
• Page Objects: Classes representing web pages with locators and actions.
• Tests: Test classes containing test methods using assertions.
• Utilities: Helper classes like WaitUtils implementing FluentWait with polling.
• Config: Configuration classes for environment variables, browser types, and credentials.

Configuration Patterns

• Use TestConfig.java to store environment URLs, browser choices, and credentials.
• Load configurations from properties files or environment variables for flexibility.
• Allow switching browsers (Chrome, Firefox) via config to run tests on different browsers.
• Configure FluentWait polling interval and timeout values in WaitUtils or config files.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports to generate XML/HTML test reports after execution.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests automatically on code changes.
• Configure reports to show pass/fail status and detailed failure reasons including wait timeouts.
• Use screenshots on failure to help debug wait-related issues.

Framework Design Principles

• Use FluentWait for flexible waiting: Allows setting timeout, polling interval, and ignoring exceptions.
• Centralize wait logic: Implement FluentWait in utility classes to reuse across tests.
• Use explicit waits over implicit waits: Avoid flaky tests by waiting only where needed.
• Handle exceptions gracefully: Ignore common exceptions like NoSuchElementException during polling.
• Keep locators in Page Objects: Separate page structure from wait logic for maintainability.

Self Check

Where in this folder structure would you add a new utility method that uses FluentWait to wait for an element to be clickable?

Key Result

Use FluentWait with polling in utility classes to create flexible, reusable wait conditions in Selenium Java frameworks.

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