dwaite-cucumber 0.3.101

data/features/cucumber_cli_outlines.feature

@@ -0,0 +1,109 @@
+Feature: Cucumber command line
+  In order to write better software
+  Developers should be able to execute requirements as tests
+
+  @mri186
+  Scenario: Run scenario outline with filtering on outline name
+    When I run cucumber -q features --name "Test state"
+    Then it should fail with
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | missing | passing     |
+            | passing | passing     |
+            | failing | passing     |
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+            features/outline_sample.feature:6:in `Given <state> without a table'
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      4 scenarios (1 failed, 1 undefined, 2 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+
+  @mri186
+  Scenario: Run scenario outline steps only
+    When I run cucumber -q features/outline_sample.feature:7
+    Then it should fail with
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | missing | passing     |
+            | passing | passing     |
+            | failing | passing     |
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+            features/outline_sample.feature:6:in `Given <state> without a table'
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      4 scenarios (1 failed, 1 undefined, 2 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+
+  @mri186
+  Scenario: Run single failing scenario outline table row
+    When I run cucumber features/outline_sample.feature:12
+    Then it should fail with
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state          # features/outline_sample.feature:5
+          Given <state> without a table       # features/step_definitions/sample_steps.rb:15
+          Given <other_state> without a table # features/step_definitions/sample_steps.rb:12
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | failing | passing     |
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+            features/outline_sample.feature:6:in `Given <state> without a table'
+
+      1 scenario (1 failed)
+      2 steps (1 failed, 1 skipped)
+
+      """
+
+  # There are 10 characters in the progress, but only 8 reported steps. Needs investigation.
+  # Looks like we're outputting too many characters.
+  @mri186
+  Scenario: Run all with progress formatter
+    When I run cucumber -q --format progress features/outline_sample.feature
+    Then it should fail with
+      """
+      --U-..F-..
+
+      (::) failed steps (::)
+
+      FAIL (RuntimeError)
+      ./features/step_definitions/sample_steps.rb:2:in `flunker'
+      ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+      features/outline_sample.feature:6:in `Given <state> without a table'
+
+      5 scenarios (1 failed, 1 undefined, 3 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+

data/features/custom_formatter.feature

@@ -0,0 +1,11 @@
+Feature: Custom Formatter
+
+  Scenario: count tags
+    When I run cucumber --format Cucumber::Formatter::TagCloud features
+    Then it should fail with
+      """
+      | after_file | background_tagged_before_on_outline | four | lots | one | sample_four | sample_one | sample_three | sample_two | three | two |
+      | 1          | 1                                   | 1    | 1    | 1   | 2           | 1          | 2            | 1          | 2     | 1   |
+
+      """
+    

data/features/drb_server_integration.feature

@@ -0,0 +1,173 @@
+Feature: DRb Server Integration
+  To prevent waiting for Rails and other large Ruby applications to load their environments
+  for each feature run Cucumber ships with a DRb client that can speak to a server which
+  loads up the environment only once.
+
+  Background: App with Spork support
+    Spork is a gem that has a DRb server and the scenarios below illustrate how to use it.
+    However, any DRb server that adheres to the protocol that the client expects would work.
+
+    Given a standard Cucumber project directory structure
+    And a file named "features/support/env.rb" with:
+      """
+      require 'rubygems'
+      require 'spork'
+
+      Spork.prefork do
+        puts "I'm loading all the heavy stuff..."
+      end
+
+      Spork.each_run do
+        puts "I'm loading the stuff just for this run..."
+      end
+      """
+    And a file named "features/sample.feature" with:
+      """
+      # language: en
+      Feature: Sample
+        Scenario: this is a test
+          Given I am just testing stuff
+      """
+    And a file named "features/essai.feature" with:
+      """
+      # language: fr
+      Fonction: Essai
+        Scenario: ceci est un test
+          Soit je teste
+      """
+    And a file named "features/step_definitions/all_your_steps_are_belong_to_us.rb" with:
+    """
+    Given /^I am just testing stuff$/ do
+      # no-op
+    end
+
+    Soit /^je teste$/ do
+      # no-op
+    end
+    """
+
+  Scenario: Feature Passing with --drb flag
+    Given I am running spork in the background
+
+    When I run cucumber features --drb
+    Then it should pass
+    And STDERR should be empty
+    And the output should contain
+      """
+      1 step (1 passed)
+      """
+    And the output should contain
+      """
+      I'm loading the stuff just for this run...
+      """
+    And the output should not contain
+      """
+      I'm loading all the heavy stuff...
+      """
+
+  Scenario: Feature Failing with --drb flag
+    Given a file named "features/step_definitions/all_your_steps_are_belong_to_us.rb" with:
+    """
+    Given /^I am just testing stuff$/ do
+      raise "Oh noes!"
+    end
+    """
+    And I am running spork in the background
+
+    When I run cucumber features --drb
+    Then it should fail
+    And the output should contain
+      """
+      1 step (1 failed)
+      """
+    And the output should contain
+      """
+      I'm loading the stuff just for this run...
+      """
+    And the output should not contain
+      """
+      I'm loading all the heavy stuff...
+      """
+
+  Scenario: Feature Run with --drb flag with no DRb server running
+            Cucumber will fall back on running the features locally in this case.
+
+    Given I am not running a DRb server in the background
+
+    When I run cucumber features --drb
+    Then it should pass
+    And STDERR should match
+      """
+      No DRb server is running. Running features locally:
+      """
+    And the output should contain
+      """
+      I'm loading all the heavy stuff...
+      I'm loading the stuff just for this run...
+      """
+    And the output should contain
+      """
+      1 step (1 passed)
+      """
+
+
+  Scenario: Feature Run with --drb flag *defined in a profile* with no DRb server running
+
+    Given I am not running a DRb server in the background
+    And the following profile is defined:
+      """
+      server: --drb features
+      """
+
+    When I run cucumber --profile server
+    Then it should pass
+    And STDERR should match
+      """
+      No DRb server is running. Running features locally:
+      """
+    And the output should contain
+      """
+      I'm loading all the heavy stuff...
+      I'm loading the stuff just for this run...
+      """
+
+  Scenario: Feature Run with --drb specifying a non-standard port
+
+    Given I am running spork in the background on port 9000
+
+    When I run cucumber features --drb --port 9000
+    Then it should pass
+    And STDERR should be empty
+    And the output should contain
+      """
+      1 step (1 passed)
+      """
+    And the output should contain
+      """
+      I'm loading the stuff just for this run...
+      """
+    And the output should not contain
+      """
+      I'm loading all the heavy stuff...
+      """
+
+  Scenario: Feature Run with $CUCUMBER_DRB environment variable
+
+    Given I have environment variable CUCUMBER_DRB set to "9000"
+    And I am running spork in the background on port 9000
+
+    When I run cucumber features/ --drb
+    Then it should pass
+    And STDERR should be empty
+    And the output should contain
+      """
+      1 step (1 passed)
+      """
+    And the output should contain
+      """
+      I'm loading the stuff just for this run...
+      """
+    And the output should not contain
+      """
+      I'm loading all the heavy stuff...
+      """

data/features/exception_in_after_block.feature

@@ -0,0 +1,102 @@
+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 a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step does something naughty$/ do
+        @naughty = true
+      end
+
+      Given /^this step works$/ do
+      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
+      """
+
+  @mri186
+  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 works
+      """
+    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/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 works # features/step_definitions/steps.rb:5
+
+      Failing Scenarios:
+      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
+
+      2 scenarios (1 failed, 1 passed)
+      2 steps (2 passed)
+
+      """
+
+  @mri186
+  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             |
+          | works                  |
+          | does something naughty |
+          | works                  |
+
+        Scenario: Success
+          Given this step works
+
+      """
+    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/step_definitions/steps.rb:5
+
+          Examples: 
+            | Might Work             |
+            | works                  |
+            | does something naughty |
+            This scenario has been very very naughty (NaughtyScenarioException)
+            ./features/support/env.rb:4:in `After'
+            | works                  |
+
+        Scenario: Success       # features/naughty_step_in_scenario_outline.feature:12
+          Given this step works # features/step_definitions/steps.rb:5
+
+      4 scenarios (1 failed, 3 passed)
+      4 steps (4 passed)
+
+      """
+

data/features/exception_in_after_step_block.feature

@@ -0,0 +1,104 @@
+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 a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step does something naughty$/ do
+        @naughty = true
+      end
+
+      Given /^this step works$/ do
+      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
+      """
+
+  @mri186
+  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 works
+      """
+    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/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 works # features/step_definitions/steps.rb:5
+
+      Failing Scenarios:
+      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
+
+      2 scenarios (1 failed, 1 passed)
+      2 steps (1 failed, 1 passed)
+
+      """
+
+  @mri186
+  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             |
+          | works                  |
+          | does something naughty |
+          | works                  |
+
+        Scenario: Success
+          Given this step works
+
+      """
+    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/step_definitions/steps.rb:5
+
+          Examples: 
+            | Might Work             |
+            | works                  |
+            | 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:4:in `Given this step <Might Work>'
+            | works                  |
+
+        Scenario: Success       # features/naughty_step_in_scenario_outline.feature:12
+          Given this step works # features/step_definitions/steps.rb:5
+
+      4 scenarios (1 failed, 3 passed)
+      4 steps (1 failed, 3 passed)
+
+      """
+

data/features/exception_in_before_block.feature

@@ -0,0 +1,47 @@
+Feature: Exception in Before Block
+  In order to know with confidence that my before blocks have run OK
+  As a developer
+  I want exceptions raised in Before blocks to be handled gracefully and reported by the formatters
+
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step works$/ do
+      end
+      """
+    And a file named "features/support/env.rb" with:
+      """
+      class SomeSetupException < Exception; end
+      class BadStepException < Exception; end
+      Before do
+        raise SomeSetupException.new("I cannot even start this scenario")
+      end
+      """
+
+  @mri186
+  Scenario: Handle Exception in standard scenario step and carry on
+    Given a file named "features/naughty_step_in_scenario.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Run a good step
+          Given this step works
+      """
+    When I run cucumber features
+    Then it should fail with
+      """
+      Feature: Sample
+
+        Scenario: Run a good step # features/naughty_step_in_scenario.feature:3
+        I cannot even start this scenario (SomeSetupException)
+        ./features/support/env.rb:4:in `Before'
+          Given this step works   # features/step_definitions/steps.rb:1
+
+      Failing Scenarios:
+      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Run a good step
+
+      1 scenario (1 failed)
+      1 step (1 skipped)
+
+      """

data/features/exclude_files.feature

@@ -0,0 +1,20 @@
+Feature: Exclude ruby and feature files from runs
+  Developers should be able to easily exclude files from cucumber runs
+  This is a nice feature to have in conjunction with profiles, so you can exclude
+  certain environment files from certain runs.
+
+  Scenario: exclude ruby files
+    Given a standard Cucumber project directory structure
+    And a file named "features/support/dont_require_me.rb"
+    And a file named "features/step_definitions/fooz.rb"
+    And a file named "features/step_definitions/foof.rb"
+    And a file named "features/step_definitions/foot.rb"
+    And a file named "features/support/require_me.rb"
+
+    When I run cucumber features -q --verbose --exclude features/support/dont --exclude foo[zf]
+
+    Then "features/support/require_me.rb" should be required
+    And "features/step_definitions/foot.rb" should be required
+    And "features/support/dont_require_me.rb" should not be required
+    And "features/step_definitions/foof.rb" should not be required
+    And "features/step_definitions/fooz.rb" should not be required

data/features/expand.feature

@@ -0,0 +1,49 @@
+Feature: --expand option
+  In order to make it easier to writhe certain editor plugins
+  and also for some people to understand scenarios, Cucumber
+  should expand examples in outlines.
+
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/expand_me.feature" with:
+      """
+      Feature: submit guess
+        Scenario Outline: submit guess
+          Given the secret code is <code>
+          When I guess <guess>
+          Then the mark should be <mark>
+
+        Examples: all colors correct
+          | code    | guess   | mark |
+          | r g y c | r g y c | bbbb |
+          | r g y c | r g c y | bbww |
+      """
+
+  Scenario: Expand the outline
+    When I run cucumber -i -q --expand features/expand_me.feature
+    Then STDERR should be empty
+    And it should pass with
+      """
+      Feature: submit guess
+
+        Scenario Outline: submit guess
+          Given the secret code is <code>
+          When I guess <guess>
+          Then the mark should be <mark>
+
+          Examples: all colors correct
+
+            Scenario: | r g y c | r g y c | bbbb |
+              Given the secret code is r g y c
+              When I guess r g y c
+              Then the mark should be bbbb
+
+            Scenario: | r g y c | r g c y | bbww |
+              Given the secret code is r g y c
+              When I guess r g c y
+              Then the mark should be bbww
+
+      2 scenarios (2 undefined)
+      6 steps (6 undefined)
+      
+      """