Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Short answer:</strong> Adding class names to source code is the correct direction and should be considered as good practice, however, after that, using <code>:class</code> locator isn't good enough in most of the case, try use <code>:xpath</code> or <code>:css</code>. Therefore, you, as a developer, go ahead and add the class names, but you need make sure your QA people know how to use Watir, don't simply use <code>:id</code> or <code>:class</code> for all locators.</p> <p><strong>Long answer:</strong> If the site is simple enough, adding IDs would be easiest and the best one. However, nowadays, many JavaScript frameworks like <a href="http://docs.sencha.com/extjs/4.2.1/extjs-build/examples/build/KitchenSink/ext-theme-neptune/" rel="nofollow">ExtJS</a>, create dynamic IDs, so in that case adding class names to source code would be better.</p> <p>After adding the class names, for example in your case, using <code>:class</code> locator is a bad choice, which might be even worse than <code>:id</code>, as IDs are supposed to be unique. For complex pages, <code>:class</code> locator is pretty much useless, which will find unwanted elements.</p> <p>Here, your error message means you might have more than one elements with class <code>save-btn</code>, the first one isn't visible to be interacted with. </p> <p>Selenium WebDriver or Watir WebDriver, both support XPath and CssSelector, so you should use <code>:xpath</code> or <code>:css</code> when necessary, instead of <code>:id</code>, <code>:class</code> etc.</p> <p>For example, something like:</p> <pre><code>links(:item, :css=&gt; '.save-btn:not([style*='display:none'])')[0] </code></pre> <p><strong>Jarmo Pertman</strong> suggests using ID/Class is in favor of XPath/Css Selectors, which is not completely correct. ID/Class are just subsets of XPath/Css Selectors, if it's easy enough, use ID/Class, however unnecessary chaining is not a good practice, in the example he gave,</p> <pre><code>browser.div(id: "container").span(class: "save-btn") </code></pre> <p>is equivalent to CSS selector <code>div#container span.save-btn</code>, therefore, there are no fragile or maintenance issues for CSS selector, because they are identical.</p> <p>XPath/CSS selectors are powerful tools, everyone should be learning, but only use them if really needed. Bad XPath/Css Selector are fragile, try find the good ones. (But bear in mind that XPath is slow, should be considered as last option)</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing class names in Watir
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USYi Zeng
    1. USYi Zeng
    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. 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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COUsing class attributes is pretty normal and recommending xpath or css locators is bad practice. See my answer.
      singulars
      1. PO
      1. USJarmo Pertman
    2. CO@JarmoPertman: In real world, nope, if you take a look at how StackOverflow questions, most people consider XPath or CssSelector. Imagine `browser.div(id: "container").div(class: 'something1').div(class: 'something2').div(class: 'something3').span(class: "save-btn")` and `#container .something1 .something2 .something3 .save-btn`, which would you choose? Bad XPath/Css Selector are fragile, because they are the bad ones, try find the good ones.Maybe you have a point, but your example is far from convincing. By ID/Class are just subset of XPath/CSS Selector,so use them only if they can handle it.
      singulars
      1. PO
      1. USYi Zeng
    3. COWell, i myself am a developer (also coincidentally a core developer for watir-classic and a little for watir-webdriver) and have never seen anything like you've just shown in the real world. It would make semantically good sense to add some id attribute in the chain because usually pages have meaningful sections. For example, there's a user edit form where the button "save-btn" is. This is how it would look: `browser.div(id: "user-form").span(class: "save-btn")`. I have never used more than one context element. Also, being a developer, the quality of SO answers have been decreasing...
      singulars
      1. PO
      1. USJarmo Pertman
 

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