meeane-page-object 0.1.8

data/features/page_level_actions.feature

@@ -0,0 +1,90 @@
+Feature: Page level actions
+  In order to act on pages from a web site
+  Testers will need to use the page object to encapsulate access
+
+  Background:
+    Given I am on the static elements page
+
+
+  Scenario: Getting the text from a web page
+    Then the page should contain the text "Static Elements Page"
+
+  Scenario: Getting the html from a web page
+    Then the page should contain the html "<title>Static Elements Page</title>"
+
+  Scenario: Getting the title from a web page
+    Then the page should have the title "Static Elements Page"
+    
+  Scenario: Validating the page title
+    Then the page should have the expected title
+
+  Scenario: Validating the expected element
+    Then the page should have the expected element
+    
+  Scenario: Validating that an expected element does not exist
+    Then the page should not have the expected element
+
+  Scenario: Waiting for something
+    Then I should be able to wait for a block to return true
+
+  Scenario: Handling alert popups
+    When I handle the alert
+    Then I should be able to get the alert's message
+
+  Scenario: Handling possible alert popups
+    When I handle the possible alert
+    Then I should be able to verify the popup didn't have a message
+
+  Scenario: Handling alert popups that reload the page
+    When I handle the alert that reloads the page
+    Then I should be able to get the alert's message
+
+  Scenario: Handling confirm popups
+    When I handle the confirm
+    Then I should be able to get the confirm message
+
+  Scenario: Handling possible confirm popups
+    When I handle the possible confirm
+    Then I should be able to verify the popup didn't have a message
+
+  Scenario: Handling confirm popups that reload the page
+    When I handle the confirm that reloads the page
+    Then I should be able to get the confirm message
+
+  Scenario: Handling prompt popups
+    When I handle the prompt
+    Then I should be able to get the message and default value
+
+  Scenario: Handling possible prompt popups
+    When I handle the possible prompt
+    Then I should be able to verify the popup didn't have a message
+    
+  Scenario: Attach to window using title
+    When I open a second window
+    Then I should be able to attach to a page object using title
+
+  Scenario: Attach to window using title with multiple windows
+    When I open a second window
+    When I open a third window
+    Then I should be able to attach to a page object using title
+    
+  Scenario: Attach to window using url
+    When I open a second window
+    Then I should be able to attach to a page object using url
+
+  Scenario: Attach to window using url with multiple windows
+    When I open a second window
+    When I open a third window
+    Then I should be able to attach to a page object using url
+    
+  Scenario: Refreshing the page
+    Then I should be able to refresh the page
+    
+  Scenario: Going back and forward
+    When I select the link labeled "Google Search"
+    Then the page should contain the text "Success"
+    When I press the back button
+    Then the page should contain the text "Static Elements Page"
+    When I press the forward button
+    Then the page should contain the text "Success"
+    

data/features/paragraph.feature

@@ -0,0 +1,35 @@
+Feature: Paragraph
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the text from a paragraph
+    When I get the text from the paragraph
+    Then the text should be "Static Elements Page"
+
+  Scenario Outline: Locating paragraphs on the page
+    When I search for the paragraph by "<search_by>"
+    Then the text should be "Static Elements Page"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | name      |
+    | css       |
+
+  Scenario Outline: Locating paragraphs using multiple parameters
+    When I search for the paragraph by "<param1>" and "<param2>"
+    Then the text should be "Static Elements Page"
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a paragraph dynamically
+    When I get the text from a paragraph while the script is executing
+    Then I should see that the paragraph exists
+    And the text should be "Static Elements Page"

data/features/radio_button.feature

@@ -0,0 +1,58 @@
+Feature: Radio Buttons
+  In order to interact with radio buttons
+  Testers will need access and interrogation ability
+
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Selecting and clearing a radio button
+    When I select the "Milk" radio button
+    Then the "Milk" radio button should be selected
+    When I select the "Butter" radio button
+    Then the "Butter" radio button should be selected
+
+  Scenario Outline: Locating radio buttons on the Page
+    When I search for the radio button by "<search_by>"
+    And I select the radio button
+    Then the "Milk" radio button should be selected
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | value     |
+    | index     |
+    | label     |
+
+  @selenium_only
+  Scenario Outline: Locating radio buttons on the Page
+    When I search for the radio button by "<search_by>"
+    And I select the radio button
+    Then the "Milk" radio button should be selected
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating radio buttons using multiple parameters
+    When I search for the radio button by "<param1>" and "<param2>"
+    And I select the radio button
+    Then the "Milk" radio button should be selected
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Retrieve a radio button
+    When I retrieve a radio button
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario: Finding a radio button dynamically
+    When I select the radio button while the script is executing
+    Then I should see that the radio button exists
+    And the "Milk" radio button should be selected

data/features/radio_button_group.feature

@@ -0,0 +1,29 @@
+Feature: Radio Button Groups
+  In order to interact with radio button groups
+  Testers will need access and interrogation ability
+
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Confirm existence of a radio button group
+    Then I should see that the radio button group exists
+
+  Scenario: No radio buttons in the group have been selected
+    When no radio buttons have been selected
+    Then no radio buttons should be selected in the group
+
+  Scenario: Selecting grouped radio buttons by value
+    When I select the "ched" radio button in the group
+    Then the "ched" radio button should be selected in the group
+    And the "emmen" radio button should not be selected
+    And the "muen" radio button should not be selected
+    When I select the "muen" radio button in the group
+    Then the "ched" radio button should not be selected
+    And the "emmen" radio button should not be selected
+    And the "muen" radio button should be selected in the group
+
+  Scenario: Getting an array of elements for each radio button in the group
+    When I ask for the elements of a radio button group
+    Then I should have an array with elements for each radio button
+    And the radio button element values should be "ched", "emmen", "muen"