jkotests / watirways Goto Github PK

Add a section for elements/situations where the basic locator rules may not apply. The big one is the handling of frames/iframes, which need to be explicitly mentioned.

Watir-Webdriver was switched to explicitly differentiate frames from iframes. The element type methods will need to be updated accordingly.

Leanpub books support a "parts" section, which basically gives another level to break the book down.

The initial thought is that instead of having chapters like "Locating an Element - Basics" and "Locating an Element - Relationships", we can switch to:

• Locating an Element (a part)
  • Basics (a chapter)
  • Relationships (a chapter)

The html element cannot be found with browser.html, which returns the html of the page. A different locator needs to be used such as browser.element(:tag_name => 'html').

I had originally written a post about this - http://jkotests.wordpress.com/2012/11/23/get-attribute-values-of-the-html-element/.

Add a section for handling nested tables - ie using trs vs rows and tds vs cells.

We should include the performance notes for when not using a nested table - ie blog post http://jkotests.wordpress.com/2012/09/25/nested-tables-trs-vs-rows-and-tds-vs-cells/.

Add an example for counting the number of matching elements - ie using .size or .length.

Add a section on iterating over a collection of elements.

Start with the basics of using each.

Then we can go into other examples such as:

• Using other enumerable methods such as map
• Using the short-cut for blocks - such as .map(&:text)
• Clicking each link. We would want to discuss how to iterate through a serious of links that navigate to another page and therefore need to be re-located each time. We might also want to consider scenarios where the links cause content to change asynchronously. I recall a situation where we had to click the links from the bottom up instead of top down.
• Collecting several items into say an array that we export to CSV.

The Element Existence section has the text:

Element#exists? checks if the element is in the DOM (or HTML). Element#visible? checks if the element can be seen by the user, but throws an exception if the element is not in the DOM. Element#present? is the same as Element#visible? except that it returns false, instead of an exception, when the element is not in the DOM.
Conclusion

While the three methods are definitely different, I think, at least from my experience, that you should typically be using Element#present?.

There is an extra "Conclusion" text that must have been copied from the original blog post.