druid-ts 0.0.1 → 1.1.0

data/features/checkbox.feature

@@ -5,7 +5,7 @@ Feature: Check Box
   Background:
     Given I am on the static elements page
 
-  Scenario: Selecting an element on the checkbox
+  Scenario: Selecting a checkbox
     When I select the First check box
     Then the First check box should be selected
     When I unselect the First check box
@@ -22,6 +22,7 @@ Feature: Check Box
     | name      |
     | xpath     |
     | index     |
+    | value     |
 
   Scenario: Retrieve a CheckBox
     When I retrieve a check box element
@@ -37,3 +38,8 @@ Feature: Check Box
     | param1  | param2  |
     | class   | index   |
     | name    | index   |
+
+  @locator
+  Scenario: Finding a check box dynamically
+    When I select the first check box while the script is executing
+    Then the First check box should be selected

data/features/div.feature

@@ -21,6 +21,7 @@ Feature: Div
     | xpath     |
     | index     |
     | name      |
+    | text      |
 
   Scenario: Getting the div element
     When I retrieve the div element
@@ -36,3 +37,8 @@ Feature: Div
     | param1  | param2  |
     | class   | index   |
     | name    | index   |
+
+  @locator
+  Scenario: Finding a div dynamically
+    When I get the text from a div while the script is executing
+    Then the text should be "page-object rocks!"

data/features/element.feature

@@ -3,6 +3,12 @@ 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
+    When I check a disabled button
+    Then it should know it is not enabled
+
   Scenario: Link element methods
     When I retrieve a link element
     Then I should know it exists
@@ -112,3 +118,97 @@ Feature: Elements
     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
+    And I should know its' value is ""
+
+  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

data/features/file_field.feature

@@ -0,0 +1,35 @@
+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     |
+
+  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 The file field should exist

data/features/form.feature

@@ -17,13 +17,19 @@ Feature: Form
     | class     |
     | xpath     |
     | index     |
+    | action    |
 
   @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
+    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   |
 
-      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 be able to submit the form

data/features/frames.feature

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

data/features/heading.feature

@@ -0,0 +1,164 @@
+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     |
+     | name      |
+     | xpath     |
+     | index     |
+
+   @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   |
+     | name    | 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     |
+     | name      |
+     | xpath     |
+     | index     |
+
+   @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   |
+     | name    | 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     |
+     | name      |
+     | xpath     |
+     | index     |
+
+   @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   |
+     | name    | 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     |
+     | name      |
+     | xpath     |
+     | index     |
+
+   @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   |
+     | name    | 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     |
+     | name      |
+     | xpath     |
+     | index     |
+
+   @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     |
+     | name      |
+     | xpath     |
+     | index     |
+
+   @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

@@ -21,6 +21,7 @@ Feature: Hidden Fields
     | tag_name  |
     | index     |
     | text      |
+    | value     |
 
   @multi
   Scenario Outline: Locating a hidden field using multiple parameters
@@ -31,3 +32,8 @@ Feature: Hidden Fields
     | 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 hidden field element should contains "12345"