druid-ts 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6bfc5bbc0d62062451dde2bf3d508d4d3a0c2383
-  data.tar.gz: b67836bb6d42f79df16267ecad88edbfa64a4ad1
+  metadata.gz: d2dec581163c0013714c91706f42d9cb98b57528
+  data.tar.gz: 2021b07a2de1dd8f82f09d8917d393b84f543aa6
 SHA512:
-  metadata.gz: 1886bcb9184acf5c0c1c4fbbc2cd4bd09606fea1e879c9af98a8e703b460b7ae610e2b08ce621cbc5ae14e6ad3cabf970d2904a60eb7963c4b963d0033d707ce
-  data.tar.gz: 6e1dd82de64f6be46c6fb271f7e5742a3a7fe182d06f3194455e7928355eba239053ddbb4e8c35b8fdec917172bb68e41696019fa88f0ea00deb2f0f79784381
+  metadata.gz: 3bb08a0611d113d459b1937df83a8c817b275da04a4af823c9eedbddd9efb2ae2cbe32cfdcd5d9d53dc2f03093a629229220cc22d196091ec5ad143369b2e3bf
+  data.tar.gz: 4a2bf46cda253433dffbeb5b3d49047149ec106e4b0d35223db96a3e64cc68f0e0993f1bc38a3018b1aae6369171f9b0216878bd823d327e37a95a63ba017d5d

data/.travis.yml

@@ -1,7 +1,22 @@
-language: ruby
+sudo: required
+dist: trusty
 rvm:
-  - 2.3.0
+  - 2.2.5
+  - 2.3.1
+cache: bundler
 before_script:
+  - export CHROME_BIN=/usr/bin/google-chrome
   - "export DISPLAY=:99.0"
   - "sh -e /etc/init.d/xvfb start"
-script: rake features:watir_webdriver
+  - sudo apt-get update
+  - sudo apt-get install -y libappindicator1 fonts-liberation
+  - wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
+  - sudo dpkg -i google-chrome*.deb
+  - CHROMEDRIVER_VERSION=$(curl -s http://chromedriver.storage.googleapis.com/LATEST_RELEASE)
+  - curl -L -O "http://chromedriver.storage.googleapis.com/${CHROMEDRIVER_VERSION}/chromedriver_linux64.zip"
+  - unzip chromedriver_linux64.zip
+  - chmod +x chromedriver
+  - sudo mv chromedriver /usr/local/bin
+script: bundle exec rake $RAKE_TASK
+env:
+  - RAKE_TASK=features:watir

data/ChangeLog

@@ -1,6 +1,33 @@
+===Version 1.2.1/ 2017-01-26
+* Enhancements
+  * Added array methods to section collections
+  * Added ability to call style method with no parameters
+  * clean up frame and iframe nesting
+  * Update travis.yml
+  * Added numerous missing element types
+  * Added two new methods that check without throwing exception
+  * Update to use watir 6 instead of watir-webdriver
+  * Added focused? method on element
+  * Added the following methods to Element
+    - outer_html
+    - inner_html
+    - stale?
+  * Added the selected? method to Option
+  * Added the append method to TextArea
+=== 2017-01-25
+* Enhancements
+  * 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 optimization for OrderedList
+  * Added support for the Italic(i) element
+  * Added size and location methods to all elements
+  * Added width, height, and centre methods for elements
 ===Version 1.2.0/ 2017-01-24
 * Enhancements
   * Added new page_section/ page_sections method to accessor
+  * Added row accessors method and support for finding row elements directly
+  * Default element tag to element
 === Version 1.1.9/2017-01-22
 * Enhancements
   * Populate_page_with now supports radio groups

data/Gemfile

@@ -1,11 +1,13 @@
 source "http://rubygems.org"
 
-gem 'simplecov', :require => false, :group => :test
+# adding rake so travis-ci will build properly
 gem 'rake'
-gem 'watir-webdriver', '0.9.3'
-gem 'selenium-webdriver', '2.53.4'
-gem 'rspec'
-gem 'cucumber'
-gem 'rack'
+gem 'rb-fsevent', :require => false if RUBY_PLATFORM =~ /darwin/i
+gem 'listen', '3.0.8'
 gem 'net-http-persistent'
-gem 'page_navigation'
+
+if ENV['WATIR_BRANCH']
+  gem 'watir', :git => 'https://github.com/watir/watir.git', :branch => ENV['WATIR_BRANCH']
+end
+
+gemspec

data/README.md

@@ -2,7 +2,7 @@
 [![Build Status](https://travis-ci.org/timsheng/druid.png)](https://travis-ci.org/timsheng)
 
 
-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 watir-webdriver
+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 watir
 
 ### Defining your page object
 
@@ -58,7 +58,7 @@ login_page.login_with 'cheezy', 'secret'
 ````
 
 ### Creating your druid
-druid supports [watir-webdriver](https://github.com/jarib/watir-webdriver)
+druid supports [watir](https://github.com/watir/watir)
 The page object can be create like this:
 
 ````ruby

data/Rakefile

@@ -27,7 +27,7 @@ task :default => :spec
 
 
 namespace :features do
-  Cucumber::Rake::Task.new(:watir_webdriver, "Run features with Watir webdriver") do |t|
+  Cucumber::Rake::Task.new(:watir, "Run features with Watir webdriver") do |t|
     t.profile = "watir"
   end
 end

data/druid.gemspec

@@ -13,15 +13,16 @@ Gem::Specification.new do |s|
   s.summary = %q{Druid DSL for browser testing}
   s.description = %q{Druid DSL that works with Watir}
   s.license = 'MIT'
-  s.rubyforge_project = "druid"
+  s.files = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(pkg|spec|features|coverage)/})}
   s.files = `git ls-files`.split("\n")
   s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
   s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f)}
   s.require_paths = ["lib"]
-
-  s.add_dependency "watir-webdriver", ">= 0.9.1"
+  s.add_dependency "watir", "~> 6.0"
   s.add_dependency "page_navigation", ">= 0.10"
-  s.add_development_dependency "rspec", ">= 3.4.0"
-  s.add_development_dependency "cucumber", ">= 1.3.20"
+  s.add_dependency "net-http-persistent", "~> 2.9.4"
+
+  s.add_development_dependency "rspec", ">= 3.0.0"
+  s.add_development_dependency "cucumber", ">= 2.0.0"
   s.add_development_dependency "rack", ">= 1.0"
 end

data/features/async.feature

@@ -1,24 +1,16 @@
 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
+  Background:
+    Given I am on the async elements page
 
   Scenario: Click a button when it is visible
-    Given I am on the async elements page
     When I make the button invisible
     Then I should be able to click it when it becomes 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 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,37 +31,33 @@ 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 from the page
+    Then I should know that its volume is 1
 
-  #Scenario: Should know its volume
-    #When I retrieve the audio element
-    #Then I should know that its volume is 1
+  Scenario: Should know if it has ended
+    When I retrieve the audio element from the page
+    Then I should know that it has not ended
 
-  #Scenario: Should know if it has ended
-      #When I retrieve the audio element
-      #Then I should know that it has not ended
+  Scenario: Should know if it is seeking
+    When I retrieve the audio element from the page
+    Then I should know that it is not seeking
 
-  #Scenario: Should know if it is seeking
-    #When I retrieve the audio element
-    #Then I should know that it is not seeking
+  Scenario: Should know if it is in a loop
+    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 in a loop
-    #When I retrieve the audio element
-    #Then I should know that it is not in a loop
-
-  #Scenario: Should know if it is muted
-    #When I retrieve the audio element
-    #Then I should know that it is muted
+  Scenario: Should know if it is muted
+    When I retrieve the audio element from the page
+    Then I should know that it is muted

data/features/element.feature

@@ -15,6 +15,16 @@ Feature: Elements
     When I set the focus to the test text_field
     Then I should know that the text_field has the focus
 
+  Scenario: Checking focus of the element with focus
+    And I set the focus to the test text_field
+    When I retrieve the focus state of the text_field
+    Then I should know that the text_field is focused
+
+  Scenario: Checking focus of the element without focus
+    And I set the focus off the test text_field
+    When I retrieve the focus state of the text_field
+    Then I should know that the text_field is not focused
+
   Scenario: Link element methods
     When I retrieve a link element
     Then I should know it exists
@@ -259,3 +269,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/html/multi_elements.html

@@ -140,5 +140,6 @@
     <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

@@ -42,16 +42,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">
-      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>
@@ -96,7 +86,7 @@
         </tr>
       </thead>
       <tbody>
-        <tr>
+        <tr id="tr_id" class='tr_class'>
           <td>Data1</td>
           <td>Data2</td>
         </tr>
@@ -175,6 +165,7 @@
 
     <a href="success.html" target="_blank">New Window</a>
     <input type="text" id="onfocus_text_field" onfocus="document.getElementById('onfocus_test').innerHTML = 'changed by onfocus event'" />
+    <input type="text" id="unfocus_text_field" />
     <div id="onfocus_test"></div>
 
     <div id="parent_div">
@@ -194,5 +185,8 @@
       <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>
+    <input id="input_button" type="button" value="This button is a input" />
+      <img src="images/non_existent.jpg" id="non_existent" >
   </body>
 </html>

data/features/image.feature

@@ -41,3 +41,7 @@ Feature: Image
     Then I should see that the image exists
     And the image should be "106" pixels wide
     And the image should be "106" pixels tall
+
+  Scenario: Check an image loaded
+    When I get the image element load status
+    Then I should see that the image loaded

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
+
+  Examples:
+  | search_by |
+  | id        |
+  | class     |
+  | name      |
+  | xpath     |
+  | index     |
+  | css       |

data/features/link.feature

@@ -48,3 +48,11 @@ Feature: Links
   Scenario: Getting the href for a link
     When I get the href for the link
     Then I should know it was "success.html"
+
+  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

data/features/multi_elements.feature

@@ -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"

data/features/sample-app/public/audio_video.html

@@ -0,0 +1,19 @@
+<html>
+<head>
+  <title>Audio and Video</title>
+</head>
+  <body>
+    <h2>Audio & Video</h2>
+    <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>
+  </body>
+</html>

data/features/section.feature

@@ -126,3 +126,7 @@ Feature: Sections
     Given I select multiple sections
     When I filter by a specific value of the sections
     Then I will find all sections with that value
+
+  Scenario: Sections roots can be accessed
+    When I have a page section
+    Then methods called on the section are passed to the root if missing

data/features/select_list.feature

@@ -76,7 +76,7 @@ Feature: Select List
 
   Scenario: Selecting an option by its value
     When I select an option using the value "option2"
-    Then the selected option should be "Test 2
+    Then the selected option should be "Test 2"
 
   Scenario: Getting the value from a selected option
     When I select an option using the value "option2"

data/features/step_definations/audio_steps.rb

@@ -1,13 +1,9 @@
-When(/^I retrieve the audio element$/) do
-  @element = @page.audio_id_element
-end
-
 When(/^I search for the audio element by "([^"]*)"$/) do |how|
-  @element = @page.send "audio_#{how}_element"
+  @element = @avpage.send "audio_#{how}_element"
 end
 
 When(/^I search for the audio element by "([^"]*)" and "([^"]*)"$/) do |param1, param2|
-  @element = @page.send "audio_#{param1}_#{param2}_element"
+  @element = @avpage.send "audio_#{param1}_#{param2}_element"
 end
 
 Then(/^I should know the audio is not autoplay$/) do
@@ -22,10 +18,30 @@ Then(/^I should know that the audio is paused$/) do
   expect(@element).to be_paused
 end
 
-Then(/^I should know that the duration is greater than (\d+) seconds$/) do |duration|
-  expect(@element.duration).to be > duration.to_f
-end
-
 Then(/^I should know that its volume is (\d+)$/) do |volume|
   expect(@element.volume).to eql volume.to_i
 end
+
+Given(/^I am on the audio video page$/) do
+  @avpage = visit AudioVideoPage
+end
+
+When(/^I retrieve the audio element from the page$/) do
+  @element = @avpage.audio_id_element
+end
+
+Then(/^I should know that it has not ended$/) do
+  expect(@element).not_to be_ended
+end
+
+Then(/^I should know that it is not seeking$/) do
+  expect(@element).not_to be_seeking
+end
+
+Then(/^I should know that it is not in a loop$/) do
+  expect(@element).not_to be_loop
+end
+
+Then(/^I should know that it is muted$/) do
+  expect(@element).not_to be_muted
+end