meeane-page-object 0.1.8

data/features/table.feature

@@ -0,0 +1,114 @@
+Feature: Table
+  In order to interact with tables
+  Testers will need access and interrogation ability
+
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Retrieve a table
+    When I retrieve a table element
+    Then I should know it is visible
+
+  Scenario: Determine if a table exists
+    When I retrieve a table element
+    Then I should know it exists
+
+  Scenario: Retrieve the data from a table
+    When I retrieve a table element
+    Then the data for row "2" should be "Data1" and "Data2"
+    And the data for row "3" should be "Data3" and "Data4"
+    And the table should have "3" rows
+    And row "2" should have "2" columns
+    And the data for the second row should be "Data1" and "Data2"
+    And the data for the last row should be "Data3" and "Data4"
+    
+  Scenario: Retrieve data from a table using a row header
+    When I retrieve a table element
+    Then the data for row "Data3" should be "Data3" and "Data4"
+
+  Scenario: Retrieve data from a table using a partial row header
+    When I retrieve a table element
+    Then the data for row "ata3" should be "Data3" and "Data4"
+
+  Scenario: Retrieve data from a table using a row header in the 2nd column
+    When I retrieve a table element
+    Then the data for row "Data4" should be "Data3" and "Data4"
+
+  Scenario: Retrieve data from a table using a partial row header in the 2nd column
+    When I retrieve a table element
+    Then the data for row "ata4" should be "Data3" and "Data4"
+    
+  Scenario: Retrieve data from a table using a column header
+    When I retrieve a table element
+    Then the data for column "Header" and row "3" should be "Data4"
+
+  Scenario: Retrieve data from a table with a thead using a column header
+    When I retrieve a table with thead element
+    Then the data for column "Col1" and row "2" should be "Data1"
+
+  Scenario: Retrieve data from the first row of a table with a thead using a column header
+    When I retrieve a table with thead element
+    Then the data for column "Col1" and row "1" should be "Col1"
+
+  Scenario: Retrieve data from a table using a partial column header
+    When I retrieve a table element
+    Then the data for column "eader" and row "3" should be "Data4"
+    
+  Scenario: Retrieve data from a table using both headers
+    When I retrieve a table element
+    Then the data for row "Data3" and column "eader" should be "Data4"
+    
+  Scenario: Retrieve data from a table with an incorrect row header
+    When I retrieve a table element
+    Then the data for row "Data20" should be nil
+
+  Scenario: Retrieve data from a table with an incorrect column header
+    When I retrieve a table element
+    Then the data for row "Data3" and column "Data20" should be nil
+
+  Scenario: Retrieve data from a table that does not have a cell which corresponds to a column header
+    When I retrieve a table with thead element
+    Then the data for row "Data5" and column "Col2" should be nil
+
+  Scenario Outline: Locating table cells on the Page
+    When I retrieve a table element by "<search_by>"
+    Then the data for row "2" should be "Data1" and "Data2"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | name      |
+
+  @selenium_only
+  Scenario Outline: Locating table cells on the Page
+    When I retrieve a table element by "<search_by>"
+    Then the data for row "2" should be "Data1" and "Data2"
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating table using multiple parameters
+    When I retrieve a table element by "<param1>" and "<param2>"
+    Then the data for row "2" should be "Data1" and "Data2"
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a table dynamically
+    When I retrieve a table element while the script is executing
+    And the data for row "2" should be "Data1" and "Data2"
+
+  @watir_only
+  Scenario: Finding an existing table
+    Then I should see that the table exists
+    
+  Scenario: Getting the text from a table
+    Then I should see the text includes "Data1" when I retrieve it by "id"
+    And I should see the text includes "Data2" when I retrieve it by "id"

data/features/table_cell.feature

@@ -0,0 +1,45 @@
+Feature: Table Cell
+
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Retrieving the text from a table cell
+    When I retrieve the data from the table cell
+    Then the cell data should be 'Data4'
+
+  Scenario Outline: Locating table cells on the Page
+    When I search for the table cell by "<search_by>"
+    Then the cell data should be 'Data4'
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | name      |
+    | text      |
+    | css       |
+
+  @watir_only
+  Scenario Outline: Locating table cells on the Page with watir
+    When I search for the table cell by "<search_by>"
+    Then the cell data should be 'Data4'
+
+  Scenarios:
+    | search_by |
+    | index     |
+
+  Scenario Outline: Locating table cell using multiple parameters
+    When I retrieve a table cell element by "<param1>" and "<param2>"
+    Then the cell data should be 'Data4'
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a table cell dynamically
+    When I retrieve a table cell element while the script is executing
+    Then I should see that the cell exists
+    And the cell data should be 'Data4'

data/features/text_area.feature

@@ -0,0 +1,51 @@
+Feature: Text Area
+
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Setting and getting a value from a text area
+    When I type "abcdefghijklmnop" into the text area
+    Then the text area should contain "abcdefghijklmnop"
+
+  Scenario Outline: Locating text area on the Page
+    When I search for the text area by "<search_by>"
+    Then I should be able to type "I found it" into the area
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | label     |
+
+  @selenium_only
+  Scenario Outline: Locating text area on the Page
+    When I search for the text area by "<search_by>"
+    Then I should be able to type "I found it" into the area
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating a text area using multiple parameters
+    When I search for the text area by "<param1>" and "<param2>"
+    Then I should be able to type "I found it" into the area
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a text area dynamically
+    When I find a text area while the script is executing
+    Then I should see that the text area exists
+    And I should be able to type "I found it" into the area element
+
+  Scenario: Clearing the text area
+    When I type "abcdefghijklmnop" into the text area
+    Then the text area should contain "abcdefghijklmnop"
+    When I clear the text area
+    Then the text area should contain ""

data/features/text_field.feature

@@ -0,0 +1,70 @@
+Feature: Text Fields
+  In order to interact with text fields
+  Testers will need access and interrogation ability
+
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Setting and getting a value from a text field
+    When I type "abcDEF" into the text field
+    Then the text field should contain "abcDEF"
+
+  Scenario Outline: Locating text fields on the Page
+    When I search for the text field by "<search_by>"
+    Then I should be able to type "I found it" into the field
+
+  Examples:
+    | search_by  |
+    | id         |
+    | class      |
+    | name       |
+    | xpath      |
+    | index      |
+    | title      |
+    | text       |
+    | label      |
+
+
+  @watir_only
+  Scenario Outline: Locating text fields on the Page using Watir
+    When I search for the text field by "<search_by>"
+    Then I should be able to type "I found it" into the field
+  Examples:
+    | search_by  |
+    | data_field |
+
+  @selenium_only
+  Scenario Outline: Locating text fields on the Page using Selenium
+    When I search for the text field by "<search_by>"
+    Then I should be able to type "I found it" into the field
+
+  Examples:
+    | search_by |
+    | css       |
+
+
+  Scenario Outline: Locating a text field using multiple parameters
+    When I search for the text field by "<param1>" and "<param2>"
+    Then I should be able to type "I found it" into the field
+
+  Examples:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Retrieve a text field
+    When I retrieve a text field
+    Then I should know it exists
+    And I should know it is visible
+
+  Scenario: Finding a text field dynamically
+    When I find a text field while the script is executing
+    Then I should see that the text field exists
+    And I should be able to type "I found it" into the field element
+
+  Scenario: Appending text to a text field
+    When I type "abcd" into the text field
+    And I append "efg" to the text field
+    Then the text field should contain "abcdefg"
+

data/features/unordered_list.feature

@@ -0,0 +1,56 @@
+Feature: Unordered list
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: Getting the first element from the unordered list
+    When I get the first item from the unordered list
+    Then the list items text should be "Item One"
+
+  Scenario Outline: Locating unordered lists on the page
+    When I search for the unordered list by "<search_by>"
+    And I get the first item from the list
+    Then the list items text should be "Item One"
+    And the list should contain 3 items
+    And each item should contain "Item"
+
+  Scenarios:
+    | search_by |
+    | id        |
+    | class     |
+    | xpath     |
+    | index     |
+    | name      |
+
+  @selenium_only
+  Scenario Outline: Locating unordered lists on the page
+    When I search for the unordered list by "<search_by>"
+    And I get the first item from the list
+    Then the list items text should be "Item One"
+    And the list should contain 3 items
+    And each item should contain "Item"
+
+  Scenarios:
+    | search_by |
+    | css       |
+
+  Scenario Outline: Locating unordered lists using multiple parameters
+    When I search for the unordered list by "<param1>" and "<param2>"
+    And I get the first item from the list
+    Then the list items text should be "Item One"
+
+  Scenarios:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Finding a unordered list dynamically
+    When I search for the unordered list while the script is executing
+    Then I should see that the unordered list exists
+    When I get the first item from the list
+    Then the list items text should be "Item One"
+
+  Scenario: Getting the text from an unordered list
+    Then the text for the unordered list should contain "Item One"
+    And the text for the unordered list should contain "Item Two"
+    And the text for the unordered list should contain "Item Three"

data/features/video.feature

@@ -0,0 +1,73 @@
+Feature: Support for video element
+
+  Background:
+    Given I am on the static elements page
+
+  Scenario: finding an video element
+    When I retrieve the video element
+    Then I should know it exists
+    And I should know it is visible
+    
+  Scenario Outline: Locating a video element on the page
+    When I search for the video element by "<search_by>"
+    Then I should know it is visible
+
+  Examples:
+    | search_by |
+    | id        |
+    | class     |
+    | name      |
+    | xpath     |
+    | index     |
+    | css       |
+
+  Scenario Outline: Locating videos using multiple parameters
+    When I search for the video element by "<param1>" and "<param2>"
+    Then I should know it is visible
+
+  Examples:
+    | param1 | param2 |
+    | class  | index  |
+    | name   | index  |
+
+  Scenario: Should know if it is autoplay
+    When I retrieve the video element
+    Then I should know the video is not autoplay
+    
+  Scenario: Should know if the controls are displayed
+    When I retrieve the video element
+    Then I should know that the controls are displayed
+
+  Scenario: Should know if it is paused
+    When I retrieve the video element
+    Then I should know that the video is paused
+
+  Scenario: Should know its duration
+    When I retrieve the video element
+    Then I should know that the duration is greater than 12 seconds
+
+  Scenario: Should know its volume
+    When I retrieve the video element
+    Then I should know that its volume is 1
+
+  Scenario: Should know its height and width
+    When I retrieve the video element
+    Then I should know that its height is 240 pixels
+    And I should knot what its width is 320 pixels
+    
+  Scenario: Should know if it has ended
+    When I retrieve the video element
+    Then I should know that it has not ended
+
+  Scenario: Should know if it is seeking
+    When I retrieve the video element
+    Then I should know that it is not seeking
+
+  Scenario: Should know if it is in a loop
+    When I retrieve the video element
+    Then I should know that it is not in a loop
+
+  Scenario: Should know if it is muted
+    When I retrieve the video element
+    Then I should know that it is muted
+