cuke_modeler 1.2.1 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 4779a73d0414df470da374597d5a5db928e9f1fd
-  data.tar.gz: fd1e0ab88380b774e1301789d50a89cce58716e8
+  metadata.gz: 6f6ce507c3e4cce81b178759608f8421995acb33
+  data.tar.gz: 28e38d785382112db34e4bd8ad21c2ab2d520fb2
 SHA512:
-  metadata.gz: '029706fe40a199ddb8b12c90de6c61b61576afab23c29603b43524f22b88c6d4373b52aa059f34f2a495c11f8f787956785684a5145ed5ac0f3dc2ff0bc994a8'
-  data.tar.gz: 3e41b0e4310907be62af428dcdc4e511ee783aa82e4aae93f5ec4977cc7724400ba83911b0b2ca5af65a2716e1391750c86e17d2cdda1f2b305a42247112a91a
+  metadata.gz: 6468b515b7f55540cf96319c3862ef04d7560b583294a694c71a3077becc915516465dec013e414c24d05b6fe8cfa0ef37844b4eab23dc1f62068b876b0fa17c
+  data.tar.gz: c636a5d624e5ad31be581134f0429bf63cd2d52bbef6a0278c5484ac8a2d0e18519e0d372051d5de44f4a012959dd7d93801559eda4f693e44247b779dd0c210

data/.simplecov

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

data/.travis.yml

@@ -6,9 +6,6 @@ language: ruby
 rvm:
   - 1.8.7
   - 1.9.3
-  - 2.0.0
-  - 2.1.6
-  - 2.2.2
   - 2.3.3
   - 2.4.0
   - jruby-9.1.7.0
@@ -17,6 +14,7 @@ gemfile:
   - testing/gemfiles/gherkin2.gemfile
   - testing/gemfiles/gherkin3.gemfile
   - testing/gemfiles/gherkin4.gemfile
+  - testing/gemfiles/gherkin5.gemfile
 
 matrix:
   exclude:
@@ -26,6 +24,9 @@ matrix:
   # gherkin 4.x does not work with Ruby 1.8.x
   - rvm: 1.8.7
     gemfile: testing/gemfiles/gherkin4.gemfile
+  # gherkin 5.x does not work with Ruby 1.8.x
+  - rvm: 1.8.7
+    gemfile: testing/gemfiles/gherkin5.gemfile
   # Travis does not provide 1.8.7 on OSX
   - rvm: 1.8.7
     os: osx

data/Gemfile

@@ -23,6 +23,6 @@ elsif RUBY_VERSION =~ /^2\./
     gem 'test-unit'
   end
 
-  gem 'gherkin', '~> 4.0'
+  gem 'gherkin', '~> 5.0'
 
 end

data/History.md

@@ -1,3 +1,8 @@
+### Version 1.3.0 / 2017-10-19
+
+* Now compatible with Gherkin 5.x.
+
+
 ### Version 1.2.1 / 2017-04-25
 
 * Now officially compatible with Rake 12.x.

data/README.md

@@ -3,7 +3,8 @@
 [![Build Status](https://travis-ci.org/enkessler/cuke_modeler.svg?branch=dev)](https://travis-ci.org/enkessler/cuke_modeler)
 [![Build status](https://ci.appveyor.com/api/projects/status/is8xqvoqn3pjh9l0/branch/dev?svg=true)](https://ci.appveyor.com/project/enkessler/cuke-modeler/branch/dev)
 [![Coverage Status](https://coveralls.io/repos/github/enkessler/cuke_modeler/badge.svg?branch=dev)](https://coveralls.io/github/enkessler/cuke_modeler?branch=dev)
-[![MIT Licence](https://badges.frapsoft.com/os/mit/mit.svg?v=103)](https://opensource.org/licenses/mit-license.php)
+[![Code Quality](https://codeclimate.com/github/enkessler/cuke_modeler/badges/gpa.svg)](https://codeclimate.com/github/enkessler/cuke_modeler)
+[![Project License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/mit-license.php)
 
 
 # CukeModeler

data/Rakefile

@@ -31,6 +31,25 @@ namespace 'cuke_modeler' do
     Rake::Task['cuke_modeler:test_everything'].invoke(rspec_args, cucumber_args)
   end
 
+
+  # The task used to publish the current feature file documentation to Relish
+  desc 'Publish feature files to Relish'
+  task :publish_features do
+    # Get existing versions
+    this_dir = File.dirname(__FILE__)
+    output = `relish versions enkessler/CukeModeler`
+
+    # Add the current version if it doesn't exist
+    unless output =~ /#{Regexp.escape(CukeModeler::VERSION)}/
+      output = `relish versions:add enkessler/CukeModeler:#{CukeModeler::VERSION}`
+      puts output
+    end
+
+    # Publish the features
+    output = `relish push enkessler/CukeModeler:#{CukeModeler::VERSION} path #{this_dir}/testing/cucumber`
+    puts output
+  end
+
 end
 
 

data/appveyor.yml

@@ -2,35 +2,36 @@ version: '1.0.{build}'
 
 environment:
   matrix:
-    - RUBY_VERSION: 187-x64
+    - RUBY_VERSION: 193
       BUNDLE_GEMFILE: testing/gemfiles/gherkin2.gemfile
-    - RUBY_VERSION: 193-x64
-      BUNDLE_GEMFILE: testing/gemfiles/gherkin2.gemfile
-    - RUBY_VERSION: 200-x64
-      BUNDLE_GEMFILE: testing/gemfiles/gherkin2.gemfile
-    - RUBY_VERSION: 21-x64
-      BUNDLE_GEMFILE: testing/gemfiles/gherkin2.gemfile
-    - RUBY_VERSION: 22-x64
+      # AppVeyor does not have a 64-bit Ruby 1.9.3
+      # Gherkin 2.x does not appear to support 32-bit Ruby 2.x and it's not worth it to investigate if this is true or not
+    - RUBY_VERSION: 23-x64
       BUNDLE_GEMFILE: testing/gemfiles/gherkin2.gemfile
 
-    - RUBY_VERSION: 193-x64
+    - RUBY_VERSION: 193
       BUNDLE_GEMFILE: testing/gemfiles/gherkin3.gemfile
-    - RUBY_VERSION: 200-x64
+      # AppVeyor does not have a 64-bit Ruby 1.9.3
+    - RUBY_VERSION: 23
       BUNDLE_GEMFILE: testing/gemfiles/gherkin3.gemfile
-    - RUBY_VERSION: 21-x64
-      BUNDLE_GEMFILE: testing/gemfiles/gherkin3.gemfile
-    - RUBY_VERSION: 22-x64
+    - RUBY_VERSION: 23-x64
       BUNDLE_GEMFILE: testing/gemfiles/gherkin3.gemfile
 
-    - RUBY_VERSION: 193-x64
-      BUNDLE_GEMFILE: testing/gemfiles/gherkin4.gemfile
-    - RUBY_VERSION: 200-x64
+    - RUBY_VERSION: 193
       BUNDLE_GEMFILE: testing/gemfiles/gherkin4.gemfile
-    - RUBY_VERSION: 21-x64
+      # AppVeyor does not have a 64-bit Ruby 1.9.3
+    - RUBY_VERSION: 23
       BUNDLE_GEMFILE: testing/gemfiles/gherkin4.gemfile
-    - RUBY_VERSION: 22-x64
+    - RUBY_VERSION: 23-x64
       BUNDLE_GEMFILE: testing/gemfiles/gherkin4.gemfile
 
+    - RUBY_VERSION: 193
+      BUNDLE_GEMFILE: testing/gemfiles/gherkin5.gemfile
+      # AppVeyor does not have a 64-bit Ruby 1.9.3
+    - RUBY_VERSION: 23
+      BUNDLE_GEMFILE: testing/gemfiles/gherkin5.gemfile
+    - RUBY_VERSION: 23-x64
+      BUNDLE_GEMFILE: testing/gemfiles/gherkin5.gemfile
 
 install:
   - set PATH=C:\Ruby%RUBY_VERSION%\bin;%PATH%

data/cuke_modeler.gemspec

@@ -18,7 +18,7 @@ Gem::Specification.new do |spec|
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
   spec.require_paths = ["lib"]
 
-  spec.add_runtime_dependency 'gherkin', '< 5.0'
+  spec.add_runtime_dependency 'gherkin', '< 6.0'
   spec.add_runtime_dependency('json', '>= 1.0', '< 3.0')
   spec.add_runtime_dependency('multi_json', '~> 1.0')
 

data/lib/cuke_modeler/adapters/gherkin_4_adapter.rb

@@ -1,6 +1,6 @@
 module CukeModeler
 
-  # An adapter that can convert the output of version 4.x of the *gherkin* gem into input that is consumable by this gem.
+  # An adapter that can convert the output of version 4.x and 5.x of the *gherkin* gem into input that is consumable by this gem.
 
   class Gherkin4Adapter
 

data/lib/cuke_modeler/parsing.rb

@@ -19,7 +19,7 @@ module CukeModeler
     # will be done with an 'adapter' appropriate to the version of the *gherkin* gem that has been activated.
 
     case Gem.loaded_specs['gherkin'].version.version
-      when /^4\./
+      when /^[54]\./
         require 'gherkin/parser'
         require 'cuke_modeler/adapters/gherkin_4_adapter'
 

data/lib/cuke_modeler/version.rb

@@ -1,4 +1,4 @@
 module CukeModeler
   # The gem version
-  VERSION = '1.2.1'
+  VERSION = '1.3.0'
 end

data/testing/cucumber/features/analysis/test_comparison.feature

@@ -1,9 +1,6 @@
 Feature: Test comparison
 
-  Gherkin elements that contain steps (i.e. backgrounds, scenarios, and outlines) can be compared with one another
-  in order to determine equality. Elements are considered equal if the base text of their steps match. That is, the
-  keyword used for the step and any table or doc string that may be associated with that step are ignored for the
-  purposes of comparison.
+  Gherkin elements that contain steps (i.e. backgrounds, scenarios, and outlines) can be compared with one another in order to determine equality. Elements are considered equal if the base text of their steps match. That is, the keyword used for the step and any table or doc string that may be associated with that step are ignored for the purposes of comparison.
 
 
   Scenario: Comparing tests

data/testing/cucumber/features/modeling/background_modeling.feature

@@ -1,7 +1,6 @@
 Feature: Background modeling
 
-  Background models represent the Background portion of a feature. They expose several attributes of the background
-  that they represent, as well as containing models for the steps that are present in that background.
+  Background models represent the Background portion of a feature. They expose several attributes of the background that they represent, as well as containing models for the steps that are present in that background.
 
 
   Background:

data/testing/cucumber/features/modeling/background_output.feature

@@ -1,7 +1,6 @@
 Feature: Background output
 
-  A background model's string output is a Gherkin representation of itself. As such, output from a background model can be used as
-  input for the same kind of model.
+  A background model's string output is a Gherkin representation of itself. As such, output from a background model can be used as input for the same kind of model.
 
 
   Scenario: Outputting a background model

data/testing/cucumber/features/modeling/cell_modeling.feature

@@ -1,7 +1,6 @@
 Feature: Cell modeling
 
-  Cell models represent an individual cell in a table row (either a step table or an example table). They expose
-  several attributes of the cell that they represent.
+  Cell models represent an individual cell in a table row (either a step table or an example table). They expose several attributes of the cell that they represent.
 
 
   Background:

data/testing/cucumber/features/modeling/comment_modeling.feature

@@ -1,7 +1,6 @@
 Feature: Comment modeling
 
-  Comment models represent a comment portion of a feature. They expose several attributes of the comment
-  that they represent.
+  Comment models represent a comment portion of a feature. They expose several attributes of the comment that they represent.
 
 
   Background:

data/testing/cucumber/features/modeling/comment_output.feature

@@ -1,7 +1,6 @@
 Feature: Comment output
 
-  A comment model's string output is a Gherkin representation of itself. As such, output from a comment model can be used as
-  input for the same kind of model.
+  A comment model's string output is a Gherkin representation of itself. As such, output from a comment model can be used as input for the same kind of model.
 
 
   Scenario: Outputting a comment model

data/testing/cucumber/features/modeling/directory_modeling.feature

@@ -1,9 +1,6 @@
 Feature: Directory modeling
 
-
-  Directory models are the top level element of a model tree. They expose several attributes of the directory that they
-  represent, as well as containing models for any feature files or subdirectories that are present in the directory
-  that they represent.
+  Directory models are the top level element of a model tree. They expose several attributes of the directory that they represent, as well as containing models for any feature files or subdirectories that are present in the directory that they represent.
 
 
   Background: An existing test suite

data/testing/cucumber/features/modeling/directory_output.feature

@@ -1,7 +1,6 @@
 Feature: Directory output
 
-  A directory model's string output is simply the file path of the directory that it models. As such, output from a directory model can be used as
-  input for the same kind of model.
+  A directory model's string output is simply the file path of the directory that it models. As such, output from a directory model can be used as input for the same kind of model.
 
 
   Scenario: Outputting a directory model

data/testing/cucumber/features/modeling/doc_string_modeling.feature

@@ -1,8 +1,6 @@
 Feature: Doc string modeling
 
-
-  Doc string models represent the doc string argument to a step. They expose several attributes of the doc string
-  that they represent.
+  Doc string models represent the doc string argument to a step. They expose several attributes of the doc string that they represent.
 
 
   Background:

data/testing/cucumber/features/modeling/doc_string_output.feature

@@ -1,7 +1,6 @@
 Feature: Doc string output
 
-  A doc string model's string output is a Gherkin representation of itself. As such, output from a doc string model can be used as
-  input for the same kind of model.
+  A doc string model's string output is a Gherkin representation of itself. As such, output from a doc string model can be used as input for the same kind of model.
 
 
   Scenario: Outputting a doc string model

data/testing/cucumber/features/modeling/example_modeling.feature

@@ -1,8 +1,6 @@
 Feature: Example modeling
 
-  Example models represent an example table of a Scenario Outline portion of a feature. They expose
-  several attributes of the example that they represent, as well as containing models for the example
-  rows and tags that are present in that example.
+  Example models represent an example table of a Scenario Outline portion of a feature. They expose several attributes of the example that they represent, as well as containing models for the example rows and tags that are present in that example.
 
 
   Background:

data/testing/cucumber/features/modeling/example_output.feature

@@ -1,7 +1,6 @@
 Feature: Example output
 
-  An example model's string output is a Gherkin representation of itself. As such, output from an example model can be used as
-  input for the same kind of model.
+  An example model's string output is a Gherkin representation of itself. As such, output from an example model can be used as input for the same kind of model.
 
 
   Scenario: Outputting an example model

data/testing/cucumber/features/modeling/feature_file_modeling.feature

@@ -1,8 +1,6 @@
 Feature: Feature file modeling
 
-
-  Feature file models represent a single .feature file in a test suite. They expose several attributes of the
-  feature file that they represent, as well as containing the model for the feature that is present in that file.
+  Feature file models represent a single .feature file in a test suite. They expose several attributes of the feature file that they represent, as well as containing the model for the feature that is present in that file.
 
 
   Background: An existing feature file

data/testing/cucumber/features/modeling/feature_file_output.feature

@@ -1,7 +1,6 @@
 Feature: Feature file output
 
-  A feature file model's string output is simply the file path of the feature file that it models. As such, output from a feature file model can be used as
-  input for the same kind of model.
+  A feature file model's string output is simply the file path of the feature file that it models. As such, output from a feature file model can be used as input for the same kind of model.
 
 
   Scenario: Outputting a feature file model

data/testing/cucumber/features/modeling/feature_modeling.feature

@@ -1,8 +1,6 @@
 Feature: Feature modeling
 
-Feature models are the top level element of the gherkin portion of the model tree. They expose several attributes of
-the feature that they represent, as well as containing models for any background, scenarios, or outlines that are
-present in that feature.
+Feature models are the top level element of the gherkin portion of the model tree. They expose several attributes of the feature that they represent, as well as containing models for any background, scenarios, or outlines that are present in that feature.
 
 
   Background:
@@ -97,8 +95,7 @@ present in that feature.
 
   Scenario: Modeling a feature's tags
 
-  Note: Although a feature does not inherit tags from anything else, they can still
-  be requested in the same manner as other models that have tags.
+  Note: Although a feature does not inherit tags from anything else, they can still be requested in the same manner as other models that have tags.
 
     When the feature's tags are requested
       """

data/testing/cucumber/features/modeling/feature_output.feature

@@ -1,7 +1,6 @@
 Feature: Feature output
 
-  A feature model's string output is a Gherkin representation of itself. As such, output from a feature model can be used as
-  input for the same kind of model.
+  A feature model's string output is a Gherkin representation of itself. As such, output from a feature model can be used as input for the same kind of model.
 
 
   Scenario: Outputting a feature model

data/testing/cucumber/features/modeling/model_output.feature

@@ -1,8 +1,6 @@
 Feature: Model output
 
-  All models can be output in text form. For models that represent parts of the file structure, this text
-  will be a path and for models that represent parts of a feature file, this text will be Gherkin (see the
-  model output documentation for specific models for details).
+  All models can be output in text form. For models that represent parts of the file structure, this text will be a path and for models that represent parts of a feature file, this text will be Gherkin (see the model output documentation for specific models for details).
 
 
   Scenario: Outputting a model

data/testing/cucumber/features/modeling/model_structure.feature

@@ -1,13 +1,8 @@
 Feature: Model structure
 
-When modeling an existing test suite, that suite is parsed and models are created for each element of the
-suite. These models form a nested structure of parent and child models which has the same shape as whatever
-portion of the suite that they represent (see the documentation for specific models for details).
+When modeling an existing test suite, that suite is parsed and models are created for each element of the suite. These models form a nested structure of parent and child models which has the same shape as whatever portion of the suite that they represent (see the documentation for specific models for details).
 
-However, all models can also be used in an 'abstract' manner. That is, they can be created without any input
-(such as a file path or snippet of Gherkin) that would normally be used for determining their structure and
-properties. In these cases, their parent/child relationships and properties can be set directly rather than
-being populated dynamically based on an actual test suite.
+However, all models can also be used in an 'abstract' manner. That is, they can be created without any input (such as a file path or snippet of Gherkin) that would normally be used for determining their structure and properties. In these cases, their parent/child relationships and properties can be set directly rather than being populated dynamically based on an actual test suite.
 
 
   Scenario: Creating abstract models
@@ -36,8 +31,7 @@ being populated dynamically based on an actual test suite.
 
   Scenario: Accessing the parsing data
 
-  Note: Directory models do not store any parsing data because parsing Gherkin source text
-  does not come into play until the feature file level of modeling.
+  Note: Directory models do not store any parsing data because parsing Gherkin source text does not come into play until the feature file level of modeling.
 
     Given the models provided by CukeModeler
     Then  all of them provide access to the parsing data that was used to create them

data/testing/cucumber/features/modeling/outline_modeling.feature

@@ -1,7 +1,6 @@
 Feature: Outline modeling
 
-  Outline models represent a Scenario Outline portion of a feature. They expose several attributes of the outline
-  that they represent, as well as containing models for the steps, tags, and examples that are present in that outline.
+  Outline models represent a Scenario Outline portion of a feature. They expose several attributes of the outline that they represent, as well as containing models for the steps, tags, and examples that are present in that outline.
 
 
   Background:

data/testing/cucumber/features/modeling/outline_output.feature

@@ -1,7 +1,6 @@
 Feature: Outline output
 
-  An outline model's string output is a Gherkin representation of itself. As such, output from an outline model can be used as
-  input for the same kind of model.
+  An outline model's string output is a Gherkin representation of itself. As such, output from an outline model can be used as input for the same kind of model.
 
 
   Scenario: Outputting an outline model

data/testing/cucumber/features/modeling/row_modeling.feature

@@ -1,7 +1,6 @@
 Feature: Row modeling
 
-  Row models represent an individual row in a step or example table. They expose several attributes of the row
-  that they represent.
+  Row models represent an individual row in a step or example table. They expose several attributes of the row that they represent.
 
 
   Background: