page-object 1.1.0 → 1.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5e87a5991df66aba958bfa1d69bd5defb8f5dbfc
-  data.tar.gz: 2fccd9a610ae80b2c9762a0f9bdc2827b55ac5e7
+  metadata.gz: e9da44e461744eab4d446edf6dae5566da91c771
+  data.tar.gz: 76d49ecd39139b07d5883a6ce88b29443e65e47c
 SHA512:
-  metadata.gz: f7c67f99e80f010e75da294dcd4894454d0d4a30ffdb9b9396e48c2c440abaa41a853491f1f7de0c184e9486ddeb7580d7efca54477c8e221acc8395f2648e11
-  data.tar.gz: ae0f71731920795dd10e2eb77c7702bc6fc64bca0c4c9ef52a9a3da459399a2ec67d95c79fc371f625b313b29d9b72296e9d8e86335822faf452901ca324b210
+  metadata.gz: ed083f8285b0c1ed5cad169b809e89263f8a4bb4d2ea99e803df0c79d7f8178ef272c9b133b01227d9fd07e92f14318900dd26f457add8e9d120e15dc0847497
+  data.tar.gz: d789f587282a2106d9543ca7e23e735e315c653d3c3b8289a3467e7c2ff0be1eafc4008b99f7eba84929fe54af92271e9d03a99560014d42b6159ca5c00ec410

data/.coveralls.yml

@@ -0,0 +1 @@
+service_name: travis-ci

data/.gitignore

@@ -5,3 +5,4 @@ Gemfile.lock
 pkg
 TAGS
 chromedriver.log
+coverage

data/.travis.yml

@@ -1,10 +1,15 @@
+sudo: false
 language: ruby
+cache: bundler
 rvm:
-  - 1.9.3
   - 2.0.0
-  - 2.1.2
+  - 2.1
+  - 2.2
   - jruby-19mode
 
 before_script:
   - "export DISPLAY=:99.0"
   - "sh -e /etc/init.d/xvfb start"
+
+script:
+  - "bundle exec rake test_with_coveralls"

data/ChangeLog

@@ -1,4 +1,17 @@
-=== Version 1.1.0
+=== Version 1.1.1 / 2016-1-7
+* Enhancements
+  * Added row accessor method and support for finding row elements directly (Thanks Ethan Hedrick)
+  * Added list_items method to UnorderedList to get an array of children.
+  * Speed optimizations for UnorderedList
+  * Added list_items method to OrderedList to get an array of children.
+  * Speed optimizations for OrderedList
+  * Added ability to check if a section is visible?, present?, or exists? (Thanks Donavan Stanley)
+  * Added support for the Italic (i) element (Thanks Sergey Morozov)
+  * Added size and location methods to all elements (Thanks Steve Jackson)
+  * Added width, height, and centre methods for elements (Thanks David Selby)
+  * Added missing right_click method for watir (Thanks David Selby)
+
+=== Version 1.1.0 / 2015-5-2
 * Enhancements
   * Performance enhancements when initializing elements (Thanks Dane Andersen)
   * Enabled button elements to return text when using selenium-webdriver.

data/Gemfile

@@ -2,12 +2,14 @@ source "http://rubygems.org"
 
 # adding rake so travis-ci will build properly
 gem 'rake'
-gem 'fuubar'
-gem 'fuubar-cucumber'
+gem 'fuubar', '>= 2.0.0'
+gem 'fuubar-cucumber', '>= 0.0.22'
 gem 'rb-fsevent', :require => false if RUBY_PLATFORM =~ /darwin/i
 gem 'growl'
 gem 'guard-rspec'
 gem 'guard-cucumber'
 gem 'net-http-persistent'
+gem 'coveralls', require: false
+
 
 gemspec

data/README.md

@@ -1,6 +1,8 @@
 # page-object
 
+[![Gem Version](https://badge.fury.io/rb/page-object.svg)](https://rubygems.org/gems/page-object)
 [![Build Status](https://travis-ci.org/cheezy/page-object.png)](https://travis-ci.org/cheezy/page-object)
+[![Coverage Status](https://coveralls.io/repos/cheezy/page-object/badge.svg?nocache)](https://coveralls.io/r/cheezy/page-object)
 
 
 A simple gem that assists in creating flexible page objects for testing browser based applications. The goal is to facilitate creating abstraction layers in your tests to decouple the tests from the item they are testing and to provide a simple interface to the elements on a page. It works with both watir-webdriver and selenium-webdriver.

data/Rakefile

@@ -3,7 +3,9 @@ require 'bundler'
 require 'rspec/core/rake_task'
 require 'cucumber'
 require 'cucumber/rake/task'
+require 'coveralls/rake/task'
 
+Coveralls::RakeTask.new
 Bundler::GemHelper.install_tasks
 
 RSpec::Core::RakeTask.new(:spec) do |spec|
@@ -32,4 +34,6 @@ task :lib do
   $LOAD_PATH.unshift(File.expand_path("lib", File.dirname(__FILE__)))
 end
 
-task :default => :test
+task :test_with_coveralls => [:test, 'coveralls:push']
+
+task :default => :test_with_coveralls

data/features/async.feature

@@ -1,29 +1,20 @@
 Feature: Handling Asynch calls
 
-  Scenario: Link element methods
-    Given I am on the static elements page
-    When I retrieve a link element
-    Then I should be able to wait until it is present
-    And I should be able to wait until it is visible
-    And I should be able to wait until it is not visible
-    And I should be able to wait until a block returns true
-
-  Scenario: Click a button when it is visible
+  Background:
     Given I am on the async elements page
+  
+  Scenario: Click a button when it is visible
     When I make the button invisible
     Then I should be able to click it when it becomses visible
 
   Scenario: Wait until something is not visible
-    Given I am on the async elements page
     Then I should be able to wait until the button becomes invisible
 
   Scenario: Wait for an element to appear on the page
-    Given I am on the async elements page
     When I add a button a few seconds from now
     Then I should be able to click it when it gets added
 
   Scenario: Wait for an element to disappear from the page
-    Given I am on the async elements page
     When I add a button a few seconds from now
     And I remove a button a few seconds from now
     Then I should not be able to find the button

data/features/audio.feature

@@ -1,10 +1,10 @@
 Feature:  Support for the audio element
 
   Background:
-    Given I am on the static elements page
+    Given I am on the audio video page
 
   Scenario: finding an audio element
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know it exists
     And I should know it is visible
 
@@ -31,38 +31,34 @@ Feature:  Support for the audio element
     | name   | index  |
 
   Scenario: Should know if it is autoplay
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know the audio is not autoplay
     
   Scenario: Should know if the controls are displayed
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that the controls are displayed
 
   Scenario: Should know if it is paused
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that the audio is paused
 
-  Scenario: Should know its duration
-    When I retrieve the audio element
-    Then I should know that the duration is greater than 74 seconds
-
   Scenario: Should know its volume
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that its volume is 1
 
   Scenario: Should know if it has ended
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that it has not ended
 
   Scenario: Should know if it is seeking
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that it is not seeking
 
   Scenario: Should know if it is in a loop
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that it is not in a loop
 
   Scenario: Should know if it is muted
-    When I retrieve the audio element
+    When I retrieve the audio element from the page
     Then I should know that it is muted
 

data/features/element.feature

@@ -320,3 +320,24 @@ Feature: Elements
 
   Scenario: Selecting the text for an element
     Then I should be able to select "Elements" from the paragraph
+
+  Scenario: Element location
+    When I retrieve a link element
+    Then I should be able to know its location
+
+  Scenario: Element size
+    When I retrieve a link element
+    Then I should be able to know its size
+
+  Scenario: Getting the height of an element
+    When I retrieve a link element
+    Then the element height is not 0
+
+  Scenario: Getting the width of an element
+    When I retrieve a link element
+    Then the element width is not 0
+
+  Scenario: Getting the centre of an element
+    When I retrieve a button element
+    Then the element centre should be greater than element y position
+    And the element centre should be greater than element x position

data/features/gxt_table_extension.feature

@@ -8,7 +8,6 @@ Feature: Gxt Table Extension
     And I have registered the GxtTable with PageObject
     And I define a page-object using that widget
     And I am on the Gxt Examples page
-    And I have the Basic Grid opened
 
   Scenario: Retrieve a GxtTable
     When I retrieve a GxtTable widget
@@ -21,4 +20,4 @@ Feature: Gxt Table Extension
 
   Scenario: Confirm a correct row count from a GxtTable
     When I retrieve a GxtTable widget
-    Then the GxtTable should have "13" rows
+    Then the GxtTable should have "3" rows

data/features/html/multi_elements.html

@@ -19,7 +19,7 @@
     <textarea rows="2" cols="20" class="textarea">textarea 1</textarea>
     <textarea rows="2" cols="20" class="textarea">textarea 2</textarea>
     <textarea rows="2" cols="20" class="textarea">textarea 3</textarea>
-    
+
     <select class="selectlist">
       <option value="selectlist 1">Option 1</option>
     </select>
@@ -33,7 +33,7 @@
     <a href="blah.html" class="link">link 1</a>
     <a href="blah.html" class="link">link 2</a>
     <a href="blah.html" class="link">link 3</a>
-    
+
     <input class="checkbox" type="checkbox" value="checkbox 1"/>
     <input class="checkbox" type="checkbox" value="checkbox 2"/>
     <input class="checkbox" type="checkbox" value="checkbox 3"/>
@@ -41,15 +41,15 @@
     <input type="radio" class="radio" value="radio 1">
     <input type="radio" class="radio" value="radio 2">
     <input type="radio" class="radio" value="radio 3">
-    
+
     <div class="div">Div 1</div>
     <div class="div">Div 2</div>
     <div class="div">Div 3</div>
-    
+
     <span class="span">Span 1</span>
     <span class="span">Span 2</span>
     <span class="span">Span 3</span>
-    
+
     <label class="label">Label 1</label>
     <label class="label">Label 2</label>
     <label class="label">Label 3</label>
@@ -77,7 +77,7 @@
         <td>Data 9</td>
       </tr>
     </table>
-    
+
     <img src="images/circle.png" class="image", alt="image 1">
     <img src="images/circle.png" class="image", alt="image 2">
     <img src="images/circle.png" class="image", alt="image 3">
@@ -115,11 +115,11 @@
     <h2 class="h2">H2 One</h2>
     <h2 class="h2">H2 Two</h2>
     <h2 class="h2">H2 Three</h2>
-    
+
     <h3 class="h3">H3 One</h3>
     <h3 class="h3">H3 Two</h3>
     <h3 class="h3">H3 Three</h3>
-    
+
     <h4 class="h4">H4 One</h4>
     <h4 class="h4">H4 Two</h4>
     <h4 class="h4">H4 Three</h4>
@@ -127,7 +127,7 @@
     <h5 class="h5">H5 One</h5>
     <h5 class="h5">H5 Two</h5>
     <h5 class="h5">H5 Three</h5>
-   
+
     <h6 class="h6">H6 One</h6>
     <h6 class="h6">H6 Two</h6>
     <h6 class="h6">H6 Three</h6>
@@ -135,10 +135,11 @@
     <p class="p">Paragraph One</p>
     <p class="p">Paragraph Two</p>
     <p class="p">Paragraph Three</p>
-    
+
     <input type="file" class="file_field_class" title="File Field 1" />
     <input type="file" class="file_field_class" title="File Field 2" />
     <input type="file" class="file_field_class" title="File Field 3" />
     In bold <b>One B</b> and <b>Two B</b> for example text
+    In italic <i>One I</i> and <i>Two I</i> for example text
   </body>
 </html>

data/features/html/static_elements.html

@@ -43,20 +43,6 @@
       ctx.fillRect(0,0,150,75);
     </script>
 
-    <audio controls id="audio" name="audio" class="audio">
-      <source src="04-Death_Becomes_Fur.mp4"
-              type='audio/mp4'/>
-      <source src="04-Death_Becomes_Fur.oga"
-              type='audio/ogg; codecs=vorbis'/>
-      <p>Your user agent does not support the HTML5 Audio element.</p>
-    </audio>
-
-    <video width="320" height="240" controls="controls" id="video" name="video" class="video">
-      <source src="movie.mp4" type="video/mp4" />
-      <source src="movie.ogg" type="video/ogg" />
-      Your browser does not support the video tag.
-    </video>
-
     <svg width="100" height="100" id="the_svg">
       <circle cx="50" cy="50" r="40" fill="red" stroke="blue" stroke-width="5" />
     </svg>
@@ -100,7 +86,7 @@
         </tr>
       </thead>
       <tbody>
-        <tr>
+        <tr id='tr_id' class='tr_class'>
           <td>Data1</td>
           <td>Data2</td>
         </tr>
@@ -194,11 +180,12 @@
     <summary id='summary_id'>The summary</summary>
     The details
   </details>
-  
+
   <figure id='figure_id'>
     <img src="images/img_pulpit.jpg" alt="The Pulpit Rock" width="304" height="228">
   </figure>
   This text have <b id="b_id" class="b_class" name="b_name">some text in bold</b>
+  This text have <i id="i_id" class="i_class" name="i_name">some text in italic</i>
   <button id="button_button">This button is a button</button>
   <input id="input_button" type="button" value="This button is a input" />
   </body>

data/features/html/widgets.html

@@ -0,0 +1,20 @@
+<html>
+<body>
+<div class="x-grid3">
+    <table>
+        <tr>
+            <th>Column1</th>
+            <th>Column2</th>
+        </tr>
+        <tr>
+            <td>1</td>
+            <td>2</td>
+        </tr>
+        <tr>
+            <td>3</td>
+            <td>4</td>
+        </tr>
+    </table>
+</div>
+</body>
+</html>

data/features/italic.feature

@@ -0,0 +1,21 @@
+Feature: Italic
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text of headings
+    When I get the italic text for the "i" element
+    Then I should see "some text in italic" in italic
+
+  Scenario Outline: Locating i on the Page
+    When I search italic text for the i by "<search_by>"
+    Then I should see "some text in italic" in italic
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |

data/features/multi_elements.feature

@@ -9,7 +9,7 @@ Feature: Multi Elements
     And the value of button 1 should be "Button 1"
     And the value of button 2 should be "Button 2"
     And the value of button 3 should be "Button 3"
-    
+
   Scenario: Selecting buttons using no identifier
     When I select all buttons using no identifier
     Then I should have 3 buttons
@@ -20,7 +20,7 @@ Feature: Multi Elements
     And the value of text field 1 should be "text 1"
     And the value of text field 2 should be "text 2"
     And the value of text field 3 should be "text 3"
-    
+
   Scenario: Selecting text fields using no identifier
     When I select all text fields using no identifier
     Then I should have 3 text fields
@@ -79,7 +79,7 @@ Feature: Multi Elements
   Scenario: Selecting checkboxes using no identifier
     When I select checboxes using no identifier
     Then I should have 3 checkboxes
-    
+
   Scenario: Selecting radio buttons using an identifier
     When I select the radio button with class "radio"
     Then I should have 3 radio buttons
@@ -141,7 +141,7 @@ Feature: Multi Elements
     And the alt for image 1 should be "image 1"
     And the alt for image 2 should be "image 2"
     And the alt for image 3 should be "image 3"
-    
+
   Scenario: Selecting images using no identifier
     When I select the images using no identifier
     Then I should have 3 images
@@ -152,7 +152,7 @@ Feature: Multi Elements
     And the action for form 1 should be "form1"
     And the action for form 2 should be "form2"
     And the action for form 3 should be "form3"
-    
+
   Scenario: Selecting forms using no identifier
     When I select the forms using no identifier
     Then I should have 3 forms
@@ -163,7 +163,7 @@ Feature: Multi Elements
     And the text for list item 1 should be "Item One"
     And the text for list item 2 should be "Item Two"
     And the text for list item 3 should be "Item Three"
-    
+
   Scenario: Selecting list items using no identifier
     When I select the list items using no identifier
     Then I should have 8 list items
@@ -174,18 +174,18 @@ Feature: Multi Elements
     And the text for the first item in unordered list 1 should be "Item One"
     And the text for the first item in unordered list 2 should be "Item Four"
     And the text for the first item in unordered list 3 should be "Item Five"
-    
+
   Scenario: Selecting unordered lists using no identifier
     When I select the unordered list using no parameter
     Then I should have 3 unordered lists
-    
+
   Scenario: Selecting ordered lists using an identifier
     When I select the ordered lists with class "ol"
     Then I should have 3 ordered lists
     And the text for the first item in ordered list 1 should be "Number One"
     And the text for the first item in ordered list 2 should be "Number Two"
     And the text for the first item in ordered list 3 should be "Number Three"
-    
+
   Scenario: Selecting ordered lists using no identifier
     When I select the ordered lists using no identifier
     Then I should have 3 ordered lists
@@ -196,7 +196,7 @@ Feature: Multi Elements
     And the text for h1 1 should be "H1 One"
     And the text for h1 2 should be "H1 Two"
     And the text for h1 3 should be "H1 Three"
-    
+
   Scenario: Selecting h1s using no identifier
     When I select h1s using no identifier
     Then I should have 3 h1s
@@ -207,7 +207,7 @@ Feature: Multi Elements
     And the text for h2 1 should be "H2 One"
     And the text for h2 2 should be "H2 Two"
     And the text for h2 3 should be "H2 Three"
-    
+
   Scenario: Selecting h2s using no identifier
     When I select h2s using no identifier
     Then I should have 3 h2s
@@ -218,7 +218,7 @@ Feature: Multi Elements
     And the text for h3 1 should be "H3 One"
     And the text for h3 2 should be "H3 Two"
     And the text for h3 3 should be "H3 Three"
-    
+
   Scenario: Selecting h3s using no identifier
     When I select h3s using no identifier
     Then I should have 3 h3s
@@ -229,18 +229,18 @@ Feature: Multi Elements
     And the text for H4 1 should be "H4 One"
     And the text for H4 2 should be "H4 Two"
     And the text for H4 3 should be "H4 Three"
-    
+
   Scenario: Selecting h4s using no identifier
     When I select h4s using no identifier
     Then I should have 3 h4s
-    
+
   Scenario: Selecting h5s using an identifier
     When I select the h5s with the class "h5"
     Then I should have 3 h5s
     And the text for H5 1 should be "H5 One"
     And the text for H5 2 should be "H5 Two"
     And the text for H5 3 should be "H5 Three"
-    
+
   Scenario: Selecting h5s using no identifier
     When I select h5s using no identifier
     Then I should have 3 h5s
@@ -251,7 +251,7 @@ Feature: Multi Elements
     And the text for H6 1 should be "H6 One"
     And the text for H6 2 should be "H6 Two"
     And the text for H6 3 should be "H6 Three"
-    
+
   Scenario: Selecting h6s using no identifier
     When I select h6s using no identifier
     Then I should have 3 h6s
@@ -295,7 +295,7 @@ Feature: Multi Elements
     And the text of div 1 should be "Div 1"
     And the text of div 2 should be "Div 2"
     And the text of div 3 should be "Div 3"
-    
+
   Scenario: Selecting all divs using a block instead of an identifier
     When I select the divs using a block
     Then I should have 3 divs
@@ -421,35 +421,35 @@ Feature: Multi Elements
     And the text for h1 1 should be "H1 One"
     And the text for h1 2 should be "H1 Two"
     And the text for h1 3 should be "H1 Three"
-    
+
   Scenario: Selecting h2s based on a class declaration
     When I select the h2s using the generated method
     Then I should have 3 h2s
     And the text for h2 1 should be "H2 One"
     And the text for h2 2 should be "H2 Two"
     And the text for h2 3 should be "H2 Three"
-    
+
   Scenario: Selecting h3s based on a class declaration
     When I select the h3s using the generated method
     Then I should have 3 h3s
     And the text for h3 1 should be "H3 One"
     And the text for h3 2 should be "H3 Two"
     And the text for h3 3 should be "H3 Three"
-    
+
   Scenario: Selecting h4s based on a class declaration
     When I select the h4s using the generated method
     Then I should have 3 h4s
     And the text for H4 1 should be "H4 One"
     And the text for H4 2 should be "H4 Two"
     And the text for H4 3 should be "H4 Three"
-    
+
   Scenario: Selecting h5s based on a class declaration
     When I select the h5s using the generated method
     Then I should have 3 h5s
     And the text for H5 1 should be "H5 One"
     And the text for H5 2 should be "H5 Two"
     And the text for H5 3 should be "H5 Three"
-    
+
   Scenario: Selecting h6s based on a class declaration
     When I select the h6s using the generated method
     Then I should have 3 h6s
@@ -490,3 +490,9 @@ Feature: Multi Elements
     Then I should have 2 bs
     And the text for b 1 should be "One B"
     And the text for b 2 should be "Two B"
+
+  Scenario: Selecting is using an identifier
+    When I select the is
+    Then I should have 2 is
+    And the text for i 1 should be "One I"
+    And the text for i 2 should be "Two I"