cucumber 3.0.0 → 3.1.0

data/features/docs/events/step_activated_event.feature

@@ -1,36 +0,0 @@
-Feature: Step Activated Event
-
-  This event is fired when Cucumber finds a matching definition for a Gherkin step.
-
-  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/StepActivated)
-  for more information about the data available on this event.
-
-  Scenario: Activate a step
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /a step/ do
-        # automation goes here
-      end
-      """
-    And a file named "features/test.feature" with:
-      """
-      Feature:
-        Scenario:
-          Given a step
-      """
-    And a file named "features/support/events.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.on_event :step_activated do |event|
-          config.out_stream.puts "The step: #{event.test_step.location}"
-          config.out_stream.puts "The step definition: #{event.step_match.location}"
-        end
-      end
-      """
-    When I run `cucumber`
-    Then it should pass with:
-      """
-      The step: features/test.feature:3
-      The step definition: features/step_definitions/steps.rb:1
-      """
-

data/features/docs/events/step_definition_registered_event.feature

@@ -1,29 +0,0 @@
-Feature: Step definition registered
-
-  This event is fired when Cucumber loads the user's step definitions. Typically, this is
-  when the `Given /^my step$/ do` methods are called.
-
-  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/StepDefinitionRegistered) for more information about the data available on this event.
-
-  Scenario: Register a new step definition
-    Given the standard step definitions
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /a step/ do
-        # automation goes here
-      end
-      """
-    And a file named "features/support/events.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.on_event :step_definition_registered do |event|
-          config.out_stream.puts "The step definition: #{event.step_definition.location}"
-        end
-      end
-      """
-    When I run `cucumber`
-    Then it should pass with:
-      """
-      The step definition: features/step_definitions/steps.rb:1
-      """
-

data/features/docs/events/test_case_finished_event.feature

@@ -1,35 +0,0 @@
-Feature: Test Case Finished Event
-
-  This event is fired after each scenario or examples table row (generally named a 
-  Test Case) has finished executing. You can use the event to learn about the 
-  result of the test case.
-
-  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/TestCaseFinished) for more information about the data available on this event.
-
-  Scenario: Test case passes
-    Given the standard step definitions
-    And a file named "features/passing.feature" with:
-      """
-      Feature: A feature
-        Scenario: A scenario
-          Given this step passes
-      """
-    And a file named "features/support/events.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.on_event :test_case_finished do |event|
-          config.out_stream.puts "Results"
-          config.out_stream.puts "-------"
-          config.out_stream.puts "Test case: #{event.test_case.name}"
-          config.out_stream.puts "The result is: #{event.result}"
-        end
-      end
-      """
-    When I run `cucumber`
-    Then it should pass with:
-      """
-      Results
-      -------
-      Test case: A scenario
-      The result is: ✓
-      """

data/features/docs/events/test_case_started_event.feature

@@ -1,54 +0,0 @@
-@wip
-Feature: Test Case Started 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/TestCaseStarted) 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_started 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

@@ -1,40 +0,0 @@
-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_started_event.feature

@@ -1,41 +0,0 @@
-Feature: Test Run Started 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/TestRunStarted) 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_started do |event|
-          config.out_stream.puts "test run started"
-          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 started
-      features/bar.feature:2
-      features/foo.feature:2
-      """
-

data/features/docs/events/test_step_finished_event.feature

@@ -1,47 +0,0 @@
-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}"
-          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_started_event.feature

@@ -1,43 +0,0 @@
-Feature: Test Step Started 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/TestStepStarted) 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_started 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

@@ -1,127 +0,0 @@
-Feature: Exception in After Block
-  In order to use custom assertions at the end of each scenario
-  As a developer
-  I want exceptions raised in After blocks to be handled gracefully and reported by the formatters
-
-  Background:
-    Given the standard step definitions
-    And a file named "features/step_definitions/naughty_steps.rb" with:
-      """
-      Given /^this step does something naughty$/ do x=1
-        @naughty = true
-      end
-      """
-    And a file named "features/support/env.rb" with:
-      """
-      class NaughtyScenarioException < Exception; end
-      After do
-        if @naughty
-          raise NaughtyScenarioException.new("This scenario has been very very naughty")
-        end
-      end
-      """
-
-  @spawn @todo-windows
-  Scenario: Handle Exception in standard scenario step and carry on
-    Given a file named "features/naughty_step_in_scenario.feature" with:
-      """
-      Feature: Sample
-
-        Scenario: Naughty Step
-          Given this step does something naughty
-
-        Scenario: Success
-          Given this step passes
-      """
-    When I run `cucumber features`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        Scenario: Naughty Step                   # features/naughty_step_in_scenario.feature:3
-          Given this step does something naughty # features/step_definitions/naughty_steps.rb:1
-            This scenario has been very very naughty (NaughtyScenarioException)
-            ./features/support/env.rb:4:in `After'
-
-        Scenario: Success        # features/naughty_step_in_scenario.feature:6
-          Given this step passes # features/step_definitions/steps.rb:1
-
-      Failing Scenarios:
-      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
-
-      2 scenarios (1 failed, 1 passed)
-      2 steps (2 passed)
-
-      """
-
-  @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:
-      """
-      Feature: Sample
-
-        Scenario Outline: Naughty Step
-          Given this step <Might Work>
-
-          Examples:
-          | Might Work             |
-          | passes                 |
-          | does something naughty |
-          | passes                 |
-
-        Scenario: Success
-          Given this step passes
-
-      """
-    When I run `cucumber features -q`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        Scenario Outline: Naughty Step
-          Given this step <Might Work>
-
-          Examples: 
-            | Might Work             |
-            | passes                 |
-            | does something naughty |
-            This scenario has been very very naughty (NaughtyScenarioException)
-            ./features/support/env.rb:4:in `After'
-            | passes                 |
-
-        Scenario: Success
-          Given this step passes
-
-      Failing Scenarios:
-      cucumber features/naughty_step_in_scenario_outline.feature:9
-
-      4 scenarios (1 failed, 3 passed)
-      4 steps (4 passed)
-
-      """
-
-  @todo-windows
-  Scenario: Handle Exception using the progress format
-    Given a file named "features/naughty_step_in_scenario.feature" with:
-      """
-      Feature: Sample
-
-        Scenario: Naughty Step
-          Given this step does something naughty
-
-        Scenario: Success
-          Given this step passes
-      """
-    When I run `cucumber features --format progress`
-    Then it should fail with:
-      """
-      .F.
-
-      Failing Scenarios:
-      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
-
-      2 scenarios (1 failed, 1 passed)
-      2 steps (2 passed)
-
-      """
-

data/features/docs/exception_in_after_step_hook.feature

@@ -1,104 +0,0 @@
-Feature: Exception in AfterStep Block
-  In order to use custom assertions at the end of each step
-  As a developer
-  I want exceptions raised in AfterStep blocks to be handled gracefully and reported by the formatters
-
-  Background:
-    Given the standard step definitions
-    And a file named "features/step_definitions/naughty_steps.rb" with:
-      """
-      Given /^this step does something naughty$/ do x=1
-        @naughty = true
-      end
-      """
-    And a file named "features/support/env.rb" with:
-      """
-      class NaughtyStepException < Exception; end
-      AfterStep do
-        if @naughty
-          raise NaughtyStepException.new("This step has been very very naughty")
-        end
-      end
-      """
-
-  @todo-windows
-  Scenario: Handle Exception in standard scenario step and carry on
-    Given a file named "features/naughty_step_in_scenario.feature" with:
-      """
-      Feature: Sample
-
-        Scenario: Naughty Step
-          Given this step does something naughty
-
-        Scenario: Success
-          Given this step passes
-      """
-    When I run `cucumber features`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        Scenario: Naughty Step                   # features/naughty_step_in_scenario.feature:3
-          Given this step does something naughty # features/step_definitions/naughty_steps.rb:1
-            This step has been very very naughty (NaughtyStepException)
-            ./features/support/env.rb:4:in `AfterStep'
-            features/naughty_step_in_scenario.feature:4:in `Given this step does something naughty'
-
-        Scenario: Success        # features/naughty_step_in_scenario.feature:6
-          Given this step passes # features/step_definitions/steps.rb:1
-
-      Failing Scenarios:
-      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
-
-      2 scenarios (1 failed, 1 passed)
-      2 steps (2 passed)
-
-      """
-
-  @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:
-      """
-      Feature: Sample
-
-        Scenario Outline: Naughty Step
-          Given this step <Might Work>
-
-          Examples:
-          | Might Work             |
-          | passes                 |
-          | does something naughty |
-          | passes                 |
-
-        Scenario: Success
-          Given this step passes
-
-      """
-    When I run `cucumber features`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        Scenario Outline: Naughty Step # features/naughty_step_in_scenario_outline.feature:3
-          Given this step <Might Work> # features/naughty_step_in_scenario_outline.feature:4
-
-          Examples: 
-            | Might Work             |
-            | passes                 |
-            | does something naughty |
-            This step has been very very naughty (NaughtyStepException)
-            ./features/support/env.rb:4:in `AfterStep'
-            features/naughty_step_in_scenario_outline.feature:9:in `Given this step does something naughty'
-            features/naughty_step_in_scenario_outline.feature:4:in `Given this step <Might Work>'
-            | passes                 |
-
-        Scenario: Success        # features/naughty_step_in_scenario_outline.feature:12
-          Given this step passes # features/step_definitions/steps.rb:1
-
-      Failing Scenarios:
-      cucumber features/naughty_step_in_scenario_outline.feature:9 # Scenario Outline: Naughty Step, Examples (#2)
-
-      4 scenarios (1 failed, 3 passed)
-      4 steps (4 passed)
-
-      """

data/features/docs/exception_in_around_hook.feature

@@ -1,80 +0,0 @@
-Feature: Exceptions in Around Hooks
-
-  Around hooks are awkward beasts to handle internally.
-
-  Right now, if there's an error in your Around hook before you call `block.call`,
-  we won't even print the steps for the scenario.
-
-  This is because that `block.call` invokes all the logic that would tell Cucumber's
-  UI about the steps in your scenario. If we never reach that code, we'll never be
-  told about them.
-
-  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:
-      """
-      Around do |scenario, block|
-        fail "this should be reported"
-        block.call
-      end
-      """
-    And a file named "features/test.feature" with:
-      """
-      Feature:
-        Scenario:
-          Given this step passes
-      """
-    When I run `cucumber -q`
-    Then it should fail with exactly:
-      """
-      Feature: 
-
-        Scenario: 
-        this should be reported (RuntimeError)
-        ./features/support/env.rb:2:in `Around'
-      
-      Failing Scenarios:
-      cucumber features/test.feature:2
-      
-      1 scenario (1 failed)
-      0 steps
-      
-      """
-
-  @todo-windows
-  Scenario: Exception after the test case is run
-    Given the standard step definitions
-    And a file named "features/support/env.rb" with:
-      """
-      Around do |scenario, block|
-        block.call
-        fail "this should be reported"
-      end
-      """
-    And a file named "features/test.feature" with:
-      """
-      Feature:
-        Scenario:
-          Given this step passes
-      """
-    When I run `cucumber -q`
-    Then it should fail with exactly:
-      """
-      Feature: 
-
-        Scenario: 
-          Given this step passes
-            this should be reported (RuntimeError)
-            ./features/support/env.rb:3:in `Around'
-      
-      Failing Scenarios:
-      cucumber features/test.feature:2
-      
-      1 scenario (1 failed)
-      1 step (1 passed)
-
-      """