meeane-page-object 0.1.8

data/features/element.feature

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

data/features/file_field.feature

@@ -0,0 +1,40 @@
+Feature: File Field
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Setting the value on the file field
+    When I set the file field to the step definition file
+    Then its' value should equal that file
+
+  Scenario Outline: Locating file fields on the Page
+    When I search for the file field by "<search_by>"
+    Then I should be able to set the file field
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | title     |
+    | index     |
+    | label     |
+
+  @selenium_only
+  Scenario Outline: Locating file fields on the Page
+    When I search for the file field by "<search_by>"
+    Then I should be able to set the file field
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating file fields using multiple parameters
+    When I search for the file field by "<param1>" and "<param2>"
+    Then I should be able to set the file field
+
+  Examples:
+  | param1 | param2 |
+  | class  | index  |
+  | name   | index  |

data/features/form.feature

@@ -0,0 +1,43 @@
+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
+
+  Scenario Outline: Locating a form on the page
+    When I locate the form by "<search_by>"
+    Then I should be able to submit the form
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | action    |
+
+  @selenium_only
+  Scenario Outline: Locating a form on the page
+    When I locate the form by "<search_by>"
+    Then I should be able to submit the form
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating table using multiple parameters
+    When I locate the form using "<param1>" and "<param2>"
+    Then I should be able to submit the form
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a form dynamically
+    When I locate a form while the script is executing
+    Then I should see that the form exists
+    And I should be able to submit the form

data/features/frames.feature

@@ -0,0 +1,75 @@
+Feature: Handling frames
+
+  Scenario: Accessing elements within the frame
+    Given I am on the frame elements page
+    When I type "page-object" into the text field for frame 2 using "id"
+    Then I should verify "page-object" is in the text field for frame 2 using "id"
+    When I type "page-object" into the text field for frame 2 using "name"
+    Then I should verify "page-object" is in the text field for frame 2 using "name"
+    When I type "page-object" into the text field for frame 2 using "index"
+    Then I should verify "page-object" is in the text field for frame 2 using "index"
+    #And I should be able to get the text fields text from frame 2 using "index"
+
+@watir_only    
+  Scenario: Accessing elements within the frame using Regexp
+    Given I am on the frame elements page
+    When I type "page-object" into the text field for frame 2 using "regex"
+    Then I should verify "page-object" is in the text field for frame 2 using "regex"
+
+@watir_only    
+  Scenario: Accessing elements within the frame using multiple identifiers
+    Given I am on the iframe elements page
+    When I type "page-object" into the text field for frame 2 using "multiple identifiers"
+    Then I should verify "page-object" is in the text field for frame 2 using "multiple identifiers"
+
+  Scenario: Switching between frames
+    Given I am on the frame elements page
+    When I type "page-object" into the text field for frame 2 using "id"
+    And I type "page-object" into the text field from frame 1 using "id"
+    Then I should verify "page-object" is in the text field for frame 2 using "id"
+    And I should verify "page-object" is in the text field for frame 1 using "id"
+
+  Scenario: Accessing elements within the frame
+    Given I am on the iframe elements page
+    When I type "page-object" into the text field for frame 2 using "id"
+    Then I should verify "page-object" is in the text field for frame 2 using "id"
+    When I type "page-object" into the text field for frame 2 using "name"
+    Then I should verify "page-object" is in the text field for frame 2 using "name"
+    When I type "page-object" into the text field for frame 2 using "index"
+    Then I should verify "page-object" is in the text field for frame 2 using "index"
+
+  Scenario: Switching between frames
+    Given I am on the iframe elements page
+    When I type "page-object" into the text field for frame 2 using "id"
+    And I type "page-object" into the text field from frame 1 using "id"
+    Then I should verify "page-object" is in the text field for frame 2 using "id"
+    And I should verify "page-object" is in the text field for frame 1 using "id"
+    
+  Scenario: Nested frames
+    Given I am on the nested frame elements page
+    Then I should be able to click the link in the frame
+
+  Scenario: Identifying items in frames at runtime
+    Given I am on the frame elements page
+    When I type "page-object" into the text field from frame 1 identified dynamically
+    Then I should verify "page-object" in the text field for frame 1 identified dynamically
+
+  Scenario: Identifying items in iframes at runtime
+    Given I am on the iframe elements page
+    When I type "page-object" into the text field from iframe 1 identified dynamically
+    Then I should verify "page-object" in the text field for iframe 1 identified dynamically
+
+  Scenario: Handling alerts inside frames
+    Given I am on the frame elements page
+    When I trigger an alert within a frame
+    Then I should be able to get the alert's message
+
+  Scenario: Handling confirms inside frames
+    Given I am on the frame elements page
+    When I trigger a confirm within a frame
+    Then I should be able to get the confirm message
+
+  Scenario: Handling prompts inside frames
+    Given I am on the frame elements page
+    When I trigger a prompt within a frame
+    Then I should be able to get the message and default value

data/features/generic_elements.feature

@@ -0,0 +1,29 @@
+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"
+
+  Scenario: getting properties from a svg element
+    When I get the svg element
+    Then the svg width should be "100"
+    And the svg height should be "100"

data/features/gxt_table_extension.feature

@@ -0,0 +1,24 @@
+Feature: Gxt Table Extension
+  As a Quality Engineer working on a Gxt or Gwt project
+  In order to easily create test widgets to interact with application widgets
+  I need to define, register and use widgets as if they were normal elements
+
+  Background:
+    Given I have defined a GxtTable class extending Table
+    And I have registered the GxtTable with PageObject
+    And I define a page-object using that widget
+    And I am on the Gxt Examples page
+    And I have the Basic Grid opened
+
+  Scenario: Retrieve a GxtTable
+    When I retrieve a GxtTable widget
+    Then I should know it is visible
+
+  @watir_only
+  Scenario: Determine if a GxtTable exists
+    When I retrieve a GxtTable widget
+    Then I should know it exists
+
+  Scenario: Confirm a correct row count from a GxtTable
+    When I retrieve a GxtTable widget
+    Then the GxtTable should have "13" rows

data/features/headings.feature

@@ -0,0 +1,97 @@
+Feature: Headings
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text of headings
+    When I get the text for the "h1" element
+    Then I should see "h1's are cool"
+    When I get the text for the "h2" element
+    Then I should see "h2's are cool"
+    When I get the text for the "h3" element
+    Then I should see "h3's are cool"
+    When I get the text for the "h4" element
+    Then I should see "h4's are cool"
+    When I get the text for the "h5" element
+    Then I should see "h5's are cool"
+    When I get the text for the "h6" element
+    Then I should see "h6's are cool"
+
+  Scenario Outline: Locating h1s on the Page
+    When I search for the heading1 by "<search_by>"
+    Then I should see "h1's are cool"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating h2s on the Page
+    When I search for the heading2 by "<search_by>"
+    Then I should see "h2's are cool"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating h3s on the Page
+    When I search for the heading3 by "<search_by>"
+    Then I should see "h3's are cool"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating h4s on the Page
+    When I search for the heading4 by "<search_by>"
+    Then I should see "h4's are cool"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating h5s on the Page
+    When I search for the heading5 by "<search_by>"
+    Then I should see "h5's are cool"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating h6s on the Page
+    When I search for the heading6 by "<search_by>"
+    Then I should see "h6's are cool"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+

data/features/hidden_field.feature

@@ -0,0 +1,45 @@
+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"
+
+  Scenario Outline: Locating hidden fields on the Page
+    When I search for the hidden field by "<search_by>"
+    Then the hidden field element should contain "12345"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | text      |
+    | value     |
+
+  @selenium_only
+  Scenario Outline: Locating hidden fields on the Page
+    When I search for the hidden field by "<search_by>"
+    Then the hidden field element should contain "12345"
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating a hidden field using multiple parameters
+    When I search for the hidden field by "<param1>" and "<param2>"
+    Then the hidden field element should contain "12345"
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a hidden field dynamically
+    When I find a hidden field while the script is executing
+    Then I should see that the hidden field exists
+    And the hidden field element should contain "12345"