cuke_modeler 0.4.1 → 1.0.0

data/features/modeling/gherkin3/directory_output.feature

@@ -1,14 +0,0 @@
-@gherkin3
-Feature: Outputting directory elements
-
-  The output of an element model is a representation of the element as it would
-  appear in gherkin.
-
-
-  Scenario: Output of a directory
-    Given a directory element based on "some_directory"
-    When it is outputted
-    Then the following text is provided:
-    """
-    path_to/some_directory
-    """

data/features/modeling/gherkin3/doc_string_modeling.feature

@@ -1,53 +0,0 @@
-@gherkin3
-Feature: Doc string elements can be modeled.
-
-
-  Acceptance criteria
-
-    1. All conceptual pieces of a doc string can be modeled:
-      - the doc string's content type
-      - the doc string's contents
-      - the doc string's raw element
-
-    2. Doc string can be outputted in a convenient form
-
-
-  Background: Test file setup.
-    Given the following feature file:
-    """
-    Feature:
-
-      Scenario:
-        * some wordy step:
-        \"\"\" content type
-      some text
-          
-            some more text
-        
-        \"\"\"
-        * some wordy step:
-        \"\"\"
-        \"\"\"
-    """
-    When the file is read
-
-
-  Scenario: The raw doc string element is modeled.
-    Then the doc string correctly stores its underlying implementation
-
-  Scenario: The doc string's content type is modeled.
-    Then the step "1" doc string content type is "content type"
-    And the step "2" doc string has no content type
-
-  Scenario: The doc string's contents are modeled.
-    Then the step "1" doc string has the following contents:
-      """
-      some text
-        
-          some more text
-      
-      """
-    And the step "2" doc string contents are empty
-
-  Scenario: Convenient output of an a doc string
-    Then the doc string has convenient output

data/features/modeling/gherkin3/doc_string_output.feature

@@ -1,72 +0,0 @@
-@gherkin3
-Feature: Outputting doc string elements
-
-  The output of an element model is a representation of the element as it would
-  appear in gherkin.
-
-
-  Scenario: Output of an empty doc string
-    Given a doc string element based on the following gherkin:
-    """
-    \"\"\"
-    \"\"\"
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    \"\"\"
-    \"\"\"
-    """
-
-  Scenario: Output of a doc string without a content type
-    Given a doc string element based on the following gherkin:
-    """
-    \"\"\"
-    Some text
-      
-      some more text
-    
-    \"\"\"
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    \"\"\"
-    Some text
-      
-      some more text
-    
-    \"\"\"
-    """
-
-  Scenario: Output of a doc string with a content type
-    Given a doc string element based on the following gherkin:
-    """
-    \"\"\" the type
-    Some text
-      
-      some more text
-    
-    \"\"\"
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    \"\"\" the type
-    Some text
-      
-      some more text
-    
-    \"\"\"
-    """
-
-  Scenario: Output of a doc string with a triple quotes in its contents
-
-    Since triple quotes mark the beginning and end of a doc string, any triple
-    quotes inside of the doc string (which would have had to have been escaped
-    to get inside in the first place) will be escaped when outputted so as to
-    retain the quality of being able to use the output directly as gherkin.
-
-    Given a doc string element based on the string """" the type\n* a step\n  \"\"\"\n  that also has a doc string\n  \"\"\"\n""""
-    When it is outputted
-    Then the text provided is """" the type\n* a step\n  \"\"\"\n  that also has a doc string\n  \"\"\"\n""""

data/features/modeling/gherkin3/example_modeling.feature

@@ -1,100 +0,0 @@
-@gherkin3
-Feature: Example elements can be modeled.
-
-
-  Acceptance criteria
-
-    1. All conceptual pieces of an example block can be modeled:
-      - the example's name
-      - the example's description
-      - the example's parameters
-      - the example's rows
-      - the example's tags
-      - the example's applied tags
-      - the example's source line
-      - the example's raw element
-
-    2. Example blocks 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:
-        * a step
-
-      Examples: text describing the significance of the examples
-
-        Some example description.
-
-      Some more.
-          Even more.
-        |param1| param2 | extra param |
-        |x     | y      |      ?      |
-        |1     | 2      |      3      |
-      @example_tag @another_one
-      Examples: some examples with different significance and a tag
-        | param1 |
-        | a      |
-    """
-    And parameter delimiters of "*" and "*"
-    When the file is read
-
-
-  Scenario: The raw example element is modeled.
-    Then the test example block correctly stores its underlying implementation
-
-  Scenario: The example's source line is modeled.
-    Then the test example block "1" is found to have the following properties:
-      | source_line | 8 |
-    And the test example block "2" is found to have the following properties:
-      | source_line | 18 |
-
-  Scenario: The examples' name is modeled.
-    Then the test example block "1" is found to have the following properties:
-      | name | text describing the significance of the examples |
-    And the test example block "2" is found to have the following properties:
-      | name | some examples with different significance and a tag |
-
-  Scenario: The examples' description is modeled.
-    Then the test example block "1" has the following description:
-      """
-          Some example description.
-  
-        Some more.
-            Even more.
-      """
-    And the test example block "2" has no description
-
-  Scenario: The examples' tags are modeled.
-    Then the test example block "1" has no tags
-    And the test example block "2" is found to have the following tags:
-      | @example_tag |
-      | @another_one |
-
-  Scenario: The examples' applied tags are modeled.
-    Then the test example block "2" is found to have the following applied tags:
-      | @a_feature_level_tag |
-      | @outline_tag         |
-
-  Scenario: The examples' parameters are modeled.
-    Then the test example block "1" parameters are as follows:
-      | param1      |
-      | param2      |
-      | extra param |
-    And the test example block "2" parameters are as follows:
-      | param1 |
-
-  Scenario: The examples' rows are modeled.
-    Then the test example block "1" rows are as follows:
-      | x,y,? |
-      | 1,2,3 |
-    And the test example block "2" rows are as follows:
-      | a |
-
-  Scenario: Convenient output of an example block
-    Then the example block has convenient output

data/features/modeling/gherkin3/example_output.feature

@@ -1,207 +0,0 @@
-@gherkin3
-Feature: Outputting example elements
-
-  The output of an element model is a representation of the element as it would
-  appear in gherkin.
-
-
-  Scenario: Output of an example that does not have a name
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that does have a name
-    Given an example element based on the following gherkin:
-    """
-    Examples: with a name
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples: with a name
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that does not have tags
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that does have tags
-    Given an example element based on the following gherkin:
-    """
-    @tag1@tag2
-    @tag3
-    Examples:
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    @tag1 @tag2 @tag3
-    Examples:
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that has a description, no first line buffer
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-    Some description.
-    Some more description.
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      
-      Some description.
-      Some more description.
-
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that has a description, first line is blank
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-
-    Some description.
-    Some more description.
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      
-      Some description.
-      Some more description.
-
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that has a description, first line is only whitespace
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-       
-    Some description.
-    Some more description.
-    |param|
-    |value|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      
-      Some description.
-      Some more description.
-
-      | param |
-      | value |
-    """
-
-  Scenario: Output of an example that has one rows
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-    |param1|param2|
-    |value1|value2|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      | param1 | param2 |
-      | value1 | value2 |
-    """
-
-  Scenario: Output of an example that has multiple rows
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-    |param1|param2|
-    |value1|value2|
-    |value3|value4|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      | param1 | param2 |
-      | value1 | value2 |
-      | value3 | value4 |
-    """
-
-  Scenario: Output of an example that contains all possible parts
-    Given an example element based on the following gherkin:
-    """
-    @tag1@tag2
-    @tag3
-    Examples: with a name
-    Some description.
-    Some more description.
-    |param1|param2|
-    |value1|value2|
-    |value3|value4|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    @tag1 @tag2 @tag3
-    Examples: with a name
-      
-      Some description.
-      Some more description.
-
-      | param1 | param2 |
-      | value1 | value2 |
-      | value3 | value4 |
-    """
-
-  Scenario: Whitespace buffers are based on the longest value or parameter in a column
-    Given an example element based on the following gherkin:
-    """
-    Examples:
-    |parameter_name|x|
-    |y|value_name|
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    Examples:
-      | parameter_name | x          |
-      | y              | value_name |
-    """