macros4cuke 0.5.14 → 0.5.15

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7cb356982999fd02630dd75bbda6beb095efb947
-  data.tar.gz: 54a135b208d24ee455ed7fb58da0c85c0a616400
+  metadata.gz: 1f585f9021fd1f335181c02c792d82f651012e5a
+  data.tar.gz: 71ecc879f73740225a10181a4068417f45c6a5da
 SHA512:
-  metadata.gz: d3e9d7bb5e298df844b119c64e4486d3f048352a14d4ef94fb75c7070f7f4996f94f21638277d6e4ed5c390518b58fed16dd54564f1b2ae7abf43a755d6e750b
-  data.tar.gz: f9fd3bb3a6563c05a41528ea048ac701c4685af8168b7a81eb1ce88e35df3a46b2af3a18cae4f507f1c6609cbf4bc0086cb39b7abf65508df62f6604f9a2644b
+  metadata.gz: a8bf9ed9629fcd69f8df584bb006b24dc531144f2e1b7f345a587f3f4595f3f5f4dab9483ad4452e00d489aef92aba803da6963910e0b57e763ee6b5c98717cd
+  data.tar.gz: 5c3f819372840ecc854d7b4b9a150a96b00fac39d8fe51389a9795e3d42a5a45458e8dc87917b64ac8e57d9a7c7a6fc6dbcbabb6a1907396620462ae7d6cd1b2

data/.travis.yml

@@ -1,20 +1,18 @@
 language: ruby
 rvm:
   - ruby-head
-  - 2.2.2
-  - 2.2.0
-  - 2.1.0
-  - 2.0.0
-  - 1.9.3
-  - jruby-head
-  - jruby-19mode
-
+  - jruby-head  
+  - 2.3.3
+  - 2.2.6
+  - 2.1.9
+  - 2.0.0  
+  - jruby    
 
 # Workaround issue of jruby-head configuration on Travis CI
 matrix:
   allow_failures:
-    - rvm: jruby-head
     - rvm: ruby-head
+    - rvm: jruby-head
 
 gemfile:
   - Gemfile

data/CHANGELOG.md

@@ -1,3 +1,12 @@
+### 0.5.15 / 2016-12-21
+* [NEW] File `appveyor.yml`: Added AppVeyor CI so that Macros4Cuke builds also
+can be tested on Windows. This complements the Travis CI which runs on Linux.
+* [CHANGE] File `README.md` Added AppVeyor badge
+* [CHANGE] A pass to adapt code style in order to please Rubocop 0.46.0
+* [CHANGE] File `.travis.yml` Added support for Ruby 2.3.x, dropped Ruby 1.9.3
+* [CHANGE] File `macros4cuke.gemspec` Minimal Ruby version supported is now Ruby 2.0.0
+
+
 ### 0.5.14 / 2016-03-16
 * [FIX] File `macro_steps`: Cucumber complained about allusion to deprecated class `Cucumber::Ast::Table`.
 
@@ -106,9 +115,9 @@
 * [CHANGE] File `.rubocop.yml`: Disabled a few new 0.15.0 cops
 * [CHANGE] Files from `lib` and `spec` dirs updated for Rubocop 0.15.0
 
-### 0.4.00 / 2013-11-17 
+### 0.4.00 / 2013-11-17
 #### Version number bumped. New feature: to list all encountered macro definitions into a single feature file.
-* [FEATURE] Sample `demo07.feature` file illustrates the new step that will list all macro definitions. 
+* [FEATURE] Sample `demo07.feature` file illustrates the new step that will list all macro definitions.
 * [NEW] Class CollWalkerFactory. Creates specialized Enumerators that walk over the macro collection.
 * [NEW] Module Formatter. Purpose: Grouping of all classes that render macro definitions
 * [NEW] File `all-notifications.rb` List of macro collection visit events.
@@ -145,16 +154,16 @@
 ### 0.3.37 / 2013-06-27
 * [FIX] File `macros4cuke.gemspec`: added README.md in extra_rdoc_files option.
 * [CHANGE] File `README.md`: Re-formatting so that it is better rendered with darkfish (from YARD).
-* [CHANGE] File `.yardopts` : grouped the exclude options on one line. 
+* [CHANGE] File `.yardopts` : grouped the exclude options on one line.
 
 ### 0.3.36 / 2013-06-27
 * [FIX] File `macros4cuke.gemspec`: corrected the rdoc_options to exclude doc from examples, features and spec folders.
   This was necessary because all but the latest versions of RDoc have difficulties to cope with utf-8.
-* [CHANGE] File `.yardopts` : added more folders to exclude from documentation generation. 
+* [CHANGE] File `.yardopts` : added more folders to exclude from documentation generation.
 
 ### 0.3.35 / 2013-06-27
 * [CHANGE] File `macros4cuke.gemspec`: added rdoc_options to exclude doc from examples, features and spec folders.
-  This was necessary because all but the latest versions of RDoc have difficulties to cope with utf-8. 
+  This was necessary because all but the latest versions of RDoc have difficulties to cope with utf-8.
 
 ### 0.3.34 / 2013-06-20
 * [CHANGE] Most files: Except for the i18n sample files, the utf-8 encoding comment was in all Ruby files of the project.
@@ -243,7 +252,7 @@
 
 ### 0.3.16 / 2013-05-20
 * [CHANGE] File `demo06.feature`: Added a scenario that causes a specific exception to be raised.
-* [CHANGE] File `demo_steps.rb`: Added a specific step that raises a TableNotException. It is captured and compared to expectations. 
+* [CHANGE] File `demo_steps.rb`: Added a specific step that raises a TableNotException. It is captured and compared to expectations.
 * [CHANGE] File `engine.rb`: Removed two lines that were never executed.
 
 ### 0.3.15 / 2013-05-20
@@ -289,7 +298,7 @@
 * [NEW] File `.travis.yml`: Added for integration with Travis CI
 * [NEW] File `Gemfile`: Added for integration with Bundler
 * [NEW] File `Rakefile`: Added with test tasks
-* [CHANGE] File `macros4cuke.gemspec`: added development dependency on rake. 
+* [CHANGE] File `macros4cuke.gemspec`: added development dependency on rake.
 
 ### 0.3.03 / 2013-05-11
 * [CHANGE] File `README.md`: added section on conditional section.
@@ -304,7 +313,7 @@
 * [CHANGE] Method `Engine#compile_sction` completed and tested to support section elements.
 * [CHANGE] Method `Section#variables` expanded to support section elements.
 * [CHANGE] Method `Engine#variables` expanded to support section elements.
-* [CHANGE] Method `Engine#compile_line` added two formatting rules. 
+* [CHANGE] Method `Engine#compile_line` added two formatting rules.
 * [CHANGE] Method `MacroStep#scan_arguments` now un-escape the \" sequence into plain quote.
 * [CHANGE] examples/ folder expanded and reorganized
 * [FIX] Method `Section#render` fixed typo in call to __method__
@@ -428,7 +437,7 @@
 
 ### 0.2.01 / 2013-4-26
 
-* [CHANGE] Regexps in step definitions accept escape character sequence. 
+* [CHANGE] Regexps in step definitions accept escape character sequence.
 * [CHANGE] Expanded `README.md` file.
 * [FIX] Corrected remnant of Mustache template in `travelling_demo.feature` file.
 
@@ -457,7 +466,7 @@
 ### 0.1.05 / Unreleased
 
 * [CHANGE] `demo_steps.rb`. Added few step definitions that emit output to the screen (so that at least something is shown in the demo).  
-* [CHANGE] `MacroStep` class: regexp slightly reworked to accept escaped double quotes in actual values. 
+* [CHANGE] `MacroStep` class: regexp slightly reworked to accept escaped double quotes in actual values.
 * [CHANGE] `travelling_demo.feature`: Added one example with escaped quotes in actual value.
 
 
@@ -481,4 +490,4 @@
 
 ### 0.0.01 / 2013-04-21
 
-* [FEATURE] Initial public working version
+* [FEATURE] Initial public working version

data/Gemfile

@@ -4,7 +4,7 @@ source 'https://rubygems.org'
 gem 'cucumber', ['>= 1.3.18']
 
 group :development do
-  gem 'rake',  '>= 0.9.2' 
+  gem 'rake',  '>= 10.0.0' 
   gem 'rspec', '>= 3.0.0'
-  gem 'simplecov', '>= 0.6.2'
+  gem 'simplecov', '>= 0.7.0'
 end

data/LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2013-2016 Dimitri Geshef
+Copyright (c) 2013-2017 Dimitri Geshef
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -4,7 +4,8 @@ _Extend Cucumber with macro-steps._
 [Homepage](https://github.com/famished-tiger/Macros4Cuke)  
 [Documentation] (https://www.relishapp.com/famished-tiger/macros4cuke/docs)
 
-[![Build Status](https://travis-ci.org/famished-tiger/Macros4Cuke.png?branch=master)](https://travis-ci.org/famished-tiger/Macros4Cuke)
+[![Linux Build Status](https://travis-ci.org/famished-tiger/Macros4Cuke.png?branch=master)](https://travis-ci.org/famished-tiger/Macros4Cuke)
+[![Windows Build status](https://ci.appveyor.com/api/projects/status/amsdudnqo1jqfody?svg=true)](https://ci.appveyor.com/project/famished-tiger/macros4cuke)
 [![Code Climate](https://codeclimate.com/github/famished-tiger/Macros4Cuke.png)](https://codeclimate.com/github/famished-tiger/Macros4Cuke.png)
 [![Gem Version](https://badge.fury.io/rb/macros4cuke.png)](http://badge.fury.io/rb/macros4cuke)
 [![Dependency Status](https://gemnasium.com/famished-tiger/Macros4Cuke.png)](https://gemnasium.com/famished-tiger/Macros4Cuke)
@@ -15,17 +16,17 @@ __Macros4Cuke__ is a Cucumber extension that adds a macro facility for your Cucu
   All this can be done directly in your feature files without programming step definitions.
 
 ### Highlights ###
-* Works with out-of-the-box Cucumber (including version 2.0.0!)
+* Works with out-of-the-box Cucumber
 * Simple installation and setup (no programming required),
 * Familiar syntax for macro-step definitions,
-* Substep sequence can be of arbitrary length,
+* Sub-step sequence can be of arbitrary length,
 * Macro-steps may have data arguments,
 * Data values can be passed to the sub-steps,
 * Domain neutral: applicable to any kind of application that can be driven with Cucumber,
 * A group of sub-steps can be made conditional.
 
 
-Since version 0.4.00, it is also possible to [list all the encountered macro definitions](#listing-all-the-macro-definitions). 
+Since version 0.4.00, it is also possible to [list all the encountered macro definitions](#listing-all-the-macro-definitions).
 
 ## A quick example ##
 Here is a macro-step example taken from our demo files:  
@@ -49,13 +50,13 @@ the macro-step is invoked(used) elsewhere in a feature file.
 
 That macro-step can then be used/invoked in a scenario like this:  
 
-```cucumber 
+```cucumber
     When I [enter my userid "jdoe" and password "hello-world"]
 ```
 
 Once it is executing, the invoked macro-step should be equivalent to:  
 
-```cucumber 
+```cucumber
     Given I landed in the homepage  
     When I click "Sign in"  
     And I fill in "Username" with "jdoe"  
@@ -84,27 +85,27 @@ Macros4Cuke requires Cucumber.
 ### Installation ###
 The macros4cuke gem installation is fairly standard.  
 If you have a `Gemfile`, add `macros4cuke` to it. Otherwise, install the gem like this:
- 
+
 ```bash  
 $[sudo] gem install macros4cuke
 ```
 
 ### Configuring your Cucumber projects ####
 The procedure to add support for macros in an existing Cucumber project
-was simplified since version 0.5.00. 
- 
+was simplified since version 0.5.00.
+
 There are two possible ways to do it:  
 - By editing manually a support file; or,  
 - Let Macros4cuke configure your project.   
- 
+
 #### Alternative 1: manually add one line in a support file  
 Require the library in one of your ruby files under `features/support` (e.g. `env.rb`):  
- 
+
 ```ruby
 # /features/support/env.rb
 # Add the next single line
 require 'macros4cuke/cucumber'  
-``` 
+```
 
 That's it! Now you can start writing macros in your Cucumber project.
 
@@ -121,7 +122,7 @@ already the directory containing the Cucumber project, then the
 command-line is simply:  
 ```bash  
 $[sudo] macros4cuke --setup .
-``` 
+```
 
 Notice that ending dot above means "the current directory".
 
@@ -174,7 +175,7 @@ A phrase can be without argument as in:
   # A phrase without argument
   [enter my credentials]
 ```
-  
+
 Alternatively, a phrase can have one or more arguments enclosed between chevrons <...>.
 For instance, the next first phrase has two arguments, the second has three arguments:  
 
@@ -186,13 +187,13 @@ For instance, the next first phrase has two arguments, the second has three argu
 Each argument (variable) is enclosed between <...> chevrons. In our last example,
 the argument names are: _origin_ and _destination_. Notice that _origin_ and _destination_ are
  variable names that will take a value (if any) when the step is invoked _(more on this later)_.
- 
+
 
 #### Specifying the sub-steps of a macro-step ####
-The sub-steps are placed in a Gherkin multiline text, that is, a text that is enclosed between 
+The sub-steps are placed in a Gherkin multiline text, that is, a text that is enclosed between
  triple quotes ("""). In the next example,  
 
-```cucumber 
+```cucumber
   Given I define the step "When I [enter my credentials]" to mean:  
   """  
   Given I landed in the homepage   
@@ -201,12 +202,12 @@ The sub-steps are placed in a Gherkin multiline text, that is, a text that is en
   And I click "Sign in"  
   """  
 ```  
-  
+
 the text between triple quotes enumerates the sub-steps associated with the macro-step.  
  A pleasing aspect is the familiar syntax the sub-steps have: they closely look to genuine steps of a scenario.  
-Sub-steps can also have macro arguments. 
+Sub-steps can also have macro arguments.
  For instance, the previous step sequence could have two arguments called _userid_ and _password_:  
- 
+
 ```cucumber  
   """  
   Given I landed in the homepage   
@@ -214,7 +215,7 @@ Sub-steps can also have macro arguments.
   And I fill in "Password" with "<password>"  
   And I click "Sign in"  
   """  
-``` 
+```
 
 ### Using (invoking) a macro-step ###
 A macro-step can only be invoked after its definition has been read by Cucumber.  
@@ -226,7 +227,7 @@ The syntax rules for using a given macro-step in a scenario are pretty straightf
 Consider the following macro-step definition:  
 
 ```cucumber
-  Given I define the step "When I [log in as <userid>]" to mean: 
+  Given I define the step "When I [log in as <userid>]" to mean:
   """
   # Sub-steps come here...
   """
@@ -234,7 +235,7 @@ Consider the following macro-step definition:
 
 Its quoted sentence is ```"When I [log in as <userid>]"```, therefore
  the macro-step can be invoked in a scenario like this:  
- 
+
 ```cucumber
   Given I do this ...
   When I [log in as "jdoe"]
@@ -245,7 +246,7 @@ Its quoted sentence is ```"When I [log in as <userid>]"```, therefore
 Here is another -partial- macro-step definition:  
 
 ```cucumber
-  Given I define the step "When I [travel from <origin> to <destination> via <stop>]" to mean: 
+  Given I define the step "When I [travel from <origin> to <destination> via <stop>]" to mean:
   """
   # Sub-steps come here...
   """
@@ -293,17 +294,17 @@ This step can be used like this:
   |city| Old White Castle|  
   |postcode|JK345|  
 ```
-  
+
 Here are few observations worth noticing:   
 - The data table has two columns.  
 - Each row is of the form: |argument name| actual value|. For instance, the argument _street_address_ takes
 the value "Main Street, 22".  
-- Data rows don't have to follow strictly the order of the arguments in the sub-step sequence. 
+- Data rows don't have to follow strictly the order of the arguments in the sub-step sequence.
 
 ## Macro-step arguments ##
 
 ### Argument names ###
-In line with most computer languages, Macros4Cuke accepts argument names containing alphanumeric characters and 
+In line with most computer languages, Macros4Cuke accepts argument names containing alphanumeric characters and
 underscores.  
 In fact, the only characters that are not allowed in argument names are the following punctuation or delimiting
 signs:  
@@ -315,7 +316,7 @@ An argument appearing in the phrase MUST always be bound to a value at the step
 Taking again a previous example of a -partial- macro-step definition:  
 
 ```cucumber
-  Given I define the step "When I [travel from <origin> to <destination> via <stop>]" to mean: 
+  Given I define the step "When I [travel from <origin> to <destination> via <stop>]" to mean:
   """
   # Sub-steps come here...
   """
@@ -334,7 +335,7 @@ The next invokation is syntactically correct for Macros4Cuke:
   When I [travel from "San Francisco" to "" via "Las Vegas"]
 ```
 
-The _destination_ argument gets an empty text as actual value. 
+The _destination_ argument gets an empty text as actual value.
 
 For any argument that can receive a value through a data table, three situations can occur:  
 1. A row for that argument together with a text value are specified at invokation. The argument is bound to that text value.  
@@ -361,7 +362,7 @@ Consider the following attempt of a macro-step definition:
 ```
 
 This will result in an error. The issue is caused by the nesting of triple quotes:
-Cucumber simply doesn't allow this. In fact, the error is reported by [Gherkin](https://github.com/cucumber/gherkin), 
+Cucumber simply doesn't allow this. In fact, the error is reported by [Gherkin](https://github.com/cucumber/gherkin),
 a component used by Cucumber.  
 As Gherkin has other [issues](https://github.com/cucumber/gherkin/issues/124) with docstrings, we
 need a workaround today until the fixes are applied.  
@@ -387,8 +388,8 @@ Thus to make the previous example work, one must change it like follows:
 
 ## Conditional sections in substeps. ##
 To make the macros more flexible, it is possible to define conditional sections in the substep sequence.  
-The general pattern for the conditional section is: 
- 
+The general pattern for the conditional section is:
+
 ```cucumber
   <?foobar>
   substep1
@@ -423,7 +424,7 @@ Consider the following example:
 ```
 
 When invoked like this:
-  
+
 ```cucumber
   When I [fill in the form with]:
   |firstname     |Alice|
@@ -454,7 +455,7 @@ the email macro argument.
 
 
 A typical use case for conditional sections is to prevent the execution of one or more steps in
-absence of a given data item. This simulates, for instance, the behaviour of a user that skips 
+absence of a given data item. This simulates, for instance, the behaviour of a user that skips
 one or more widgets in a page/screen. From a user interface testing viewpoint, entering an empty
 text in an entry field may be noticeably different than skipping that same entry field.
 Think of specific UI-events that can trigger some special system response.
@@ -480,7 +481,7 @@ This specialized step has the following syntax:
 ```
 
 Where `all_macros.feature` is a feature file that will be generated when Cucumber
-terminates. The resulting feature file lists all the macros (one per scenario) in 
+terminates. The resulting feature file lists all the macros (one per scenario) in
 the familiar Gherkin syntax. The file is placed in the current directory (i.e. the directory where
 Cucumber was launched).
 
@@ -488,12 +489,12 @@ Cucumber was launched).
 
 ## A word on Step Argument Transforms##
 Cucumber provides a handy facility that helps to convert implicitly the values of step arguments.
-A first description of this lesser-known functionality is available at 
+A first description of this lesser-known functionality is available at
 [Step Argument Transforms] (https://github.com/cucumber/cucumber/wiki/Step-Argument-Transforms).  
 Does Macros4Cuke provide such a facility for its own macro-step arguments?  
 The answer is no: if macro-steps had their own kind of transformations, then these would have interfere with the ones defined directly in Cucumber.
 In fact, Cucumber will happily apply transformations on any step, including the macro definition steps and the
-steps invoking macros. Stated otherwise, all the rules pertaining to the Step Argument Transforms work as usual. Or almost. 
+steps invoking macros. Stated otherwise, all the rules pertaining to the Step Argument Transforms work as usual. Or almost.
 There is one very specific case where Cucumber behaves slightly differently: the transforms aren't applied when a sub-step is executed.
 Internally, Macros4Cuke calls the `Cucumber::RbSupport::RbWorld::#steps` method that allows to run a Gherkin snippet (the substeps),
 and it appears that this method does not trigger the transforms. In practice, this doesn't prevent the use of transforms together
@@ -503,7 +504,7 @@ with Macros4Cuke. In the vast majority of cases both will work fine as expected.
 ## FAQ ##
 __Q__: Can I define a macro in one scenario and invoke it in another scenario in the same feature file?  
 __A__: Yes. Once a macro is defined in a feature file it can be invoked in any scenario that follows the definition.  
-In fact, the macro can be invoked in any scenario from any feature file, provided the invokation takes place _after_ the 
+In fact, the macro can be invoked in any scenario from any feature file, provided the invokation takes place _after_ the
 macro definition.  
 
 __Q__: So, a macro can be shared between multiple files.  
@@ -518,7 +519,7 @@ __Q__: Can I define a macro-step in a `Background` section?
 __A__: No. Here is why: every step from the Background section is executed in each scenario (outline).
 If a macro were defined in the Background, then the macro definition will occur multiple times, which is
  flagged as an error by Macros4Cuke.  
- 
+
 __Q__: Can I define a macro-step in a `Scenario Outline`?  
 __A__: No, if the scenario outline has multiple rows then an error will occur. Bear in mind,
 that steps in a scenario outline are repeating n times, n being the number of rows in the example table.
@@ -533,7 +534,7 @@ __A__: Yes. As a macro-step can be invoked multiple times.
 ## Changelog
 
 Macros4Cuke's changelog is available [here](CHANGELOG.md).
- 
+
 ## More resources:
 -   [**Detailed CI status**](https://travis-ci.org/famished-tiger/Macros4Cuke)
 -   [**Suggest an improvement**](https://github.com/famished-tiger/Macros4Cuke/issues)
@@ -550,7 +551,7 @@ In addition __Macros4Cuke__ allows advanced users to craft their own steps witho
 This last argument becomes important in the context of user acceptance testing, a domain where the assumption that
  every tester is also Rubyist is -alas!- far from the truth.
 
- 
+
 Macros with Cucumber is a hot topic, so it is good to know what other people say about it:  
 [Support for Macros] (https://github.com/cucumber/gherkin/issues/178)  
 [Substeps - macro request for the nth time] (http://grokbase.com/t/gg/cukes/133ey063b8/cucumber-substeps-macro-request-for-the-nth-time)
@@ -558,4 +559,4 @@ Macros with Cucumber is a hot topic, so it is good to know what other people say
 
 Copyright
 ---------
-Copyright (c) 2014-2016, Dimitri Geshef. Macros4Cuke is released under the MIT License see [LICENSE.txt](https://github.com/famished-tiger/Macros4Cuke/blob/master/LICENSE.txt) for details.
+Copyright (c) 2014-2017, Dimitri Geshef. Macros4Cuke is released under the MIT License see [LICENSE.txt](https://github.com/famished-tiger/Macros4Cuke/blob/master/LICENSE.txt) for details.

data/Rakefile

@@ -1,54 +1,54 @@
-require 'rubygems'
-require_relative './lib/macros4cuke/constants'
-
-namespace :gem do
-desc 'Push the gem to rubygems.org'
-task :push do
-  system("gem push macros4cuke-#{Macros4Cuke::Version}.gem")
-end
-end # namespace
-
-# Testing-specific tasks
-
-# Cucumber as testing tool
-require 'cucumber/rake/task'
-# UGLY workaround for bug in Cucumber's rake task
-if Gem::VERSION[0].to_i >= 2 && Cucumber::VERSION <= '1.3.2'
-  # Monkey-patch a buggy method
-  module Cucumber
-    module Rake
-      class Task
-        class ForkedCucumberRunner
-          def gem_available?(gemname)
-            if Gem::VERSION[0].to_i >= 2 
-              gem_available_new_rubygems?(gemname)
-            else
-              gem_available_old_rubygems?(gemname)
-            end
-          end  
-        end # class
-      end # class
-    end # module
-  end # module
-end
-
-Cucumber::Rake::Task.new do |_|
-end
-
-# RSpec as testing tool
-require 'rspec/core/rake_task'
-desc 'Run RSpec'
-RSpec::Core::RakeTask.new do |spec|
-  spec.pattern = 'spec/**/*_spec.rb'
-end
-
-
-# Combine RSpec and Cucumber tests
-desc 'Run tests, with RSpec and Cucumber'
-task test: [:spec, :cucumber]
-
-
-# Default rake task
-task default: :test
-
-# End of file
+require 'rubygems'
+require_relative './lib/macros4cuke/constants'
+
+namespace :gem do
+desc 'Push the gem to rubygems.org'
+task :push do
+  system("gem push macros4cuke-#{Macros4Cuke::Version}.gem")
+end
+end # namespace
+
+# Testing-specific tasks
+
+# Cucumber as testing tool
+require 'cucumber/rake/task'
+# UGLY workaround for bug in Cucumber's rake task
+if Gem::VERSION[0].to_i >= 2 && Cucumber::VERSION <= '1.3.2'
+  # Monkey-patch a buggy method
+  module Cucumber
+    module Rake
+      class Task
+        class ForkedCucumberRunner
+          def gem_available?(gemname)
+            if Gem::VERSION[0].to_i >= 2 
+              gem_available_new_rubygems?(gemname)
+            else
+              gem_available_old_rubygems?(gemname)
+            end
+          end  
+        end # class
+      end # class
+    end # module
+  end # module
+end
+
+Cucumber::Rake::Task.new do |_|
+end
+
+# RSpec as testing tool
+require 'rspec/core/rake_task'
+desc 'Run RSpec'
+RSpec::Core::RakeTask.new do |spec|
+  spec.pattern = 'spec/**/*_spec.rb'
+end
+
+
+# Combine RSpec and Cucumber tests
+desc 'Run tests, with RSpec and Cucumber'
+task test: [:spec, :cucumber]
+
+
+# Default rake task
+task default: :test
+
+# End of file

data/appveyor.yml

@@ -0,0 +1,20 @@
+version: '{build}'
+max_jobs: 3
+environment:
+  matrix:
+  - Ruby_version: 200
+  - Ruby_version: 200-x64
+  - Ruby_version: 21
+  - Ruby_version: 21-x64
+  - Ruby_version: 22
+  - Ruby_version: 22-x64
+  - Ruby_version: 23
+  - Ruby_version: 23-x64
+install:
+- cmd: >-
+    SET PATH=C:\Ruby%Ruby_version%\bin;%PATH%
+
+    bundle install --retry=3 --clean
+build: off
+test_script:
+- cmd: bundle exec rake

data/bin/macros4cuke

@@ -1,15 +1,14 @@
-#!/usr/bin/env ruby
-# File: macros4cuke
-# The 'executable' of the Macros4Cuke library.
-
-mydir = File.dirname(__FILE__)
-lib_dir = mydir + '/../lib'
-$LOAD_PATH.unshift lib_dir unless $LOAD_PATH.include?(lib_dir)
-
-require 'macros4cuke' # Load the Cukedep::Application class	
-
-# The application's entry point
-app = Macros4Cuke::Application.new
-app.run!(ARGV.dup)
-
-# End of file
+#!/usr/bin/env ruby
+# File: macros4cuke
+# The 'executable' of the Macros4Cuke library.
+mydir = File.dirname(__FILE__)
+lib_dir = mydir + '/../lib'
+$LOAD_PATH.unshift lib_dir unless $LOAD_PATH.include?(lib_dir)
+
+require 'macros4cuke' # Load the Cukedep::Application class	
+
+# The application's entry point
+app = Macros4Cuke::Application.new
+app.run!(ARGV.dup)
+
+# End of file

data/lib/macro_steps.rb

@@ -34,7 +34,7 @@ end
 #  When I [log in as "guest"]
 #
 When(/^I \[((?:[^\\\]]|\\.)+)\]$/) do |macro_phrase|
-  invoke_macro(macro_phrase)  # This will call the macro with the given phrase
+  invoke_macro(macro_phrase) # This will call the macro with the given phrase
 end
 
 
@@ -47,9 +47,9 @@ end
 #  |password|unguessable|
 When(/^I \[([^\]]+)\]:$/) do |macro_phrase, table_argument|
   # Ensure that the second argument is of the correct type
-  #unless table_argument.is_a?(Cucumber::Ast::Table)
+  # unless table_argument.is_a?(Cucumber::Ast::Table)
   unless table_argument.is_a?(Cucumber::MultilineArgument::DataTable)
-    fail(Macros4Cuke::DataTableNotFound.new(macro_phrase))
+    raise(Macros4Cuke::DataTableNotFound.new(macro_phrase))
   end
 
   # This will call the macro with the given phrase.

data/lib/macros4cuke/application.rb

@@ -9,8 +9,6 @@ module Macros4Cuke # Module used as a namespace
 class Application
   attr_reader(:options)
 
-  public
-
   def initialize()
     @options = {}
   end
@@ -43,7 +41,7 @@ class Application
     destination = prefix + aPath.to_s + '/' + file_name + '.rb'
 
     begin
-      fail SupportFileExists.new(destination) if File.exist?(destination)
+      raise SupportFileExists.new(destination) if File.exist?(destination)
 
       template_pathname =
         Macros4Cuke::RootDir + 'templates/use_macros4cuke.erb'