cucumber 3.0.0.pre.1 → 3.0.0.pre.2

data/features/docs/events/test_case_starting_event.feature

@@ -0,0 +1,54 @@
+@wip
+Feature: Test Case Starting Event
+
+  This event is fired just before each scenario or scenario outline example row
+  (generally named a Test Case) starts to be executed. This event is read-only.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/TestCaseStarting) for more information about the data available on this event and the result object.
+
+  Background:
+    Given the standard step definitions
+    And a file named "features/test.feature" with:
+      """
+      @feature
+      Feature: A feature
+
+        @scenario
+        Scenario: A passing scenario
+          Given this is a step
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      stdout = nil
+      AfterConfiguration do |config|
+        stdout = config.out_stream # make sure all the `puts` calls can write to the same output
+        config.on_event :test_case_starting do |event|
+          stdout.puts "before"
+          stdout.puts event.test_case.tags.map(&:name)
+        end
+        config.on_event :test_case_finished do |event|
+          stdout.puts "after"
+        end
+      end
+
+      Given(/this is a step/) do 
+      end
+
+      """
+
+  Scenario: Run the test case
+    When I run `cucumber -q`
+    Then it should pass with:
+      """
+      before
+      @feature
+      @scenario
+      @feature
+      Feature: A feature
+      
+        @scenario
+        Scenario: A passing scenario
+          Given this is a step
+      after
+      """
+

data/features/docs/events/test_run_finished_event.feature

@@ -0,0 +1,40 @@
+Feature: Test Run Finished
+
+  This event is fired after all the test cases have been executed.
+
+  Typically, a formatter would use this to print out summary information.
+
+  At the moment this event contains no data, but it could be extended 
+  in the future to carry the summary information for the convenience 
+  of formatter authors.
+
+  Background:
+    Given the standard step definitions
+    And a file named "features/test.feature" with:
+      """
+      Feature: A feature
+
+        Scenario: A passing scenario
+          Given this is a step
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      class MyFormatter
+        def initialize(config)
+          config.on_event :test_case_finished do
+            config.out_stream.puts "test case finished"
+          end
+          config.on_event :test_run_finished do
+            config.out_stream.puts "the end"
+          end
+        end
+      end
+      """
+
+  Scenario: Run the test case
+    When I run `cucumber -q -f MyFormatter`
+    Then it should pass with:
+      """
+      test case finished
+      the end
+      """

data/features/docs/events/test_run_starting_event.feature

@@ -0,0 +1,41 @@
+Feature: Test Run Starting Event
+
+  This event is fired once all test cases have been filtered, just before
+  the first one is executed.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/TestRunStarting) for more information about the data available on this event.
+
+  Background:
+    Given the standard step definitions
+    And a file named "features/foo.feature" with:
+      """
+      Feature: Foo
+        Scenario:
+          Given a passing step
+      """
+    And a file named "features/bar.feature" with:
+      """
+      Feature: Foo
+        Scenario:
+          Given a passing step
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.on_event :test_run_starting do |event|
+          config.out_stream.puts "test run starting"
+          config.out_stream.puts event.test_cases.map(&:location)
+        end
+      end
+      """
+
+  @todo-windows
+  Scenario: Run the test case
+    When I run `cucumber -q`
+    Then it should pass with:
+      """
+      test run starting
+      features/bar.feature:2
+      features/foo.feature:2
+      """
+

data/features/docs/events/test_step_finished_event.feature

@@ -0,0 +1,47 @@
+Feature: Test Step Finished Event
+
+  This event is fired after each step in a scenario or scenario outline example 
+  (generally named a Test Step) has finished executing. You can use the event to learn about the 
+  result of the test step.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/TestStepFinished) for more information about the data available on this event and the result object.
+
+  Background:
+    Given the standard step definitions
+    And a file named "features/test.feature" with:
+      """
+      Feature: A feature
+
+        @pass
+        Scenario: A passing scenario
+          Given this step passes
+
+        @fail
+        Scenario: A failing scenario
+          Given this step fails
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.on_event :test_step_finished do |event|
+          config.out_stream.puts "Test step: #{event.test_step.name}"
+          config.out_stream.puts "The result is: #{event.result}"
+        end
+      end
+      """
+
+  Scenario: Test step passes
+    When I run `cucumber --tags @pass`
+    Then it should pass with:
+      """
+      Test step: this step passes
+      The result is: ✓
+      """
+
+  Scenario: Test step fails
+    When I run `cucumber --tags @fail`
+    Then it should fail with:
+      """
+      Test step: this step fails
+      The result is: ✗
+      """

data/features/docs/events/test_step_starting_event.feature

@@ -0,0 +1,43 @@
+Feature: Test Step Starting Event
+
+  This event is fired just before each step in a scenario or scenario outline example 
+  (generally named a Test Step) starts to be executed. This event is read-only, so there
+  is no way to prevent the test step from running, but you can use it for logging or user
+  notification.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/TestStepStarting) for more information about the data available on this event and the result object.
+
+  Background:
+    Given the standard step definitions
+    And a file named "features/test.feature" with:
+      """
+      Feature: A feature
+
+        Scenario: A passing scenario
+          Given this is a step
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      stdout = nil
+      AfterConfiguration do |config|
+        stdout = config.out_stream # make sure all the `puts` calls can write to the same output
+        config.on_event :test_step_starting do |event|
+          stdout.puts "before"
+        end
+        config.on_event :test_step_finished do |event|
+          stdout.puts "after"
+        end
+      end
+      Given(/this is a step/) do
+        stdout.puts "during"
+      end
+      """
+
+  Scenario: Test step passes
+    When I run `cucumber`
+    Then it should pass with:
+      """
+      before
+      during
+      after
+      """

data/features/docs/exception_in_after_hook.feature

@@ -21,7 +21,7 @@ Feature: Exception in After Block
       end
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Handle Exception in standard scenario step and carry on
     Given a file named "features/naughty_step_in_scenario.feature" with:
       """
@@ -54,7 +54,7 @@ Feature: Exception in After Block
 
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Handle Exception in scenario outline table row and carry on
     Given a file named "features/naughty_step_in_scenario_outline.feature" with:
       """
@@ -100,6 +100,7 @@ Feature: Exception in After Block
 
       """
 
+  @todo-windows
   Scenario: Handle Exception using the progress format
     Given a file named "features/naughty_step_in_scenario.feature" with:
       """

data/features/docs/exception_in_after_step_hook.feature

@@ -21,6 +21,7 @@ Feature: Exception in AfterStep Block
       end
       """
 
+  @todo-windows
   Scenario: Handle Exception in standard scenario step and carry on
     Given a file named "features/naughty_step_in_scenario.feature" with:
       """
@@ -54,6 +55,7 @@ Feature: Exception in AfterStep Block
 
       """
 
+  @todo-windows
   Scenario: Handle Exception in scenario outline table row and carry on
     Given a file named "features/naughty_step_in_scenario_outline.feature" with:
       """

data/features/docs/exception_in_around_hook.feature

@@ -12,6 +12,7 @@ Feature: Exceptions in Around Hooks
   There's another scenario to consider, where the exception occurs after the steps
   have been run. How would we want to report in that case?
 
+  @todo-windows
   Scenario: Exception before the test case is run
     Given the standard step definitions
     And a file named "features/support/env.rb" with:
@@ -44,6 +45,7 @@ Feature: Exceptions in Around Hooks
       
       """
 
+  @todo-windows
   Scenario: Exception after the test case is run
     Given the standard step definitions
     And a file named "features/support/env.rb" with:

data/features/docs/exception_in_before_hook.feature

@@ -14,7 +14,7 @@ Feature: Exception in Before Block
       end
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Handle Exception in standard scenario step and carry on
     Given a file named "features/naughty_step_in_scenario.feature" with:
       """
@@ -41,6 +41,7 @@ Feature: Exception in Before Block
 
       """
 
+  @todo-windows
   Scenario: Handle Exception in Before hook for Scenario with Background
     Given a file named "features/naughty_step_in_before.feature" with:
       """
@@ -74,6 +75,7 @@ Feature: Exception in Before Block
 
       """
 
+  @todo-windows
   Scenario: Handle Exception using the progress format
     Given a file named "features/naughty_step_in_scenario.feature" with:
       """

data/features/docs/extending_cucumber/custom_formatter.feature

@@ -41,7 +41,27 @@ Feature: Custom Formatter
 
       """
 
-  Scenario: Use the legacy API
+  Scenario: Custom config
+    Given a file named "features/support/custom_formatter.rb" with:
+      """
+      module MyCustom
+        class Formatter
+          def initialize(config, options)
+            @io = config.out_stream
+            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,foo=bar,one=two`
+    Then it should pass with exactly:
+    """
+    {"foo"=>"bar", "one"=>"two"}
+    """
+
+ Scenario: Use the legacy API
     This is deprecated and should no longer be used.
 
     Given a file named "features/support/custom_legacy_formatter.rb" with:

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:
     """