cuke_modeler 0.0.2 → 0.1.0

data/.travis.yml

@@ -0,0 +1,23 @@
+language: ruby
+rvm:
+  - 1.8.7
+  - 1.9.3
+  - 2.0.0
+  - 2.1.6
+  - 2.2.2
+
+gemfile:
+  - gemfiles/gherkin.gemfile
+  - gemfiles/gherkin3.gemfile
+
+
+matrix:
+  exclude:
+  - rvm: 1.8.7
+    gemfile: gemfiles/gherkin3.gemfile
+
+# todo - Remove this once TravisCI fixes their bundler issue (https://github.com/alphagov/govuk_template/pull/186)
+before_install:
+  - gem install bundler -v 1.9.10
+
+script: bundle exec rake cuke_modeler:ci_build

data/Gemfile

@@ -1,4 +1,22 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in cuke_modeler.gemspec
-gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in cuke_modeler.gemspec
+gemspec
+
+# cuke_modeler can play with pretty much any version of these but they all play differently with Ruby
+if RUBY_VERSION =~ /^1\.8/
+  gem 'cucumber', '<1.3.0'
+  gem 'gherkin', '<2.12.0'
+  gem 'mime-types', '<2.0.0'
+  gem 'rest-client', '<1.7.0'
+elsif RUBY_VERSION =~ /^1\./
+  gem 'cucumber', '<2.0.0'
+end
+
+if RUBY_VERSION =~ /^2\./
+  gem 'gherkin', '>= 3.0.0'
+end
+
+if RUBY_VERSION =~ /^2\.[23456789]/
+  gem 'test-unit'
+end

data/History.rdoc

@@ -1,8 +1,14 @@
+=== Version 0.1.0 / 2016-02-10
+
+* Support for version 3.0 of the 'gherkin' gem added.
+
+
 === Version 0.0.2 / 2015-11-22
 
 * Bug fix - Fixed a bug that was causing object comparison using #== to not work when comparing some models to other
             types of objects.
 
+
 === Version 0.0.1 / 2014-06-02
 
 * Initial release

data/Rakefile

@@ -1,38 +1,38 @@
 require "bundler/gem_tasks"
-require 'cucumber/rake/task'
-require 'rspec/core/rake_task'
+require 'coveralls/rake/task'
 
+require 'racatt'
 
-def set_cucumber_options(options)
-  ENV['CUCUMBER_OPTS'] = options
-end
 
-def combine_options(set_1, set_2)
-  set_2 ? "#{set_1} #{set_2}" : set_1
-end
+namespace 'cuke_modeler' do
 
+  task :clear_coverage do
+    code_coverage_directory = "#{File.dirname(__FILE__)}/coverage"
 
-task :clear_coverage do
-  code_coverage_directory = "#{File.dirname(__FILE__)}/coverage"
+    FileUtils.remove_dir(code_coverage_directory, true)
+  end
 
-  FileUtils.remove_dir(code_coverage_directory, true)
-end
 
-desc 'Run all Cucumber tests for the gem'
-task :tests, [:options] do |t, args|
-  set_cucumber_options(combine_options("-t ~@wip -t ~@off -f progress", args[:options]))
-end
-Cucumber::Rake::Task.new(:tests)
+  Racatt.create_tasks
 
-desc 'Run all RSpec tests for the gem'
-RSpec::Core::RakeTask.new(:specs) do |t|
-  t.rspec_opts = "-t ~wip -t ~off"
-end
+  # Redefining the task from 'racatt' in order to clear the code coverage results
+  task :test_everything => :clear_coverage
+
+
+  # The task that CI will use
+  Coveralls::RakeTask.new
+  task :ci_build => [:smart_test, 'coveralls:push']
+
+  desc 'Test gem based on Ruby/dependency versions'
+  task :smart_test do |t, args|
+    rspec_args = ''
+    cucumber_args = Gem.loaded_specs['gherkin'].version.version[/^3/] ? '-t ~@gherkin' : '-t ~@gherkin3'
+    cucumber_args += ' -f progress'
+
+    Rake::Task['cuke_modeler:test_everything'].invoke(rspec_args, cucumber_args)
+  end
 
-desc 'Run All The Things'
-task :everything => :clear_coverage do
-  Rake::Task[:specs].invoke
-  Rake::Task[:tests].invoke('-t ~@redundant')
 end
 
-task :default => :everything
+
+task :default => 'cuke_modeler:smart_test'

data/cuke_modeler.gemspec

@@ -17,7 +17,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')
+  spec.add_runtime_dependency 'gherkin', '< 4.0'
   spec.add_runtime_dependency('json', '~> 1.0')
   spec.add_runtime_dependency('multi_json', '~> 1.0')
 
@@ -26,4 +26,6 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'cucumber'
   spec.add_development_dependency 'rspec', '~> 2.14.0'
   spec.add_development_dependency 'simplecov'
+  spec.add_development_dependency 'racatt', '~> 1.0'
+  spec.add_development_dependency 'coveralls'
 end

data/features/modeling/{background_modeling.feature → gherkin/background_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Background elements can be modeled.
 
 
@@ -62,14 +63,3 @@ Feature: Background elements can be modeled.
 
   Scenario: Convenient output of a background
     Then the background has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications      |
-    | background_unit_spec.rb        |
-    | background_integration_spec.rb |

data/features/modeling/{background_output.feature → gherkin/background_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting background elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{directory_modeling.feature → gherkin/directory_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Directories can be modeled.
 
 
@@ -107,14 +108,3 @@ Feature: Directories can be modeled.
 
   Scenario: Convenient output of a directory
     Then the directory has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications     |
-    | directory_unit_spec.rb        |
-    | directory_integration_spec.rb |

data/features/modeling/{directory_output.feature → gherkin/directory_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting directory elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{doc_string_modeling.feature → gherkin/doc_string_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Doc string elements can be modeled.
 
 
@@ -50,14 +51,3 @@ Feature: Doc string elements can be modeled.
 
   Scenario: Convenient output of an a doc string
     Then the doc string has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications      |
-    | doc_string_unit_spec.rb        |
-    | doc_string_integration_spec.rb |

data/features/modeling/{doc_string_output.feature → gherkin/doc_string_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting doc string elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{example_modeling.feature → gherkin/example_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Example elements can be modeled.
 
 
@@ -98,14 +99,3 @@ Feature: Example elements can be modeled.
 
   Scenario: Convenient output of an example block
     Then the example block has convenient output
-
-  @redundant
-  Scenario Outline: Example models pass all other specifications
-  Exact specifications detailing the API for example block 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   |
-    | example_unit_spec.rb        |
-    | example_integration_spec.rb |

data/features/modeling/{example_output.feature → gherkin/example_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting example elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{feature_file_modeling.feature → gherkin/feature_file_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Feature files can be modeled.
 
 
@@ -51,14 +52,3 @@ Feature: Feature files can be modeled.
 
   Scenario: Convenient output of a feature file
     Then the feature file has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications        |
-    | feature_file_unit_spec.rb        |
-    | feature_file_integration_spec.rb |

data/features/modeling/{feature_file_output.feature → gherkin/feature_file_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting feature file elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{feature_modeling.feature → gherkin/feature_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Features can be modeled.
 
 
@@ -151,14 +152,3 @@ Feature: Features can be modeled.
 
   Scenario: Convenient output of a feature
     Then the feature has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications   |
-    | feature_unit_spec.rb        |
-    | feature_integration_spec.rb |

data/features/modeling/{feature_output.feature → gherkin/feature_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting feature elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{outline_modeling.feature → gherkin/outline_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outline elements can be modeled.
 
 
@@ -87,14 +88,3 @@ Feature: Outline elements can be modeled.
 
   Scenario: Convenient output of an an outline
     Then the outline has convenient output
-
-  @redundant
-  Scenario Outline: Outline models pass all other specifications
-  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
-  Examples:
-    | additional specifications   |
-    | outline_unit_spec.rb        |
-    | outline_integration_spec.rb |

data/features/modeling/{outline_output.feature → gherkin/outline_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting outline elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{row_modeling.feature → gherkin/row_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Row elements can be modeled.
 
 
@@ -65,13 +66,3 @@ Feature: Row elements can be modeled.
 
   Scenario: Convenient output of a row
     Then the row has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications |
-    | row_unit_spec.rb          |

data/features/modeling/{row_output.feature → gherkin/row_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting row elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{scenario_modeling.feature → gherkin/scenario_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Scenario elements can be modeled.
 
 
@@ -76,14 +77,3 @@ Feature: Scenario elements can be modeled.
 
   Scenario: Convenient output of a scenario
    Then the scenario has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications    |
-    | scenario_unit_spec.rb        |
-    | scenario_integration_spec.rb |

data/features/modeling/{scenario_output.feature → gherkin/scenario_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting scenario elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{step_modeling.feature → gherkin/step_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Step elements can be modeled.
 
 
@@ -72,14 +73,3 @@ Feature: Step elements can be modeled.
 
   Scenario: Convenient output of a step
     Then the step has convenient output
-
-  @redundant
-  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 specifications are run
-    Then all of those specifications are met
-  Examples:
-    | additional specifications |
-    | step_unit_spec.rb         |
-    | step_integration_spec.rb  |

data/features/modeling/{step_output.feature → gherkin/step_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting step elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{table_modeling.feature → gherkin/table_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Table elements can be modeled.
 
 
@@ -39,14 +40,3 @@ Feature: Table elements can be modeled.
 
   Scenario: Convenient output of a table
     Then the table has convenient output
-
-  @redundant
-  Scenario Outline: Table models pass all other specifications
-  Exact specifications detailing the API for table 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 |
-    | table_unit_spec.rb        |
-    | table_integration_spec.rb |

data/features/modeling/{table_output.feature → gherkin/table_output.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Outputting table elements
 
   The output of an element model is a representation of the element as it would

data/features/modeling/{table_row_modeling.feature → gherkin/table_row_modeling.feature}

@@ -1,3 +1,4 @@
+@gherkin
 Feature: Table Row elements can be modeled.
 
 
@@ -54,14 +55,3 @@ Feature: Table Row elements can be modeled.
 
   Scenario: Convenient output of a table row
     Then the table row has convenient output
-
-  @redundant
-  Scenario Outline: Table row models pass all other specifications
-  Exact specifications detailing the API for table table row 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     |
-    | table_row_unit_spec.rb        |
-    | table_row_integration_spec.rb |