kbaum-cucumber 0.4.5.pre

data/features/cucumber_cli_diff_disabled.feature

@@ -0,0 +1,52 @@
+Feature: Cucumber command line
+  In order to write better software
+  Developers should be able to execute requirements as tests
+
+  Scenario: Run single failing scenario with default diff enabled
+    When I run cucumber -q features/failing_expectation.feature
+    Then it should fail with
+      """
+      Feature: Failing expectation
+
+        Scenario: Failing expectation
+          Given failing expectation
+            expected: "that",
+                 got: "this" (using ==)
+            
+             Diff:
+            @@ -1,2 +1,2 @@
+            -that
+            +this
+             (Spec::Expectations::ExpectationNotMetError)
+            ./features/step_definitions/sample_steps.rb:63:in `/^failing expectation$/'
+            features/failing_expectation.feature:4:in `Given failing expectation'
+      
+      Failing Scenarios:
+      cucumber features/failing_expectation.feature:3 # Scenario: Failing expectation
+      
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+
+  Scenario: Run single failing scenario with diff output disabled
+    When I run cucumber -q --no-diff features/failing_expectation.feature
+    Then it should fail with
+      """
+      Feature: Failing expectation
+
+        Scenario: Failing expectation
+          Given failing expectation
+            expected: "that",
+                 got: "this" (using ==) (Spec::Expectations::ExpectationNotMetError)
+            ./features/step_definitions/sample_steps.rb:63:in `/^failing expectation$/'
+            features/failing_expectation.feature:4:in `Given failing expectation'
+
+      Failing Scenarios:
+      cucumber features/failing_expectation.feature:3 # Scenario: Failing expectation
+      
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+

data/features/cucumber_cli_outlines.feature

@@ -0,0 +1,105 @@
+Feature: Cucumber command line
+  In order to write better software
+  Developers should be able to execute requirements as tests
+
+  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)
+
+      """
+
+  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)
+
+      """
+
+  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.
+  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,47 @@
+Feature: Custom Formatter
+
+  Scenario: count tags
+    When I run cucumber --format Cucumber::Formatter::TagCloud features
+    Then STDERR should be empty
+    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    |
+
+      """
+
+  Scenario: my own formatter
+    Given a standard Cucumber project directory structure
+    And a file named "features/f.feature" with:
+      """
+      Feature: i'll use my own
+        Scenario: just print me
+          Given this step works
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step works$/ do
+      end
+      """
+    And a file named "features/support/ze/formator.rb" with:
+      """
+      module Ze
+        class Formator
+          def initialize(step_mother, io, options)
+            @step_mother = step_mother
+            @io = io
+          end
+
+          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 Ze::Formator
+    Then STDERR should be empty
+    Then it should pass with
+      """
+      $ JUST PRINT ME
+
+      """

data/features/default_snippets.feature

@@ -0,0 +1,42 @@
+Feature: Print snippets
+  In order to make it easier to implement step definitions
+  Developers should get a scaffolding for undefined step definitions
+  
+  Scenario: Cucumber doesn't know what language, and defaults to Ruby
+    Given a standard Cucumber project directory structure
+    And a file named "features/x.feature" with:
+      """
+      Feature: X
+        Scenario: Y
+          Given Z
+          Given Q
+      """
+    When I run cucumber features
+    Then STDERR should be empty
+    And it should pass with
+      """
+      Feature: X
+
+        Scenario: Y # features/x.feature:2
+          Given Z   # features/x.feature:3
+          Given Q   # features/x.feature:4
+
+      1 scenario (1 undefined)
+      2 steps (2 undefined)
+
+      You can implement step definitions for undefined steps with these snippets:
+      
+      Given /^Z$/ do
+        pending # express the regexp above with the code you wish you had
+      end
+
+      Given /^Q$/ do
+        pending # express the regexp above with the code you wish you had
+      end
+
+      If you want snippets in a different programming language, just make sure a file
+      with the appropriate file extension exists where cucumber looks for step definitions.
+
+
+      """
+  

data/features/drb_server_integration.feature

@@ -0,0 +1,174 @@
+@spork
+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,100 @@
+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
+      """
+
+  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)
+
+      """
+
+  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)
+
+      """
+