Before you go — grab our most downloaded resource.
QA cheat sheets used by 30,000+ testers.
🔒 No spam, ever. Join 30,000+ QA engineers. Unsubscribe anytime.
No thanks, I'll skip the free cheat sheetsHit an exception mid-run, or got asked one in an interview? This free Selenium exception lookup covers the exceptions every SDET meets — each with its root cause, when it shows up, the Java fix you can paste, and the crisp answer that lands in an interview panel.
A handful of Selenium exceptions account for most flaky-test pain and most interview questions: StaleElementReferenceException, NoSuchElementException, TimeoutException, ElementClickInterceptedException and ElementNotInteractableException. For each, know the one-line cause and the fix by heart — it signals real hands-on experience faster than almost anything else.
Search by the exception name or by what you were doing (“click”, “stale”, “timeout”). Each entry gives the root cause, the scenarios that trigger it, and a ready Java fix — usually an explicit wait on the right condition, a re-locate of the element, or a scroll-into-view. Copy the snippet, adapt the locator, and move on.
Yes, it runs in your browser with nothing to install.
The element reference you held became invalid because the DOM re-rendered. Re-locate the element right before you interact with it, or wait for the new element to be present.
Almost always a timing issue — replace sleeps with an explicit wait on the exact condition (presence, visibility or clickability) for that element.
Each exception includes a concise interview-ready answer, because knowing the cause and fix of common exceptions is one of the most common practical Selenium interview checks.