cuke_modeler 0.0.2 → 0.1.0

data/features/modeling/gherkin3/row_modeling.feature

@@ -0,0 +1,68 @@
+@gherkin3
+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

data/features/modeling/gherkin3/row_output.feature

@@ -0,0 +1,28 @@
+@gherkin3
+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/gherkin3/scenario_modeling.feature

@@ -0,0 +1,78 @@
+@gherkin3
+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

data/features/modeling/gherkin3/scenario_output.feature

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

data/features/modeling/gherkin3/step_modeling.feature

@@ -0,0 +1,75 @@
+@gherkin3
+Feature: Step elements can be modeled.
+
+
+  Acceptance criteria
+
+    1. All conceptual pieces of a step can be modeled:
+      - the step's keyword
+      - the text of the step
+      - the step's arguments, if any
+      - the step's associated block, if any
+      - the step's source line
+      - the step's raw element
+
+    2. Steps can be outputted in a convenient form
+
+
+  Background: Test file setup.
+    Given the following feature file:
+    """
+    Feature:
+
+      Scenario:
+        Given some setup step
+        And some big setup step:
+        \"\"\" content_type
+      some text
+            some more text
+        \"\"\"
+        When this *parameterized* step takes a table:
+          | data      | a header |
+          | more data | a value  |
+        Then a step with a *parameter*
+    """
+    And parameter delimiters of "*" and "*"
+    When the file is read
+
+
+  Scenario: The raw step element is modeled.
+    Then the test step correctly stores its underlying implementation
+
+  Scenario: The step's source line is modeled.
+    Then the test step "1" source line is "4"
+    And  the test step "2" source line is "5"
+    And  the test step "3" source line is "10"
+    And  the test step "4" source line is "13"
+
+  Scenario: The step's keyword is modeled.
+    Then the test step "1" keyword is "Given"
+    And the test step "2" keyword is "And"
+    And the test step "3" keyword is "When"
+    And the test step "4" keyword is "Then"
+
+  Scenario: The text of the step is modeled.
+    Then test step "1" text is "some setup step"
+    And test step "2" text is "some big setup step:"
+    And test step "3" text is "this *parameterized* step takes a table:"
+    And test step "4" text is "a step with a *parameter*"
+
+  Scenario: The step's arguments are modeled.
+    Then test step "1" has no arguments
+    And test step "2" has no arguments
+    And test step "3" arguments are:
+      | parameterized |
+    And test step "4" arguments are:
+      | parameter |
+
+  Scenario: The steps's block is modeled.
+    Then step "1" has no block
+    Then step "2" has a "doc string"
+    And step "3" has a "table"
+    And step "4" has no block
+
+  Scenario: Convenient output of a step
+    Then the step has convenient output

data/features/modeling/gherkin3/step_output.feature

@@ -0,0 +1,53 @@
+@gherkin3
+Feature: Outputting step elements
+
+  The output of an element model is a representation of the element as it would
+  appear in gherkin.
+
+
+  Scenario: Output of a step without a block
+    Given a step element based on the following gherkin:
+    """
+    * a step
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    * a step
+    """
+
+  Scenario: Output of a step with a doc string
+    Given a step element based on the following gherkin:
+    """
+    * a step
+    \"\"\"
+    Some text
+
+      some more text
+    \"\"\"
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    * a step
+      \"\"\"
+      Some text
+      
+        some more text
+      \"\"\"
+    """
+
+  Scenario: Output of a step with a table
+    Given a step element based on the following gherkin:
+    """
+    * a step
+    |value1|
+    |value2|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    * a step
+      | value1 |
+      | value2 |
+    """