Handling StaleElementReferenceException in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to catch the StaleElementReferenceException.

Selenium Java

try {
    WebElement element = driver.findElement(By.id("submit"));
    element.click();
} catch ([1] e) {
    System.out.println("Element is stale.");
}

Drag options to blanks, or click blank then click option'

AStaleElementReferenceException

BNoSuchElementException

CTimeoutException

DElementNotVisibleException

Attempts:

3 left

💡 Hint

Common Mistakes

Using NoSuchElementException instead of StaleElementReferenceException.

Catching TimeoutException which is unrelated here.

The StaleElementReferenceException is the exception thrown when the element is no longer attached to the DOM.

2fill in blank

medium

Complete the code to retry finding the element after catching the exception.

Selenium Java

WebElement element;
try {
    element = driver.findElement(By.id("username"));
    element.sendKeys("user1");
} catch (StaleElementReferenceException e) {
    element = driver.[1](By.id("username"));
    element.sendKeys("user1");
}

Drag options to blanks, or click blank then click option'

AfindElements

BfindElement

CgetElement

DlocateElement

Attempts:

3 left

💡 Hint

Common Mistakes

Using findElements which returns a list, not a single element.

Using non-existent methods like getElement or locateElement.

After catching the stale element exception, you need to find the element again using findElement.

3fill in blank

hard

Fix the error in the retry logic to handle stale element properly.

Selenium Java

WebElement button = driver.findElement(By.id("login"));
try {
    button.click();
} catch (StaleElementReferenceException e) {
    button = driver.findElement(By.id("login")); // [1]
    button.click();
}

Drag options to blanks, or click blank then click option'

Are-find element before clicking

Bignore exception

Cretry without re-finding element

Duse Thread.sleep before clicking

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to click the old stale element again without re-finding.

Ignoring the exception without handling.

You must find the element again inside the catch block before clicking to avoid stale reference.

4fill in blank

hard

Fill both blanks to implement a retry loop that handles StaleElementReferenceException.

Selenium Java

int attempts = 0;
while (attempts < 3) {
    try {
        WebElement link = driver.[1](By.linkText("Home"));
        link.click();
        break;
    } catch ([2] e) {
        attempts++;
    }
}

Drag options to blanks, or click blank then click option'

AfindElement

BStaleElementReferenceException

CfindElements

DNoSuchElementException

Attempts:

3 left

💡 Hint

Common Mistakes

Using findElements which returns a list instead of a single element.

Catching NoSuchElementException instead of StaleElementReferenceException.

Use findElement to get the element and catch StaleElementReferenceException to retry.

5fill in blank

hard

Fill all three blanks to create a method that safely clicks an element with retries on stale reference.

Selenium Java

public void safeClick(By locator) {
    int retries = 0;
    while (retries < 2) {
        try {
            WebElement element = driver.[1](locator);
            element.[2]();
            break;
        } catch ([3] e) {
            retries++;
        }
    }
}

Drag options to blanks, or click blank then click option'

AfindElement

Bclick

CStaleElementReferenceException

DsendKeys

Attempts:

3 left

💡 Hint

Common Mistakes

Using sendKeys instead of click for clicking.

Not catching the correct exception type.

The method finds the element, clicks it, and catches StaleElementReferenceException to retry.

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