RubyGems - cucumber_analytics - Versions diffs - 1.4.2 → 1.5.0 - Mend

cucumber_analytics 1.4.2 → 1.5.0

Files changed (84) hide show

data/History.rdoc +7 -0
data/README.rdoc +4 -0
data/Rakefile +1 -1
data/cucumber_analytics.gemspec +3 -1
data/features/modeling/background_modeling.feature +27 -13
data/features/modeling/background_output.feature +130 -0
data/features/modeling/directory_modeling.feature +11 -6
data/features/modeling/directory_output.feature +13 -0
data/features/modeling/doc_string_modeling.feature +18 -11
data/features/modeling/doc_string_output.feature +71 -0
data/features/modeling/example_modeling.feature +30 -19
data/features/modeling/example_output.feature +192 -0
data/features/modeling/feature_file_modeling.feature +9 -4
data/features/modeling/feature_file_output.feature +13 -0
data/features/modeling/feature_modeling.feature +33 -20
data/features/modeling/feature_output.feature +244 -0
data/features/modeling/outline_modeling.feature +29 -16
data/features/modeling/outline_output.feature +197 -0
data/features/modeling/row_modeling.feature +9 -4
data/features/modeling/row_output.feature +27 -0
data/features/modeling/scenario_modeling.feature +27 -14
data/features/modeling/scenario_output.feature +147 -0
data/features/modeling/step_modeling.feature +13 -8
data/features/modeling/step_output.feature +52 -0
data/features/modeling/table_modeling.feature +9 -4
data/features/modeling/table_output.feature +42 -0
data/features/modeling/table_row_modeling.feature +9 -4
data/features/modeling/table_row_output.feature +27 -0
data/features/modeling/tag_modeling.feature +10 -5
data/features/modeling/tag_output.feature +16 -0
data/features/step_definitions/action_steps.rb +3 -0
data/features/step_definitions/background_steps.rb +17 -4
data/features/step_definitions/directory_steps.rb +11 -0
data/features/step_definitions/doc_string_steps.rb +18 -15
data/features/step_definitions/feature_file_steps.rb +12 -1
data/features/step_definitions/feature_steps.rb +23 -6
data/features/step_definitions/outline_steps.rb +70 -9
data/features/step_definitions/step_steps.rb +9 -1
data/features/step_definitions/table_steps.rb +35 -2
data/features/step_definitions/tag_steps.rb +8 -0
data/features/step_definitions/test_steps.rb +14 -3
data/features/step_definitions/verification_steps.rb +9 -0
data/features/support/env.rb +1 -0
data/lib/cucumber_analytics/background.rb +12 -0
data/lib/cucumber_analytics/directory.rb +5 -0
data/lib/cucumber_analytics/doc_string.rb +22 -0
data/lib/cucumber_analytics/example.rb +55 -0
data/lib/cucumber_analytics/feature.rb +26 -0
data/lib/cucumber_analytics/feature_element.rb +25 -1
data/lib/cucumber_analytics/feature_file.rb +5 -0
data/lib/cucumber_analytics/outline.rb +18 -0
data/lib/cucumber_analytics/parsing.rb +3 -1
data/lib/cucumber_analytics/row.rb +5 -0
data/lib/cucumber_analytics/scenario.rb +13 -0
data/lib/cucumber_analytics/step.rb +8 -0
data/lib/cucumber_analytics/table.rb +21 -0
data/lib/cucumber_analytics/table_row.rb +5 -0
data/lib/cucumber_analytics/tag.rb +5 -0
data/lib/cucumber_analytics/taggable.rb +4 -0
data/lib/cucumber_analytics/test_element.rb +8 -0
data/lib/cucumber_analytics/version.rb +1 -1
data/spec/integration/background_integration_spec.rb +12 -0
data/spec/integration/example_integration_spec.rb +21 -0
data/spec/integration/feature_integration_spec.rb +29 -0
data/spec/integration/outline_integration_spec.rb +22 -0
data/spec/integration/scenario_integration_spec.rb +16 -0
data/spec/integration/step_integration_spec.rb +20 -0
data/spec/integration/table_integration_spec.rb +11 -0
data/spec/unit/background_unit_spec.rb +28 -0
data/spec/unit/directory_unit_spec.rb +12 -0
data/spec/unit/doc_string_unit_spec.rb +43 -3
data/spec/unit/example_unit_spec.rb +53 -0
data/spec/unit/feature_element_unit_specs.rb +9 -2
data/spec/unit/feature_file_unit_spec.rb +12 -0
data/spec/unit/feature_unit_spec.rb +30 -0
data/spec/unit/outline_unit_spec.rb +30 -0
data/spec/unit/row_unit_spec.rb +19 -7
data/spec/unit/scenario_unit_spec.rb +30 -0
data/spec/unit/step_unit_spec.rb +25 -1
data/spec/unit/table_row_unit_spec.rb +12 -0
data/spec/unit/table_unit_spec.rb +25 -0
data/spec/unit/tag_unit_spec.rb +12 -0
metadata +165 -86
checksums.yaml +0 -15

data/features/modeling/outline_modeling.feature CHANGED

@@ -1,17 +1,19 @@
-Feature: Scenario Outline elements can be modeled.
+Feature: Outline elements can be modeled.
   Acceptance criteria
-  All conceptual pieces of a Scenario Outline can be modeled:
-    1. the outline's name
-    2. the outline's description
-    3. the outline's steps
-    4. the outline's tags
-    5. the outline's applied tags
-    6. the outline's example blocks
-    7. the outline's source line
-    8. the outline's raw element
+    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.
@@ -22,8 +24,11 @@ Feature: Scenario Outline elements can be modeled.
       @outline_tag
       Scenario Outline: The scenario outline's name.
-          Some outline description
-          Some more description
+        Some outline description.
+      Some more.
+          Even more.
         Given a <setup> step
         When an action step
@@ -52,9 +57,14 @@ Feature: Scenario Outline elements can be modeled.
       | name | The scenario outline's name. |
   Scenario: The outline description is modeled.
-    Then the test descriptive lines are as follows:
-      | Some outline description |
-      | Some more description    |
+    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:
@@ -75,8 +85,11 @@ Feature: Scenario Outline elements can be modeled.
       | example 1 |
       | example 2 |
+  Scenario: Convenient output of an an outline
+    Then the outline has convenient output
   Scenario Outline: Outline models pass all other specifications
-  Exact specifications detailing the API for Scenario Outline models.
+  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

data/features/modeling/outline_output.feature ADDED

@@ -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 CHANGED

@@ -3,10 +3,12 @@ Feature: Row elements can be modeled.
   Acceptance criteria
-  All conceptual pieces of a Row can be modeled:
-  1. the row's source line
-  2. the row's cells
-  3. the row's raw element
+    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.
@@ -61,6 +63,9 @@ Feature: Row elements can be modeled.
     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
   Scenario Outline: Row models pass all other specifications
   Exact specifications detailing the API for Row models.
     Given that there are "<additional specifications>" detailing models

data/features/modeling/row_output.feature ADDED

@@ -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 CHANGED

@@ -3,14 +3,16 @@ Feature: Scenario elements can be modeled.
   Acceptance criteria
-  All conceptual pieces of a Scenario can be modeled:
-    1. the scenario's name
-    2. the scenario's description
-    3. the scenario's steps
-    4. the scenario's tags
-    5. the scenario's applied tags
-    6. the scenario's source line
-    7. the scenario's raw element
+    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.
@@ -22,8 +24,11 @@ Feature: Scenario elements can be modeled.
       @a_tag
       @another_tag
       Scenario:The first scenario's name.
-          Some scenario description
-          Some more description
+        Some scenario description.
+      Some more.
+          Even more.
         Given a setup step
         When an action step
@@ -45,9 +50,14 @@ Feature: Scenario elements can be modeled.
       | name | The first scenario's name. |
   Scenario: The scenario description is modeled.
-    Then the test descriptive lines are as follows:
-      | Some scenario description |
-      | Some more description     |
+    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:
@@ -64,8 +74,11 @@ Feature: Scenario elements can be 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
   Scenario Outline: Scenario models pass all other specifications
-  Exact specifications detailing the API for Scenario models.
+  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

data/features/modeling/scenario_output.feature ADDED

@@ -0,0 +1,147 @@
+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
+        \"\"\"
+    """