Handling StaleElementReferenceException in Selenium Java - Test Execution Trace

Test Overview

This test checks how to handle the StaleElementReferenceException in Selenium Java. It verifies that the test retries finding an element if it becomes stale after a page update.

Test Code - JUnit 5 with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.StaleElementReferenceException;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertEquals;

public class StaleElementHandlingTest {
    WebDriver driver;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        driver.get("https://example.com/dynamic");
    }

    @AfterEach
    public void tearDown() {
        driver.quit();
    }

    @Test
    public void testHandleStaleElement() {
        WebElement dynamicText = driver.findElement(By.id("dynamic-text"));
        WebElement button = driver.findElement(By.id("refresh-btn"));
        button.click();

        int attempts = 0;
        while (attempts < 3) {
            try {
                String text = dynamicText.getText();
                assertEquals("Updated Text", text);
                break;
            } catch (StaleElementReferenceException e) {
                dynamicText = driver.findElement(By.id("dynamic-text"));
                attempts++;
            }
        }
    }
}

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts and Chrome browser opens	Browser opened at https://example.com/dynamic	—	PASS
2	Find element with id 'refresh-btn'	Button element located on page	—	PASS
3	Click the 'refresh-btn' button to update page content	Page content starts updating dynamically	—	PASS
4	Try to find element with id 'dynamic-text' and get its text	Element may be stale due to page update	Check if element text equals 'Updated Text'	FAIL
5	Catch StaleElementReferenceException and retry finding element	Element reference refreshed after retry	Check if element text equals 'Updated Text'	PASS
6	Assertion passes confirming text is 'Updated Text'	Test confirms updated page content	assertEquals("Updated Text", text)	PASS
7	Test ends and browser closes	Browser closed	—	PASS

Failure Scenario

Failing Condition: The element 'dynamic-text' remains stale after all retry attempts

Execution Trace Quiz - 3 Questions

What causes the StaleElementReferenceException in this test?

A The element locator is incorrect

B The element was removed or refreshed after the page update

C The browser failed to open the page

D The assertion text is wrong

Key Result

Always re-locate web elements after page updates to avoid stale element exceptions. Use retry logic or explicit waits to handle dynamic page changes gracefully.

Practice

1. What causes a StaleElementReferenceException in Selenium WebDriver?

easy

A. The locator syntax is incorrect.

B. The web element is no longer attached to the current page DOM.

C. The browser window is not maximized.

D. The WebDriver instance is not initialized.

Solution

1. Step 1: Understand the exception cause

   StaleElementReferenceException occurs when the element you found earlier is no longer present in the page's current DOM structure.

2. Step 2: Identify the correct cause

   Incorrect locator or browser state issues do not cause this exception. It specifically relates to the element's presence in the DOM.

3. Final Answer:

   The web element is no longer attached to the current page DOM. -> Option B

4. Quick Check:

   Stale element = Detached from DOM [OK]

Hint: Stale means element lost from page DOM, re-find it [OK]

Common Mistakes:

• Confusing stale element with wrong locator syntax
• Thinking browser size causes stale element
• Assuming WebDriver initialization causes this

2. Which of the following is the correct way to catch a StaleElementReferenceException in Java Selenium?

easy

A. try { element.click(); } catch (ElementNotVisibleException e) { /* handle */ }

B. try { element.click(); } catch (NoSuchElementException e) { /* handle */ }

C. try { element.click(); } catch (TimeoutException e) { /* handle */ }

D. try { element.click(); } catch (StaleElementReferenceException e) { /* handle */ }

Solution

1. Step 1: Identify the exception to catch

   The exception to handle stale elements is StaleElementReferenceException.

2. Step 2: Match the catch block

   Only try { element.click(); } catch (StaleElementReferenceException e) { /* handle */ } catches StaleElementReferenceException correctly.

3. Final Answer:

   try { element.click(); } catch (StaleElementReferenceException e) { /* handle */ } -> Option D

4. Quick Check:

   Catch stale element exception = try { element.click(); } catch (StaleElementReferenceException e) { /* handle */ } [OK]

Hint: Catch StaleElementReferenceException to handle stale elements [OK]

Common Mistakes:

• Catching wrong exceptions like NoSuchElementException
• Not catching any exception causing test failure
• Using deprecated exceptions

3. Consider the following code snippet:

WebElement button = driver.findElement(By.id("submit"));
button.click();
// Page reloads here
button.click();

What will happen when the second button.click() runs?

medium

A. The click will succeed without any exception.

B. The test will hang indefinitely.

C. A StaleElementReferenceException will be thrown.

D. A NoSuchElementException will be thrown.

Solution

1. Step 1: Analyze element usage after page reload

   The element button was found before the page reload. After reload, the old reference is invalid.

2. Step 2: Understand exception on stale element use

   Using the old button reference after reload causes StaleElementReferenceException.

3. Final Answer:

   A StaleElementReferenceException will be thrown. -> Option C

4. Quick Check:

   Using old element after reload = StaleElementReferenceException [OK]

Hint: After page reload, re-find elements to avoid stale exception [OK]

Common Mistakes:

• Assuming element reference stays valid after reload
• Confusing stale element with no such element
• Thinking test hangs instead of throwing exception

4. You have this code that sometimes throws StaleElementReferenceException. How can you fix it?

WebElement link = driver.findElement(By.linkText("Home"));
link.click();
link.click();

medium

A. Wrap the second click in a try-catch and re-find the element inside catch.

B. Increase the implicit wait time to 30 seconds.

C. Use Thread.sleep(5000) before the second click.

D. Change locator to XPath instead of linkText.

Solution

1. Step 1: Identify cause of stale element

   The first click likely changes the page, making the old link reference stale.

2. Step 2: Fix by catching exception and re-finding element

   Wrapping the second click in try-catch and re-finding the element inside catch handles the stale reference properly.

3. Final Answer:

   Wrap the second click in a try-catch and re-find the element inside catch. -> Option A

4. Quick Check:

   Catch stale exception and re-find element [OK]

Hint: Catch stale exception and re-find element before retry [OK]

Common Mistakes:

• Relying only on waits without handling stale exception
• Using Thread.sleep which is unreliable
• Changing locator without reason

5. You want to click a button that reloads the page, but avoid StaleElementReferenceException. Which approach is best?

public void clickButtonWithRetry() {
  int attempts = 0;
  while (attempts < 3) {
    try {
      WebElement btn = driver.findElement(By.id("reloadBtn"));
      btn.click();
      break;
    } catch (StaleElementReferenceException e) {
      attempts++;
    }
  }
}

hard

A. This retry loop handles stale element by re-finding and retrying clicks.

B. This code will cause infinite loop if stale exception occurs.

C. The code should use explicit wait instead of retry loop.

D. The button should be found once outside the loop to improve performance.

Solution

1. Step 1: Understand retry logic for stale element

   The loop tries to find and click the button up to 3 times, catching stale exceptions and retrying.

2. Step 2: Confirm this approach avoids stale element errors

   Re-finding the element inside the loop ensures a fresh reference each attempt, preventing stale exceptions.

3. Final Answer:

   This retry loop handles stale element by re-finding and retrying clicks. -> Option A

4. Quick Check:

   Retry with re-find fixes stale element [OK]

Hint: Retry clicks with re-find inside loop to fix stale element [OK]

Common Mistakes:

• Thinking loop causes infinite retries without break
• Using waits alone without retry logic
• Finding element once outside loop causing stale reference