druid-s 1.0.0

data/features/page_level_actions.feature

@@ -0,0 +1,116 @@
+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
+
+  Scenario: Getting the text from a web page
+    Given I am on the static elements page
+    Then the page should contain the text "Static Elements Page"
+
+  Scenario: Getting the html from a web page
+    Given I am on the static elements page
+    Then the page should contain the html "<title>Static Elements Page</title>"
+
+  Scenario: Getting the title from a web page
+    Given I am on the static elements page
+    Then the page should have the title "Static Elements Page"
+
+  Scenario: Going to baidu.com from a web page
+    Given I am on the static elements page
+    Then I am able to go to baidu.com
+
+  Scenario: Going to baidu.com by default
+    Given I can goto baidu.com by default
+    Then the page should have the title "百度"
+
+  Scenario: Using the visit_page methods without block
+    Given I can goto baidu.com using visit_page without block
+    Then the page should have the title "百度" using on_page without block
+
+  Scenario: Using the visit_page methods with block
+    Given I can goto baidu.com using visit_page with block
+    Then the page should have the title "百度" using on_page with block
+
+  Scenario: Validating the page title
+    Given I am on the static elements page
+    Then the page should have the expected title
+
+  Scenario: Validating the expected element
+    Given I am on the static elements page
+    Then the page should have the expected element
+
+  Scenario: Validating that an expected element does not exist
+    Given I am on the static elements page
+    Then the page should not have the expected element
+
+  Scenario: Waiting for something
+    Given I am on the static elements page
+    Then I should be able to wait for a block to return true
+
+  Scenario: Handling alert popups
+    Given I am on the static elements page
+    When I handle the alert
+    Then I should be able to get the alert's message
+
+  Scenario: Handling possible alert popups
+    Given I am on the static elements page
+    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
+    Given I am on the static elements 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
+    Given I am on the static elements page
+    When I handle the confirm
+    Then I should be able to get the confirm's message
+
+  Scenario: Handling possible confirm popups
+    Given I am on the static elements page
+    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
+    Given I am on the static elements page
+    When I handle the confirm that reloads the page
+    Then I should be able to get the confirm's message
+
+  Scenario: Handling prompt popups
+    Given I am on the static elements page
+    When I handle the prompt
+    Then I should be able to get the message and default value
+
+  Scenario: Handling possible prompt popups
+    Given I am on the static elements page
+    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
+    Given I am on the static elements page
+    When I open a second window
+    Then I should be able to attach to page object using title
+
+  Scenario: Attach to window using url
+    Given I am on the static elements page
+    When I open a second window
+    Then I should be able to attach to page object using url
+
+  Scenario: Attach to widnow using index
+    Given I am on the static elements page
+    When I open a second window
+    Then I should be able to attach to page object using index
+
+  Scenario: Refreshing the page
+    Given I am on the static elements page
+    Then I should be able to refresh the page
+
+  @dev
+  Scenario: Going back and forward
+    Given I am on the static elements page
+    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,33 @@
+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"
+
+    Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | 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"
+
+    Examples:
+    | param1  | param2  |
+    | class   | 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/populate_page_with.feature

@@ -0,0 +1,25 @@
+Feature: Populate Page With
+  In order to quickly fill out forms on a page
+  A tester will use the populate_page_with method
+  To fill in text, select options, check boxes, and select radio buttons
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario:
+    When I populate the page with the data:
+      | text_field_id   | abcDEF            |
+      | text_area_id    | abcdefghijklmnop  |
+      | select_list_id  | Test 2            |
+      | cb_id           | check             |
+      | butter_id       | check             |
+      | favorite_cheese | muen              |
+    Then the text field should contain "abcDEF"
+    And the text area should contain "abcdefghijklmnop"
+    And the selected option should be "Test 2"
+    And the First check box should be selected
+    And the "Butter" radio button should be selected
+    And the "muen" radio button should be selected in the group
+    When I populate the page with the data:
+      | select_list_id | option3 |
+    Then the selected option should be "Test/Test 3"

data/features/radio_button.feature

@@ -0,0 +1,51 @@
+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 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
+
+  @dev
+  Scenario Outline: Locating radio buttons on the Page
+    When I locate the radio button by "<locate_by>"
+    And I select the radio button
+    Then the "Milk" radio button should be selected
+
+    Scenarios:
+    | locate_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | value     |
+    | label     |
+    | css       |
+
+  Scenario: Retrieve a radio button
+    When I retrieve a radio button
+    Then I should know it exists
+    And I should know it is visible
+
+  @multi
+  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
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  @locator
+  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,28 @@
+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
+    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"

data/features/sample-app/public/audio_video.html

@@ -0,0 +1,19 @@
+<html>
+<head>
+  <title>Audio and Video</title>
+</head>
+  <body>
+    <h2>Audio & Video</h2>
+    <audio controls id="audio" name="audio" class="audio">
+      <source src="04-Death_Becomes_Fur.mp4" type="audio/mp4">
+      <source src="04-Death_Becomes_Fur.oga" type="audio/ogg; codecs=vorbis">
+      <p>Your user agent does not support the HTML5 Audio element.</p>
+    </audio>
+
+    <video width="320" height="240" controls="controls" id="video" name="video" class="video">
+      <source src="movie.mp4" type="video/mp4" />
+      <source src="movie.ogg" type="video/ogg" />
+      Your browser does not support the video tag.
+    </video>
+  </body>
+</html>