Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>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:</p> <pre><code>boolean isElementDisplayed(final WebDriver driver, final WebElement element, final int timeoutInSeconds) { try { ExpectedCondition condition = new ExpectedCondition&lt;Boolean&gt;() { @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; } </code></pre> <p>Use it like this:</p> <pre><code>WebElement we = driver.findElement(By.name("Complete")); if (isElementDisplayed(driver, we, 30)) { we.click(); } </code></pre> <p>This will make the driver wait (30 sec max.) till the element <strong>we</strong> becomes visible and then the driver clicks on it. If it works, then my supposition is right and you could change the method for:</p> <pre><code> void clickOn(final WebDriver driver, final WebElement element, final int timeoutInSeconds) { try { ExpectedCondition condition = new ExpectedCondition&lt;Boolean&gt;() { @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; } </code></pre> <p>and use it instead of <code>we.click()</code>, like:</p> <pre><code>WebElement we = driver.findElement(By.name("Complete")); clickOn(driver, we, 30); </code></pre> <p>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 <em>your</em> 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 <code>util</code> package. </p> <p>Also, the method's signature is 'overweight'. Restructuring your util code, you should be able to write in your tests just this: <code>clickOn(element)</code>.</p> <p>Hope it helps ;)</p> <p><strong>UPDATE</strong> Actually, with these components I had never run into a similar problem:</p> <ol> <li><code>selenium-server-standalone</code> version 2.32.0</li> <li>IEDriverServer_x64_2.30.1.exe</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POIEDriver implementation fails the test
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSergio Pelin
    1. USSergio Pelin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COOops, 'isElementDisplayed(driver, we, 30)' is always false here. But 'System.out.println("The Size of the button is"+driver.findElements(By.name("Complete")).size());' is 1.
      singulars
      1. PO
      1. USKarthikeyan
    2. CO@ Karthikeyan Ok. Resuming what we have here: 1-The code works with other browsers (at least with FF); 2-With IE Selenium is able to find the button, but finds it like not displayed (i.e. not clickable); 3-The issue is not due to IE slowness, as the button stays not displayed even after 30 seconds. Could you do the following: 1-Change the name of the button for something less common (e.g. 'MySeleniumButton'), to just be sure that Selenium finds this and not other element; 2-Open your application in IE, verify that you are able to click the button and then copy and post here button's HTML code.
      singulars
      1. PO
      1. USSergio Pelin
    3. CO1.No its not working with FF too. 2.Yes, it can find it. Hence System.out.println("The Size of the button is"+driver.findElements(By.name("Complete")).size());' is 1. I have no access to the AUT code for now. The same is working with selenium 2.23(With out IEDriver)
      singulars
      1. PO
      1. USKarthikeyan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload