cucumber 2.99.0 → 3.0.0

data/features/docs/extending_cucumber/custom_formatter.feature

@@ -19,7 +19,7 @@ Feature: Custom Formatter
         class Formatter
           def initialize(config)
             @io = config.out_stream
-            config.on_event Cucumber::Events::BeforeTestCase do |event|
+            config.on_event :test_case_started do |event|
               print_test_case_name(event.test_case)
             end
           end
@@ -41,33 +41,25 @@ Feature: Custom Formatter
 
       """
 
-  Scenario: Implement v2.0 formatter methods
-    Note that this method is likely to be deprecated in favour of events - see above.
-
+  Scenario: Pass custom config to your formatter from the CLI
     Given a file named "features/support/custom_formatter.rb" with:
       """
       module MyCustom
         class Formatter
-          def initialize(config)
+          def initialize(config, options)
             @io = config.out_stream
-          end
-
-          def before_test_case(test_case)
-            feature = test_case.source.first
-            scenario = test_case.source.last
-            @io.puts feature.short_name.upcase
-            @io.puts "  #{scenario.name.upcase}"
+            config.on_event :test_run_finished do |event|
+              @io.print options.inspect
+            end
           end
         end
       end
       """
-    When I run `cucumber features/f.feature --format MyCustom::Formatter`
+    When I run `cucumber features/f.feature --format MyCustom::Formatter,foo=bar,one=two`
     Then it should pass with exactly:
-      """
-      I'LL USE MY OWN
-        JUST PRINT ME
-
-      """
+    """
+    {"foo"=>"bar", "one"=>"two"}
+    """
 
   Scenario: Use the legacy API
     This is deprecated and should no longer be used.
@@ -93,38 +85,10 @@ Feature: Custom Formatter
     When I run `cucumber features/f.feature --format MyCustom::LegacyFormatter`
     Then it should pass with exactly:
       """
-      I'LL USE MY OWN
-        JUST PRINT ME
-
-      """
-
-  Scenario: Use both old and new
-    You can use a specific shim to opt-in to both APIs at once.
-
-    Given a file named "features/support/custom_mixed_formatter.rb" with:
-      """
-      module MyCustom
-        class MixedFormatter
-
-          def initialize(runtime, io, options)
-            @io = io
-          end
-
-          def before_test_case(test_case)
-            feature = test_case.source.first
-            @io.puts feature.short_name.upcase
-          end
+      WARNING: The formatter MyCustom::LegacyFormatter is using the deprecated formatter API which will be removed in v4.0 of Cucumber.
 
-          def scenario_name(keyword, name, file_colon_line, source_indent)
-            @io.puts "  #{name.upcase}"
-          end
-        end
-      end
-      """
-    When I run `cucumber features/f.feature --format MyCustom::MixedFormatter`
-    Then it should pass with exactly:
-      """
       I'LL USE MY OWN
         JUST PRINT ME
 
       """
+

data/features/docs/formatters/json_formatter.feature

@@ -104,7 +104,7 @@ Feature: JSON output formatter
       """
 
   # Need to investigate why this won't pass in-process. error_message doesn't get det?
-  @spawn
+  @spawn @todo-windows
   Scenario: one feature, one passing scenario, one failing scenario
     When I run `cucumber --format json features/one_passing_one_failing.feature`
     Then it should fail with JSON:
@@ -195,7 +195,7 @@ Feature: JSON output formatter
 
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: one feature, one passing scenario, one failing scenario with prettyfied json
     When I run `cucumber --format json_pretty features/one_passing_one_failing.feature`
     Then it should fail with JSON:
@@ -395,7 +395,7 @@ Feature: JSON output formatter
 
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: scenario outline
     When I run `cucumber --format json features/outline.feature`
     Then it should fail with JSON:
@@ -541,7 +541,7 @@ Feature: JSON output formatter
 
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: scenario outline expanded
     When I run `cucumber --expand --format json features/outline.feature`
     Then it should fail with JSON:

data/features/docs/formatters/junit_formatter.feature

@@ -59,7 +59,7 @@ Feature: JUnit output formatter
             | is undefined |
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: one feature, one passing scenario, one failing scenario
     When I run `cucumber --format junit --out tmp/ features/one_passing_one_failing.feature`
     Then it should fail with:
@@ -101,7 +101,7 @@ Feature: JUnit output formatter
 
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: one feature in a subdirectory, one passing scenario, one failing scenario
     When I run `cucumber --format junit --out tmp/ features/some_subdirectory/one_passing_one_failing.feature --require features`
     Then it should fail with:
@@ -225,7 +225,8 @@ Feature: JUnit output formatter
       </testsuite>
 
       """
-    
+
+  @todo-windows
   Scenario: run all features
     When I run `cucumber --format junit --out tmp/ features`
     Then it should fail with:
@@ -246,7 +247,7 @@ can't convert .* into String \(TypeError\)
 You *must* specify --out DIR for the junit formatter
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: strict mode, one feature, one scenario outline, four examples: one passing, one failing, one pending, one undefined
     When I run `cucumber --strict --format junit --out tmp/ features/scenario_outline.feature`
     Then it should fail with:
@@ -328,7 +329,7 @@ You *must* specify --out DIR for the junit formatter
 
       """ 
 
-  @spawn
+  @spawn @todo-windows
   Scenario: strict mode with --expand option, one feature, one scenario outline, four examples: one passing, one failing, one pending, one undefined
     When I run `cucumber --strict --expand --format junit --out tmp/ features/scenario_outline.feature`
     Then it should fail with exactly:
@@ -410,7 +411,7 @@ You *must* specify --out DIR for the junit formatter
 
       """ 
 
-  @spawn
+  @spawn @todo-windows
   Scenario: run test cases from different features interweaved
     When I run `cucumber --format junit --out tmp/ features/one_passing_one_failing.feature:3 features/pending.feature:3 features/one_passing_one_failing.feature:6`
     Then it should fail with:

data/features/docs/formatters/pretty_formatter.feature

@@ -17,6 +17,7 @@ Feature: Pretty output formatter
     When I run `cucumber features/scenario_outline_with_undefined_steps.feature --format pretty --expand `
     Then it should pass
 
+  @todo-windows
   Scenario: when using a profile the output should include 'Using the default profile...'
     And a file named "cucumber.yml" with:
     """

data/features/docs/formatters/progress_formatter.feature

@@ -17,6 +17,7 @@ Feature: Progress output formatter
     When I run `cucumber features/scenario_outline_with_undefined_steps.feature --format progress --expand `
     Then it should pass
 
+  @todo-windows
   Scenario: when using a profile the output should include 'Using the default profile...'
     And a file named "cucumber.yml" with:
     """

data/features/docs/formatters/rerun_formatter.feature

@@ -18,6 +18,7 @@ Feature: Rerun formatter
   Background:
     Given the standard step definitions
 
+  @todo-windows
   Scenario: Exit code is zero
     Given a file named "features/mixed.feature" with:
       """
@@ -70,6 +71,7 @@ Feature: Rerun formatter
       """
       """
 
+  @todo-windows
   Scenario: Exit code is not zero, regular scenario
     Given a file named "features/mixed.feature" with:
       """

data/features/docs/formatters/summary_formatter.feature

@@ -0,0 +1,35 @@
+Feature: Spec formatter
+
+  This formatter mimics the output from tools like RSpec or Mocha, giving an 
+  overview of each feature and scenario but omitting the steps.
+
+  Background:
+    Given the standard step definitions
+
+  @todo-windows
+  Scenario: A couple of scenarios
+    Given a file named "features/test.feature" with:
+    """
+    Feature: Test
+      Scenario: Passing
+        Given this step passes
+
+      Scenario: Failing
+        Given this step fails
+    """
+    When I run `cucumber --format summary`
+    Then it should fail with exactly:
+    """
+    Test
+      Passing ✓
+      Failing ✗
+
+    Failing Scenarios:
+    cucumber features/test.feature:5 # Scenario: Failing
+
+    2 scenarios (1 failed, 1 passed)
+    2 steps (1 failed, 1 passed)
+    0m0.012s
+
+    """
+

data/features/docs/formatters/usage_formatter.feature

@@ -30,6 +30,7 @@ Feature: Usage formatter
       Given(/D/) { }
       """
 
+  @todo-windows
   Scenario: Run with --format usage
     When I run `cucumber -f usage --dry-run`
     Then it should pass with exactly:
@@ -55,6 +56,7 @@ Feature: Usage formatter
 
       """
 
+  @todo-windows
   Scenario: Run with --expand --format usage
     When I run `cucumber -x -f usage --dry-run`
     Then it should pass with exactly:
@@ -80,6 +82,7 @@ Feature: Usage formatter
 
       """
 
+    @todo-windows
     Scenario: Run with --format stepdefs
       When I run `cucumber -f stepdefs --dry-run`
       Then it should pass with exactly:

data/features/docs/getting_started.feature

@@ -3,7 +3,7 @@ Feature: Getting started
   To get started, just open a command prompt in an empty directory and run 
   `cucumber`. You'll be prompted for what to do next.
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Run Cucumber in an empty directory
     Given a directory without standard Cucumber project directory structure
     When I run `cucumber`
@@ -12,6 +12,7 @@ Feature: Getting started
       No such file or directory - features. You can use `cucumber --init` to get started.
       """
 
+  @todo-windows
   Scenario: Accidentally run Cucumber in a folder with Ruby files in it.
     Given a directory without standard Cucumber project directory structure
     And a file named "should_not_load.rb" with:

data/features/docs/gherkin/background.feature

@@ -295,7 +295,7 @@ Feature: Background
 
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: run a feature with a background that fails
     When I run `cucumber -q features/failing_background.feature`
     Then it should fail with exactly:
@@ -324,7 +324,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: run a feature with scenario outlines that has a background that fails
     When I run `cucumber -q features/scenario_outline_failing_background.feature`
     Then it should fail with exactly:
@@ -383,7 +383,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: background passes with first scenario but fails with second
     When I run `cucumber -q features/failing_background_after_success.feature`
     Then it should fail with exactly:
@@ -412,7 +412,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: background passes with first outline scenario but fails with second
     When I run `cucumber -q features/failing_background_after_success_outline.feature`
     Then it should fail with exactly:
@@ -448,7 +448,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: background passes with first outline scenario but fails with second (--expand)
     When I run `cucumber -x -q features/failing_background_after_success_outline.feature`
     Then it should fail with exactly:

data/features/docs/gherkin/doc_strings.feature

@@ -29,6 +29,7 @@ Feature: Doc strings
   You can read the content type from the argument passed into your step definition, as shown
   in the example below.
 
+  @todo-windows
   Scenario: Plain text Docstring
     Given a scenario with a step that looks like this:
       """gherkin
@@ -53,6 +54,7 @@ Feature: Doc strings
       Three
       """
 
+  @todo-windows
   Scenario: DocString passed as String
     Given a scenario with a step that looks like this:
       """gherkin

data/features/docs/gherkin/expand_option_for_outlines.feature

@@ -4,6 +4,7 @@ Feature: Scenario outlines --expand option
   for some people to understand scenarios, Cucumber will expand examples
   in outlines if you add the `--expand` option when running them.
 
+  @todo-windows
   Scenario:
     Given a file named "features/test.feature" with:
       """

data/features/docs/gherkin/outlines.feature

@@ -43,14 +43,13 @@ Feature: Scenario outlines
       Given(/^failing without a table$/) { raise RuntimeError }
       """
 
+  @todo-windows
   Scenario: Run scenario outline with filtering on outline name
     When I run `cucumber -q features/outline_sample.feature`
     Then it should fail with:
       """
       Feature: Outline Sample
 
-        Scenario: I have no steps
-
         Scenario Outline: Test state
           Given <state> without a table
           Given <other_state> without a table
@@ -72,10 +71,11 @@ Feature: Scenario outlines
       Failing Scenarios:
       cucumber features/outline_sample.feature:12
 
-      5 scenarios (1 failed, 1 undefined, 3 passed)
+      4 scenarios (1 failed, 1 undefined, 2 passed)
       8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
       """
 
+  @todo-windows
   Scenario: Run scenario outline steps only
     When I run `cucumber -q features/outline_sample.feature:7`
     Then it should fail with:
@@ -108,6 +108,7 @@ Feature: Scenario outlines
 
       """
 
+  @todo-windows
   Scenario: Run single failing scenario outline table row
     When I run `cucumber -q features/outline_sample.feature:12`
     Then it should fail with:
@@ -134,6 +135,7 @@ Feature: Scenario outlines
 
       """
 
+  @todo-windows
   Scenario: Run all with progress formatter
     When I run `cucumber -q --format progress features/outline_sample.feature`
     Then it should fail with exactly:
@@ -150,7 +152,7 @@ Feature: Scenario outlines
       Failing Scenarios:
       cucumber features/outline_sample.feature:12
 
-      5 scenarios (1 failed, 1 undefined, 3 passed)
+      4 scenarios (1 failed, 1 undefined, 2 passed)
       8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
 
       """

data/features/docs/gherkin/unicode_table.feature

@@ -1,10 +1,11 @@
-@spawn
+@spawn @wip-jruby
 Feature: Unicode in tables
 
   You are free to use unicode in your tables: we've taken care to
   ensure that the tables are properly aligned so that your output is as
   readable as possible.
 
+  @todo-windows
   Scenario:
     Given a file named "features/unicode.feature" with:
       """

data/features/docs/gherkin/using_descriptions.feature

@@ -1,3 +1,4 @@
+@todo-windows
 Feature: Using descriptions to give features context
 
   When writing your feature files its very helpful to use description

data/features/docs/gherkin/using_star_notation.feature

@@ -31,7 +31,7 @@ Feature: Using star notation instead of Given/When/Then
       """
       You can implement step definitions for undefined steps with these snippets:
 
-      Given(/^I have some cukes$/) do
+      Given("I have some cukes") do
         pending # Write code here that turns the phrase above into concrete actions
       end
       """

data/features/docs/post_configuration_hook.feature

@@ -4,27 +4,11 @@ Feature: Post Configuration Hook [#423]
   As a developer
   I want to manipulate the Cucumber configuration after it has been created
 
-  # Fails on Travis under JRuby
-  @spawn
-  @wip-jruby
-  Scenario: Using options directly gets a deprecation warning
-    Given a file named "features/support/env.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.options[:blah]
-      end
-      """
-    When I run `cucumber features`
-    Then the stderr should contain:
-      """
-      Deprecated
-      """
-
   Scenario: Changing the output format
     Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
-        config.formats << ['html', config.out_stream]
+        config.formats << ['html', {}, config.out_stream]
       end
       """
     When I run `cucumber features`

data/features/docs/rake_task.feature

@@ -16,6 +16,7 @@ Feature: Rake task
           Given I don't want this ran
       """
 
+  @todo-windows
   Scenario: rake task with a defined profile
     Given the following profile is defined:
       """
@@ -41,6 +42,7 @@ Feature: Rake task
       1 step (1 undefined)
       """
 
+  @todo-windows
   Scenario: rake task without a profile
     Given a file named "Rakefile" with:
       """
@@ -65,6 +67,7 @@ Feature: Rake task
       2 steps (2 undefined)
       """
 
+  @todo-windows
   Scenario: rake task with a defined profile and cucumber_opts
     Given the following profile is defined:
       """
@@ -91,6 +94,7 @@ Feature: Rake task
       1 step (1 undefined)
       """
 
+  @todo-windows
   Scenario: respect requires
     Given an empty file named "features/support/env.rb"
     And an empty file named "features/support/dont_require_me.rb"
@@ -114,6 +118,7 @@ Feature: Rake task
         * features/support/dont_require_me.rb
       """
 
+  @todo-windows
   Scenario: feature files with spaces
     Given a file named "features/spaces are nasty.feature" with:
        """

data/features/docs/raketask.feature

@@ -1,4 +1,4 @@
-@spawn
+@spawn @wip-jruby
 Feature: Raketask
 
   In order to use cucumber's rake task
@@ -34,10 +34,12 @@ Feature: Raketask
         end
       """
 
+  @todo-windows
   Scenario: Passing feature
     When I run `bundle exec rake pass`
     Then the exit status should be 0
 
+  @todo-windows
   Scenario: Failing feature
     When I run `bundle exec rake fail`
     Then the exit status should be 1

data/features/docs/work_in_progress.feature

@@ -37,6 +37,7 @@ Feature: Cucumber --work-in-progress switch
             | passes |
       """
 
+  @todo-windows
   Scenario: Pass with Failing Scenarios
     When I run `cucumber -q -w -t @failing features/wip.feature`
     Then the stderr should not contain anything
@@ -63,6 +64,7 @@ Feature: Cucumber --work-in-progress switch
 
       """
 
+  @todo-windows
   Scenario: Pass with Undefined Scenarios
     When I run `cucumber -q -w -t @undefined features/wip.feature`
     Then it should pass with:
@@ -82,6 +84,7 @@ Feature: Cucumber --work-in-progress switch
 
       """
 
+  @todo-windows
   Scenario: Pass with Undefined Scenarios
     When I run `cucumber -q -w -t @pending features/wip.feature`
     Then it should pass with:
@@ -104,6 +107,7 @@ Feature: Cucumber --work-in-progress switch
 
       """
 
+  @todo-windows
   Scenario: Fail with Passing Scenarios
     When I run `cucumber -q -w -t @passing features/wip.feature`
     Then it should fail with:
@@ -124,9 +128,9 @@ Feature: Cucumber --work-in-progress switch
 
       features/wip.feature:15:in `Scenario: Passing'
 
-
       """
 
+  @todo-windows
   Scenario: Fail with Passing Scenario Outline
     When I run `cucumber -q -w features/passing_outline.feature`
     Then it should fail with:
@@ -150,5 +154,4 @@ Feature: Cucumber --work-in-progress switch
 
       features/passing_outline.feature:7:in `Scenario Outline: Passing, Examples (#1)'
 
-
       """

data/features/docs/writing_support_code/after_step_hooks.feature

@@ -12,6 +12,7 @@ Feature: AfterStep Hooks
           Given this step passes
       """
 
+  @todo-windows
   Scenario: Access Test Step object in AfterStep Block
     Given a file named "features/support/env.rb" with:
       """
@@ -32,6 +33,7 @@ Feature: AfterStep Hooks
 
       """
 
+  @todo-windows
   Scenario: An AfterStep with one named argument receives only the result
     Given a file named "features/support/env.rb" with:
       """
@@ -50,4 +52,4 @@ Feature: AfterStep Hooks
       1 scenario (1 passed)
       1 step (1 passed)
 
-      """
+      """

data/features/docs/writing_support_code/around_hooks.feature

@@ -5,6 +5,7 @@ Feature: Around hooks
   that provide only a block syntax for transactions, Cucumber should
   permit definition of Around hooks.
 
+  @todo-windows
   Scenario: A single Around hook
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -38,6 +39,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Multiple Around hooks
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -84,6 +86,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Mixing Around, Before, and After hooks
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -131,6 +134,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Around hooks with tags
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -185,6 +189,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Around hooks with scenario outlines
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -228,6 +233,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Around Hooks and the Custom World
     Given a file named "features/step_definitions/steps.rb" with:
       """

data/features/docs/writing_support_code/before_hook.feature

@@ -1,5 +1,6 @@
 Feature: Before Hook
 
+  @todo-windows
   Scenario: Examine names of scenario and feature
     Given a file named "features/foo.feature" with:
       """