ExpectedConditions class in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of waiting for element visibility

What will be the result of this Selenium Java code snippet when the element with id 'submitBtn' becomes visible within 10 seconds?

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 NoSuchElementException

B true

C false

D TimeoutException

💡 Hint

visibilityOfElementLocated waits until the element is visible on the page.

The ExpectedConditions.visibilityOfElementLocated waits up to the specified time for the element to be visible. If it becomes visible, it returns the WebElement, so isDisplayed() returns true.

❓ assertion

intermediate

Correct assertion for element to be clickable

Which assertion correctly verifies that a button with id 'loginBtn' is clickable using ExpectedConditions in Selenium Java?

Selenium Java

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

A assertTrue(button.isEnabled() && button.isDisplayed());

B assertFalse(button.isEnabled());

C assertNull(button);

D assertEquals(button.getText(), "Submit");

💡 Hint

elementToBeClickable means the element is visible and enabled.

ExpectedConditions.elementToBeClickable returns the element only if it is visible and enabled. So asserting isEnabled() and isDisplayed() true confirms it is clickable.

🔧 Debug

advanced

Identify the error in ExpectedConditions usage

What is the error in this Selenium Java code snippet?

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(8));
wait.until(ExpectedConditions.presenceOfElementLocated(By.xpath("//div[@class='content']")));

A No error; code waits for element presence correctly.

B By.xpath locator syntax is invalid.

C Duration.ofSeconds should be replaced with just seconds as int.

D presenceOfElementLocated does not wait for visibility, so element may not be interactable.

💡 Hint

presenceOfElementLocated waits only for element in DOM, not visibility.

presenceOfElementLocated waits for the element to be present in the DOM but does not guarantee it is visible or interactable. This can cause issues if interaction is attempted immediately after.

🧠 Conceptual

advanced

Understanding ExpectedConditions stalenessOf

What does the ExpectedConditions.stalenessOf(WebElement element) condition check in Selenium Java?

A Checks if the element is no longer attached to the DOM.

B Checks if the element is visible on the page.

C Checks if the element is enabled and clickable.

D Checks if the element's text matches a given string.

💡 Hint

Staleness means the element reference is outdated.

stalenessOf waits until the element is no longer attached to the DOM, meaning it has been removed or refreshed. This is useful to wait for page updates.

❓ framework

expert

Best practice for waiting for multiple conditions

In Selenium Java, which approach correctly waits until both an element with id 'username' is visible and a button with id 'submit' is clickable before proceeding?

A

wait.until(ExpectedConditions.and(
    ExpectedConditions.visibilityOfElementLocated(By.id("username")),
    ExpectedConditions.elementToBeClickable(By.id("submit"))
));

B

wait.until(ExpectedConditions.or(
    ExpectedConditions.visibilityOfElementLocated(By.id("username")),
    ExpectedConditions.elementToBeClickable(By.id("submit"))
));

C

wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("username")));
wait.until(ExpectedConditions.elementToBeClickable(By.id("submit")));

D

wait.until(ExpectedConditions.not(
    ExpectedConditions.invisibilityOfElementLocated(By.id("username"))
));

💡 Hint

Chain sequential wait.until calls to ensure both conditions.

Chaining wait.until calls first waits for the username field to be visible, then for the submit button to be clickable. ExpectedConditions does not provide 'and' or 'or'; sequential waits are a standard best practice to ensure both conditions before proceeding.