When Selenium is unable to interact with an element, such as the case when an element is missing or disabled, this change will output exactly how Selenium is attempting to locate the element, such as the XPath or id of the element. This greatly speeds up troubleshooting issues, as the exception message clearly states what element is broken/missing for common problems like an ElementNotFoundException.

Signed-off-by: Luke Inman-Semerau <[email protected]>

Author: HPRichard

java/client/src/org/openqa/selenium/remote/RemoteWebDriver.java

@@ -598,6 +598,9 @@ protected Response execute(String driverCommand, Map<String, ?> parameters) {
     try {
       errorHandler.throwIfResponseFailed(response, System.currentTimeMillis() - start);
     } catch (WebDriverException ex) {
+      if (parameters != null && parameters.containsKey("using") && parameters.containsKey("value")) {
+        ex.addInfo("*** Element info", String.format("{Using=%s, value=%s}", parameters.get("using"), parameters.get("value")));
+      }
       ex.addInfo(WebDriverException.DRIVER_INFO, this.getClass().getName());
       if (getSessionId() != null) {
         ex.addInfo(WebDriverException.SESSION_ID, getSessionId().toString());