page-object 0.2 → 0.2.1

data/.gitignore

@@ -1,4 +1,5 @@
 Gemfile.lock
 .bundle
+*.swp
 .idea/
 pkg

data/.rvmrc

@@ -1 +1 @@
-rvm 1.9.2-p290@page-object
+rvm 1.9.2-p180@page-object --create

data/ChangeLog

@@ -1,3 +1,14 @@
+=== Version 0.2.1 / 2011-07-29
+* Enhancements
+  * Added ability to locate div by the contained text
+  * Added #attach_to_window so a page object and operate on another window
+  * Added #switch_to_frame to allow one to switch to a frame
+  * Added #send_keys to PageObject::Elements::Element
+  * Added #refresh to page object
+  * Work toward making drivers pluggable
+  * Updated to use selenium-webdriver 2.2.0
+  * Updated to use watir-webdriver 0.2.8
+
 === Version 0.2 / 2011-07-24
 * Enhancements
   * Async handling
@@ -10,12 +21,7 @@
   * Handling popups
     * Added #alert to page object to override default alert popup behavior
     * Added #confirm to page object to override default confirm popup behavior
-    * Added #prompt to page object to override default prompt popup behaviorit "should override prompt popup behavior" do
-      watir_browser.should_receive(:prompt)
-      watir_page_object.prompt("blah") do
-      end
-    end
-    
+    * Added #prompt to page object to override default prompt popup behavior
   * Updated to use selenium-webdriver 2.1.0
 
 === Version 0.1.1 / 2011-07-16

data/README.md

@@ -51,7 +51,7 @@ Another approach might be to create higher level methods on our page object that
       text_field(:password, :id => 'password')
       button(:login, :id => 'login')
   
-      def login_with(username, password) do
+      def login_with(username, password)
         self.username = username
         self.password = password
         login

data/Rakefile

@@ -8,7 +8,7 @@ Bundler::GemHelper.install_tasks
 
 RSpec::Core::RakeTask.new(:spec) do |spec|
   spec.ruby_opts = "-I lib:spec"
-  spec.pattern   = 'spec/**/*_spec.rb'
+  spec.pattern = 'spec/**/*_spec.rb'
 end
 task :spec
 
@@ -16,11 +16,11 @@ namespace :features do
   Cucumber::Rake::Task.new(:watir, "Run features with Watir") do |t|
     t.profile = "watir"
   end
-  
+
   Cucumber::Rake::Task.new(:selenium, "Run features with Selenium") do |t|
     t.profile = "selenium"
   end
-  
+
   desc 'Run all features'
   task :all => [:watir, :selenium]
 end
@@ -33,19 +33,3 @@ task :lib do
 end
 
 task :default => :spec
-
-
-begin
-  require 'yard'
-  Rake::Task[:lib].invoke
-  require "yard/handlers/page-object"
-  YARD::Rake::YardocTask.new do |task|
-    task.options = %w[--debug] # this is pretty slow, so nice with some output
-  end
-rescue LoadError
-  task :yard do
-    abort "YARD is not available. In order to run yardoc, you must: sudo gem install yard"
-  end
-end
-
-

data/features/async.feature

@@ -1,11 +1,11 @@
 Feature: Handling Asynch calls
 
-Background:
-  Given I am on the static elements page
+  Background:
+    Given I am on the static elements page
 
-Scenario: Link element methods
-  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: Link element methods
+    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/button.feature

@@ -2,14 +2,14 @@ Feature: Button
   In order to interact with buttons
   Testers will need access and interrogation ability
 
-  
+
   Background:
     Given I am on the static elements page
-  
+
   Scenario: Getting the text from a div
     When I click the button
     Then I should be on the success page
-    
+
   Scenario: Retrieve a button element
     When I retrieve a button element
     Then I should know it exists
@@ -24,7 +24,7 @@ Feature: Button
     | id        |
     | class     |
     | name      |
-    | xpath     |  
+    | xpath     |
     | index     |
 
   @watir_only
@@ -41,6 +41,6 @@ Feature: Button
     Then I should be able to click the button
 
   Scenarios:
-    | param1  | param2  |
-    | class   | index   |
-    | name    | index   |
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |

data/features/check_box.feature

@@ -2,10 +2,10 @@ Feature: Check Box
   In order to interact with check boxes
   Testers will need access and interrogation ability
 
-  
+
   Background:
     Given I am on the static elements page
-  
+
   Scenario: Selecting an element on the select list
     When I select the First check box
     Then the First check box should be selected
@@ -15,13 +15,13 @@ Feature: Check Box
   Scenario Outline: Locating check boxes on the page
     When I search for the check box by "<search_by>"
     Then I should be able to check the check box
-    
+
   Scenarios:
     | search_by |
     | id        |
     | class     |
     | name      |
-    | xpath     |  
+    | xpath     |
     | index     |
 
   Scenario Outline: Locating check boxes using multiple parameters
@@ -29,11 +29,11 @@ Feature: Check Box
     Then I should be able to check the check box
 
   Scenarios:
-    | param1  | param2  |
-    | class   | index   |
-    | name    | index   |
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
 
-   
   Scenario: Retrieve a CheckBox
     When I retrieve a check box element
     Then I should know it exists

data/features/div.feature

@@ -2,10 +2,10 @@ Feature: Div
   In order to interact with divs
   Testers will need access and interrogation ability
 
-  
+
   Background:
     Given I am on the static elements page
-  
+
   Scenario: Getting the text from a div
     When I get the text from the div
     Then the text should be "page-object rocks!"
@@ -23,15 +23,16 @@ Feature: Div
     | search_by |
     | id        |
     | class     |
-    | xpath     |  
+    | xpath     |
     | index     |
     | name      |
+    | text      |
 
   Scenario Outline: Locating divs using multiple parameters
     When I search for the div by "<param1>" and "<param2>"
     Then the text should be "page-object rocks!"
 
   Scenarios:
-    | param1  | param2  |
-    | class   | index   |
-    | name    | index   |
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |

data/features/element_attributes.feature

@@ -12,12 +12,12 @@ Feature: Attributes on Elements
     And I should know its' tag name is "a"
     And I should know the attribute "readonly" is false
     And I should be able to click it
-    
+
   @watir_only
   Scenario: Link element methods for watir
     When I retrieve a link element
     Then I should know its' value is ""
-    
+
 
   Scenario: Button element methods
     When I retrieve a button element
@@ -28,7 +28,7 @@ Feature: Attributes on Elements
     And I should know its' tag name is "input"
     And I should know the attribute "readonly" is false
     And I should be able to click it
-    
+
   @watir_only
   Scenario: Button element methods for watir
     When I retrieve a button element
@@ -44,7 +44,7 @@ Feature: Attributes on Elements
     And I should know its' tag name is "input"
     And I should know the attribute "readonly" is false
     And I should be able to click it
-  
+
   Scenario: Div element methods
     When I retrieve the div element
     Then I should know it exists
@@ -59,7 +59,7 @@ Feature: Attributes on Elements
   Scenario: Div element methods for watir
     When I retrieve the div element
     Then I should know its' value is ""
-  
+
   @selenium_only
   Scenario: Div element methods for selenium
     When I retrieve the div element
@@ -83,7 +83,7 @@ Feature: Attributes on Elements
     And I should know its' text includes "Test 1"
     And I should know its' value is "option1"
     And I should know it is equal to itself
-    And I should know its' tag name is "select"      
+    And I should know its' tag name is "select"
     And I should know the attribute "readonly" is false
     And I should be able to click it
 
@@ -92,7 +92,7 @@ Feature: Attributes on Elements
     Then I should know it is visible
     And I should know its' text includes "Data1"
     And I should know it is equal to itself
-    And I should know its' tag name is "table"      
+    And I should know its' tag name is "table"
     And I should know the attribute "readonly" is false
     And I should be able to click it
 
@@ -101,19 +101,19 @@ Feature: Attributes on Elements
     When I retrieve a table element
     Then I should know it exists
     And I should know its' value is ""
-  
+
   @selenium_only
   Scenario: Table element methods in selenium
     When I retrieve a table element
     Then I should know its' value is nil
-  
+
   Scenario: Table Cell element methods
     When I retrieve table cell
     Then I should know it exists
     And I should know it is visible
     And I should know its' text includes "Data4"
     And I should know it is equal to itself
-    And I should know its' tag name is "td"      
+    And I should know its' tag name is "td"
     And I should know the attribute "readonly" is false
     And I should be able to click it
 
@@ -134,7 +134,7 @@ Feature: Attributes on Elements
     And I should know its' text includes ""
     And I should know its' value is ""
     And I should know it is equal to itself
-    And I should know its' tag name is "input"      
+    And I should know its' tag name is "input"
     And I should know the attribute "readonly" is false
     And I should be able to click it
 
@@ -145,7 +145,7 @@ Feature: Attributes on Elements
     And I should know its' text includes ""
     And I should know its' value is ""
     And I should know it is equal to itself
-    And I should know its' tag name is "textarea"      
+    And I should know its' tag name is "textarea"
     And I should know the attribute "readonly" is false
     And I should be able to click it
 
@@ -176,7 +176,7 @@ Feature: Attributes on Elements
     And I should know its' text includes ""
     And I should know its' value is "12345"
     And I should know it is equal to itself
-    And I should know its' tag name is "input"      
+    And I should know its' tag name is "input"
     And I should know the attribute "readonly" is false
 
   Scenario: Form element methods
@@ -185,7 +185,7 @@ Feature: Attributes on Elements
     And I should know it is visible
     And I should know its' text includes ""
     And I should know it is equal to itself
-    And I should know its' tag name is "form"      
+    And I should know its' tag name is "form"
     And I should know the attribute "readonly" is false
 
   @watir_only

data/features/form.feature

@@ -2,7 +2,7 @@ Feature: Form
 
   Background:
     Given I am on the static elements page
-  
+
   Scenario: Submitting a form
     When I locate the form by "id"
     Then I should be able to submit the form
@@ -15,7 +15,7 @@ Feature: Form
     | search_by |
     | id        |
     | class     |
-    | xpath     |  
+    | xpath     |
     | index     |
 
   Scenario Outline: Locating table using multiple parameters
@@ -23,7 +23,7 @@ Feature: Form
     Then I should be able to submit the form
 
   Scenarios:
-    | param1  | param2  |
-    | class   | index   |
-    | name    | index   |
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
 

data/features/frames.feature

@@ -0,0 +1,12 @@
+Feature: Handling frames
+
+  Background:
+    Given I am on the frame elements page
+
+  Scenario: Switching to a frame by id
+    When I switch to a frame using id "frame_2"
+    Then I should see "Frame 2" in the frame
+
+  Scenario: Switching to a frame by index
+    When I switch to a frame using index "1"
+    Then I should see "Frame 2" in the frame

data/features/hidden_field.feature

@@ -2,7 +2,7 @@ Feature: Hidden Fields
 
   Background:
     Given I am on the static elements page
-  
+
   Scenario: Setting and getting a value from a hidden field
     When I retrieve the hidden field element
     Then I should see the hidden field contains "12345"
@@ -16,7 +16,7 @@ Feature: Hidden Fields
     | id        |
     | class     |
     | name      |
-    | xpath     |  
+    | xpath     |
     | css       |
     | tag_name  |
     | index     |
@@ -27,6 +27,6 @@ Feature: Hidden Fields
     Then hidden field element should contains "12345"
 
   Scenarios:
-    | param1  | param2  |
-    | class   | index   |
-    | name    | index   |
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |

data/features/html/frame_1.html

@@ -0,0 +1,18 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+    <head>
+        <title>Frame 1</title>
+        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+    </head>
+    <body onload="document.senderForm.senderElement.focus()">
+        <h1>Frame 1</h1>
+        <p>Nam accumsan. Donec nisi pede, interdum eget, ultrices ac, vulputate vitae, nunc. Nulla lorem. Duis cursus pharetra dolor. Nulla accumsan hendrerit leo. Vivamus commodo. Nullam dignissim adipiscing est. Aliquam vitae orci in risus lobortis luctus. Ut luctus fermentum ligula. Nullam ipsum. Suspendisse sit amet nisi.</p>
+        <form action="" method="post" name="senderForm">
+            <fieldset>
+                <input type="text" name="senderElement" id="senderElement" value="send_this_value" />
+                <input type="button" id="send" onclick="parent.frame2.document.recieverForm.recieverElement.value = document.senderForm.senderElement.value" value="Send!" />
+            </fieldset>
+        </form>
+        <div id="set_by_js" />
+    </body>
+</html>

data/features/html/frame_2.html

@@ -0,0 +1,16 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+    <head>
+        <title>Frame 2</title>
+        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+    </head>
+    <body>
+        <h1>Frame 2</h1>
+        <p>Vestibulum dignissim mauris id tellus. Nulla volutpat bibendum ante. Nam malesuada, lacus vel ultrices luctus, lorem purus tristique magna, quis pharetra leo ipsum nec neque. Cras ornare tincidunt sem. In hac habitasse platea dictumst. Suspendisse commodo turpis at est. Sed quis tortor. Aenean non massa. Phasellus scelerisque nulla vel lectus. Quisque lorem. Praesent volutpat dignissim risus. Fusce vulputate ligula eu ipsum.</p>
+        <form action="" method="post" name="recieverForm">
+            <fieldset>
+                <input type="text" name="recieverElement" value="old_value" />
+            </fieldset>
+        </form>
+    </body>
+</html>