cucumber 1.3.20 → 2.0.0.beta.1

data/{legacy_features → features/docs}/wire_protocol_table_diffing.feature

@@ -5,8 +5,7 @@ Feature: Wire protocol table diffing
   I want to be able to ask for a table diff during a step definition invocation
 
   Background:
-    Given a standard Cucumber project directory structure
-    And a file named "features/wired.feature" with:
+    Given a file named "features/wired.feature" with:
       """
       Feature: Hello
         Scenario: Wired
@@ -20,6 +19,7 @@ Feature: Wire protocol table diffing
 
       """
 
+  @spawn
   Scenario: Invoke a step definition tries to diff the table and fails
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                                                                                             |
@@ -28,9 +28,9 @@ Feature: Wire protocol table diffing
       | ["invoke",{"id":"1","args":[]}]                      | ["diff",[[["a","b"],["c","d"]],[["x","y"],["z","z"]]]]                                               |
       | ["diff_failed"]                                      | ["fail",{"message":"Not same", "exception":"DifferentException", "backtrace":["a.cs:12","b.cs:34"]}] |
       | ["end_scenario"]                                     | ["success"]                                                                                          |
-    When I run cucumber -f progress --backtrace
-    Then STDERR should be empty
-    And it should fail with
+    When I run `cucumber -f progress --backtrace`
+    Then the stderr should not contain anything
+    And it should fail with:
       """
       F
 
@@ -57,8 +57,8 @@ Feature: Wire protocol table diffing
       | ["invoke",{"id":"1","args":[]}]                      | ["diff",[[["a"],["b"]],[["a"],["b"]]]] |
       | ["diff_ok"]                                          | ["success"]                            |
       | ["end_scenario"]                                     | ["success"]                            |
-    When I run cucumber -f progress
-    And it should pass with
+    When I run `cucumber -f progress`
+    Then it should pass with:
       """
       .
 
@@ -67,6 +67,7 @@ Feature: Wire protocol table diffing
 
       """
 
+  @spawn
   Scenario: Invoke a step definition which successfully diffs a table but then fails
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                                                      |
@@ -75,8 +76,8 @@ Feature: Wire protocol table diffing
       | ["invoke",{"id":"1","args":[]}]                      | ["diff",[[["a"],["b"]],[["a"],["b"]]]]                        |
       | ["diff_ok"]                                          | ["fail",{"message":"I wanted things to be different for us"}] |
       | ["end_scenario"]                                     | ["success"]                                                   |
-    When I run cucumber -f progress
-    And it should fail with
+    When I run `cucumber -f progress`
+    Then it should fail with:
       """
       F
 
@@ -93,6 +94,7 @@ Feature: Wire protocol table diffing
 
       """
 
+  @spawn
   Scenario: Invoke a step definition which asks for an immediate diff that fails
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                            |
@@ -100,14 +102,14 @@ Feature: Wire protocol table diffing
       | ["begin_scenario"]                                   | ["success"]                         |
       | ["invoke",{"id":"1","args":[]}]                      | ["diff!",[[["a"]],[["b"]]]]         |
       | ["end_scenario"]                                     | ["success"]                         |
-    When I run cucumber -f progress
-    And it should fail with
+    When I run `cucumber -f progress`
+    And it should fail with:
       """
       F
 
       (::) failed steps (::)
 
-      Tables were not identical (Cucumber::Ast::Table::Different)
+      Tables were not identical (Cucumber::MultilineArgument::DataTable::Different)
       features/wired.feature:3:in `Given we're all wired'
 
       Failing Scenarios:

data/{legacy_features → features/docs}/wire_protocol_tags.feature

@@ -4,7 +4,6 @@ Feature: Wire protocol tags
   scenario in the begin_scenario and end_scenario messages
 
   Background:
-    Given a standard Cucumber project directory structure
     And a file named "features/step_definitions/some_remote_place.wire" with:
       """
       host: localhost
@@ -29,9 +28,9 @@ Feature: Wire protocol tags
       | ["begin_scenario", {"tags":["bar","baz","foo"]}]     | ["success"]                         |
       | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
       | ["end_scenario", {"tags":["bar","baz","foo"]}]       | ["success"]                         |
-    When I run cucumber -f pretty -q
-    Then STDERR should be empty
-    And it should pass with
+    When I run `cucumber -f pretty -q`
+    Then the stderr should not contain anything
+    And it should pass with:
       """
       @foo @bar
       Feature: Wired
@@ -66,9 +65,9 @@ Feature: Wire protocol tags
     | ["begin_scenario", {"tags":["bar","baz","foo"]}]     | ["success"]                         |
     | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
     | ["end_scenario", {"tags":["bar","baz","foo"]}]       | ["success"]                         |
-  When I run cucumber -f pretty -q
-  Then STDERR should be empty
-  And it should pass with
+  When I run `cucumber -f pretty -q`
+  Then the stderr should not contain anything
+  And it should pass with:
     """
     @foo @bar
     Feature: Wired

data/{legacy_features → features/docs}/wire_protocol_timeouts.feature

@@ -5,7 +5,6 @@ Feature: Wire protocol timeouts
   to take a while to execute, if that's what they need.
 
   Background:
-    Given a standard Cucumber project directory structure
     And a file named "features/wired.feature" with:
       """
       Feature: Telegraphy
@@ -21,12 +20,13 @@ Feature: Wire protocol timeouts
       port: 54321
 
       """
-    When I run cucumber -f progress
-    Then STDERR should match
+    When I run `cucumber -f progress`
+    Then the stderr should contain:
       """
       Unable to contact the wire server at localhost:54321
       """
 
+  @spawn
   Scenario: Invoke a step definition that takes longer than its timeout
     Given a file named "features/step_definitions/some_remote_place.wire" with:
       """
@@ -43,9 +43,9 @@ Feature: Wire protocol timeouts
       | ["invoke",{"id":"1","args":["wired"]}]               | ["success"]                                                  |
       | ["end_scenario"]                                     | ["success"]                                                  |
     And the wire server takes 0.2 seconds to respond to the invoke message
-    When I run cucumber -f pretty
-    Then STDERR should be empty
-    And it should fail with
+    When I run `cucumber -f pretty`
+    Then the stderr should not contain anything
+    And it should fail with:
       """
       Feature: Telegraphy
 

data/{legacy_features → features/docs}/work_in_progress.feature

@@ -1,3 +1,4 @@
+@spawn
 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
@@ -5,124 +6,119 @@ Feature: Cucumber --work-in-progress switch
             - 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:
+    Given the standard step definitions
+    And a file named "features/wip.feature" with:
       """
       Feature: WIP
         @failing
         Scenario: Failing
-          Given a failing step
+          Given this step raises an error
 
         @undefined
         Scenario: Undefined
-          Given an undefined step
+          Given this step is undefined
 
         @pending
         Scenario: Pending
-          Given a pending step
+          Given this step is pending
 
         @passing
         Scenario: Passing
-          Given a passing step
+          Given this step passes
       """
     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 this step <what>
 
-      Given /^a passing step$/ do
-      end
-
-      Given /^a pending step$/ do
-        pending
-      end
+          Examples:
+            | what   |
+            | passes |
       """
 
   Scenario: Pass with Failing Scenarios
-    When I run cucumber -q -w -t @failing features/wip.feature
-    Then STDERR should be empty
-    Then it should pass with
+    When I run `cucumber -q -w -t @failing features/wip.feature`
+    Then the stderr should not contain anything
+    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'
-      
+          Given this step raises an error
+            error (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^this step raises an error$/'
+            features/wip.feature:4:in `Given this step raises an error'
+
       Failing Scenarios:
       cucumber features/wip.feature:3
 
       1 scenario (1 failed)
       1 step (1 failed)
-
+      """
+    And the output should contain:
+      """
       The --wip switch was used, so the failures were expected. All is good.
 
       """
 
   Scenario: Pass with Undefined Scenarios
-    When I run cucumber -q -w -t @undefined features/wip.feature
-    Then it should pass with
+    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
+          Given this step is undefined
 
       1 scenario (1 undefined)
       1 step (1 undefined)
-
+      """
+    And the output should contain:
+      """
       The --wip switch was used, so the failures were expected. All is good.
 
       """
 
   Scenario: Pass with Undefined Scenarios
-    When I run cucumber -q -w -t @pending features/wip.feature
-    Then it should pass with
+    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
+          Given this step is pending
             TODO (Cucumber::Pending)
-            ./features/step_definitions/steps.rb:9:in `/^a pending step$/'
-            features/wip.feature:12:in `Given a pending step'
+            ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+            features/wip.feature:12:in `Given this step is pending'
 
       1 scenario (1 pending)
       1 step (1 pending)
-
+      """
+    And the output should contain:
+      """
       The --wip switch was used, so the failures were expected. All is good.
 
       """
 
   Scenario: Fail with Passing Scenarios
-    When I run cucumber -q -w -t @passing features/wip.feature
-    Then it should fail with
+    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
+          Given this step passes
 
       1 scenario (1 passed)
       1 step (1 passed)
-
+      """
+    And the output should contain:
+      """
       The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
       (::) passed scenarios (::)
 
@@ -132,25 +128,27 @@ Feature: Cucumber --work-in-progress switch
       """
 
   Scenario: Fail with Passing Scenario Outline
-    When I run cucumber -q -w features/passing_outline.feature
-    Then it should fail with
+    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
-      
+          Given this step <what>
+
           Examples: 
-            | what    |
-            | passing |
+            | what   |
+            | passes |
 
       1 scenario (1 passed)
       1 step (1 passed)
-
+      """
+    And the output should contain:
+      """
       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 |'
+      features/passing_outline.feature:7:in `Scenario Outline: Passing, Examples (row 1)'
 
 
       """

data/{legacy_features → features/docs/writing_support_code}/around_hooks.feature

@@ -1,14 +1,15 @@
+@spawn
 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:
+    Given a file named "features/step_definitions/steps.rb" with:
       """
       Then /^the hook is called$/ do
-        $hook_called.should == true
+        expect($hook_called).to be true
       end
       """
     And a file named "features/support/hooks.rb" with:
@@ -24,8 +25,8 @@ Feature: Around hooks
         Scenario: using hook
           Then the hook is called
       """
-    When I run cucumber features/f.feature
-    Then it should pass with
+    When I run `cucumber features/f.feature`
+    Then it should pass with:
       """
       Feature: Around hooks
 
@@ -38,11 +39,10 @@ Feature: Around hooks
       """
 
   Scenario: Multiple Around hooks
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
+    Given 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']
+        expect($hooks_called).to eq ['A', 'B', 'C']
       end
       """
     And a file named "features/support/hooks.rb" with:
@@ -71,8 +71,8 @@ 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
+    When I run `cucumber features/f.feature`
+    Then it should pass with:
       """
       Feature: Around hooks
 
@@ -85,11 +85,10 @@ Feature: Around hooks
       """
 
   Scenario: Mixing Around, Before, and After hooks
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
+    Given 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']
+        expect($hooks_called).to eq ['Around', 'Before']
       end
       """
     And a file named "features/support/hooks.rb" with:
@@ -99,7 +98,7 @@ Feature: Around hooks
         $hooks_called << 'Around'
         block.call
         $hooks_called << 'Around'
-        $hooks_called.should == ['Around', 'Before', 'After', 'Around']
+        $hooks_called.should == ['Around', 'Before', 'After', 'Around'] #TODO: Find out why this fails using the new rspec expect syntax.
       end
 
       Before do |scenario|
@@ -110,7 +109,7 @@ Feature: Around hooks
       After do |scenario|
         $hooks_called ||= []
         $hooks_called << 'After'
-        $hooks_called.should == ['Around', 'Before', 'After']
+        expect($hooks_called).to eq ['Around', 'Before', 'After']
       end
       """
     And a file named "features/f.feature" with:
@@ -119,8 +118,8 @@ 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
+    When I run `cucumber features/f.feature`
+    Then it should pass with:
       """
       Feature: Around hooks
 
@@ -133,11 +132,10 @@ Feature: Around hooks
       """
 
   Scenario: Around hooks with tags
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
+    Given 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']
+        expect($hooks_called).to eq ['one', 'one or two']
       end
       """
     And a file named "features/support/hooks.rb" with:
@@ -173,8 +171,8 @@ Feature: Around hooks
         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
+    When I run `cucumber -q -t @one features/f.feature`
+    Then it should pass with:
       """
       Feature: Around hooks
 
@@ -188,11 +186,10 @@ Feature: Around hooks
       """
 
   Scenario: Around hooks with scenario outlines
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
+    Given a file named "features/step_definitions/steps.rb" with:
       """
       Then /^the hook is called$/ do
-        $hook_called.should == true
+        expect($hook_called).to be true
       end
       """
     And a file named "features/support/hooks.rb" with:
@@ -213,13 +210,13 @@ Feature: Around hooks
             | one    |
             | two    |
       """
-    When I run cucumber features/f.feature
-    Then it should pass with
+    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
+          Then the hook is called    # features/f.feature:3
 
           Examples: 
             | Number |