druid-s 1.0.0

data/features/element.feature

@@ -0,0 +1,281 @@
+Feature: Elements
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Elements enbaled?
+    When I click an enabled button
+    Then it should know it is enabled
+    And it should know that it is 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: Checking focus of the element with focus
+    And I set the focus to the test text_field
+    When I retrieve the focus state of the text_field
+    Then I should know that the text_field is focused
+
+  Scenario: Checking focus of the element without focus
+    And I set the focus off the test text_field
+    When I retrieve the focus state of the text_field
+    Then I should know that the text_field is not focused
+
+  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 its' 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 its' 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
+
+  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 its' value is "Click Me"
+    And I should know its' text is "Click Me"
+    And I should know it is equal to itself
+    And I should know its' tag name is "input"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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 its' text is ""
+    And I should know its' value is "1"
+    And I should know it is equal to itself
+    And I should know its' 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 its' text is "page-object rocks!"
+    And I should know it is equal to itself
+    And I should know its' tag name is "div"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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 its' text is ""
+    And I should know its' value is "Milk"
+    And I should know it is equal to itself
+    And I should know its' 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 its' text includes "Test 1"
+    And I should know its' value is "option1"
+    And I should know it is equal to itself
+    And I should know its' 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
+    Then I should know it exists
+    And I should know its' text includes "Data1"
+    And I should know it is equal to itself
+    And I should know its' tag name is "table"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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 its' text includes "Data4"
+    And I should know it is equal to itself
+    And I should know its' tag name is "td"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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 its' text includes ""
+    And I should know its' value is ""
+    And I should know it is equal to itself
+    And I should know its' tag name is "input"
+    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 its' text includes ""
+    And I should know it is equal to itself
+    And I should know its' tag name is "img"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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 its' text includes ""
+    And I should know its' value is "12345"
+    And I should know it is equal to itself
+    And I should know its' 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 its' text includes ""
+    And I should know it is equal to itself
+    And I should know its' tag name is "form"
+    And I should know the attribute "readonly" is false
+
+  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 its' text includes ""
+    And I should know its' value is ""
+    And I should know it is equal to itself
+    And I should know its' tag name is "textarea"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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 its' text is "Item One"
+    And I should know it is equal to itself
+    And I should know its' 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 a unordered list element
+    Then I should know it exists
+    And I should know it is visible
+    And I should know its' text includes "Item One"
+    And I should know its' text includes "Item Two"
+    And I should know its' text includes "Item Three"
+    And I should know it is equal to itself
+    And I should know its' 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 a ordered list element
+    Then I should know it exists
+    And I should know it is visible
+    And I should know its' text includes "Number One"
+    And I should know its' text includes "Number Two"
+    And I should know its' text includes "Number Three"
+    And I should know it is equal to itself
+    And I should know its' tag name is "ol"
+    And I should know the attribute "readonly" is false
+    And I should be able to click it
+
+  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: 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 its' text is "h1's are cool"
+    And I should know it is equal to itself
+    And I should know its' 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: 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: 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: Getting an element's id
+    When I retrieve a button element
+    Then I should know its id is "button_id"
+
+  Scenario: Expanding how we find elemnts to include non-stardard 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 uisng 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

data/features/file_field.feature

@@ -0,0 +1,38 @@
+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 This filefield element should exist
+
+  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     |
+    | 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   |
+
+  @locator
+  Scenario: Finding a file field dynamically
+    When I locate a file field while the script is executing
+    Then I should see that the file field element exists
+    And The file field should exist

data/features/form.feature

@@ -0,0 +1,37 @@
+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 "<locate_by>"
+    Then I should be able to submit the form
+
+    Examples:
+    | locate_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | action    |
+    | css       |
+
+  @multi
+  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
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  @locator
+  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,76 @@
+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"
+
+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 iframe
+  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 iframes
+  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 an confirm within a frame
+  Then I should be able to get the confirm's message
+
+Scenario: Handling prompts inside frames
+  Given I am on the frame elements page
+  When I trigger an prompt within a frame
+  Then I should be able to get the message and default value
+
+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"
+
+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: Frames in sections
+  Given I am on the frame section page
+  Then I should be able to access an element in the frame in the section repeatedly

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/heading.feature

@@ -0,0 +1,160 @@
+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"
+
+     Examples:
+     | search_by |
+     | id        |
+     | class     |
+     | xpath     |
+     | index     |
+     | css       |
+
+   @multi
+   Scenario Outline: Locating h1 using multiple parameters
+     When I locate the h1 using "<param1>" and "<param2>"
+     Then the text should be "h1's are cool"
+
+     Examples:
+     | param1  | param2  |
+     | class   | index   |
+
+   @locator
+   Scenario: Finding a h1 dynamically
+     When I locate a h1 while the script is executing
+     Then the text should be "h1's are cool"
+
+   Scenario Outline: Locating h2s on the Page
+     When I search for the heading2 by "<search_by>"
+     Then I should see "h2's are cool"
+
+     Examples:
+     | search_by |
+     | id        |
+     | class     |
+     | xpath     |
+     | index     |
+     | css       |
+
+   @multi
+   Scenario Outline: Locating h2 using multiple parameters
+     When I locate the h2 using "<param1>" and "<param2>"
+     Then the text should be "h2's are cool"
+
+     Examples:
+     | param1  | param2  |
+     | class   | index   |
+
+   @locator
+   Scenario: Finding a h2 dynamically
+     When I locate a h2 while the script is executing
+     Then the text should be "h2's are cool"
+
+   Scenario Outline: Locating h3s on the Page
+     When I search for the heading3 by "<search_by>"
+     Then I should see "h3's are cool"
+
+     Examples:
+     | search_by |
+     | id        |
+     | class     |
+     | xpath     |
+     | index     |
+     | css       |
+
+   @multi
+   Scenario Outline: Locating h3 using multiple parameters
+     When I locate the h3 using "<param1>" and "<param2>"
+     Then the text should be "h3's are cool"
+
+     Examples:
+     | param1  | param2  |
+     | class   | index   |
+
+   @locator
+   Scenario: Finding a h3 dynamically
+     When I locate a h3 while the script is executing
+     Then the text should be "h3's are cool"
+
+
+   Scenario Outline: Locating h4s on the Page
+     When I search for the heading4 by "<search_by>"
+     Then I should see "h4's are cool"
+
+     Examples:
+     | search_by |
+     | id        |
+     | class     |
+     | xpath     |
+     | index     |
+     | css       |
+
+   @multi
+   Scenario Outline: Locating h4 using multiple parameters
+     When I locate the h4 using "<param1>" and "<param2>"
+     Then the text should be "h4's are cool"
+
+     Examples:
+     | param1  | param2  |
+     | class   | index   |
+
+
+   @locator
+   Scenario: Finding a h4 dynamically
+     When I locate a h4 while the script is executing
+     Then the text should be "h4's are cool"
+
+   Scenario Outline: Locating h5s on the Page
+     When I search for the heading5 by "<search_by>"
+     Then I should see "h5's are cool"
+
+     Examples:
+     | search_by |
+     | id        |
+     | class     |
+     | xpath     |
+     | index     |
+     | css       |
+
+   @locator
+   Scenario: Finding a h5 dynamically
+     When I locate a h5 while the script is executing
+     Then the text should be "h5's are cool"
+
+
+   Scenario Outline: Locating h6s on the Page
+     When I search for the heading6 by "<search_by>"
+     Then I should see "h6's are cool"
+
+     Examples:
+     | search_by |
+     | id        |
+     | class     |
+     | xpath     |
+     | index     |
+     | css       |
+
+   @locator
+   Scenario: Finding a h6 dynamically
+     When I locate a h6 while the script is executing
+     Then the text should be "h6's are cool"

data/features/hidden_field.feature

@@ -0,0 +1,39 @@
+Feature: Hidden Fields
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: 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 locate the hidden field by "<locate_by>"
+    Then hidden field element should contains "12345"
+
+    Examples:
+    | locate_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | text      |
+    | value     |
+    | css       |
+
+  @multi
+  Scenario Outline: Locating a hidden field using multiple parameters
+    When I search for the hidden field by "<param1>" and "<param2>"
+    Then hidden field element should contains "12345"
+
+    Examples:
+    | param1  | param2  |
+    | class   | index   |
+    | name    | index   |
+
+  @locator
+  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 hidden field element should contains "12345"

data/features/html/async.html

@@ -0,0 +1,31 @@
+<html>
+  <head>
+    <title>Async Page</title>
+    <script type="text/javascript">
+      function unhide() {
+        document.getElementById("target").style.display="block";
+      }
+      function hide() {
+        document.getElementById("target").style.display="none";
+      }
+      function addDiv() {
+        var button = document.createElement("input");
+        button.setAttribute("type", "button");
+        button.setAttribute("value", "New Button");
+        button.setAttribute("id", "new_button");
+        document.body.appendChild(button);
+      }
+      function removeDiv() {
+        var button = document.getElementById("new_button");
+        document.body.removeChild(button);
+      }
+    </script>
+  </head>
+  <body>
+    <input type="button" id="target" value="Target"/>
+    <input type="button" onclick="setTimeout(function() {hide();}, 2000);" value="Hide Button"/>
+    <input type="button" onclick="setTimeout(function() {unhide();}, 2000);" value="Unhide Button"/>
+    <input type="button" onclick="setTimeout(function() {addDiv();}, 2000);" value="Create Button"/>
+    <input type="button" onclick="setTimeout(function() {removeDiv();}, 2000);" value="Remove Button"/>
+  </body>
+</html>