cuke_modeler 0.4.1 → 1.0.0

data/features/modeling/gherkin3/tag_modeling.feature

@@ -1,49 +0,0 @@
-@gherkin3
-Feature: Tag elements can be modeled.
-
-
-  Acceptance criteria
-
-    1. All conceptual pieces of a tag can be modeled:
-      - the tag's name
-      - the tags's source line
-      - the tags's raw element
-
-    2. Features can be outputted in a convenient form
-
-
-  Background: Test file setup.
-    Given the following feature file:
-    """
-    @feature_tag
-    Feature:
-
-      @outline_tag
-      Scenario Outline:
-        * a step
-
-      @example_tag
-      Examples:
-        | a param |
-        | a value |
-    """
-    When the file is read
-
-
-  Scenario: The raw tag element is modeled.
-    Then the feature tag correctly stores its underlying implementation
-    And the test tag correctly stores its underlying implementation
-    And the example tag correctly stores its underlying implementation
-
-  Scenario: The tag's source line is modeled.
-    Then the feature tag source line "1"
-    And the test tag source line "4"
-    And the example tag source line "8"
-
-  Scenario: The tag name is modeled.
-    Then the feature tag name is "@feature_tag"
-    And the test tag name is "@outline_tag"
-    And the example tag name is "@example_tag"
-
-  Scenario: Convenient output of a tag
-    Then the tag has convenient output

data/features/modeling/gherkin3/tag_output.feature

@@ -1,17 +0,0 @@
-@gherkin3
-Feature: Outputting tag elements
-
-  The output of an element model is a representation of the element as it would
-  appear in gherkin.
-
-
-  Scenario: Output of a tag that has a name
-    Given a tag element based on the following gherkin:
-    """
-    @some_tag
-    """
-    When it is outputted
-    Then the following text is provided:
-    """
-    @some_tag
-    """

data/features/modeling/gherkin4/background_modeling.feature

@@ -1,64 +0,0 @@
-@gherkin4
-Feature: Background elements can be modeled.
-
-
-  Acceptance criteria
-
-  1. All conceptual pieces of a background can be modeled:
-  - the background's name
-  - the background's description
-  - the background's steps
-  - the background's source line
-  - the background's raw element
-
-  2. Backgrounds can be outputted in a convenient form
-
-
-  Background: Test file setup.
-    Given the following feature file:
-    """
-    Feature:
-
-      Background: Some general test setup stuff.
-            
-        Some background description.
-    
-      Some more.
-          Even more.
-
-        Given a setup step
-        And another setup step
-        When an action step
-    """
-    And parameter delimiters of "*" and "*"
-    When the file is read
-
-
-  Scenario: The raw background element is modeled.
-    Then the background correctly stores its underlying implementation
-
-  Scenario: The background source line is modeled.
-    Then the background is found to have the following properties:
-      | source_line | 3 |
-
-  Scenario: The background name is modeled.
-    Then the background is found to have the following properties:
-      | name | Some general test setup stuff. |
-
-  Scenario: The background description is modeled.
-    Then the background has the following description:
-      """
-          Some background description.
-
-        Some more.
-            Even more.
-      """
-
-  Scenario: The background steps are modeled.
-    Then the background's steps are as follows:
-      | a setup step       |
-      | another setup step |
-      | an action step     |
-
-  Scenario: Convenient output of a background
-    Then the background has convenient output

data/features/modeling/gherkin4/background_output.feature

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

data/features/modeling/gherkin4/directory_modeling.feature

@@ -1,110 +0,0 @@
-@gherkin4
-Feature: Directories can be modeled.
-
-
-  Acceptance criteria
-
-  1. Directories containing feature files can be modeled:
-  - the directory's name
-  - the directory's full path
-  - all feature files contained
-  - all directories contained
-
-  2. Directories can be outputted in a convenient form
-
-
-  Background: Setup test directories
-    Given a directory "feature_directory"
-    And the following feature file "test_file_1.feature":
-    """
-    Feature: The test feature 1.
-
-      Scenario: The first scenario's name.
-        Given the first step
-        When the second step
-        Then the third step
-    """
-    And the following feature file "test_file_2.feature":
-    """
-    Feature: The test feature 2.
-
-      Scenario: The first scenario's name.
-        Given the first step
-        When the second step
-        Then the third step
-    """
-    And the following feature file "test_file_3.feature":
-    """
-    Feature: The test feature 3.
-
-      Scenario: The first scenario's name.
-        Given the first step
-        When the second step
-        Then the third step
-    """
-    And the following file "random.file":
-    """
-    Not a .feature file.
-    """
-    Given a directory "feature_directory/nested_directory"
-    And the following feature file "test_file_4.feature":
-    """
-    Feature: The test feature 1.
-
-      Scenario: The first scenario's name.
-        Given the first step
-        When the second step
-        Then the third step
-    """
-    And the following feature file "test_file_5.feature":
-    """
-    Feature: The test feature 2.
-
-      Scenario: The first scenario's name.
-        Given the first step
-        When the second step
-        Then the third step
-    """
-    And the following file "another_random.file":
-    """
-    Not a .feature file.
-    """
-    When the directory "feature_directory" is read
-    And the directory "feature_directory/nested_directory" is read
-
-  Scenario: The directory's name is modeled.
-    Then directory "1" is found to have the following properties:
-      | name | feature_directory |
-    And directory "2" is found to have the following properties:
-      | name | nested_directory |
-
-  Scenario: The directory's full path is modeled.
-    Then directory "1" is found to have the following properties:
-      | path | path_to/feature_directory |
-    And directory "2" is found to have the following properties:
-      | path | path_to/feature_directory/nested_directory |
-
-  Scenario: The directory's feature files are modeled.
-    Then directory "1" is found to have the following properties:
-      | feature_file_count | 3 |
-    And directory "1" feature files are as follows:
-      | test_file_1.feature |
-      | test_file_2.feature |
-      | test_file_3.feature |
-    Then directory "2" is found to have the following properties:
-      | feature_file_count | 2 |
-    And directory "2" feature files are as follows:
-      | test_file_4.feature |
-      | test_file_5.feature |
-
-  Scenario: The directory's directories are modeled.
-    Then directory "1" is found to have the following properties:
-      | directory_count | 1 |
-    And directory "1" directories are as follows:
-      | nested_directory |
-    Then directory "2" is found to have the following properties:
-      | directory_count | 0 |
-    And directory "2" has no directories
-
-  Scenario: Convenient output of a directory
-    Then the directory has convenient output

data/features/modeling/gherkin4/directory_output.feature

@@ -1,14 +0,0 @@
-@gherkin4
-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/gherkin4/doc_string_modeling.feature

@@ -1,53 +0,0 @@
-@gherkin4
-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