page-object 1.2.0 → 1.2.1

data/features/area.feature

@@ -1,35 +0,0 @@
-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

@@ -1,21 +0,0 @@
-Feature: Handling Asynch calls
-
-  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
-    Then I should be able to wait until the button becomes invisible
-
-  Scenario: Wait for an element to appear on the 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
-    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,64 +0,0 @@
-Feature:  Support for the audio element
-
-  Background:
-    Given I am on the audio video page
-
-  Scenario: finding an audio element
-    When I retrieve the audio element from the page
-    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 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 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 from the page
-    Then I should know that the audio is paused
-
-  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 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 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 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 muted
-    When I retrieve the audio element from the page
-    Then I should know that it is muted
-

data/features/bold.feature

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

data/features/button.feature

@@ -1,98 +0,0 @@
-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      |
-
-    @dane
-  Scenario Outline: Getting the text from a button
-    When I get the text for a button that is a "<tag>"
-    Then the text should be "This button is a <tag>"
-
-  Scenarios:
-    | tag    |
-    | button |
-    | input  |
-
-  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

@@ -1,37 +0,0 @@
-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

@@ -1,55 +0,0 @@
-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

@@ -1,45 +0,0 @@
-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!"

data/features/element.feature

@@ -1,343 +0,0 @@
-Feature: Elements
-
-  Background:
-    Given I am on the static elements page
-
-  Scenario: Clear an element
-    When I type "abcDEF" into the text field
-    Then the text field should contain "abcDEF"
-    When I clear the text field
-    Then the text field should contain ""
-
-  Scenario: Elements enabled?
-    When I check an enabled button
-    Then it should know it is enabled
-    And it should know that is it not disabled
-    When I check a disabled button
-    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
-    And I should know it is visible
-    And I should know the text is "Google Search"
-    And I should know the html is "<a href="success.html" id="link_id" name="link_name" class="link_class" title="link_title">Google Search</a>"
-    And I should know it is equal to itself
-    And I should know the tag name is "a"
-    And I should know the attribute "readonly" is false
-    And I should know the attribute "href" includes "success.html"
-    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 the value is ""
-
-
-  Scenario: Button element methods
-    When I retrieve a button element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the value is "Click Me"
-    And I should know it is equal to itself
-    And I should know the 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
-    Then I should know the text is "Click Me"
-
-  Scenario: Check Box element methods
-    When I retrieve a check box element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text is ""
-    And I should know the value is "1"
-    And I should know it is equal to itself
-    And I should know the 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
-    And I should know it is visible
-    And I should know the text is "page-object rocks!"
-    And I should know it is equal to itself
-    And I should know the tag name is "div"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  @watir_only
-  Scenario: Div element methods for watir
-    When I retrieve the div element
-    Then I should know the value is ""
-
-  @selenium_only
-  Scenario: Div element methods for selenium
-    When I retrieve the div element
-    Then I should know the value is nil
-
-  Scenario: Radio Button element methods
-    When I retrieve a radio button
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text is ""
-    And I should know the value is "Milk"
-    And I should know it is equal to itself
-    And I should know the tag name is "input"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Select List element methods
-    When I retrieve a select list
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes "Test 1"
-    And I should know the value is "option1"
-    And I should know it is equal to itself
-    And I should know the tag name is "select"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Table element methods
-    When I retrieve a table element
-    Then I should know it is visible
-    And I should know the text includes "Data1"
-    And I should know it is equal to itself
-    And I should know the tag name is "table"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  @watir_only
-  Scenario: Table element methods in watir
-    When I retrieve a table element
-    Then I should know it exists
-    And I should know the value is ""
-
-  @selenium_only
-  Scenario: Table element methods in selenium
-    When I retrieve a table element
-    Then I should know the 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 the text includes "Data4"
-    And I should know it is equal to itself
-    And I should know the tag name is "td"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  @watir_only
-  Scenario: Table Cell element methods in watir
-    When I retrieve table cell
-    Then I should know the value is ""
-
-  @selenium_only
-  Scenario: Table Cell element methods in selenium
-    When I retrieve table cell
-    Then I should know the value is nil
-
-  Scenario: Text Field element methods
-    When I retrieve a text field
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes ""
-    And I should know the value is ""
-    And I should know it is equal to itself
-    And I should know the tag name is "input"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Text Area element methods
-    When I retrieve the text area
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes ""
-    And I should know the value is ""
-    And I should know it is equal to itself
-    And I should know the tag name is "textarea"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Image element methods
-    When I get the image element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes ""
-    And I should know it is equal to itself
-    And I should know the tag name is "img"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  @watir_only
-  Scenario: Image element methods in watir
-    When I get the image element
-    Then I should know the value is ""
-
-  @selenium_only
-  Scenario: Image element methods in selenium
-    When I get the image element
-    Then I should know the value is nil
-
-  Scenario: Hidden Field element methods
-    When I retrieve the hidden field element
-    Then I should know it exists
-    And I should know it is not visible
-    And I should know the text includes ""
-    And I should know the value is "12345"
-    And I should know it is equal to itself
-    And I should know the tag name is "input"
-    And I should know the attribute "readonly" is false
-
-  Scenario: Form element methods
-    When I locate the form
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes ""
-    And I should know it is equal to itself
-    And I should know the tag name is "form"
-    And I should know the attribute "readonly" is false
-
-  @watir_only
-  Scenario: Form element methods in watir
-    When I locate the form
-    Then I should know the value is ""
-
-  @selenium_only
-  Scenario: Form element methods in selenium
-    When I locate the form
-    Then I should know the value is nil
-
-  Scenario: List item element methods
-    When I retrieve a list item element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text is "Item One"
-    And I should know it is equal to itself
-    And I should know the tag name is "li"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Unordered list element methods
-    When I retrieve an unordered list element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes "Item One"
-    And I should know the text includes "Item Two"
-    And I should know the text includes "Item Three"
-    And I should know it is equal to itself
-    And I should know the tag name is "ul"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Ordered list element methods
-    When I retrieve an ordered list element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text includes "Number One"
-    And I should know the text includes "Number Two"
-    And I should know the text includes "Number Three"
-    And I should know it is equal to itself
-    And I should know the tag name is "ol"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Heading element methods
-    When I retrieve a heading element
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text is "h1's are cool"
-    And I should know it is equal to itself
-    And I should know the tag name is "h1"
-    And I should know the attribute "readonly" is false
-    And I should be able to click it
-
-  Scenario: Firing an event
-    When I set the focus to the test text_field using the onfocus event
-    Then I should see the onfocus text "changed by onfocus event"
-    
-  Scenario: Hovering over an element
-    Given I am on the hover page
-    When I hover over the hello link
-    Then the font size should be "20px"
-    
-  Scenario: Setting focus on an element
-    When I set the focus on the test text_field
-    Then I should see the onfocus text "changed by onfocus event"
-
-  Scenario: Finding a parent element
-    When I find the child link element
-    And ask for the parent element
-    Then I should have a div parent
-
-  Scenario: Flashing an element
-    When I retrieve a button element
-    Then I should be able to flash it
-    
-  Scenario: Getting an element's id
-    When I retrieve a button element
-    Then I should know its id is "button_id"
-
-  Scenario: Double Clicking
-    Given I am on the Double Click page
-    When I double click the button
-    Then the paragraph should read "Double Click Received"
-
-  Scenario: Scrolling so an element is visible
-    When I retrieve a heading element
-    And I scroll the heading element into view
-    Then the heading element should be visible
-
-  @watir_only
-  Scenario: Expanding how we find elements to include non-standard locators
-    When I retrieve a div using data-entity
-    Then I should know it exists
-    And I should know it is visible
-    And I should know the text is "found using data-entity"
-    
-
-  Scenario: Accessing an HTML 5 element using the declaration
-    When I retrieve the figure using the declaration
-    Then I should see the figure contains an image
-
-  Scenario: Accessing an HTML 5 element using the element method
-    When I retrieve the figure using the element
-    Then I should see the figure contains an image
-
-  Scenario: Getting the class name for an element
-    When I search for the paragraph by "id"
-    Then I should know the paragraph class is "p_class"
-
-  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