druid-ts 1.1.2 → 1.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 725b5b3fc9daa4e3d593a8abfe593067bf1c101e
-  data.tar.gz: 20ab43b61b5e4d52a89a38663ea4d83df2e229d0
+  metadata.gz: c83e03d267731768c34e5a6e686dc2105e9a94ad
+  data.tar.gz: b4f5d3fa5dac92cb3f107cd78d4cc7026ce4d7e4
 SHA512:
-  metadata.gz: b5aac9457e68624faa57d386b82a72bebc915707325cdfadbb8fd46fc31be6ee63e473fd28a85b7e65d707e81014ca79e19406380fceb0ff721c613d451a883b
-  data.tar.gz: 0d378bb88a484676e14f46dbaf0cc99c48cf5d1dc932fddc355ab035d4aa21a19635cd65d4994f4b98da7171612c1665b087f22cdc56a0da8fb32ae1c55e0a79
+  metadata.gz: 00a48ae184bbc2008cc8acd0c886690fd6b52b4854f7c1e2317ed02e6104e4e27fec356d75bdcbf9b714a38260973e36431a220ade40afc46058a40deef783bd
+  data.tar.gz: 9bedf55e94feacfa9b04eb2dcc6532b30fc36cc16071d9892c4720849c0f6337d145cd13605b9253554f0dea7bf15b64784b3c224f43240920793e427058a555

data/ChangeLog

@@ -1,3 +1,24 @@
+=== 2016-12-26
+* Enhancement
+  * Changed page_url to accept a symbol that will cause it to call a corresponding method
+=== 2016-12-23
+* Enhancement
+  * Added #execute_script method to Druid
+  * Added support for finding the following using :css
+      Button
+      Link
+  * Added method to fetch generic element
+  * Support alias method 'on' for 'on_page', 'visit' for 'visit_page' on PageFactory
+  * Changed Elements.element_class_for so parameters can be strings or symbols
+  * Added element_with_focus method to return the element that has focus
+  * Added support for the label element
+=== 2016-12-20
+* Fixes
+  WARNING: This change breaks existing code
+  * Changed the generated getter for select_list to return the text instead of the value
+* Enhancements
+  * Added #expected_title method to Druid
+  * Added #expected_element method to Druid
 === Version 1.1.2 /2016-12-19
 * Enhancements
   * Added #include? and #selected? to SelectList

data/README.md

@@ -2,66 +2,76 @@
 [![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-webdriver
 
 ### Defining your page object
 
 You define a new druid by including the Druid module:
 
-    class LoginPage
-      include Druid
-    end
+````ruby
+class LoginPage
+  include Druid
+end
+````
 
 When you include this module numerous methods are added to your class that allow you to easily define your page.  For the login page you might add the following:
 
-    class LoginPage
-      include Druid
+````ruby
+class LoginPage
+  include Druid
 
-      text_field(:username, :id => 'username')
-      text_field(:password, :id => 'password')
-      button(:login, :id => 'login')
-    end
+  text_field(:username, :id => 'username')
+  text_field(:password, :id => 'password')
+  button(:login, :id => 'login')
+end
+````
 
 Calling the _text_field_ and _button_ methods adds several methods to our druid that allow us to interact with the items on the page.  To login using this page we could simply write the following code:
 
-    login_page.username = 'cheezy'
-    login_page.password = 'secret'
-    login_page.login
+````ruby
+login_page.username = 'cheezy'
+login_page.password = 'secret'
+login_page.login
+````
 
 Another approach might be to create higher level methods on our druid that hide the implementation details even further.  Our druid might look like this:
 
-    class LoginPage
-      include Druid
-
-      text_field(:username, :id => 'username')
-      text_field(:password, :id => 'password')
-      button(:login, :id => 'login')
-
-      def login_with(username, password) 
-        self.username = username
-        self.password = password
-        login
-      end
-    end
-
+````ruby
+class LoginPage
+  include Druid
+
+  text_field(:username, :id => 'username')
+  text_field(:password, :id => 'password')
+  button(:login, :id => 'login')
+
+  def login_with(username, password)
+    self.username = username
+    self.password = password
+    login
+  end
+end
+````
 and your usage of the page would become:
 
-    login_page.login_with 'cheezy', 'secret'
+````ruby
+login_page.login_with 'cheezy', 'secret'
+````
 
 ### Creating your druid
 druid supports [watir-webdriver](https://github.com/jarib/watir-webdriver)
 The page object can be create like this:
 
-    browser = Watir::Browser.new :firefox
-    my_druid = MyDruid.new(browser)
-
+````ruby
+browser = Watir::Browser.new :firefox
+my_druid = MyDruid.new(browser)
+````
 
 
 
 ## Contribute
 
 * Fork the project.
-* Test drive your feature addition or bug fix.  Adding specs is important and I will not accept a pull request that does not have tests
+* Test drive your feature addition or bug fix. Adding specs is important and I will not accept a pull request that does not have tests
 * Make sure you describe your new feature with a cucumber feature.
 * Commit, do not mess with rakefile, version, or history.
   (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)

data/features/button.feature

@@ -35,6 +35,7 @@ Feature: Button
     | index     |
     | text      |
     | value     |
+    | css       |
 
   Scenario Outline: Locating real buttons on the page
     When I locate the button by "<locate_by>"

data/features/element.feature

@@ -11,6 +11,10 @@ Feature: Elements
     Then it should know it is not enabled
     And it should know that it is disabled
 
+  Scenario: Setting focus and finding the element with focus
+    When I set the focus to the test text_field
+    Then I should know that the text_field has the focus
+
   Scenario: Link element methods
     When I retrieve a link element
     Then I should know it exists

data/features/generic_elements.feature

@@ -0,0 +1,24 @@
+Feature: Generic Elements
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text from the article element
+    When I get the text from the article
+    Then the text should be "HTML 5 Article"
+
+  Scenario: Getting the text from the header element
+    When I get the text from the header
+    Then the text should be "HTML 5 Header"
+
+  Scenario: Getting the text from the footer element
+    When I get the text from the footer
+    Then the text should be "HTML 5 Footer"
+
+  Scenario: Getting the text from the summary element
+    When I get the text from the summary
+    Then the text should be "The summary"
+
+  Scenario: Getting the text from the details element
+    When I get the text from the details
+    Then the text should be "The summary The details"

data/features/html/multi_elements.html

@@ -49,6 +49,10 @@
     <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>
+
     <table class="table" border='1'>
       <tr>
         <td class="td">Data 1</td>

data/features/html/nested_elements.html

@@ -24,6 +24,9 @@
     <span>
       My alert
     </span>
+    <label>
+      page-object is the best!
+    </label>
     <table>
       <tr>
         <td>Data1</td>

data/features/html/static_elements.html

@@ -12,7 +12,7 @@
 
     <textarea rows="2" cols="20" id="text_area_id" class="text_area_class" name="text_area_name"></textarea>
 
-    <select name="sel_list_name" id="sel_list_id", class="sel_list_class">
+    <select name="sel_list_name" id="sel_list_id" class="sel_list_class">
       <option value="option1">Test 1</option>
       <option value="option2">Test 2</option>
     </select>
@@ -33,6 +33,10 @@
       My alert
     </span>
 
+    <label id="label_id" name="label_name" class="label_class">
+      page-object is the best!
+    </label>
+
     <table id='table_id' name='table_name' class='table_class' border='1'>
       <tr>
         <td>Data1</td><td>Data2</td>
@@ -91,5 +95,14 @@
       <a href="success.html" id="child">Success</a>
     </div>
 
+    <article id="article_id">HTML 5 Article</article>
+    <header id="header_id">HTML 5 Header</header>
+    <footer id="footer_id">HTML 5 Footer</footer>
+
+    <details id="details_id">
+      <summary id="summary_id">The summary</summary>
+      The details
+    </details>
+
   </body>
 </html>

data/features/javascript.feature

@@ -11,3 +11,9 @@ Feature: Handling javascript events
     Given I am on the Prototype example page
     When I ask to compute "2+2"
     Then I should be able to wait for the answer "4"
+
+  Scenario: Executing javascript in the browser
+    Given I am on the static elements page
+    Given I execute the javascript "return 2 + 2;"
+    Then I should get the answer "4"
+    

data/features/label.feature

@@ -0,0 +1,44 @@
+Feature: Handling labels with page object
+
+  In order to interact with labels,
+  Testers will need to access the element
+  and the ability to interrogate
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text from a label
+    When I get the text from the label
+    Then the text should be "page-object is the best!"
+
+  Scenario: Getting the label element
+    When I retrieve the label element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating labels on the page
+    When I search for the label by "<search_by>"
+    Then the text should be "page-object is the best!"
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | name      |
+    | text      |
+
+  Scenario Outline: Locating lables using multiple parameters
+    When I search for the label by "<param1>" and "<param2>"
+    Then the text should be "page-object is the best!"
+
+  Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  Scenario: Finding a label dynamically
+    When I get the text from a label while the script is executing
+    Then I should see that the label exists
+    And the text should be "page-object is the best!"

data/features/link.feature

@@ -24,6 +24,7 @@ Feature: Links
     | xpath     |
     | link      |
     | link_text |
+    | css       |
 
   Scenario: Retrieve a Link
     When I retrieve a link element

data/features/multi_elements.feature

@@ -171,3 +171,10 @@ Feature: Multi Elements
      And the text for paragraph 1 should be "Paragraph One"
      And the text for paragraph 2 should be "Paragraph Two"
      And the text for paragraph 3 should be "Paragraph Three"
+
+   Scenario: Selecting labels
+     When I select the labels with class "label"
+     Then I should have 3 labels
+     And the text for label 1 should be "Label 1"
+     And the text for label 2 should be "Label 2"
+     And the text for label 3 should be "Label 3"

data/features/nested_elements.feature

@@ -104,6 +104,10 @@ Feature: Nested Elements
     When I search for a file field located in a div
     Then I should be able to retrieve the nested file field
 
+  Scenario: Finding a label within a div
+    When I search for a label located in a div
+    Then I should see the nested labels text should be "page-object is the best!"
+
   Scenario: Unordered list nested in another Unordered list
     When I get the outter unordered list
     Then I should see "One" for list item 1

data/features/page_level_actions.feature

@@ -30,6 +30,18 @@ Feature: Page level actions
     Given I can goto baidu.com using visit_page with block
     Then the page should have the title "百度" using on_page with block
 
+  Scenario: Validating the page title
+    Given I am on the static elements page
+    Then the page should have the expected title
+
+  Scenario: Validating the expected element
+    Given I am on the static elements page
+    Then the page should have the expected element
+
+  Scenario: Validating that an expected element does not exist
+    Given I am on the static elements page
+    Then the page should not have the expected element
+
   Scenario: Waiting for something
     Given I am on the static elements page
     Then I should be able to wait for a block to return true

data/features/select_list.feature

@@ -7,12 +7,13 @@ Feature: Select List
 
   Scenario: Selecting an element on the select list
     When I select "Test 2" from the select list
-    Then the current item should be "option2"
+    Then the current item should be "Test 2"
 
   Scenario Outline: Locating select lists on the Page
     When I locate the select list by "<locate_by>"
     Then I should be able to select "Test 2"
-    And the value for the selected item should be "option2"
+    And the value for the selected item should be "Test 2"
+    And the value for the option should be "option2"
 
     Examples:
     | locate_by |
@@ -40,7 +41,8 @@ Feature: Select List
   Scenario Outline: Locating a select list using multiple parameters
     When I search for the select list bys "<param1>" and "<param2>"
     Then I should be able to select "Test 2"
-    And the value for the selected item should be "option2"
+    And the value for the selected item should be "Test 2"
+    And the value for the option should be "option2"
 
     Examples:
     | param1  | param2  |

data/features/step_definations/element_steps.rb

@@ -89,3 +89,17 @@ end
 Then(/^it should know that it is disabled$/) do
   expect(@element).to be_disabled
 end
+
+When(/^I set the focus to the test text_field$/) do
+  @page.text_field_element(:id => 'onfocus_text_field').focus
+end
+
+Then(/^I should know that the text_field has the focus$/) do
+  element = @page.element_with_focus
+  expect(element).not_to be nil
+  expect(element.class).to be Druid::Elements::TextField
+end
+
+When(/^I retrieve the label element$/) do
+  @element = @page.label_id_element
+end

data/features/step_definations/generic_element_steps.rb

@@ -0,0 +1,19 @@
+When(/^I get the text from the article$/) do
+  @text = @page.article_id
+end
+
+When(/^I get the text from the header$/) do
+  @text = @page.header_id
+end
+
+When(/^I get the text from the footer$/) do
+  @text = @page.footer_id
+end
+
+When(/^I get the text from the summary$/) do
+  @text = @page.summary_id
+end
+
+When(/^I get the text from the details$/) do
+  @text = @page.details_id
+end

data/features/step_definations/javasript_steps.rb

@@ -27,3 +27,11 @@ Then(/^I should be able to wait for the answer "([^"]*)"$/) do |answer|
   @page.wait_for_ajax
   expect(@page.results).to eql answer
 end
+
+Given(/^I execute the javascript "([^"]*)"$/) do |script|
+  @answer = @page.execute_script script
+end
+
+Then(/^I should get the answer "([^"]*)"$/) do |answer|
+  expect(@answer).to eql answer.to_i
+end

data/features/step_definations/label_steps.rb

@@ -0,0 +1,19 @@
+When(/^I get the text from the label$/) do
+  @text = @page.label_id
+end
+
+When(/^I search for the label by "([^"]*)"$/) do |how|
+  @text = @page.send "label_#{how}".to_sym
+end
+
+When(/^I search for the label by "([^"]*)" and "([^"]*)"$/) do |param1, param2|
+  @text = @page.send "label_#{param1}_#{param2}".to_sym
+end
+
+When(/^I get the text from a label while the script is executing$/) do
+  @text = @page.label_element(:id => 'label_id').text
+end
+
+Then(/^I should see that the label exists$/) do
+  expect(@page.label_id?).to be true
+end