aslakhellesoy-cucumber 0.3.5 → 0.3.6.1

data/History.txt

@@ -1,3 +1,27 @@
+== 0.3.7 2209-05-21
+
+=== New Features
+* New --expand option. This will print Scenario Outlines once for each Example row - with values expanded. (#327 Aslak Hellesøy)
+* You can override the formatter in Rails-generated rake tasks with the CUCUMBER_FORMAT environment variable (#335 Aslak Hellesøy)
+
+== 0.3.6 2009-05-20
+
+Kanban! With this release you can tag features or scenarios that are work in progress
+with a tag and use the new --wip switch.
+
+Another handy feature in this release is that you can package your own formatters in RubyGems.
+
+=== New features
+* New --wip switch. See http://www.jroller.com/perryn/entry/bdd_on_a_multi_disciplined (Perryn Fowler)
+* Added a AfterStep hook (Luke Melia)
+* New aliases for Vietnamese (Ngoc Dao)
+* Automatic require of custom formatters. --require is no longer needed to load them, and they can be in Ruby gems. (Aslak Hellesøy)
+* Lazy loading of built-in formatters. Should improve startup time a little bit.
+
+=== Bugfixes
+* Gracefully handle exceptions in After block (#330 Matt Wynne)
+* Feature with only Background doesn't run hooks (#314, #329 Aslak Hellesøy)
+
 == 0.3.5 2009-05-14
 
 Let's make a new release today because two annoying bugs are fixed.

data/Manifest.txt

@@ -190,7 +190,6 @@ examples/self_test/features/sample.feature
 examples/self_test/features/search_sample.feature
 examples/self_test/features/step_definitions/sample_steps.rb
 examples/self_test/features/support/env.rb
-examples/self_test/features/support/tag_count_formatter.rb
 examples/self_test/features/tons_of_cukes.feature
 examples/self_test/features/undefined_multiline_args.feature
 examples/sinatra/Rakefile
@@ -238,12 +237,15 @@ examples/watir/Rakefile
 examples/watir/features/search.feature
 examples/watir/features/step_definitons/search_steps.rb
 examples/watir/features/support/env.rb
+features/after_block_exceptions.feature
+features/after_step_block_exceptions.feature
 features/background.feature
 features/cucumber_cli.feature
 features/cucumber_cli_diff_disabled.feature
 features/cucumber_cli_outlines.feature
 features/custom_formatter.feature
 features/exclude_files.feature
+features/expand.feature
 features/junit_formatter.feature
 features/multiline_names.feature
 features/rake_task.feature
@@ -253,6 +255,7 @@ features/step_definitions/cucumber_steps.rb
 features/step_definitions/extra_steps.rb
 features/support/env.rb
 features/usage.feature
+features/work_in_progress.feature
 gem_tasks/deployment.rake
 gem_tasks/environment.rake
 gem_tasks/features.rake
@@ -293,7 +296,6 @@ lib/cucumber/core_ext/exception.rb
 lib/cucumber/core_ext/instance_exec.rb
 lib/cucumber/core_ext/proc.rb
 lib/cucumber/core_ext/string.rb
-lib/cucumber/formatter.rb
 lib/cucumber/formatter/ansicolor.rb
 lib/cucumber/formatter/color_io.rb
 lib/cucumber/formatter/console.rb
@@ -305,6 +307,7 @@ lib/cucumber/formatter/pretty.rb
 lib/cucumber/formatter/profile.rb
 lib/cucumber/formatter/progress.rb
 lib/cucumber/formatter/rerun.rb
+lib/cucumber/formatter/tag_cloud.rb
 lib/cucumber/formatter/unicode.rb
 lib/cucumber/formatter/usage.rb
 lib/cucumber/formatters/unicode.rb

data/examples/i18n/fr/features/addition.feature

@@ -11,7 +11,7 @@ Fonctionnalité: Addition
     Lorsque je tape sur la touche "="
     Alors le résultat affiché doit être <somme>
 
-  Exemples:
-    | a | b | somme |
-    | 2 | 2 | 4     |
-    | 2 | 3 | 5     |
+    Exemples:
+      | a | b | somme |
+      | 2 | 2 | 4     |
+      | 2 | 3 | 5     |

data/features/after_block_exceptions.feature

@@ -0,0 +1,97 @@
+Feature: After Block Exceptions
+  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
+    
+      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)
+      
+      """
+  

data/features/after_step_block_exceptions.feature

@@ -0,0 +1,99 @@
+Feature: AfterStep Block Exceptions
+  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
+      """
+
+  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
+    
+      2 scenarios (1 failed, 1 passed)
+      2 steps (1 failed, 1 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 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/background.feature

@@ -253,5 +253,50 @@ Feature: backgrounds
     
     """
 
-  @josephwilk
-  Scenario: run a scenario showing explicit background steps --explicit-background
+  Scenario: https://rspec.lighthouseapp.com/projects/16211/tickets/329
+    Given a standard Cucumber project directory structure
+    And a file named "features/only_background_and_hooks.feature" with:
+      """
+      Feature: woo yeah
+
+        Background:
+          Given whatever
+
+      """
+    And a file named "features/only_background_and_hooks_steps.rb" with:
+      """
+      require 'spec/expectations'
+
+      Before do
+        $before = true
+      end
+
+      After do
+        $after = true
+      end
+
+      Given /^whatever$/ do
+        $before.should == true
+        $step = true
+      end
+
+      at_exit do
+        $before.should == true
+        $step.should == true
+        $after.should == true
+      end
+      """
+    When I run cucumber features/only_background_and_hooks.feature 
+    Then it should pass
+    And the output should be
+      """
+      Feature: woo yeah
+
+        Background:      # features/only_background_and_hooks.feature:3
+          Given whatever # features/only_background_and_hooks_steps.rb:11
+
+      0 scenarios
+      1 step (1 passed)
+      
+      """
+    And STDERR should be empty

data/features/custom_formatter.feature

@@ -1,7 +1,7 @@
 Feature: Custom Formatter
 
   Scenario: count tags
-    When I run cucumber --format Tag::Count features
+    When I run cucumber --format Cucumber::Formatter::TagCloud features
     Then it should fail with
       """
       | after_file | background_tagged_before_on_outline | four | lots | one | three | two |

data/features/step_definitions/cucumber_steps.rb

@@ -62,6 +62,10 @@ Then /^the output should not contain$/ do |text|
   last_stdout.should_not include(text)
 end
 
+Then /^the output should be$/ do |text|
+  last_stdout.should == text
+end
+
 # http://diffxml.sourceforge.net/
 Then /^"(.*)" should contain XML$/ do |file, xml|
   t = Tempfile.new('cucumber-junit')
@@ -86,6 +90,10 @@ Then /^STDERR should match$/ do |text|
   last_stderr.should =~ /#{text}/
 end
 
+Then /^STDERR should be empty$/ do
+  last_stderr.should == ""
+end
+
 Then /^"(.*)" should exist$/ do |file|
   File.exists?(file).should be_true
   FileUtils.rm(file)

data/features/work_in_progress.feature

@@ -0,0 +1,146 @@
+Feature: Cucumber --work-in-progress switch
+  In order to ensure that feature scenarios do not pass until they are expected to
+  Developers should be able to run cucumber in a mode that
+            - will fail if any scenario passes completely
+            - will not fail otherwise
+
+  Background: A passing and a pending feature
+    Given a standard Cucumber project directory structure
+    Given a file named "features/wip.feature" with:
+      """
+      Feature: WIP
+        @failing
+        Scenario: Failing
+          Given a failing step
+
+        @undefined
+        Scenario: Undefined
+          Given an undefined step
+
+        @pending
+        Scenario: Pending
+          Given a pending step
+
+        @passing
+        Scenario: Passing
+          Given a passing step
+      """
+    And a file named "features/passing_outline.feature" with:
+      """
+      Feature: Not WIP
+        Scenario Outline: Passing
+          Given a <what> step
+          
+          Examples:
+            | what    |
+            | passing |
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^a failing step$/ do
+        raise "I fail"
+      end
+
+      Given /^a passing step$/ do
+      end
+
+      Given /^a pending step$/ do
+        pending
+      end
+      """
+
+  Scenario: Pass with Failing Scenarios
+    When I run cucumber -q -w -t @failing features/wip.feature
+    Then it should pass with
+      """
+      Feature: WIP
+
+        @failing
+        Scenario: Failing
+          Given a failing step
+            I fail (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^a failing step$/'
+            features/wip.feature:4:in `Given a failing step'
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+
+  Scenario: Pass with Undefined Scenarios
+    When I run cucumber -q -w -t @undefined features/wip.feature
+    Then it should pass with
+      """
+      Feature: WIP
+
+        @undefined
+        Scenario: Undefined
+          Given an undefined step
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """
+
+  Scenario: Pass with Undefined Scenarios
+    When I run cucumber -q -w -t @pending features/wip.feature
+    Then it should pass with
+      """
+      Feature: WIP
+
+        @pending
+        Scenario: Pending
+          Given a pending step
+            TODO (Cucumber::Pending)
+            ./features/step_definitions/steps.rb:9:in `/^a pending step$/'
+            features/wip.feature:12:in `Given a pending step'
+
+      1 scenario (1 pending)
+      1 step (1 pending)
+
+      """
+
+  Scenario: Fail with Passing Scenarios
+    When I run cucumber -q -w -t @passing features/wip.feature
+    Then it should fail with
+      """
+      Feature: WIP
+
+        @passing
+        Scenario: Passing
+          Given a passing step
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
+      (::) passed scenarios (::)
+
+      features/wip.feature:15:in `Scenario: Passing'
+
+
+      """
+
+  Scenario: Fail with Passing Scenario Outline
+    When I run cucumber -q -w features/passing_outline.feature
+    Then it should fail with
+      """
+      Feature: Not WIP
+
+        Scenario Outline: Passing
+          Given a <what> step
+      
+          Examples: 
+            | what    |
+            | passing |
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
+      (::) passed scenarios (::)
+
+      features/passing_outline.feature:7:in `| passing |'
+
+
+      """