IEDriver implementation fails the test - selenium-webdriver

Question

I am using Webdriver(without IEDriver implementation) 2.23 API on windows7 machine with JDK7 and JRE7. The test scripts are working fine as expected but when i introduced IEDriver the script fails in a page with cannot click on element error message as that corresponding element is not visible. i have double checked with my application for the locator. The same can be clicked with out IEDriver implementation. I have tried by simulating all the click types including context click by Action class. No use. All click types returns the same result. Any help ?

Answer 1

Finally, i was manage to click the above said Element with the help of following code.
WebElement we = driver.findElement(By.name("Complete"));
JavascriptExecutor executor = (JavascriptExecutor)driver;
executor.executeScript("arguments[0].click();", we); // common for all we
The real source is here. This may helpful for someone.

Answer 2

As you say that the element is actually visible and the error's log says it is not, I think that the problem might be due to Internet Explorer's slowness. You could use this method for a quick test:
boolean isElementDisplayed(final WebDriver driver, final WebElement element, final int timeoutInSeconds) {
try {
ExpectedCondition condition = new ExpectedCondition<Boolean>() {
#Override
public Boolean apply(final WebDriver webDriver) {
return element.isDisplayed();
}
};
Wait w = new WebDriverWait(driver, timeoutInSeconds);
w.until(condition);
} catch (Exception ex) {
//if you get here, it's because the element is not displayed after timeoutInSeconds
return false;
}
return true;
}
Use it like this:
WebElement we = driver.findElement(By.name("Complete"));
if (isElementDisplayed(driver, we, 30)) {
we.click();
}
This will make the driver wait (30 sec max.) till the element we becomes visible and then the driver clicks on it.
If it works, then my supposition is right and you could change the method for:
void clickOn(final WebDriver driver, final WebElement element, final int timeoutInSeconds) {
try {
ExpectedCondition condition = new ExpectedCondition<Boolean>() {
#Override
public Boolean apply(final WebDriver webDriver) {
element.click();
return true;
}
};
Wait w = new WebDriverWait(driver, timeoutInSeconds);
w.until(condition);
} catch (Exception ex) {
//probably some kind of exception thrown here
}
return;
}
and use it instead of we.click(), like:
WebElement we = driver.findElement(By.name("Complete"));
clickOn(driver, we, 30);
The code above is an approximation to let you check your issue in a quick and clear way and, if you end up using it, you should adapt it to your structure of code. This kind of utility code should never appear in your tests. Your test code should be clean and the same for all the environments (browsers, version, SOs, etc.). Keep the workarounds separately, e.g. some kind of util package.
Also, the method's signature is 'overweight'. Restructuring your util code, you should be able to write in your tests just this: clickOn(element).
Hope it helps ;)
UPDATE Actually, with these components I had never run into a similar problem:
selenium-server-standalone version 2.32.0
IEDriverServer_x64_2.30.1.exe