cucumber_analytics 1.1.1 → 1.2.0

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NTZmMTk1NmM2NDY0M2RlMGUyMjhlOTIyMjQ0MzlhOTliYzU5ZGNmNw==
+    MTM1OWIzMGY3Yjk5MTY5ZGUxZmM1ODFlNjJmMTlkZjM2MGNlOTljZA==
   data.tar.gz: !binary |-
-    NGVkYTM0YzUxZDFjYWI5OGE3OTMzZDViYzQyYmZjMWQyYjg5MDhjYQ==
+    OGIxYzY2MWNjMTk2NzMyNjJlMzU2NjgxZjVlNWVlMmQyNDg3NDRiMQ==
 !binary "U0hBNTEy":
   metadata.gz: !binary |-
-    Nzg4NTJkMWYxOTE4ZGFkMTJmMDIxYmU3ZmIxZTVhY2VkNmI2YWM5MDVlZjBl
-    ZDdiZjFmNjViNDFkY2Q1Yzk4MGE5NDYwMzRmNmE0OWQ3MTc5ZGJiNzEyNDE1
-    MzZjYWVkZTNlY2UyMzJhM2QyMTMyZjNhZmQ1NGNhOGM5ZThlYTI=
+    NGU1ZDU5NDc0NDVkNjAxNmNjZWZmM2RiODE2YzhiNmMyNjE5NGRiMjhjYjQ1
+    YjkwMmJkZWYzMjBmNzUwZTg5ZmE0NmZkMTQ3MGUzZjVmYWRjNDk5MTk3NDUx
+    OWZiNDgxNjU2ZDI0MmJiNjczMmE2OGFmZGI4ZWU1YzkwOTUyYTM=
   data.tar.gz: !binary |-
-    OTc0MzBmOGFmYTE1YTM2NzkyNTg0NTI1YWY0NGM5M2EwOTgyNGE2N2FiMzhk
-    ZTE3NDJmMWM2YmRhZDNjNzE5NjYyY2UxNTQ2NDY5Y2YyZDk3YzU1ZDM4YmMx
-    ZThmM2JiNTYyNjdlNWMyOTllY2NhYzU5N2VjOGEzMzIyZDJhNDc=
+    NjgzZTRiYzU1N2M1ZjIxZWQ2OTJiN2I1MzZlMTNkZjE4YjA5ZjM0NDUxNDRk
+    NmFhYTExNTE4MzYzNTJkNGQ4NGQxZjExYjMzMzZiNjRmZWJlY2NhNThjOTY0
+    YmMzYzRmMThlMTY0YjhkNjczOTk3NjM5MTA1ZWVmYTU5Y2Q4ZDM=

data/.simplecov

@@ -1,4 +1,8 @@
 SimpleCov.start do
   root File.dirname(__FILE__)
-  merge_timeout 60
+
+  add_filter '/features/'
+  add_filter '/spec/'
+
+  merge_timeout 300
 end

data/History.rdoc

@@ -1,7 +1,18 @@
-=== Version 1.1.0 / 2013-08-03
+=== Version 1.2.0 / 2013-09-01
+
+* Bug fix: nil no longer shows up as a child element of a Feature if the Feature
+  does not have a Background object.
+* Elements now have access to their original parsed structure as returned by the
+  gherkin gem.
+* Tags are now modeled. Non-object tags are still the default in order to remain
+  backwards compatible.
+
+
+=== Version 1.1.1 / 2013-08-03
 
 * Version bumped due to publishing wrong code for version 1.1.0.
 
+
 === Version 1.1.0 / 2013-08-01
 
 * Outline example rows are now modeled.
@@ -37,7 +48,7 @@
   equivalents.
 * Bug fix: Fixed some parsing bugs based around whitespace.
 * Subdirectories within a directory are now modeled.
-* Directory collection added
+* Directory collection added.
 
 
 === Version 0.0.7 / 2013-02-01
@@ -63,21 +74,21 @@
 
 === Version 0.0.4 / 2012-12-13
 
-* Removed an unintentional gem dependency
+* Removed an unintentional gem dependency.
 * Improved 1.8.7 compatibility.
 
 
 === Version 0.0.3 / 2012-11-10
 
 * 'But' has been added to the list of recognized step keywords (formerly Given,
-When,Then, And, and *)
+When,Then, And, and *).
 * Bug fix: the number of test cases a feature is considered to contain now
 properly takes into account an outline's example rows.
 
 
 === Version 0.0.2 / 2012-11-01
 
-* Bug fix: descriptions are no longer cut short due to the presence of keywords
+* Bug fix: descriptions are no longer cut short due to the presence of keywords.
 
 
 === Version 0.0.1 / 2012-10-28

data/README.rdoc

@@ -67,6 +67,11 @@ also discovered that our team is creating several redundant steps that could be
 rewritten into a single, reusable step.
 
 
+===Other usages
+
+https://gist.github.com/enkessler/6408879 - Creating a step lexicon
+
+
 == Contributing
 
 1. Fork it

data/Rakefile

@@ -3,6 +3,11 @@ require "bundler/gem_tasks"
 require 'cucumber/rake/task'
 require 'rspec/core/rake_task'
 
+task :clear_coverage do
+  code_coverage_directory = "#{File.dirname(__FILE__)}/coverage"
+
+  FileUtils.remove_dir(code_coverage_directory, true)
+end
 
 desc 'Run all acceptance tests for the gem'
 Cucumber::Rake::Task.new(:tests)
@@ -11,7 +16,7 @@ desc 'Run all API specifications for the gem'
 RSpec::Core::RakeTask.new(:specs)
 
 desc 'Run All The Things'
-task :everything do
+task :everything => :clear_coverage do
   Rake::Task[:specs].invoke
   Rake::Task[:tests].invoke
 end

data/features/modeling/background_modeling.feature

@@ -8,6 +8,7 @@ Feature: Background elements can be modeled.
     2. the background's description
     3. the background's steps
     4. the background's source line
+    5. the background's raw element
 
   Background: Test file setup.
     Given the following feature file:
@@ -26,6 +27,9 @@ Feature: Background elements can be modeled.
     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 |
@@ -48,7 +52,7 @@ Feature: Background elements can be modeled.
   Scenario Outline: Background models pass all other specifications
   Exact specifications detailing the API for Background models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications      |

data/features/modeling/directory_modeling.feature

@@ -106,7 +106,7 @@ Feature: Directories can be modeled.
   Scenario Outline: Directory models pass all other specifications
   Exact specifications detailing the API for directory models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications     |

data/features/modeling/doc_string_modeling.feature

@@ -6,6 +6,7 @@ Feature: Doc String elements can be modeled.
   All conceptual pieces of a Doc String can be modeled:
     1. the doc string's content type
     2. the doc string's contents
+    3. the doc string's raw element
 
 
   Background: Test file setup.
@@ -26,6 +27,9 @@ Feature: Doc String elements can be modeled.
     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
@@ -39,7 +43,7 @@ Feature: Doc String elements can be modeled.
   Scenario Outline: Doc String models pass all other specifications
   Exact specifications detailing the API for Doc String models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications |

data/features/modeling/example_modeling.feature

@@ -11,6 +11,7 @@ Feature: Example elements can be modeled.
     5. the example's tags
     6. the example's applied tags
     7. the example's source line
+    8. the example's raw element
 
 
   Background: Test file setup.
@@ -39,6 +40,9 @@ Feature: Example elements can be modeled.
     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 |
@@ -87,7 +91,7 @@ Feature: Example elements can be modeled.
   Scenario Outline: Example models pass all other specifications
   Exact specifications detailing the API for Examples models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications   |

data/features/modeling/feature_file_modeling.feature

@@ -50,7 +50,7 @@ Feature: Feature files can be modeled.
   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
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications        |

data/features/modeling/feature_modeling.feature

@@ -4,15 +4,17 @@ 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
+    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
+
 
   Background: Test file setup.
     Given the following feature file "much_stuff.feature":
@@ -62,6 +64,9 @@ Feature: Features can be modeled.
     And the file "as_empty_as_it_gets.feature" is read
 
 
+  Scenario: The raw feature element is modeled.
+    Then the feature correctly stores its underlying implementation
+
   Scenario: The feature's properties are modeled.
     Then feature "1" is found to have the following properties:
       | name            | The test feature name. |
@@ -137,7 +142,7 @@ Feature: Features can be modeled.
   Scenario Outline: Feature models pass all other specifications
   Exact specifications detailing the API for Feature models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications   |

data/features/modeling/outline_modeling.feature

@@ -11,6 +11,7 @@ Feature: Scenario Outline elements can be modeled.
     5. the outline's applied tags
     6. the outline's example blocks
     7. the outline's source line
+    8. the outline's raw element
 
 
   Background: Test file setup.
@@ -38,6 +39,10 @@ Feature: Scenario Outline elements can be modeled.
     And parameter delimiters of "*" and "*"
     When the file is read
 
+
+  Scenario: The raw outline element is modeled.
+    Then the test correctly stores its underlying implementation
+
   Scenario: The outline source line is modeled.
     Then the test is found to have the following properties:
       | source_line | 5 |
@@ -73,7 +78,7 @@ Feature: Scenario Outline elements can be modeled.
   Scenario Outline: Outline models pass all other specifications
   Exact specifications detailing the API for Scenario Outline models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications   |

data/features/modeling/row_modeling.feature

@@ -6,6 +6,7 @@ Feature: Row elements can be modeled.
   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
 
 
   Background: Test file setup.
@@ -27,6 +28,9 @@ Feature: Row elements can be modeled.
     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 |
@@ -60,7 +64,7 @@ Feature: Row elements can be modeled.
   Scenario Outline: Row models pass all other specifications
   Exact specifications detailing the API for Row models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications |

data/features/modeling/scenario_modeling.feature

@@ -10,6 +10,7 @@ Feature: Scenario elements can be modeled.
     4. the scenario's tags
     5. the scenario's applied tags
     6. the scenario's source line
+    7. the scenario's raw element
 
 
   Background: Test file setup.
@@ -31,6 +32,10 @@ Feature: Scenario elements can be modeled.
     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 |
@@ -62,7 +67,7 @@ Feature: Scenario elements can be modeled.
   Scenario Outline: Scenario models pass all other specifications
   Exact specifications detailing the API for Scenario models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications    |

data/features/modeling/step_modeling.feature

@@ -9,6 +9,7 @@ Feature: Step elements can be modeled.
     3. the step's arguments, if any
     4. the step's associated block, if any
     5. the step's source line
+    6. the step's raw element
 
 
   Background: Test file setup.
@@ -31,6 +32,10 @@ Feature: Step elements can be modeled.
     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"
@@ -66,7 +71,7 @@ Feature: Step elements can be modeled.
   Scenario Outline: Step models pass all other specifications
   Exact specifications detailing the API for Step models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications |

data/features/modeling/table_modeling.feature

@@ -5,6 +5,7 @@ Feature: Table elements can be modeled.
 
   All conceptual pieces of a Table can be modeled:
     1. the table's contents
+    2. the table's raw element
 
 
   Background: Test file setup.
@@ -31,10 +32,13 @@ Feature: Table elements can be modeled.
       | value 1 |
       | value 2 |
 
+  Scenario: The raw table element is modeled.
+    Then the table correctly stores its underlying implementation
+
   Scenario Outline: Table models pass all other specifications
   Exact specifications detailing the API for Table String models.
     Given that there are "<additional specifications>" detailing models
-    When the corresponding unit tests are run
+    When the corresponding specifications are run
     Then all of those specifications are met
   Examples:
     | additional specifications |

data/features/modeling/tag_modeling.feature

@@ -0,0 +1,51 @@
+Feature: Tag elements can be modeled.
+
+
+  Acceptance criteria
+
+  All conceptual pieces of a Tag can be modeled:
+    1. the tag's name
+    2. the tags's source line
+    3. the tags's raw element
+
+
+  Background: Test file setup.
+    Given the following feature file:
+    """
+    @feature_tag
+    Feature:
+
+      @outline_tag
+      Scenario Outline:
+        * a step
+
+      @example_tag
+      Examples:
+        | a param |
+    """
+    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 Outline: Tag models pass all other specifications
+  Exact specifications detailing the API for Tag models.
+    Given that there are "<additional specifications>" detailing models
+    When the corresponding specifications are run
+    Then all of those specifications are met
+  Examples:
+    | additional specifications |
+    | tag_unit_spec.rb          |