Handling StaleElementReferenceException in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Java code snippet?

Consider the following Selenium Java code that tries to click a button after a page refresh:

WebElement button = driver.findElement(By.id("submitBtn"));
driver.navigate().refresh();
button.click();

What will happen when this code runs?

Selenium Java

WebElement button = driver.findElement(By.id("submitBtn"));
driver.navigate().refresh();
button.click();

A Throws StaleElementReferenceException because the element reference is no longer valid after refresh.

B The button is clicked successfully without any exception.

C Throws NoSuchElementException because the element is not found after refresh.

D Throws TimeoutException because the click waits too long for the element.

💡 Hint

Think about what happens to a WebElement reference after the page reloads.

After refreshing the page, the previously found WebElement becomes stale because the DOM has been reloaded. Trying to interact with it causes a StaleElementReferenceException.

❓ assertion

intermediate

Which assertion correctly verifies handling of StaleElementReferenceException?

You want to write a test that confirms your code retries finding an element after catching a StaleElementReferenceException. Which assertion best verifies this behavior?

A assertTrue(element.isDisplayed());

B assertDoesNotThrow(() -> retryFindElementAndClick());

C assertEquals("Submit", element.getText());

D assertThrows(StaleElementReferenceException.class, () -> element.click());

💡 Hint

Think about what it means to handle the exception properly in your test.

assertDoesNotThrow confirms that the retry method handles the exception internally and succeeds without throwing it to the test.

🔧 Debug

advanced

Identify the cause of StaleElementReferenceException in this code

Review this Selenium Java code snippet:

WebElement menu = driver.findElement(By.id("menu"));
menu.click();
WebElement submenu = driver.findElement(By.id("submenu"));
driver.navigate().refresh();
submenu.click();

Why does submenu.click() throw StaleElementReferenceException?

Selenium Java

WebElement menu = driver.findElement(By.id("menu"));
menu.click();
WebElement submenu = driver.findElement(By.id("submenu"));
driver.navigate().refresh();
submenu.click();

A submenu element is not clickable because it is hidden by another element.

B menu element click caused the submenu to disappear, so submenu is not found.

C driver.navigate().refresh() does not reload the page, so submenu is invalid.

D submenu element was found before page refresh, so its reference is stale after refresh.

💡 Hint

Consider when submenu was located relative to the page refresh.

The submenu element was located before the page refresh. After refresh, the DOM is new and the old reference is stale, causing the exception.

❓ framework

advanced

Which Selenium Java code snippet correctly retries after StaleElementReferenceException?

Choose the code snippet that properly retries finding and clicking an element when a StaleElementReferenceException occurs.

A

for (int i = 0; i < 3; i++) {
  try {
    driver.findElement(By.id("btn")).click();
    break;
  } catch (StaleElementReferenceException e) {
    Thread.sleep(1000);
  }
}

B

try {
  driver.findElement(By.id("btn")).click();
} catch (StaleElementReferenceException e) {
  driver.findElement(By.id("btn")).click();
}

C

while(true) {
  driver.findElement(By.id("btn")).click();
  break;
}

D

driver.findElement(By.id("btn")).click();
Thread.sleep(1000);

💡 Hint

Look for a retry loop with exception handling.

Option A retries up to 3 times, catching the exception and waiting before retrying, which is a good practice.

🧠 Conceptual

expert

Why is StaleElementReferenceException common in dynamic web pages?

Choose the best explanation for why StaleElementReferenceException frequently occurs when testing dynamic web pages with Selenium.

A Because dynamic pages block Selenium from clicking elements using JavaScript.

B Because Selenium cannot locate elements on dynamic pages due to missing IDs.

C Because dynamic pages reload or update DOM elements frequently, invalidating previously found WebElement references.

D Because dynamic pages use frames which Selenium does not support.

💡 Hint

Think about how dynamic content affects element references.

Dynamic pages often update or reload parts of the DOM, making previously found WebElement references invalid and causing StaleElementReferenceException.