cuke_modeler 0.0.1

data/features/modeling/outline_modeling.feature

@@ -0,0 +1,100 @@
+Feature: Outline elements can be modeled.
+
+
+  Acceptance criteria
+
+    1. All conceptual pieces of an outline can be modeled:
+      - the outline's name
+      - the outline's description
+      - the outline's steps
+      - the outline's tags
+      - the outline's applied tags
+      - the outline's example blocks
+      - the outline's source line
+      - the outline's raw element
+
+    2. Outlines can be outputted in a convenient form
+
+
+  Background: Test file setup.
+    Given the following feature file:
+    """
+    @a_feature_level_tag
+    Feature:
+
+      @outline_tag
+      Scenario Outline: The scenario outline's name.
+            
+        Some outline description.
+    
+      Some more.
+          Even more.
+
+        Given a <setup> step
+        When an action step
+        Then a <verification> step
+
+      Examples: example 1
+        | setup | verification |
+        | x     | y            |
+      Examples: example 2
+        | setup | verification |
+        | a     | b            |
+    """
+    And parameter delimiters of "*" and "*"
+    When the file is read
+
+
+  Scenario: The raw outline element is modeled.
+    Then the test correctly stores its underlying implementation
+
+  Scenario: The outline source line is modeled.
+    Then the test is found to have the following properties:
+      | source_line | 5 |
+
+  Scenario: The outline name is modeled.
+    Then the test is found to have the following properties:
+      | name | The scenario outline's name. |
+
+  Scenario: The outline description is modeled.
+    Then the test has the following description:
+      """
+          
+      Some outline description.
+
+      Some more.
+        Even more.
+      """
+
+  Scenario: The outline steps are modeled.
+    Then the test steps are as follows:
+      | a <setup> step        |
+      | an action step        |
+      | a <verification> step |
+
+  Scenario: The outline tags are modeled.
+    Then the test is found to have the following tags:
+      | @outline_tag |
+
+  Scenario: The outline applied tags are modeled.
+    Then the test is found to have the following applied tags:
+      | @a_feature_level_tag |
+
+  Scenario: The outline example blocks are modeled.
+    And the test example blocks are as follows:
+      | example 1 |
+      | example 2 |
+
+  Scenario: Convenient output of an an outline
+    Then the outline has convenient output
+
+  @redundant
+  Scenario Outline: Outline models pass all other specifications
+  Exact specifications detailing the API for outline models.
+    Given that there are "<additional specifications>" detailing models
+    When the corresponding specifications are run
+    Then all of those specifications are met
+  Examples:
+    | additional specifications   |
+    | outline_unit_spec.rb        |
+    | outline_integration_spec.rb |

data/features/modeling/outline_output.feature

@@ -0,0 +1,197 @@
+Feature: Outputting outline elements
+
+  The output of an element model is a representation of the element as it would
+  appear in gherkin.
+
+
+  Scenario: Output of an outline that does not have a name
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline:
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline:
+    """
+
+  Scenario: Output of an outline that does have a name
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline: with a name
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline: with a name
+    """
+
+  Scenario: Output of an outline that does have tags
+    Given an outline element based on the following gherkin:
+    """
+    @tag1@tag2
+    @tag3
+    Scenario Outline:
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    @tag1 @tag2 @tag3
+    Scenario Outline:
+    """
+
+  Scenario: Output of an outline that has a description, no first line buffer
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline:
+    Some description.
+    Some more description.
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline:
+      
+      Some description.
+      Some more description.
+    """
+
+  Scenario: Output of an outline that has a description, first line is blank
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline:
+
+    Some description.
+    Some more description.
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline:
+      
+      Some description.
+      Some more description.
+    """
+
+  Scenario: Output of an outline that has a description, first line is only whitespace
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline:
+       
+    Some description.
+    Some more description.
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline:
+       
+      Some description.
+      Some more description.
+    """
+
+  Scenario: Output of an outline that has steps
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline:
+    * a step
+    |value|
+    * another step
+    \"\"\"
+      some string
+    \"\"\"
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline:
+      * a step
+        | value |
+      * another step
+        \"\"\"
+          some string
+        \"\"\"
+    """
+
+  Scenario: Output of an outline that has examples
+    Given an outline element based on the following gherkin:
+    """
+    Scenario Outline:
+    * a <value> step
+    Examples:
+    | value |
+    | x     |
+    @example_tag
+    Examples:
+    | value |
+    | y     |
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Scenario Outline:
+      * a <value> step
+
+    Examples:
+      | value |
+      | x     |
+
+    @example_tag
+    Examples:
+      | value |
+      | y     |
+    """
+
+  Scenario: Output of an outline that contains all possible parts
+    Given an outline element based on the following gherkin:
+    """
+    @tag1@tag2
+    @tag3
+    Scenario Outline: An outline with everything it could have
+    Some description.
+    Some more description.
+    * a step
+    |value|
+    * a <value> step
+    \"\"\"
+      some string
+    \"\"\"
+    Examples:
+    Some description.
+    Some more description.
+    | value |
+    | x     |
+    @example_tag
+    Examples:
+    | value |
+    | y     |
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    @tag1 @tag2 @tag3
+    Scenario Outline: An outline with everything it could have
+      
+      Some description.
+      Some more description.
+
+      * a step
+        | value |
+      * a <value> step
+        \"\"\"
+          some string
+        \"\"\"
+
+    Examples:
+      
+      Some description.
+      Some more description.
+
+      | value |
+      | x     |
+
+    @example_tag
+    Examples:
+      | value |
+      | y     |
+    """

data/features/modeling/row_modeling.feature

@@ -0,0 +1,77 @@
+Feature: Row elements can be modeled.
+
+
+  Acceptance criteria
+
+    1. All conceptual pieces of a Row can be modeled:
+      - the row's source line
+      - the row's cells
+      - the row's raw element
+
+    2. Rows can be outputted in a convenient form
+
+
+  Background: Test file setup.
+    Given the following feature file:
+    """
+    Feature:
+
+      Scenario Outline:
+        * a step
+      Examples:
+        | param1 | param2 | extra param |
+        | x      | y      |      ?      |
+        | 1      | 2      |      3      |
+      Examples:
+        | param1 |
+        | a      |
+    """
+    And parameter delimiters of "*" and "*"
+    When the file is read
+
+
+  Scenario: The raw row element is modeled.
+    Then the test example block row correctly stores its underlying implementation
+
+  Scenario: The row's source line is modeled.
+    Then the test example block "1" row "1" is found to have the following properties:
+      | source_line | 6 |
+    And the test example block "1" row "2" is found to have the following properties:
+      | source_line | 7 |
+    And the test example block "1" row "3" is found to have the following properties:
+      | source_line | 8 |
+    And the test example block "2" row "1" is found to have the following properties:
+      | source_line | 10 |
+    And the test example block "2" row "2" is found to have the following properties:
+      | source_line | 11 |
+
+  Scenario: The row's cells are modeled.
+    Then the test example block "1" row "1" cells are as follows:
+      | param1      |
+      | param2      |
+      | extra param |
+    And the test example block "1" row "2" cells are as follows:
+      | x |
+      | y |
+      | ? |
+    And the test example block "1" row "3" cells are as follows:
+      | 1 |
+      | 2 |
+      | 3 |
+    And the test example block "2" row "1" cells are as follows:
+      | param1 |
+    And the test example block "2" row "2" cells are as follows:
+      | a |
+
+  Scenario: Convenient output of a row
+    Then the row has convenient output
+
+  @redundant
+  Scenario Outline: Row models pass all other specifications
+  Exact specifications detailing the API for Row models.
+    Given that there are "<additional specifications>" detailing models
+    When the corresponding specifications are run
+    Then all of those specifications are met
+  Examples:
+    | additional specifications |
+    | row_unit_spec.rb          |

data/features/modeling/row_output.feature

@@ -0,0 +1,27 @@
+Feature: Outputting row elements
+
+  The output of an element model is a representation of the element as it would
+  appear in gherkin.
+
+
+  Scenario: Output of a row that has one cell
+    Given a row element based on the following gherkin:
+    """
+    |value|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    | value |
+    """
+
+  Scenario: Output of a row that has multiple cells
+    Given a row element based on the following gherkin:
+    """
+    |value|another_value|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    | value | another_value |
+    """

data/features/modeling/scenario_modeling.feature

@@ -0,0 +1,89 @@
+Feature: Scenario elements can be modeled.
+
+
+  Acceptance criteria
+
+    1. All conceptual pieces of a scenario can be modeled:
+      - the scenario's name
+      - the scenario's description
+      - the scenario's steps
+      - the scenario's tags
+      - the scenario's applied tags
+      - the scenario's source line
+      - the scenario's raw element
+
+    2. Scenarios can be outputted in a convenient form
+
+
+  Background: Test file setup.
+    Given the following feature file:
+    """
+    @a_feature_level_tag
+    Feature:
+
+      @a_tag
+      @another_tag
+      Scenario:The first scenario's name.
+            
+        Some scenario description.
+    
+      Some more.
+          Even more.
+
+        Given a setup step
+        When an action step
+        Then a verification step
+    """
+    And parameter delimiters of "*" and "*"
+    When the file is read
+
+
+  Scenario: The raw scenario element is modeled.
+    Then the test correctly stores its underlying implementation
+
+  Scenario: The scenario source line is modeled.
+    Then the test is found to have the following properties:
+      | source_line | 6 |
+
+  Scenario: The scenario name is modeled.
+    Then the test is found to have the following properties:
+      | name | The first scenario's name. |
+
+  Scenario: The scenario description is modeled.
+    Then the test has the following description:
+      """
+          
+      Some scenario description.
+
+      Some more.
+        Even more.
+      """
+
+  Scenario: The scenario steps are modeled.
+    Then the test steps are as follows:
+      | a setup step        |
+      | an action step      |
+      | a verification step |
+
+  Scenario: The scenario tags are modeled.
+    Then the test is found to have the following tags:
+      | @a_tag       |
+      | @another_tag |
+
+  Scenario: The scenario applied tags are modeled.
+    Then the test is found to have the following applied tags:
+      | @a_feature_level_tag |
+
+  Scenario: Convenient output of a scenario
+   Then the scenario has convenient output
+
+  @redundant
+  Scenario Outline: Scenario models pass all other specifications
+  Exact specifications detailing the API for scenario models.
+    Given that there are "<additional specifications>" detailing models
+    When the corresponding specifications are run
+    Then all of those specifications are met
+  Examples:
+    | additional specifications    |
+    | scenario_unit_spec.rb        |
+    | scenario_integration_spec.rb |