meeane-page-object 0.1.8

data/Gemfile

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

data/Guardfile

@@ -0,0 +1,20 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+
+guard :rspec, cmd: 'rspec --color --format Fuubar' do
+  watch(%r{^spec/.+_spec\.rb$})
+  watch(%r{^lib/(.+)\.rb$})     { |m| "spec/#{m[1]}_spec.rb" }
+  watch(%r{^lib/page-object/platforms/(.+)/.+\.rb$}) do |m|
+    ["spec/page-object/platforms/#{m[1]}/", "spec/page-object/page-object_spec.rb"]
+  end
+  watch('spec/spec_helper.rb')  { "spec" }
+end
+
+guard 'cucumber', notification: true, all_after_pass: false, cli: '--profile focus'  do
+  watch(%r{^features/.+\.feature$})
+  watch(%r{^features/support/.+$})          { "features" }
+  watch(%r{^features/step_definitions/(.+)_steps\.rb$}) { |m| Dir[File.join("**/#{m[1]}.feature")][0] || 'features' }
+  watch(%r{^lib/.+\.rb$})                   { "features" }
+  watch(%r{^cucumber.yml$})                 { "features" }
+end

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2011-2012 Jeff Morgan
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,141 @@
+# meeane-page-object
+
+A simple fork of Jeff Morgan's page-object gem that assists in creating flexible page objects for testing Columbus Direct websites. The goal is to facilitate creating abstraction layers in your tests to decouple the tests from the items they are testing and to provide a simple interface to the elements on a page. It works with both watir-webdriver and selenium-webdriver.
+
+The main additions over the original page-object gem are to extend the accessors to find and interact with the particular style of radio buttons used on the Columbus Direct websites. Also, I have extended the _populate_page_with_ method to work with these page element and wait for any AJAX requests these initiate. They work in the same way as the normal radio buttons but rather than using _select_ we use _choose_.
+
+## Additional Methods Added
+
+You can declare these label elements using:
+
+````ruby
+label(:has_legal_expenses_cover_yes, :for => 'HasLegalExpensesCover_Yes')
+````
+
+This will add a _choose_ method in addition to the usual methods PageObjects creates for labels which allow you to select the element as you would a normal radio button. Call this using:
+
+````ruby
+choose_has_legal_expenses_cover_yes
+````
+
+The _populate_page_with method will pick these elements in exactly the same way as normal radio buttons. This means you can complete each page in the normal way using _populate_page_with_ without having to write any extra code.
+
+````ruby
+populate_page_with = data_for(:my_details, data)
+````
+
+#### Additional Setup
+Many of the labels on the Columbus Direct websites (including Household & Travel) initiate an AJAX call using jQuery so the _choose_ methods generated call _wait_for_ajax_ to check the page has been updated before moving on. For this to work you need to declare the javascript library your website is using. Add the following to your env.rb file for the Columbus Direct websites:
+
+````ruby
+PageObject.javascript_framework = :jquery
+````
+
+## Improvements
+
+Suggested improvements would be to add a facility to interact with the address widgets on the Columbus Direct pages. I'll look to add these at a later date but will use a different approach rather than forking the master as page-object gem already has an extension point that allows us to define our own Element types and register them with the gem. This would seem a better approach.
+
+## Documentation
+
+The project [wiki](https://github.com/cheezy/page-object/wiki/page-object) is the first place to go to learn about how to use page-object.
+
+The rdocs for this project can be found at [rubydoc.info](http://rubydoc.info/gems/page-object/frames).
+
+To see the changes from release to release please look at the [ChangeLog](https://raw.github.com/cheezy/page-object/master/ChangeLog)
+
+To read about the motivation for this gem please read this [blog entry](http://www.cheezyworld.com/2010/11/19/ui-tests-introducing-a-simple-dsl/)
+
+There is a book that describes in detail how to use this gem and others to create a complete view of testing web and other types of applications.  The book is named [Cucumber & Cheese](http://leanpub.com/cucumber_and_cheese)
+
+## Support
+
+If you need help using the page-object gem please ask your questions on [Stack Overflow](http://stackoverflow.com).  Please be sure to use the [page-object-gem](http://stackoverflow.com/questions/tagged/page-object-gem) tag.  If you wish to report an issue or request a new feature use the [github issue tracking page](http://github.com/cheezy/page-object/issues).
+
+## Basic Usage
+
+### Defining your page object
+
+You define a new page object by including the PageObject module:
+
+````ruby
+class LoginPage
+  include PageObject
+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:
+
+````ruby
+class LoginPage
+  include PageObject
+      
+  _(: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 page object that allow us to interact with the items on the page. To login using this page we could simply write the following code:
+
+````ruby
+login_page.username = 'cheezy'
+login_page.password = 'secret'
+login_page.login
+````
+    
+Another approach might be to create higher level methods on our page object that hide the implementation details even further. Our page object might look like this:
+
+````ruby
+class LoginPage
+  include PageObject
+  
+  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:
+
+````ruby
+login_page.login_with 'cheezy', 'secret'
+````
+
+### Creating your page object
+page-object supports both [watir-webdriver](https://github.com/jarib/watir-webdriver) and [selenium-webdriver](http://seleniumhq.org/docs/03_webdriver.html). The one used will be determined by which driver you pass into the constructor of your page object. The page object can be created like this:
+
+````ruby
+browser = Watir::Browser.new :firefox
+my_page_object = MyPageObject.new(browser)
+````
+
+or
+
+````ruby
+browser = Selenium::WebDriver.for :firefox
+my_page_object = MyPageObject.new(browser)
+````
+
+## Known Issues
+
+See [http://github.com/cheezy/page-object/issues](http://github.com/cheezy/page-object/issues)
+
+## 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.
+* Make sure you describe your new feature with a cucumber scenario.
+* Make sure you provide RDoc comments for any new public method you add. Remember, others will be using this gem.
+* Commit, do not mess with Rakefile, version, or ChangeLog.
+  (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)
+* Send me a pull request. Bonus points for topic branches.
+
+## Copyright
+
+Copyright (c) 2011-2012 Jeffrey S. Morgan. See LICENSE for details.

data/Rakefile

@@ -0,0 +1,35 @@
+require 'rubygems'
+require 'bundler'
+require 'rspec/core/rake_task'
+require 'cucumber'
+require 'cucumber/rake/task'
+
+Bundler::GemHelper.install_tasks
+
+RSpec::Core::RakeTask.new(:spec) do |spec|
+  spec.ruby_opts = "-I lib:spec"
+  spec.pattern = 'spec/**/*_spec.rb'
+end
+task :spec
+
+namespace :features do
+  Cucumber::Rake::Task.new(:watir_webdriver, "Run features with Watir") do |t|
+    t.profile = "watir_webdriver"
+  end
+
+  Cucumber::Rake::Task.new(:selenium_webdriver, "Run features with Selenium") do |t|
+    t.profile = "selenium_webdriver"
+  end
+
+  desc 'Run all features'
+  task :all => [:watir_webdriver, :selenium_webdriver]
+end
+
+desc 'Run all specs and cukes'
+task :test => ['spec', 'features:all']
+
+task :lib do
+  $LOAD_PATH.unshift(File.expand_path("lib", File.dirname(__FILE__)))
+end
+
+task :default => :test

data/cucumber.yml

@@ -0,0 +1,10 @@
+<%
+std_opts = "--no-source --color --format pretty" # Cucumber::Formatter::Fuubar"
+%>
+
+default: DRIVER=WATIR <%= std_opts %> --tags ~@selenium_only
+watir_webdriver: DRIVER=WATIR <%= std_opts %> --tags ~@selenium_only
+selenium_webdriver: DRIVER=SELENIUM <%= std_opts %> --tags ~@watir_only
+focus: DRIVER=WATIR <%= std_opts %> --tags ~@selenium_only --tags @focus
+#focus:  DRIVER=SELENIUM <%= std_opts %> --tags ~@watir_only --tags @focus
+

data/features/area.feature

@@ -0,0 +1,35 @@
+Feature: Area
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Retrieve an area element
+    When I retrieve the area element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating areas on the page
+    When I search for the area by "<search_by>"
+    Then I should be able to click the area
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario: Getting the coordinates for the area
+    When I retrieve the area element
+    Then I should see the coordinates are "0,0,82,126"
+
+  Scenario: Getting the shape for the area
+    When I retrieve the area element
+    Then I should see the shape is "rect"
+
+  Scenario: Getting the href from the area
+    When I retrieve the area element
+    Then I should see the href is "sun.html"
+

data/features/async.feature

@@ -0,0 +1,30 @@
+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
+    Given I am on the async elements page
+    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

@@ -0,0 +1,68 @@
+Feature:  Support for the audio element
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: finding an audio element
+    When I retrieve the audio element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating an audio element on the page
+    When I search for the audio element by "<search_by>"
+    Then I should know it is visible
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating audios using multiple parameters
+    When I search for the audio element by "<param1>" and "<param2>"
+    Then I should know it is visible
+
+  Examples:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Should know if it is autoplay
+    When I retrieve the audio element
+    Then I should know the audio is not autoplay
+    
+  Scenario: Should know if the controls are displayed
+    When I retrieve the audio element
+    Then I should know that the controls are displayed
+
+  Scenario: Should know if it is paused
+    When I retrieve the audio element
+    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
+    Then I should know that its volume is 1
+
+  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
+    Then I should know that it is not seeking
+
+  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
+

data/features/button.feature

@@ -0,0 +1,87 @@
+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: Clicking a button (type=submit)
+    When I click the button
+    Then I should be on the success page
+    
+  Scenario: Clicking a button (type=image)
+    When I click the button with type image
+    Then I should be on the success page
+    
+  Scenario: Clicking an image button by src
+    When I click the image button using src
+    Then I should be on the success page
+
+  Scenario: Clicking an image button by alt
+    When I click the image button using alt
+    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
+    And I should know it is visible
+
+  Scenario Outline: Locating buttons on the page
+    When I search for the button by "<search_by>"
+    Then I should be able to click the button
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | value     |
+    | css       |
+
+  Scenario Outline: Locating real buttons on the page
+    When I search for the button by "<search_by>"
+    Then I should be able to click the real button
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | index     |
+    | value     |
+
+  @watir_only
+  Scenario Outline: Locating buttons on Watir only
+    When I search for the button by "<search_by>"
+    Then I should be able to click the button
+
+  Scenarios:
+    | search_by |
+    | text      |
+
+  Scenario Outline: Locating button using multiple parameters
+    When I search for the button by "<param1>" and "<param2>"
+    Then I should be able to click the button
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+    
+  Scenario Outline: Locating real button using multiple parameters
+    When I search for the button by "<param1>" and "<param2>"
+    Then I should be able to click the real button
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a button dynamically
+    When I find a button while the script is executing
+    Then I should see that the button exists
+    And I should be able to click the button element
+  

data/features/canvas.feature

@@ -0,0 +1,37 @@
+Feature:  Support for the canvas element
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Retrieve a canvas element
+    When I retrieve the canvas element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating a canvas on the page
+    When I search for the canvas by "<search_by>"
+    Then I should know it is visible
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario: Determining the width and height of the canvas
+    When I retrieve the canvas element
+    Then I should see that the canvas width is "200"
+    And I should see that the canvas height is "100"
+
+  Scenario Outline: Locating canvases using multiple parameters
+    When I search for the canvas element by "<param1>" and "<param2>"
+    Then I should know it is visible
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+

data/features/check_box.feature

@@ -0,0 +1,55 @@
+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 a check box
+    When I select the First check box
+    Then the First check box should be selected
+    When I unselect the First check box
+    Then the First check box should not be selected
+
+  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     |
+    | index     |
+    | value     |
+    | label     |
+
+  @selenium_only
+  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 |
+    | css       |
+
+  Scenario Outline: Locating check boxes using multiple parameters
+    When I search for the check box by "<param1>" and "<param2>"
+    Then I should be able to check the check box
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Retrieve a CheckBox
+    When I retrieve a check box element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario: Finding a check box dynamically
+    When I select the first check box while the script is executing
+    Then I should see that the checkbox exists
+    And the First check box should be selected

data/features/div.feature

@@ -0,0 +1,45 @@
+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!"
+
+  Scenario: Getting the div element
+    When I retrieve the div element
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario Outline: Locating divs on the page
+    When I search for the div by "<search_by>"
+    Then the text should be "page-object rocks!"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | name      |
+    | text      |
+    | title     |
+    | css       |
+
+  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  |
+
+  Scenario: Finding a div dynamically
+    When I get the text from a div while the script is executing
+    Then I should see that the div exists
+    And the text should be "page-object rocks!"