cucumber_analytics 1.4.2 → 1.5.0

data/features/modeling/example_output.feature

@@ -0,0 +1,192 @@
+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|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Examples:
+      | param |
+    """
+
+  Scenario: Output of an example that does have a name
+    Given an example element based on the following gherkin:
+    """
+    Examples: with a name
+    |param|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Examples: with a name
+      | param |
+    """
+
+  Scenario: Output of an example that does not have tags
+    Given an example element based on the following gherkin:
+    """
+    Examples:
+    |param|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Examples:
+      | param |
+    """
+
+  Scenario: Output of an example that does have tags
+    Given an example element based on the following gherkin:
+    """
+    @tag1@tag2
+    @tag3
+    Examples:
+    |param|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    @tag1 @tag2 @tag3
+    Examples:
+      | param |
+    """
+
+  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|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Examples:
+      
+      Some description.
+      Some more description.
+
+      | param |
+    """
+
+  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|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Examples:
+      
+      Some description.
+      Some more description.
+
+      | param |
+    """
+
+  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|
+    """
+    When it is outputted
+    Then the following text is provided:
+    """
+    Examples:
+       
+      Some description.
+      Some more description.
+
+      | param |
+    """
+
+  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 |
+    """

data/features/modeling/feature_file_modeling.feature

@@ -3,10 +3,12 @@ Feature: Feature files can be modeled.
 
   Acceptance criteria
 
-  All conceptual pieces of a .feature file can be modeled:
-    1. the files's name
-    2. the file's full path
-    3. the file's features (one or zero per file)
+    1. All conceptual pieces of a .feature file can be modeled:
+      - the file's name
+      - the file's full path
+      - the file's features (one or zero per file)
+
+    2. Feature files can be outputted in a convenient form
 
 
   Background: Test file setup.
@@ -47,6 +49,9 @@ Feature: Feature files can be modeled.
       | feature_count | 0                                                |
     And file "3" has no features
 
+  Scenario: Convenient output of a feature file
+    Then the feature file has convenient output
+
   Scenario Outline: Feature file models pass all other specifications
   Exact specifications detailing the API for .feature file models.
     Given that there are "<additional specifications>" detailing models

data/features/modeling/feature_file_output.feature

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

data/features/modeling/feature_modeling.feature

@@ -3,17 +3,19 @@ Feature: Features can be modeled.
 
   Acceptance criteria
 
-  All conceptual pieces of a Feature can be modeled:
-    1.  the feature's name
-    2.  the feature's description
-    3.  the feature's tags
-    4.  the feature's scenarios
-    5.  the feature's outlines
-    6.  the feature's background
-    7.  the feature's total number of tests
-    8.  the feature's total number of test cases
-    9.  the feature's source line
-    10. the feature's raw element
+    1. All conceptual pieces of a feature can be modeled:
+      -  the feature's name
+      -  the feature's description
+      -  the feature's tags
+      -  the feature's scenarios
+      -  the feature's outlines
+      -  the feature's background
+      -  the feature's total number of tests
+      -  the feature's total number of test cases
+      -  the feature's source line
+      - the feature's raw element
+
+    2. Features can be outputted in a convenient form
 
 
   Background: Test file setup.
@@ -21,11 +23,14 @@ Feature: Features can be modeled.
     """
     @a_feature_level_tag @and_another
 
-     Feature:The test feature name.
+    Feature: The test feature name.
+          
       Some feature description.
-      And some more.
 
-      Background:Some general test setup stuff.
+    Some more.
+        And some more.
+
+      Background: Some general test setup stuff.
         * some setup step
 
       Scenario: The first scenario's name.
@@ -86,11 +91,16 @@ Feature: Features can be modeled.
       | source_line     | 1 |
 
   Scenario: The feature's description is modeled.
-    Then the descriptive lines of feature "1" are as follows:
-      | Some feature description. |
-      | And some more.            |
-    And feature "2" has no descriptive lines
-    And feature "3" has no descriptive lines
+    Then feature "1" has the following description:
+      """
+          
+      Some feature description.
+
+      Some more.
+        And some more.
+      """
+    And feature "2" has no description
+    And feature "3" has no description
 
   Scenario: The feature's tags are modeled.
     Then feature "1" is found to have the following tags:
@@ -139,8 +149,11 @@ Feature: Features can be modeled.
       | has_background? | false |
     And feature "3" has no background
 
+  Scenario: Convenient output of a feature
+    Then the feature has convenient output
+
   Scenario Outline: Feature models pass all other specifications
-  Exact specifications detailing the API for Feature models.
+  Exact specifications detailing the API for feature models.
     Given that there are "<additional specifications>" detailing models
     When the corresponding specifications are run
     Then all of those specifications are met

data/features/modeling/feature_output.feature

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