cucumber 1.3.20 → 2.0.0.beta.1

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

@@ -1,10 +1,10 @@
+@spawn
 Feature: Rake task
   In order to ease the development process
   As a developer and CI server administrator
   Cucumber features should be executable via Rake
 
   Background:
-    Given a standard Cucumber project directory structure
     And a file named "features/missing_step_definitions.feature" with:
       """
       Feature: Sample
@@ -16,7 +16,6 @@ Feature: Rake task
           Given I don't want this ran
       """
 
-
   Scenario: rake task with a defined profile
     Given the following profile is defined:
       """
@@ -24,16 +23,14 @@ Feature: Rake task
       """
     And a file named "Rakefile" with:
       """
-      $LOAD_PATH.unshift(CUCUMBER_LIB)
       require 'cucumber/rake/task'
 
       Cucumber::Rake::Task.new do |t|
         t.profile = "foo"
       end
       """
-    When I run rake cucumber
-    Then it should pass
-    And the output should contain
+    When I run `rake cucumber`
+    Then it should pass with:
       """
       Feature: Sample
 
@@ -44,31 +41,29 @@ Feature: Rake task
       1 step (1 undefined)
       """
 
-    Scenario: rake task without a profile
-      Given a file named "Rakefile" with:
-        """
-        $LOAD_PATH.unshift(CUCUMBER_LIB)
-        require 'cucumber/rake/task'
+  Scenario: rake task without a profile
+    Given a file named "Rakefile" with:
+      """
+      require 'cucumber/rake/task'
 
-        Cucumber::Rake::Task.new do |t|
-          t.cucumber_opts = %w{--quiet --no-color}
-        end
-        """
-      When I run rake cucumber
-      Then it should pass
-      And the output should contain
-        """
-        Feature: Sample
+      Cucumber::Rake::Task.new do |t|
+        t.cucumber_opts = %w{--quiet --no-color}
+      end
+      """
+    When I run `rake cucumber`
+    Then it should pass with:
+      """
+      Feature: Sample
 
-          Scenario: Wanted
-            Given I want to run this
+        Scenario: Wanted
+          Given I want to run this
 
-          Scenario: Unwanted
-            Given I don't want this ran
+        Scenario: Unwanted
+          Given I don't want this ran
 
-        2 scenarios (2 undefined)
-        2 steps (2 undefined)
-        """
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+      """
 
   Scenario: rake task with a defined profile and cucumber_opts
     Given the following profile is defined:
@@ -77,7 +72,6 @@ Feature: Rake task
       """
     And a file named "Rakefile" with:
       """
-      $LOAD_PATH.unshift(CUCUMBER_LIB)
       require 'cucumber/rake/task'
 
       Cucumber::Rake::Task.new do |t|
@@ -85,9 +79,8 @@ Feature: Rake task
         t.cucumber_opts = %w{--quiet --no-color}
       end
       """
-    When I run rake cucumber
-    Then it should pass
-    And the output should contain
+    When I run `rake cucumber`
+    Then it should pass with:
       """
       Feature: Sample
 
@@ -99,15 +92,14 @@ Feature: Rake task
       """
 
   Scenario: respect requires
-    Given a file named "features/support/env.rb"
-    And a file named "features/support/dont_require_me.rb"
+    Given an empty file named "features/support/env.rb"
+    And an empty file named "features/support/dont_require_me.rb"
     And the following profile is defined:
       """
       no_bomb: features/missing_step_definitions.feature:3 --require features/support/env.rb --verbose
       """
     And a file named "Rakefile" with:
       """
-      $LOAD_PATH.unshift(CUCUMBER_LIB)
       require 'cucumber/rake/task'
 
       Cucumber::Rake::Task.new do |t|
@@ -115,10 +107,9 @@ Feature: Rake task
         t.cucumber_opts = %w{--quiet --no-color}
       end
       """
-
-    When I run rake cucumber
+    When I run `rake cucumber`
     Then it should pass
-    And the output should not contain
+    And the output should not contain:
       """
         * features/support/dont_require_me.rb
       """
@@ -133,16 +124,14 @@ Feature: Rake task
        """
     And a file named "Rakefile" with:
        """
-       $LOAD_PATH.unshift(CUCUMBER_LIB)
        require 'cucumber/rake/task'
 
        Cucumber::Rake::Task.new do |t|
          t.cucumber_opts = %w{--quiet --no-color}
        end
        """
-    When I run rake cucumber
-    Then it should pass
-    And the output should contain
+    When I run `rake cucumber`
+    Then it should pass with:
        """
        Feature: The futures green
 

data/features/{raketask.feature → docs/raketask.feature}

@@ -1,30 +1,23 @@
 @spawn
 Feature: Raketask
+
   In order to use cucumber's rake task
   As a Cuker
   I do not want to see rake's backtraces when it fails
   Also I want to get zero exit status code on failures
-  And non-zero exit status code when is pases
+  And non-zero exit status code when it pases
 
   Background:
+    Given the standard step definitions
     Given a file named "features/passing_and_failing.feature" with:
       """
       Feature: Sample
 
         Scenario: Passing
-          Given passing
+          Given this step passes
 
         Scenario: Failing
-          Given failing
-      """
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      Given(/^passing$/) do
-      end
-
-      Given /^failing$/ do
-        raise "FAIL"
-      end
+          Given this step raises an error
       """
     Given a file named "Rakefile" with:
       """
@@ -48,4 +41,4 @@ Feature: Raketask
   Scenario: Failing feature
     When I run `bundle exec rake fail`
     Then the exit status should not be 0
-    And the output should not contain "rake aborted!"
+    But the output should not contain "rake aborted!"

data/features/docs/report_called_undefined_steps.feature

@@ -0,0 +1,57 @@
+Feature: Cucumber command line
+  In order to find out what step definitions need to be implemented
+  Developers should always see what step definition is missing
+
+  @wip-new-core
+  @spawn
+  Scenario: Get info at arbitrary levels of nesting
+    Given a file named "features/call_undefined_step_from_step_def.feature" with:
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly
+          Given a step definition that calls an undefined step
+
+        Scenario: Call via another
+          Given call step "a step definition that calls an undefined step"
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^a step definition that calls an undefined step$/ do
+        step 'this does not exist'
+      end
+
+      Given /^call step "(.*)"$/ do |step_name| x=1
+        step step_name
+      end
+      """
+    When I run `cucumber features/call_undefined_step_from_step_def.feature`
+    Then it should pass with:
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly                                # features/call_undefined_step_from_step_def.feature:3
+          Given a step definition that calls an undefined step # features/step_definitions/steps.rb:1
+            Undefined step: "this does not exist" (Cucumber::Undefined)
+            ./features/step_definitions/steps.rb:2:in `/^a step definition that calls an undefined step$/'
+            features/call_undefined_step_from_step_def.feature:4:in `Given a step definition that calls an undefined step'
+
+        Scenario: Call via another                                         # features/call_undefined_step_from_step_def.feature:6
+          Given call step "a step definition that calls an undefined step" # features/step_definitions/steps.rb:5
+            Undefined step: "this does not exist" (Cucumber::Undefined)
+            ./features/step_definitions/steps.rb:2:in `/^a step definition that calls an undefined step$/'
+            ./features/step_definitions/steps.rb:6:in `/^call step "(.*)"$/'
+            features/call_undefined_step_from_step_def.feature:7:in `Given call step "a step definition that calls an undefined step"'
+
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+      """
+    And the output should contain:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+
+      Given(/^this does not exist$/) do
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+
+      """

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

@@ -38,8 +38,7 @@ Feature: Wire Protocol
   #
 
   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: High strung
         Scenario: Wired
@@ -67,8 +66,8 @@ Feature: Wire Protocol
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response       |
       | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[]] |
-    When I run cucumber --dry-run --no-snippets -f progress
-    And it should pass with
+    When I run `cucumber --dry-run --no-snippets -f progress`
+    And it should pass with:
       """
       U
 
@@ -87,8 +86,8 @@ Feature: Wire Protocol
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                            |
       | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
-    When I run cucumber --dry-run -f progress
-    And it should pass with
+    When I run `cucumber --dry-run -f progress`
+    And it should pass with:
       """
       -
 
@@ -103,9 +102,8 @@ Feature: Wire Protocol
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                                                                           |
       | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[], "source":"MyApp.MyClass:123", "regexp":"we.*"}]] |
-    When I run cucumber -f stepdefs --dry-run
-    Then STDERR should be empty
-    And it should pass with
+    When I run `cucumber -f stepdefs --dry-run`
+    Then it should pass with:
       """
       -
 
@@ -115,6 +113,7 @@ Feature: Wire Protocol
       1 step (1 skipped)
 
       """
+    And the stderr should not contain anything
 
 
   #
@@ -138,6 +137,7 @@ Feature: Wire Protocol
 
   # ## Pending Steps
   #
+  @spawn
   Scenario: Invoke a step definition which is pending
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                            |
@@ -145,8 +145,8 @@ Feature: Wire Protocol
       | ["begin_scenario"]                                   | ["success"]                         |
       | ["invoke",{"id":"1","args":[]}]                      | ["pending", "I'll do it later"]     |
       | ["end_scenario"]                                     | ["success"]                         |
-    When I run cucumber -f pretty -q
-    And it should pass with
+    When I run `cucumber -f pretty -q`
+    And it should pass with:
       """
       Feature: High strung
 
@@ -169,8 +169,8 @@ Feature: Wire Protocol
       | ["begin_scenario"]                                   | ["success"]                         |
       | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
       | ["end_scenario"]                                     | ["success"]                         |
-    When I run cucumber -f progress
-    And it should pass with
+    When I run `cucumber -f progress`
+    And it should pass with:
       """
       .
 
@@ -192,6 +192,7 @@ Feature: Wire Protocol
   #
   # See the specs for Cucumber::WireSupport::WireException for more details
   #
+  @spawn
   Scenario: Invoke a step definition which fails
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response                                                                            |
@@ -199,9 +200,9 @@ Feature: Wire Protocol
       | ["begin_scenario"]                                   | ["success"]                                                                         |
       | ["invoke",{"id":"1","args":[]}]                      | ["fail",{"message":"The wires are down", "exception":"Some.Foreign.ExceptionType"}] |
       | ["end_scenario"]                                     | ["success"]                                                                         |
-    When I run cucumber -f progress
-    Then STDERR should be empty
-    And it should fail with
+    When I run `cucumber -f progress`
+    Then the stderr should not contain anything
+    And it should fail with:
       """
       F
 
@@ -242,9 +243,9 @@ Feature: Wire Protocol
       | ["begin_scenario"]                                   | ["success"]                                                  |
       | ["invoke",{"id":"1","args":["wired"]}]               | ["success"]                                                  |
       | ["end_scenario"]                                     | ["success"]                                                  |
-    When I run cucumber -f progress
-    Then STDERR should be empty
-    And it should pass with
+    When I run `cucumber -f progress`
+    Then the stderr should not contain anything
+    And it should pass with:
       """
       .
 
@@ -275,9 +276,9 @@ Feature: Wire Protocol
       | ["begin_scenario"]                                                    | ["success"]                                                 |
       | ["invoke",{"id":"1","args":["we're",[["wired"],["high"],["happy"]]]}] | ["success"]                                                 |
       | ["end_scenario"]                                                      | ["success"]                                                 |
-    When I run cucumber -f progress features/wired_on_tables.feature
-    Then STDERR should be empty
-    And it should pass with
+    When I run `cucumber -f progress features/wired_on_tables.feature`
+    Then the stderr should not contain anything
+    And it should pass with:
       """
       .
 
@@ -290,6 +291,7 @@ Feature: Wire Protocol
   #
   # # Request: 'snippets'
   #
+  @spawn
   Scenario: Wire server returns snippets for a step that didn't match
     Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                                                                          | response                         |
@@ -297,9 +299,9 @@ Feature: Wire Protocol
       | ["snippet_text",{"step_keyword":"Given","multiline_arg_class":"","step_name":"we're all wired"}] | ["success","foo()\n  bar;\nbaz"] |
       | ["begin_scenario"]                                                                               | ["success"]                      |
       | ["end_scenario"]                                                                                 | ["success"]                      |
-    When I run cucumber -f pretty
-    Then STDERR should be empty
-    And it should pass with
+    When I run `cucumber -f pretty`
+    Then the stderr should not contain anything
+    And it should pass with:
       """
       Feature: High strung
 
@@ -308,6 +310,9 @@ Feature: Wire Protocol
 
       1 scenario (1 undefined)
       1 step (1 undefined)
+      """
+    And the output should contain:
+      """
 
       You can implement step definitions for undefined steps with these snippets:
 
@@ -315,7 +320,6 @@ Feature: Wire Protocol
         bar;
       baz
 
-
       """
 
   #
@@ -323,10 +327,11 @@ Feature: Wire Protocol
   #
   Scenario: Unexpected response
     Given there is a wire server running on port 54321 which understands the following protocol:
-      | request            | response  |
-      | ["begin_scenario"] | ["yikes"] |
-    When I run cucumber -f progress
-    Then STDERR should match
+      | request                                              | response                            |
+      | ["begin_scenario"]                                   | ["yikes"]                           |
+      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
+    When I run `cucumber -f pretty`
+    Then the stdout should contain:
       """
       undefined method `handle_yikes'
-      """
+      """

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

@@ -6,8 +6,7 @@ Feature: Wire Protocol with ERB
   So that I can avoid port conflicts
 
   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: High strung
         Scenario: Wired
@@ -24,8 +23,8 @@ Feature: Wire Protocol with ERB
       And there is a wire server running on port 12345 which understands the following protocol:
         | request                                              | response       |
         | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[]] |
-      When I run cucumber --dry-run --no-snippets -f progress
-      And it should pass with
+      When I run `cucumber --dry-run --no-snippets -f progress`
+      Then it should pass with:
         """
         U
 
@@ -45,8 +44,8 @@ Feature: Wire Protocol with ERB
       And there is a wire server running on port 16816 which understands the following protocol:
         | request                                              | response       |
         | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[]] |
-      When I run cucumber --dry-run --no-snippets -f progress
-      And it should pass with
+      When I run `cucumber --dry-run --no-snippets -f progress`
+      Then it should pass with:
         """
         U