Selenium WebDriver exceptions, explained one by one

An implicit wait makes every find_element call poll for up to a set time before raising NoSuchElementException. An explicit wait (WebDriverWait with an expected condition) waits for one specific condition, such as visibility or clickability. Explicit waits are more precise. Selenium's documentation warns against mixing both, because the combination can produce unpredictable wait times.

Usually not. Since Selenium 4.6, Selenium Manager is bundled with the bindings and automatically detects your browser version, then downloads the matching driver, and can even download the browser. Manual drivers are still useful in offline or locked-down environments, but a stale manual driver on PATH is the most common cause of version mismatch errors.

The exception class comes from Selenium and maps to a W3C WebDriver error code, but the message text comes from the browser driver. ChromeDriver, GeckoDriver and SafariDriver word the same condition differently, and ChromeDriver has changed wording between versions. Search for the exception class together with the key phrase from the message.

Only sometimes. driver.execute_script('arguments[0].click()', el) bypasses the checks that produce ElementClickInterceptedException and ElementNotInteractableException, so it can click elements a real user could not reach. That may hide a real bug, such as a modal blocking the page. Use it after confirming the obstruction is cosmetic, and prefer waiting or dismissing overlays.

It shows the browser and version that the session actually used, for example chrome=131.0.6778.86. Compare it with your ChromeDriver version and with what you expect to be installed. It is the quickest way to spot that a different browser binary, or an older one, was launched than the one you intended.

Take a screenshot and save driver.page_source in an exception handler, log driver.current_url, pass descriptive messages to WebDriverWait.until(), and set an explicit window size so headless runs match local ones. Enabling driver logging also records start-up problems such as crashes, missing binaries and version mismatches.

Stable, purpose-built attributes such as id, name or a data-testid attribute, located with By.ID, By.NAME or a short CSS selector. Long XPath expressions and generated class names break whenever markup changes. Use XPath when you need to match visible text or navigate to a parent or sibling, which CSS cannot do.

Headless servers differ in window size, available fonts, shared memory, user permissions and sometimes browser version. Small default windows trigger mobile layouts that hide elements, and containers can crash Chrome on start. Set --window-size, use --headless=new, add --disable-dev-shm-usage in Docker, and log browser versions from both environments.