Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>heh, come across with similar issue. The matter is when you got a lot of AJAX on the page, the best way (imho) to handle it and the wait i like most is <code>fluentWait()</code></p> <pre><code> public WebElement fluentWait(final By locator){ Wait&lt;WebDriver&gt; wait = new FluentWait&lt;WebDriver&gt;(driver) .withTimeout(30, TimeUnit.SECONDS) .pollingEvery(1, TimeUnit.SECONDS) .ignoring(NoSuchElementException.class); WebElement foo = wait.until( new Function&lt;WebDriver, WebElement&gt;() { public WebElement apply(WebDriver driver) { return driver.findElement(locator); } } ); return foo; }; </code></pre> <p>So you actually need to find the locator of web element (xpath, or css selector) and to pass it to fluent wait. And fluent wait, in turn, returns you found web element. From the documentation: <em>An implementation of the Wait interface that may have its timeout and polling interval configured on the fly. Each FluentWait instance defines the maximum amount of time to wait for a condition, as well as the frequency with which to check the condition. Furthermore, the user may configure the wait to ignore specific types of exceptions whilst waiting, such as NoSuchElementExceptions when searching for an element on the page.</em> <strong>usage:</strong></p> <pre><code>String xPathElement =".....blablabla..."; WebElement neededElement =fluentWait(By.xpath(xPathElement)); neededElement.click(); //neededElement.getText().trim(); </code></pre> <p>you can get more info on it <a href="http://selenium.googlecode.com/svn/trunk/docs/api/java/org/openqa/selenium/support/ui/FluentWait.html" rel="nofollow">here</a></p> <p>The issue causing such kind of problem can be (from my experience ) of two types: 1) first one</p> <p>you interact with an element causing page rendering or some else 'slow' operations. Selenium tests keep on going but the page actually not rendered >> <code>staleElement</code>.</p> <p>2) second one. you interact with one element. then you interact with another causing a lot of AJAX (not complete page reload, and first element refresh). and instantly you return back to the previous one (wanna e.g. getText or click)>><code>staleElement</code>.</p> <p>So I always use fluent wait. It is comfortable from the point you can set up arbitratry exceptions ignoring. Hope this works for you.</p>
    singulars
    1. This table or related slice is empty.
    1. POSelenium - Inconsistent StaleElementReference errors
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USArran
    1. USeugene.polschikov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSelenium - Inconsistent StaleElementReference errors
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for your first reason for random StaleElementExceptions when rendering AJAX. I was pretty sure that that was my issue, but it's good to see someone confirming it.
      singulars
      1. PO
      1. USbsg
 

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