cucumber 0.8.6 → 0.8.7

data/features/around_hooks.feature

@@ -0,0 +1,232 @@
+Feature: Around hooks
+  In order to support transactional scenarios for database libraries
+  that provide only a block syntax for transactions, Cucumber should
+  permit definition of Around hooks.
+
+  Scenario: A single Around hook
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the hook is called$/ do
+        $hook_called.should == true
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hook_called = true
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        Scenario: using hook
+          Then the hook is called
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        Scenario: using hook      # features/f.feature:2
+          Then the hook is called # features/step_definitions/steps.rb:1
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Multiple Around hooks
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the hooks are called in the correct order$/ do
+        $hooks_called.should == ['A', 'B', 'C']
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'A'
+        block.call
+      end
+
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'B'
+        block.call
+      end
+
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'C'
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        Scenario: using multiple hooks
+          Then the hooks are called in the correct order
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        Scenario: using multiple hooks                   # features/f.feature:2
+          Then the hooks are called in the correct order # features/step_definitions/steps.rb:1
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Mixing Around, Before, and After hooks
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the Around hook is called around Before and After hooks$/ do
+        $hooks_called.should == ['Around', 'Before']
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'Around'
+        block.call
+        $hooks_called << 'Around'
+        $hooks_called.should == ['Around', 'Before', 'After', 'Around']
+      end
+
+      Before do |scenario|
+        $hooks_called ||= []
+        $hooks_called << 'Before'
+      end
+
+      After do |scenario|
+        $hooks_called ||= []
+        $hooks_called << 'After'
+        $hooks_called.should == ['Around', 'Before', 'After']
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        Scenario: Mixing Around, Before, and After hooks
+          Then the Around hook is called around Before and After hooks
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        Scenario: Mixing Around, Before, and After hooks               # features/f.feature:2
+          Then the Around hook is called around Before and After hooks # features/step_definitions/steps.rb:1
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Around hooks with tags
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the Around hooks with matching tags are called$/ do
+        $hooks_called.should == ['one', 'one or two']
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around('@one') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'one'
+        block.call
+      end
+
+      Around('@one,@two') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'one or two'
+        block.call
+      end
+
+      Around('@one', '@two') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'one and two'
+        block.call
+      end
+
+      Around('@two') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'two'
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        @one
+        Scenario: Around hooks with tags
+          Then the Around hooks with matching tags are called
+      """
+    When I run cucumber -q -t @one features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        @one
+        Scenario: Around hooks with tags
+          Then the Around hooks with matching tags are called
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Around hooks with scenario outlines
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the hook is called$/ do
+        $hook_called.should == true
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hook_called = true
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks with scenario outlines
+        Scenario Outline: using hook
+          Then the hook is called
+
+          Examples:
+            | Number |
+            | one    |
+            | two    |
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks with scenario outlines
+
+        Scenario Outline: using hook # features/f.feature:2
+          Then the hook is called    # features/step_definitions/steps.rb:1
+
+          Examples: 
+            | Number |
+            | one    |
+            | two    |
+
+      2 scenarios (2 passed)
+      2 steps (2 passed)
+
+      """

data/features/background.feature

@@ -1,195 +1,12 @@
-Feature: Background
+Feature: backgrounds
   In order to provide a context to my scenarios within a feature
   As a feature editor
   I want to write a background section in my features.
 
-  Background:
-    Given a file named "features/passing_background.feature" with:
-      """
-      Feature: Passing background sample
-
-        Background:
-          Given '10' cukes
-
-        Scenario: passing background
-          Then I should have '10' cukes    
-
-        Scenario: another passing background
-          Then I should have '10' cukes
-      """
-    And a file named "features/scenario_outline_passing_background.feature" with:
-      """
-      Feature: Passing background with scenario outlines sample
-
-        Background:
-          Given '10' cukes
-
-        Scenario Outline: passing background
-          Then I should have '<count>' cukes
-          Examples:
-            |count|
-            | 10  |
-
-        Scenario Outline: another passing background
-          Then I should have '<count>' cukes
-          Examples:
-            |count|
-            | 10  |
-      """
-    And a file named "features/background_tagged_before_on_outline.feature" with:
-      """
-      @background_tagged_before_on_outline
-      Feature: Background tagged Before on Outline
-
-        Background: 
-          Given passing without a table
-
-        Scenario Outline: passing background
-          Then I should have '<count>' cukes
-
-          Examples: 
-            | count |
-            | 888   |
-      """
-    And a file named "features/failing_background.feature" with:
-      """
-      Feature: Failing background sample
-
-        Background:
-          Given failing without a table
-          And '10' cukes
-
-        Scenario: failing background
-          Then I should have '10' cukes
-
-        Scenario: another failing background
-          Then I should have '10' cukes
-      """
-    And a file named "features/scenario_outline_failing_background.feature" with:
-      """
-      Feature: Failing background with scenario outlines sample
-
-        Background:
-          Given failing without a table
-
-        Scenario Outline: failing background
-          Then I should have '<count>' cukes
-          Examples:
-            |count|
-            | 10  |
-
-        Scenario Outline: another failing background
-          Then I should have '<count>' cukes
-          Examples:
-            |count|
-            | 10  |
-      """
-    And a file named "features/pending_background.feature" with:
-      """
-      Feature: Pending background sample
-
-        Background:
-          Given pending
-
-        Scenario: pending background
-          Then I should have '10' cukes
-
-        Scenario: another pending background
-          Then I should have '10' cukes
-      """
-    And a file named "features/failing_background_after_success.feature" with:
-      """
-      Feature: Failing background after previously successful background sample
-
-        Background:
-          Given passing without a table
-          And '10' global cukes
-
-        Scenario: passing background
-          Then I should have '10' global cukes
-
-        Scenario: failing background
-          Then I should have '10' global cukes
-      """
-    And a file named "features/multiline_args_background.feature" with:
-      """
-      Feature: Passing background with multiline args
-
-        Background:
-          Given table
-            |a|b|
-            |c|d|
-          And multiline string
-            \"\"\"
-            I'm a cucumber and I'm okay. 
-            I sleep all night and I test all day
-            \"\"\"
-
-        Scenario: passing background
-          Then the table should be
-            |a|b|
-            |c|d|
-          Then the multiline string should be
-            \"\"\"
-            I'm a cucumber and I'm okay. 
-            I sleep all night and I test all day
-            \"\"\"
-
-        Scenario: another passing background
-          Then the table should be
-            |a|b|
-            |c|d|
-          Then the multiline string should be
-            \"\"\"
-            I'm a cucumber and I'm okay. 
-            I sleep all night and I test all day
-            \"\"\"
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      def flunker
-        raise "FAIL"
-      end
-
-      Given /^'(.+)' cukes$/ do |cukes| x=1
-        raise "We already have #{@cukes} cukes!" if @cukes
-        @cukes = cukes
-      end
-
-      Given(/^passing without a table$/) do
-      end
-
-      Given /^failing without a table$/ do x=1
-        flunker
-      end
-
-      Given /^'(.+)' global cukes$/ do |cukes| x=1
-        $scenario_runs ||= 0
-        flunker if $scenario_runs >= 1
-        $cukes = cukes
-        $scenario_runs += 1
-      end
-
-      Then /^I should have '(.+)' global cukes$/ do |cukes| x=1
-        $cukes.should == cukes
-      end
-
-      Then /^I should have '(.+)' cukes$/ do |cukes| x=1
-        @cukes.should == cukes
-      end
-
-      Before('@background_tagged_before_on_outline') do
-        @cukes = '888'
-      end
-
-      After('@background_tagged_before_on_outline') do
-        @cukes.should == '888'
-      end
-      """
-
   Scenario: run a specific scenario with a background
-    When I run `cucumber -q features/passing_background.feature:9`
-    Then it should pass with exactly:
+    When I run cucumber -q features/background/passing_background.feature:9 --require features
+    Then STDERR should be empty
+    Then it should pass with
     """
     Feature: Passing background sample
     
@@ -201,13 +18,12 @@ Feature: Background
 
     1 scenario (1 passed)
     2 steps (2 passed)
-    0m0.012s
-
+    
     """
   
   Scenario: run a feature with a background that passes
-    When I run `cucumber -q features/passing_background.feature`
-    Then it should pass with exactly:
+    When I run cucumber -q features/background/passing_background.feature --require features
+    Then it should pass with
     """
     Feature: Passing background sample
 
@@ -222,13 +38,12 @@ Feature: Background
 
     2 scenarios (2 passed)
     4 steps (4 passed)
-    0m0.012s
-
+    
     """
 
   Scenario: run a feature with scenario outlines that has a background that passes
-    When I run `cucumber -q features/scenario_outline_passing_background.feature`
-    Then it should pass with exactly:
+    When I run cucumber -q features/background/scenario_outline_passing_background.feature --require features
+    Then it should pass with
     """
     Feature: Passing background with scenario outlines sample
 
@@ -251,13 +66,12 @@ Feature: Background
 
     2 scenarios (2 passed)
     4 steps (4 passed)
-    0m0.012s
 
     """
 
   Scenario: run a feature with scenario outlines that has a background that passes
-    When I run `cucumber -q features/background_tagged_before_on_outline.feature`
-    Then it should pass with exactly:
+    When I run cucumber -q features/background/background_tagged_before_on_outline.feature --require features
+    Then it should pass with
     """
     @background_tagged_before_on_outline
     Feature: Background tagged Before on Outline
@@ -274,22 +88,22 @@ Feature: Background
 
     1 scenario (1 passed)
     2 steps (2 passed)
-    0m0.012s
 
     """
 
   Scenario: run a feature with a background that fails
-    When I run `cucumber -q features/failing_background.feature`
-    Then it should fail with exactly:
+    When I run cucumber -q features/background/failing_background.feature --require features
+    Then it should fail with
     """
+    @after_file
     Feature: Failing background sample
 
       Background: 
         Given failing without a table
           FAIL (RuntimeError)
-          ./features/step_definitions/steps.rb:2:in `flunker'
-          ./features/step_definitions/steps.rb:14:in `/^failing without a table$/'
-          features/failing_background.feature:4:in `Given failing without a table'
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+          features/background/failing_background.feature:5:in `Given failing without a table'
         And '10' cukes
 
       Scenario: failing background
@@ -299,26 +113,26 @@ Feature: Background
         Then I should have '10' cukes
 
     Failing Scenarios:
-    cucumber features/failing_background.feature:7 # Scenario: failing background
+    cucumber features/background/failing_background.feature:8 # Scenario: failing background
     
     2 scenarios (1 failed, 1 skipped)
     6 steps (1 failed, 5 skipped)
-    0m0.012s
-    
+
     """
+    And "fixtures/self_test/tmp/after.txt" should exist
 
   Scenario: run a feature with scenario outlines that has a background that fails
-    When I run `cucumber -q features/scenario_outline_failing_background.feature`
-    Then it should fail with exactly:
+    When I run cucumber -q features/background/scenario_outline_failing_background.feature --require features
+    Then it should fail with
     """
     Feature: Failing background with scenario outlines sample
 
       Background: 
         Given failing without a table
           FAIL (RuntimeError)
-          ./features/step_definitions/steps.rb:2:in `flunker'
-          ./features/step_definitions/steps.rb:14:in `/^failing without a table$/'
-          features/scenario_outline_failing_background.feature:4:in `Given failing without a table'
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+          features/background/scenario_outline_failing_background.feature:4:in `Given failing without a table'
 
       Scenario Outline: failing background
         Then I should have '<count>' cukes
@@ -335,17 +149,16 @@ Feature: Background
           | 10    |
 
     Failing Scenarios:
-    cucumber features/scenario_outline_failing_background.feature:6 # Scenario: failing background
+    cucumber features/background/scenario_outline_failing_background.feature:6 # Scenario: failing background
 
     2 scenarios (1 failed, 1 skipped)
     4 steps (1 failed, 3 skipped)
-    0m0.012s
-    
+
     """
 
   Scenario: run a feature with a background that is pending
-    When I run `cucumber -q features/pending_background.feature`
-    Then it should pass with exactly:
+    When I run cucumber -q features/background/pending_background.feature --require features
+    Then it should pass with
     """
     Feature: Pending background sample
 
@@ -360,13 +173,12 @@ Feature: Background
 
     2 scenarios (2 undefined)
     4 steps (2 skipped, 2 undefined)
-    0m0.012s
-    
+
     """
 
   Scenario: background passes with first scenario but fails with second
-    When I run `cucumber -q features/failing_background_after_success.feature`
-    Then it should fail with exactly:
+    When I run cucumber -q features/background/failing_background_after_success.feature --require features
+    Then it should fail with
     """
     Feature: Failing background after previously successful background sample
 
@@ -380,86 +192,84 @@ Feature: Background
       Scenario: failing background
         And '10' global cukes
           FAIL (RuntimeError)
-          ./features/step_definitions/steps.rb:2:in `flunker'
-          ./features/step_definitions/steps.rb:19:in `/^'(.+)' global cukes$/'
-          features/failing_background_after_success.feature:5:in `And '10' global cukes'
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:37:in `/^'(.+)' global cukes$/'
+          features/background/failing_background_after_success.feature:5:in `And '10' global cukes'
         Then I should have '10' global cukes
 
     Failing Scenarios:
-    cucumber features/failing_background_after_success.feature:10 # Scenario: failing background
+    cucumber features/background/failing_background_after_success.feature:10 # Scenario: failing background
 
     2 scenarios (1 failed, 1 passed)
     6 steps (1 failed, 1 skipped, 4 passed)
-    0m0.012s
-    
+
     """
 
   Scenario: background with multline args
-    Given a file named "features/step_definitions/multiline_steps.rb" with:
-      """
-      Given /^table$/ do |table| x=1
-        @table = table
-      end
-
-      Given /^multiline string$/ do |string| x=1
-        @multiline = string
-      end
-
-      Then /^the table should be$/ do |table| x=1
-        @table.raw.should == table.raw
-      end
+  When I run cucumber -q features/background/multiline_args_background.feature --require features
+  Then it should pass with
+    """
+    Feature: Passing background with multiline args
 
-      Then /^the multiline string should be$/ do |string| x=1
-        @multiline.should == string
-      end
-      """
-    When I run `cucumber -q features/multiline_args_background.feature`
-    Then it should pass with exactly:
-      """
-      Feature: Passing background with multiline args
-
-        Background: 
-          Given table
-            | a | b |
-            | c | d |
-          And multiline string
-            \"\"\"
+      Background: 
+        Given table
+          | a | b |
+          | c | d |
+        And multiline string
+          \"\"\"
             I'm a cucumber and I'm okay. 
             I sleep all night and I test all day
-            \"\"\"
-
-        Scenario: passing background
-          Then the table should be
-            | a | b |
-            | c | d |
-          Then the multiline string should be
-            \"\"\"
+          \"\"\"
+
+      Scenario: passing background
+        Then the table should be
+          | a | b |
+          | c | d |
+        Then the multiline string should be
+          \"\"\"
             I'm a cucumber and I'm okay. 
             I sleep all night and I test all day
-            \"\"\"
-
-        Scenario: another passing background
-          Then the table should be
-            | a | b |
-            | c | d |
-          Then the multiline string should be
-            \"\"\"
+          \"\"\"
+
+      Scenario: another passing background
+        Then the table should be
+          | a | b |
+          | c | d |
+        Then the multiline string should be
+          \"\"\"
             I'm a cucumber and I'm okay. 
             I sleep all night and I test all day
-            \"\"\"
+          \"\"\"
 
-      2 scenarios (2 passed)
-      8 steps (8 passed)
-      0m0.012s
+    2 scenarios (2 passed)
+    8 steps (8 passed)
     
-      """
+    """
+
+  Scenario: background with name
+    When I run cucumber -q features/background/background_with_name.feature --require features
+    Then it should pass with
+    """
+    Feature: background with name
+
+      Background: I'm a background and I'm ok
+        Given '10' cukes
+
+      Scenario: example
+        Then I should have '10' cukes
+
+    1 scenario (1 passed)
+    2 steps (2 passed)
+    
+    """
 
   Scenario: https://rspec.lighthouseapp.com/projects/16211/tickets/329
-    Given a file named "features/only_background_and_hooks.feature" with:
+    Given a standard Cucumber project directory structure
+    And a file named "features/only_background_and_hooks.feature" with:
       """
       Feature: woo yeah
 
-        Background: Whatever
+        Background:
           Given whatever
 
       """
@@ -483,16 +293,17 @@ Feature: Background
         $after.should == true
       end
       """
-    When I run `cucumber features/only_background_and_hooks.feature`
-    Then it should pass with exactly:
+    When I run cucumber features/only_background_and_hooks.feature 
+    Then it should pass
+    And the output should be
       """
       Feature: woo yeah
 
-        Background: Whatever # features/only_background_and_hooks.feature:3
-          Given whatever     # features/only_background_and_hooks_steps.rb:11
+        Background:      # features/only_background_and_hooks.feature:3
+          Given whatever # features/only_background_and_hooks_steps.rb:11
 
       0 scenarios
       1 step (1 passed)
-      0m0.012s
-
+      
       """
+    And STDERR should be empty