cucumber 1.3.10 → 2.0.0

data/features/{background.feature → docs/gherkin/background.feature}

@@ -1,8 +1,16 @@
 Feature: Background
-  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.
 
+  Often you find that several scenarios in the same feature start with 
+  a common context.
+  
+  Cucumber provides a mechanism for this, by providing a `Background` keyword
+  where you can specify steps that should be run before each scenario in the
+  feature. Typically these will be `Given` steps, but you can use any steps
+  that you need to.
+  
+  **Hint:** if you find that some of the scenarios don't fit the background,
+  consider splitting them into a separate feature.
+  
   Background:
     Given a file named "features/passing_background.feature" with:
       """
@@ -42,7 +50,7 @@ Feature: Background
       Feature: Background tagged Before on Outline
 
         Background: 
-          Given passing without a table
+          Given this step passes
 
         Scenario Outline: passing background
           Then I should have '<count>' cukes
@@ -56,7 +64,7 @@ Feature: Background
       Feature: Failing background sample
 
         Background:
-          Given failing without a table
+          Given this step raises an error
           And '10' cukes
 
         Scenario: failing background
@@ -70,7 +78,7 @@ Feature: Background
       Feature: Failing background with scenario outlines sample
 
         Background:
-          Given failing without a table
+          Given this step raises an error
 
         Scenario Outline: failing background
           Then I should have '<count>' cukes
@@ -89,7 +97,7 @@ Feature: Background
       Feature: Pending background sample
 
         Background:
-          Given pending
+          Given this step is pending
 
         Scenario: pending background
           Then I should have '10' cukes
@@ -102,7 +110,7 @@ Feature: Background
       Feature: Failing background after previously successful background sample
 
         Background:
-          Given passing without a table
+          Given this step passes
           And '10' global cukes
 
         Scenario: passing background
@@ -111,6 +119,29 @@ Feature: Background
         Scenario: failing background
           Then I should have '10' global cukes
       """
+    And a file named "features/failing_background_after_success_outline.feature" with:
+      """
+      Feature: Failing background after previously successful background sample
+
+        Background:
+          Given this step passes
+          And '10' global cukes
+
+        Scenario Outline: passing background
+          Then I should have '<count>' global cukes
+
+          Examples: 
+            | count |
+            | 10    |
+
+        Scenario Outline: failing background
+          Then I should have '<count>' global cukes
+
+          Examples: 
+            | count |
+            | 10    |
+
+      """
     And a file named "features/multiline_args_background.feature" with:
       """
       Feature: Passing background with multiline args
@@ -145,37 +176,27 @@ Feature: Background
             I sleep all night and I test all day
             \"\"\"
       """
-    And a file named "features/step_definitions/steps.rb" with:
+    And the standard step definitions
+    And a file named "features/step_definitions/cuke_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
+        raise 'FAIL' if $scenario_runs >= 1
         $cukes = cukes
         $scenario_runs += 1
       end
 
       Then /^I should have '(.+)' global cukes$/ do |cukes| x=1
-        $cukes.should == cukes
+        expect($cukes).to eq cukes
       end
 
       Then /^I should have '(.+)' cukes$/ do |cukes| x=1
-        @cukes.should == cukes
+        expect(@cukes).to eq cukes
       end
 
       Before('@background_tagged_before_on_outline') do
@@ -183,7 +204,7 @@ Feature: Background
       end
 
       After('@background_tagged_before_on_outline') do
-        @cukes.should == '888'
+        expect(@cukes).to eq '888'
       end
       """
 
@@ -263,7 +284,7 @@ Feature: Background
     Feature: Background tagged Before on Outline
 
       Background: 
-        Given passing without a table
+        Given this step passes
 
       Scenario Outline: passing background
         Then I should have '<count>' cukes
@@ -286,11 +307,10 @@ Feature: Background
     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'
+        Given this step raises an error
+          error (RuntimeError)
+          ./features/step_definitions/steps.rb:2:in `/^this step raises an error$/'
+          features/failing_background.feature:4:in `Given this step raises an error'
         And '10' cukes
 
       Scenario: failing background
@@ -301,9 +321,10 @@ Feature: Background
 
     Failing Scenarios:
     cucumber features/failing_background.feature:7
+    cucumber features/failing_background.feature:10
     
-    2 scenarios (1 failed, 1 skipped)
-    6 steps (1 failed, 5 skipped)
+    2 scenarios (2 failed)
+    6 steps (2 failed, 4 skipped)
     0m0.012s
     
     """
@@ -316,11 +337,10 @@ Feature: Background
     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'
+        Given this step raises an error
+          error (RuntimeError)
+          ./features/step_definitions/steps.rb:2:in `/^this step raises an error$/'
+          features/scenario_outline_failing_background.feature:4:in `Given this step raises an error'
 
       Scenario Outline: failing background
         Then I should have '<count>' cukes
@@ -337,10 +357,11 @@ Feature: Background
           | 10    |
 
     Failing Scenarios:
-    cucumber features/scenario_outline_failing_background.feature:6
+    cucumber features/scenario_outline_failing_background.feature:10
+    cucumber features/scenario_outline_failing_background.feature:16
 
-    2 scenarios (1 failed, 1 skipped)
-    4 steps (1 failed, 3 skipped)
+    2 scenarios (2 failed)
+    4 steps (2 failed, 2 skipped)
     0m0.012s
     
     """
@@ -352,7 +373,10 @@ Feature: Background
     Feature: Pending background sample
 
       Background: 
-        Given pending
+        Given this step is pending
+          TODO (Cucumber::Pending)
+          ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+          features/pending_background.feature:4:in `Given this step is pending'
 
       Scenario: pending background
         Then I should have '10' cukes
@@ -360,8 +384,8 @@ Feature: Background
       Scenario: another pending background
         Then I should have '10' cukes
 
-    2 scenarios (2 undefined)
-    4 steps (2 skipped, 2 undefined)
+    2 scenarios (2 pending)
+    4 steps (2 skipped, 2 pending)
     0m0.012s
     
     """
@@ -374,7 +398,7 @@ Feature: Background
     Feature: Failing background after previously successful background sample
 
       Background: 
-        Given passing without a table
+        Given this step passes
         And '10' global cukes
 
       Scenario: passing background
@@ -383,8 +407,7 @@ 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/step_definitions/cuke_steps.rb:8:in `/^'(.+)' global cukes$/'
           features/failing_background_after_success.feature:5:in `And '10' global cukes'
         Then I should have '10' global cukes
 
@@ -397,8 +420,85 @@ Feature: Background
     
     """
 
+  @spawn
+  Scenario: background passes with first outline scenario but fails with second
+    When I run `cucumber -q features/failing_background_after_success_outline.feature`
+    Then it should fail with exactly:
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given this step passes
+        And '10' global cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+      Scenario Outline: failing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+          | count |
+          | 10    |
+          FAIL (RuntimeError)
+          ./features/step_definitions/cuke_steps.rb:8:in `/^'(.+)' global cukes$/'
+          features/failing_background_after_success_outline.feature:5:in `And '10' global cukes'
+
+    Failing Scenarios:
+    cucumber features/failing_background_after_success_outline.feature:19
+
+    2 scenarios (1 failed, 1 passed)
+    6 steps (1 failed, 1 skipped, 4 passed)
+    0m0.012s
+    
+    """
+
+  @spawn
+  Scenario: background passes with first outline scenario but fails with second (--expand)
+    When I run `cucumber -x -q features/failing_background_after_success_outline.feature`
+    Then it should fail with exactly:
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given this step passes
+        And '10' global cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+ 
+          Scenario: | 10 |
+            Then I should have '10' global cukes
+
+      Scenario Outline: failing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+
+          Scenario: | 10 |
+            And '10' global cukes
+          FAIL (RuntimeError)
+          ./features/step_definitions/cuke_steps.rb:8:in `/^'(.+)' global cukes$/'
+          features/failing_background_after_success_outline.feature:5:in `And '10' global cukes'
+            Then I should have '10' global cukes
+
+    Failing Scenarios:
+    cucumber features/failing_background_after_success_outline.feature:19
+
+    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 a file named "features/step_definitions/steps.rb" with:
       """
       Given /^table$/ do |table| x=1
         @table = table
@@ -409,11 +509,11 @@ Feature: Background
       end
 
       Then /^the table should be$/ do |table| x=1
-        @table.raw.should == table.raw
+        expect(@table.raw).to eq table.raw
       end
 
       Then /^the multiline string should be$/ do |string| x=1
-        @multiline.should == string
+        expect(@multiline).to eq string
       end
       """
     When I run `cucumber -q features/multiline_args_background.feature`
@@ -457,45 +557,3 @@ Feature: Background
     
       """
 
-  Scenario: https://rspec.lighthouseapp.com/projects/16211/tickets/329
-    Given a file named "features/only_background_and_hooks.feature" with:
-      """
-      Feature: woo yeah
-
-        Background: Whatever
-          Given whatever
-
-      """
-    And a file named "features/only_background_and_hooks_steps.rb" with:
-      """
-      begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
-
-      Before do
-        $before = true
-      end
-
-      After do
-        $after = true
-      end
-
-      Given(/^whatever$/) { $before.should == true; $step = true }
-
-      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 with exactly:
-      """
-      Feature: woo yeah
-
-        Background: Whatever # 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
-
-      """

data/features/{doc_strings.feature → docs/gherkin/doc_strings.feature}

@@ -24,6 +24,7 @@ Feature: Doc strings
     """ruby
     puts "hello world"
     """
+  ```
   
   You can read the content type from the argument passed into your step definition, as shown
   in the example below.

data/features/docs/gherkin/expand_option_for_outlines.feature

@@ -0,0 +1,46 @@
+Feature: Scenario outlines --expand option
+
+  In order to make it easier to write certain editor plugins and also
+  for some people to understand scenarios, Cucumber will expand examples
+  in outlines if you add the `--expand` option when running them.
+
+  Scenario:
+    Given a file named "features/test.feature" with:
+      """
+      Feature:
+        Scenario Outline:
+          Given the secret code is <code>
+          When I guess <guess>
+          Then I am <verdict>
+
+        Examples:
+          | code | guess | verdict |
+          | blue | blue  | right   |
+          | red  | blue  | wrong   |
+      """
+    When I run `cucumber -i -q --expand`
+    Then the stderr should not contain anything
+    And it should pass with:
+      """
+      Feature: 
+
+        Scenario Outline: 
+          Given the secret code is <code>
+          When I guess <guess>
+          Then I am <verdict>
+
+          Examples: 
+
+            Scenario: | blue | blue | right |
+              Given the secret code is blue
+              When I guess blue
+              Then I am right
+
+            Scenario: | red | blue | wrong |
+              Given the secret code is red
+              When I guess blue
+              Then I am wrong
+
+      2 scenarios (2 undefined)
+      6 steps (6 undefined)
+      """

data/features/docs/gherkin/language_from_header.feature

@@ -0,0 +1,32 @@
+Feature: Choosing the language from the feature file header
+
+  In order to simplify command line and settings in IDEs, Cucumber picks
+  up the parser language from a `# language` comment at the beginning of
+  any feature file. See the examples below for the exact syntax.
+
+  Scenario: LOLCAT
+    Given a file named "features/lolcat.feature" with:
+      """
+      # language: en-lol
+      OH HAI: STUFFING
+        B4: HUNGRY
+          I CAN HAZ EMPTY BELLY
+        MISHUN: CUKES
+          DEN KTHXBAI
+      """
+    When I run `cucumber -i features/lolcat.feature -q`
+    Then it should pass with:
+      """
+      # language: en-lol
+      OH HAI: STUFFING
+
+        B4: HUNGRY
+          I CAN HAZ EMPTY BELLY
+
+        MISHUN: CUKES
+          DEN KTHXBAI
+
+      1 scenario (1 undefined)
+      2 steps (2 undefined)
+
+      """

data/features/docs/gherkin/outlines.feature

@@ -0,0 +1,158 @@
+@spawn
+Feature: Scenario outlines
+
+  Copying and pasting scenarios to use different values quickly
+  becomes tedious and repetitive. Scenario outlines allow us to more
+  concisely express these examples through the use of a template with
+  placeholders, using Scenario Outline, Examples with tables and < >
+  delimited parameters.
+
+  The Scenario Outline steps provide a template which is never directly
+  run. A Scenario Outline is run once for each row in the Examples section
+  beneath it (not counting the first row).
+
+  The way this works is via placeholders. Placeholders must be contained
+  within < > in the Scenario Outline's steps - see the examples below.
+
+  **IMPORTANT:** Your step definitions will never have to match a
+  placeholder. They will need to match the values that will replace the
+  placeholder.
+
+  Background:
+    Given a file named "features/outline_sample.feature" with:
+      """
+      Feature: Outline Sample
+
+        Scenario: I have no steps
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+        Examples: Rainbow colours
+          | state    | other_state |
+          | missing  | passing     |
+          | passing  | passing     |
+          | failing  | passing     |
+      Examples:Only passing
+          | state    | other_state |
+          | passing  | passing     |
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given(/^passing without a table$/) { }
+      Given(/^failing without a table$/) { raise RuntimeError }
+      """
+
+  Scenario: Run scenario outline with filtering on outline name
+    When I run `cucumber -q features/outline_sample.feature`
+    Then it should fail with:
+      """
+      Feature: Outline Sample
+
+        Scenario: I have no steps
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | missing | passing     |
+            | passing | passing     |
+            | failing | passing     |
+            RuntimeError (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
+            features/outline_sample.feature:12:in `Given failing without a table'
+            features/outline_sample.feature:6:in `Given <state> without a table'
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      Failing Scenarios:
+      cucumber features/outline_sample.feature:12
+
+      5 scenarios (1 failed, 1 undefined, 3 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+      """
+
+  Scenario: Run scenario outline steps only
+    When I run `cucumber -q features/outline_sample.feature:7`
+    Then it should fail with:
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | missing | passing     |
+            | passing | passing     |
+            | failing | passing     |
+            RuntimeError (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
+            features/outline_sample.feature:12:in `Given failing without a table'
+            features/outline_sample.feature:6:in `Given <state> without a table'
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      Failing Scenarios:
+      cucumber features/outline_sample.feature:12
+
+      4 scenarios (1 failed, 1 undefined, 2 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+
+  Scenario: Run single failing scenario outline table row
+    When I run `cucumber -q features/outline_sample.feature:12`
+    Then it should fail with:
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | failing | passing     |
+            RuntimeError (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
+            features/outline_sample.feature:12:in `Given failing without a table'
+            features/outline_sample.feature:6:in `Given <state> without a table'
+
+      Failing Scenarios:
+      cucumber features/outline_sample.feature:12
+
+      1 scenario (1 failed)
+      2 steps (1 failed, 1 skipped)
+
+      """
+
+  Scenario: Run all with progress formatter
+    When I run `cucumber -q --format progress features/outline_sample.feature`
+    Then it should fail with exactly:
+      """
+      --UU..FF..
+
+      (::) failed steps (::)
+
+      RuntimeError (RuntimeError)
+      ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
+      features/outline_sample.feature:12:in `Given failing without a table'
+      features/outline_sample.feature:6:in `Given <state> without a table'
+
+      Failing Scenarios:
+      cucumber features/outline_sample.feature:12
+
+      5 scenarios (1 failed, 1 undefined, 3 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+      0m0.012s
+
+      """
+

data/features/docs/gherkin/unicode_table.feature

@@ -0,0 +1,32 @@
+@spawn
+Feature: Unicode in tables
+
+  You are free to use unicode in your tables: we've taken care to
+  ensure that the tables are properly aligned so that your output is as
+  readable as possible.
+
+  Scenario:
+    Given a file named "features/unicode.feature" with:
+      """
+      Feature: Featuring unicode
+
+        Scenario: table with unicode
+          Given passing
+            | Brüno | abc |
+            | Bruno | æøå |
+      """
+    When I run `cucumber -q --dry-run features/unicode.feature`
+    Then it should pass with:
+      """
+      Feature: Featuring unicode
+
+        Scenario: table with unicode
+          Given passing
+            | Brüno | abc |
+            | Bruno | æøå |
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """
+