cucumber 1.3.10 → 2.0.0

data/features/docs/gherkin/using_descriptions.feature

@@ -0,0 +1,88 @@
+Feature: Using descriptions to give features context
+
+  When writing your feature files its very helpful to use description
+  text at the beginning of the feature file, to write a preamble to the
+  feature describing clearly exactly what the feature does.
+
+  You can also write descriptions attached to individual scenarios - see
+  the examples below for how this can be used.
+
+  It's possible to have your descriptions run over more than one line,
+  and you can have blank lines too. As long as you don't start a line
+  with a Given, When, Then, Background:, Scenario: or similar, you're
+  fine: otherwise Gherkin will start to pay attention.
+
+  Background:
+    Given the standard step definitions
+
+  Scenario: Everything with a description
+    Given a file named "features/test.feature" with:
+    """
+    Feature: descriptions everywhere
+
+      We can put a useful description here of the feature, which can
+      span multiple lines.
+
+      Background:
+
+        We can also put in descriptions showing what the background is
+        doing.
+
+        Given this step passes
+
+      Scenario: I'm a scenario with a description
+
+        You can also put descriptions in front of individual scenarios.
+
+        Given this step passes
+
+      Scenario Outline: I'm a scenario outline with a description
+
+        Scenario outlines can have descriptions.
+
+        Given this step <state>
+        Examples: Examples
+
+          Specific examples for an outline are allowed to have
+          descriptions, too.
+
+          |  state |
+          | passes |
+    """
+    When I run `cucumber -q`
+    Then the stderr should not contain anything
+    Then it should pass with exactly:
+    """
+    Feature: descriptions everywhere
+      
+      We can put a useful description here of the feature, which can
+      span multiple lines.
+
+      Background: 
+        
+        We can also put in descriptions showing what the background is
+        doing.
+        Given this step passes
+
+      Scenario: I'm a scenario with a description
+        
+        You can also put descriptions in front of individual scenarios.
+        Given this step passes
+
+      Scenario Outline: I'm a scenario outline with a description
+        
+        Scenario outlines can have descriptions.
+        Given this step <state>
+
+        Examples: Examples
+          
+          Specific examples for an outline are allowed to have
+          descriptions, too.
+          | state  |
+          | passes |
+
+    2 scenarios (2 passed)
+    4 steps (4 passed)
+    0m0.012s
+
+    """

data/features/docs/gherkin/using_star_notation.feature

@@ -0,0 +1,37 @@
+Feature: Using star notation instead of Given/When/Then
+
+  Cucumber supports the star notation when writing features: instead of
+  using Given/When/Then, you can simply use a star rather like you would
+  use a bullet point.
+
+  When you run the feature for the first time, you still get a nice
+  message showing you the code snippet you need to use to implement the
+  step.
+
+  Scenario: Use some *
+    Given a file named "features/f.feature" with:
+      """
+      Feature: Star-notation feature
+        Scenario: S
+          * I have some cukes
+      """
+    When I run `cucumber features/f.feature`
+    Then the stderr should not contain anything
+    And it should pass with:
+      """
+      Feature: Star-notation feature
+
+        Scenario: S           # features/f.feature:2
+          * I have some cukes # features/f.feature:3
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+    And it should pass with:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+
+      Given(/^I have some cukes$/) do
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+      """

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

@@ -4,47 +4,46 @@ Feature: Post Configuration Hook [#423]
   As a developer
   I want to manipulate the Cucumber configuration after it has been created
 
+  # Fails on Travis under JRuby
+  @spawn
+  @wip-jruby
   Scenario: Using options directly gets a deprecation warning
-
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
+    Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
         config.options[:blah]
       end
       """
-    When I run cucumber features
-    Then STDERR should match
+    When I run `cucumber features`
+    Then the stderr should contain:
       """
       Deprecated
       """
 
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
+  Scenario: Changing the output format
+    Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
         config.formats << ['html', config.out_stream]
       end
       """
-    When I run cucumber features
-    Then STDERR should be empty
-    And the output should contain
+    When I run `cucumber features`
+    Then the stderr should not contain anything
+    And the output should contain:
       """
       html
       """
 
   Scenario: feature directories read from configuration
-
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
+    Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
-        config.out_stream << "AfterConfiguration hook read feature directories: #{config.feature_dirs.join(', ')}" 
+        config.out_stream << "AfterConfiguration hook read feature directories: #{config.feature_dirs.join(', ')}"
       end
       """
-    When I run cucumber features
-    Then STDERR should be empty
-    And the output should contain
+    When I run `cucumber features`
+    Then the stderr should not contain anything
+    And the output should contain:
       """
       AfterConfiguration hook read feature directories: features
-      """
+      """

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

@@ -1,4 +1,5 @@
 Feature: Profiles
+
   In order to save time and prevent carpal tunnel syndrome
   Cucumber users can save and reuse commonly used cucumber flags in a 'cucumber.yml' file.
   These named arguments are called profiles and the yml file should be in the root of your project.
@@ -7,15 +8,14 @@ Feature: Profiles
   http://wiki.github.com/cucumber/cucumber/cucumber.yml
 
   Background: Basic App
-    Given a standard Cucumber project directory structure
-    And a file named "features/sample.feature" with:
+    Given a file named "features/sample.feature" with:
       """
       Feature: Sample
         Scenario: this is a test
-          Given I am just testing stuff
+          Given this step raises an error
       """
-    And a file named "features/support/env.rb"
-    And a file named "features/support/super_env.rb"
+    And an empty file named "features/support/env.rb"
+    And an empty file named "features/support/super_env.rb"
     And the following profiles are defined:
       """
       default: features/sample.feature --require features/support/env.rb -v
@@ -23,8 +23,8 @@ Feature: Profiles
       """
 
   Scenario: Explicitly defining a profile to run
-    When I run cucumber features/sample.feature --profile super
-    Then the output should contain
+    When I run `cucumber features/sample.feature --profile super`
+    Then the output should contain:
       """
       Using the super profile...
       """
@@ -36,29 +36,29 @@ Feature: Profiles
       <% requires = "--require features/support/super_env.rb" %>
       super: <%= "features/sample.feature #{requires} -v" %>
       """
-    When I run cucumber features/sample.feature --profile super
-    Then the output should contain
+    When I run `cucumber features/sample.feature --profile super`
+    Then the output should contain:
       """
       Using the super profile...
       """
     And exactly these files should be loaded: features/support/super_env.rb
 
   Scenario: Defining multiple profiles to run
-    When I run cucumber features/sample.feature --profile default --profile super
-    Then the output should contain
+    When I run `cucumber features/sample.feature --profile default --profile super`
+    Then the output should contain:
       """
       Using the default and super profiles...
       """
     And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
 
   Scenario: Arguments passed in but no profile specified
-    When I run cucumber -v
+    When I run `cucumber -v`
     Then the default profile should be used
     And exactly these files should be loaded: features/support/env.rb
 
   Scenario: Trying to use a missing profile
-    When I run cucumber -p foo
-    Then STDERR should be
+    When I run `cucumber -p foo`
+    Then the stderr should contain:
       """
       Could not find profile: 'foo'
 
@@ -69,26 +69,25 @@ Feature: Profiles
       """
 
   Scenario Outline: Disabling the default profile
-    When I run cucumber -v features/ <Flag>
-    Then the output should contain
+    When I run `cucumber -v features/ <flag>`
+    Then the output should contain:
       """
       Disabling profiles...
       """
     And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
 
     Examples:
-    |   Flag          |
-    | -P              |
-    | --no-profile    |
-
+      | flag         |
+      | -P           |
+      | --no-profile |
 
   Scenario: Overriding the profile's features to run
     Given a file named "features/another.feature" with:
       """
       Feature: Just this one should be ran
       """
-      When I run cucumber -p default features/another.feature
-      Then exactly these features should be ran: features/another.feature
+    When I run `cucumber -p default features/another.feature`
+    Then exactly these features should be ran: features/another.feature
 
   Scenario: Overriding the profile's formatter
     You will most likely want to define a formatter in your default formatter.
@@ -101,26 +100,21 @@ Feature: Profiles
       """
       default: features/sample.feature --require features/support/env.rb -v --format profile
       """
-    When I run cucumber features --format pretty
-    And the output should contain
+    When I run `cucumber features --format pretty`
+    Then the output should contain:
       """
       Feature: Sample
       """
 
   Scenario Outline: Showing profiles when listing failing scenarios
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^I am just testing stuff$/ do
-        raise 'BANG'
-      end
-      """
-    When I run cucumber -q -p super -p default -f <format> features/sample.feature --require features/step_definitions/steps.rb
-    Then it should fail
-    And the output should contain
+    Given the standard step definitions
+    When I run `cucumber -q -p super -p default -f <format> features/sample.feature --require features/step_definitions/steps.rb`
+    Then it should fail with:
        """
        cucumber -p super features/sample.feature:2
        """
+
     Examples:
-      | format  |
-      | pretty  |
-      | progress|
+      | format   |
+      | pretty   |
+      | progress |

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/{legacy_features/wire_protocol_erb.feature → features/docs/wire_protocol/erb_configuration.feature}

@@ -1,13 +1,12 @@
 @wire
-Feature: Wire Protocol with ERB
-  In order to be allow Cucumber to touch my app in intimate places
+Feature: ERB configuration
+
   As a developer on server with multiple users
   I want to be able to configure which port my wire server runs on
   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
 

data/features/docs/wire_protocol/handle_unexpected_response.feature

@@ -0,0 +1,30 @@
+@wire
+Feature: Handle unexpected response
+
+  When the server sends us back a message we don't understand, this is how Cucumber will behave.
+
+  Background:
+    Given a file named "features/wired.feature" with:
+      """
+      Feature: High strung
+        Scenario: Wired
+          Given we're all wired
+
+      """
+    And a file named "features/step_definitions/some_remote_place.wire" with:
+      """
+      host: localhost
+      port: 54321
+
+      """
+
+  Scenario: Unexpected response
+    Given there is a wire server running on port 54321 which understands the following protocol:
+      | 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 output should contain:
+      """
+      undefined method `handle_yikes'
+      """