cucumber 1.3.10 → 2.0.0

data/features/docs/cli/run_specific_scenarios.feature

@@ -0,0 +1,75 @@
+Feature: Run specific scenarios
+
+  You can choose to run a specific scenario using the file:line format,
+  or you can pass in a file with a list of scenarios using @-notation.
+
+  The line number can fall anywhere within the body of a scenario, including
+  steps, tags, comments, description, data tables or doc strings.
+
+  For scenario outlines, if the line hits one example row, just that one
+  will be run. Otherwise all examples in the table or outline will be run.
+
+  Background:
+    Given the standard step definitions
+
+  Scenario: Two scenarios, run just one of them
+    Given a file named "features/test.feature" with:
+      """
+      Feature: 
+
+        Scenario: Miss
+          Given this step is undefined
+
+        Scenario: Hit
+          Given this step passes
+      """
+    When I run `cucumber features/test.feature:7 --format pretty --quiet`
+    Then it should pass with:
+      """
+      Feature: 
+
+        Scenario: Hit
+          Given this step passes
+
+      1 scenario (1 passed)
+      """
+
+  Scenario: Use @-notation to specify a file containing feature file list
+    Given a file named "features/test.feature" with:
+      """
+      Feature: Sample
+        Scenario: Passing
+          Given this step passes
+      """
+    And a file named "list-of-features.txt" with:
+      """
+      features/test.feature:2
+      """
+    When I run `cucumber -q @list-of-features.txt`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        Scenario: Passing
+          Given this step passes
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+      """
+
+  Scenario: Specify order of scenarios
+    Given a file named "features/test.feature" with:
+      """
+      Feature: 
+        Scenario:
+          Given this step passes
+
+        Scenario:
+          Given this step fails
+      """
+    When I run `cucumber features/test.feature:5 features/test.feature:3 -f progress`
+    Then it should fail with:
+      """
+      F.
+      """
+

data/features/docs/cli/showing_differences.feature

@@ -0,0 +1,43 @@
+Feature: Showing differences to expected output
+
+  Cucumber will helpfully show you the expectation error that your
+  testing library gives you, in the context of the failing scenario.
+  When using RSpec, for example, this will show the difference between
+  the expected and the actual output.
+
+  Scenario: Run single failing scenario with default diff enabled
+    Given a file named "features/failing_expectation.feature" with:
+      """
+      Feature: Failing expectation
+
+        Scenario: Failing expectation
+          Given failing expectation
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^failing expectation$/ do x=1
+        expect('this').to eq 'that'
+      end
+      """
+    When I run `cucumber -q features/failing_expectation.feature`
+    Then it should fail with:
+      """
+      Feature: Failing expectation
+      
+        Scenario: Failing expectation
+          Given failing expectation
+            
+            expected: "that"
+                 got: "this"
+            
+            (compared using ==)
+             (RSpec::Expectations::ExpectationNotMetError)
+            ./features/step_definitions/steps.rb:2:in `/^failing expectation$/'
+            features/failing_expectation.feature:4:in `Given failing expectation'
+
+      Failing Scenarios:
+      cucumber features/failing_expectation.feature:3
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+      """

data/features/docs/cli/specifying_multiple_formatters.feature

@@ -0,0 +1,44 @@
+@spawn
+Feature: Running multiple formatters
+
+  When running cucumber, you are able to using multiple different
+  formatters and redirect the output to text files.
+
+  Scenario: Multiple formatters and outputs
+    Given a file named "features/test.feature" with:
+    """
+    Feature: Lots of undefined
+
+      Scenario: Implement me
+        Given it snows in Sahara
+        Given it's 40 degrees in Norway
+        And it's 40 degrees in Norway
+        When I stop procrastinating
+        And there is world peace
+    """
+    When I run `cucumber --no-color --format progress --out progress.txt --format pretty --out pretty.txt --no-source --dry-run --no-snippets features/test.feature`
+    Then the stderr should not contain anything
+    Then the file "progress.txt" should contain:
+      """
+      UUUUU
+
+      1 scenario (1 undefined)
+      5 steps (5 undefined)
+
+      """
+    And the file "pretty.txt" should contain:
+      """
+      Feature: Lots of undefined
+
+        Scenario: Implement me
+          Given it snows in Sahara
+          Given it's 40 degrees in Norway
+          And it's 40 degrees in Norway
+          When I stop procrastinating
+          And there is world peace
+
+      1 scenario (1 undefined)
+      5 steps (5 undefined)
+
+      """
+

data/features/docs/cli/strict_mode.feature

@@ -0,0 +1,64 @@
+Feature: Strict mode
+
+  Using the `--strict` flag will cause cucumber to fail unless all the
+  step definitions have been defined.
+
+  Background:
+    Given a file named "features/missing.feature" with:
+    """
+    Feature: Missing
+      Scenario: Missing
+        Given this step passes
+    """
+    And a file named "features/pending.feature" with:
+    """
+    Feature: Pending
+      Scenario: Pending
+        Given this step is pending
+    """
+
+  Scenario: Fail with --strict due to undefined step
+    When I run `cucumber -q features/missing.feature --strict`
+    Then it should fail with:
+      """
+      Feature: Missing
+
+        Scenario: Missing
+          Given this step passes
+            Undefined step: "this step passes" (Cucumber::Undefined)
+            features/missing.feature:3:in `Given this step passes'
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+
+  Scenario: Fail with --strict due to pending step
+    Given the standard step definitions
+    When I run `cucumber -q features/pending.feature --strict`
+    Then it should fail with:
+      """
+      Feature: Pending
+
+        Scenario: Pending
+          Given this step is pending
+            TODO (Cucumber::Pending)
+            ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+            features/pending.feature:3:in `Given this step is pending'
+
+      1 scenario (1 pending)
+      1 step (1 pending)
+      """
+
+  Scenario: Succeed with --strict
+    Given the standard step definitions
+    When I run `cucumber -q features/missing.feature --strict`
+    Then it should pass with:
+    """
+    Feature: Missing
+
+      Scenario: Missing
+        Given this step passes
+
+    1 scenario (1 passed)
+    1 step (1 passed)
+    """

data/features/{nested_steps.feature → docs/defining_steps/nested_steps.feature}

@@ -1,6 +1,5 @@
 Feature: Nested Steps
 
-
   Background:
     Given a scenario with a step that looks like this:
       """gherkin
@@ -112,16 +111,14 @@ Feature: Nested Steps
         step "I have a couple turtles"
       end
 
-      When /I have a couple turtles/ do
-        raise 'error'
-      end
+      When(/I have a couple turtles/) { raise 'error' }
       """
     When I run the feature with the progress formatter
     Then it should fail with:
       """
       error (RuntimeError)
-      ./features/step_definitions/test_steps2.rb:6:in `/I have a couple turtles/'
-      ./features/step_definitions/test_steps2.rb:2:in `/two turtles/'
+      ./features/step_definitions/steps2.rb:5:in `/I have a couple turtles/'
+      ./features/step_definitions/steps2.rb:2:in `/two turtles/'
       features/test_feature_1.feature:3:in `Given two turtles'
 
       Failing Scenarios:
@@ -130,3 +127,52 @@ Feature: Nested Steps
       1 scenario (1 failed)
       1 step (1 failed)
       """
+
+  Scenario: Undefined nested step
+    Given a file named "features/call_undefined_step_from_step_def.feature" with:
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly
+          Given a step that calls an undefined step
+
+        Scenario: Call via another
+          Given a step that calls a step that calls an undefined step
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^a step that calls an undefined step$/ do
+        step 'this does not exist'
+      end
+
+      Given /^a step that calls a step that calls an undefined step$/ do
+        step 'a step that calls an undefined step'
+      end
+      """
+    When I run `cucumber -q features/call_undefined_step_from_step_def.feature`
+    Then it should fail with exactly:
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly
+          Given a step that calls an undefined step
+            Undefined dynamic step: "this does not exist" (Cucumber::UndefinedDynamicStep)
+            ./features/step_definitions/steps.rb:2:in `/^a step that calls an undefined step$/'
+            features/call_undefined_step_from_step_def.feature:4:in `Given a step that calls an undefined step'
+
+        Scenario: Call via another
+          Given a step that calls a step that calls an undefined step
+            Undefined dynamic step: "this does not exist" (Cucumber::UndefinedDynamicStep)
+            ./features/step_definitions/steps.rb:2:in `/^a step that calls an undefined step$/'
+            ./features/step_definitions/steps.rb:6:in `/^a step that calls a step that calls an undefined step$/'
+            features/call_undefined_step_from_step_def.feature:7:in `Given a step that calls a step that calls an undefined step'
+
+      Failing Scenarios:
+      cucumber features/call_undefined_step_from_step_def.feature:3
+      cucumber features/call_undefined_step_from_step_def.feature:6
+
+      2 scenarios (2 failed)
+      2 steps (2 failed)
+      0m0.012s
+
+      """

data/features/{nested_steps_i18n.feature → docs/defining_steps/nested_steps_i18n.feature}

@@ -1,7 +1,5 @@
-@fails_on_1_8_7
 Feature: Nested Steps in I18n
 
-
   Background:
     Given a scenario with a step that looks like this in japanese:
       """gherkin

data/features/{step_definitions.feature → docs/defining_steps/one_line_step_definitions.feature}

@@ -1,4 +1,4 @@
-Feature: Step Definitions
+Feature: One line step definitions
 
   Everybody knows you can do step definitions in Cucumber
   but did you know you can do this?
@@ -12,7 +12,7 @@ Feature: Step Definitions
         end
 
         def assert_done
-          @done.should be_true
+          expect(@done).to be true
         end
       end
       World(Driver)
@@ -39,7 +39,7 @@ Feature: Step Definitions
         end
 
         def assert_done
-          @done.should be_true
+          expect(@done).to be true
         end
       end
 

data/features/docs/defining_steps/printing_messages.feature

@@ -0,0 +1,148 @@
+Feature: Pretty formatter - Printing messages
+
+  When you want to print to Cucumber's output, just call `puts` from
+  a step definition. Cucumber will grab the output and print it via
+  the formatter that you're using.
+  
+  Your message will be printed out after the step has run.
+
+  Background:
+    Given the standard step definitions
+    And a file named "features/step_definitions/puts_steps.rb" with:
+      """
+      Given /^I use puts with text "(.*)"$/ do |ann|
+        puts(ann)
+      end
+
+      Given /^I use multiple putss$/ do
+        puts("Multiple")
+        puts("Announce","Me")
+      end
+
+      Given /^I use message (.+) in line (.+) (?:with result (.+))$/ do |ann, line, result|
+        puts("Last message") if line == "3"
+        puts("Line: #{line}: #{ann}")
+        fail if result =~ /fail/i
+      end
+
+      Given /^I use puts and step fails$/ do
+        puts("Announce with fail")
+        fail
+      end
+
+      Given /^I puts the world$/ do
+        puts(self)
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature:
+
+        Scenario:
+          Given I use puts with text "Ann"
+          And this step passes
+
+        Scenario:
+          Given I use multiple putss
+          And this step passes
+
+        Scenario Outline:
+          Given I use message <ann> in line <line>
+
+          Examples:
+            | line | ann   |
+            | 1    | anno1 |
+            | 2    | anno2 |
+            | 3    | anno3 |
+
+        Scenario:
+          Given I use puts and step fails
+          And this step passes
+
+        Scenario Outline:
+          Given I use message <ann> in line <line> with result <result>
+
+          Examples:
+            | line | ann   | result |
+            | 1    | anno1 | fail   |
+            | 2    | anno2 | pass   |
+      """
+
+    And a file named "features/puts_world.feature" with:
+      """
+      Feature: puts_world
+        Scenario: puts_world
+          Given I puts the world
+      """
+
+    # Don't know why, but we need to spawn this for JRuby otherwise it gives wierd errors
+    @spawn
+    Scenario: Delayed messages feature
+      When I run `cucumber --quiet --format pretty features/f.feature`
+      Then the stderr should not contain anything
+      And the output should contain:
+      """
+      Feature: 
+
+        Scenario: 
+          Given I use puts with text "Ann"
+            Ann
+          And this step passes
+
+        Scenario: 
+          Given I use multiple putss
+            Multiple
+            Announce
+            Me
+          And this step passes
+
+        Scenario Outline: 
+          Given I use message <ann> in line <line>
+
+          Examples: 
+            | line | ann   |
+            | 1    | anno1 |
+            | 2    | anno2 |
+            | 3    | anno3 |
+
+        Scenario: 
+          Given I use puts and step fails
+            Announce with fail
+             (RuntimeError)
+            ./features/step_definitions/puts_steps.rb:18:in `/^I use puts and step fails$/'
+            features/f.feature:21:in `Given I use puts and step fails'
+          And this step passes
+
+        Scenario Outline: 
+          Given I use message <ann> in line <line> with result <result>
+
+          Examples: 
+            | line | ann   | result |
+            | 1    | anno1 | fail   |  Line: 1: anno1
+             (RuntimeError)
+            ./features/step_definitions/puts_steps.rb:13:in `/^I use message (.+) in line (.+) (?:with result (.+))$/'
+            features/f.feature:29:in `Given I use message anno1 in line 1 with result fail'
+            features/f.feature:25:in `Given I use message <ann> in line <line> with result <result>'
+            | 2    | anno2 | pass   |  Line: 2: anno2
+      """
+
+    Scenario: Non-delayed messages feature (progress formatter)
+      When I run `cucumber --format progress features/f.feature`
+      Then the output should contain:
+        """
+        Ann
+        ..
+        Multiple
+        
+        Announce
+        
+        Me
+        ..-UUUUUU
+        Announce with fail
+        F--
+        Line: 1: anno1
+        FFF
+        Line: 2: anno2
+        ...
+        """
+

data/features/docs/defining_steps/skip_scenario.feature

@@ -0,0 +1,62 @@
+Feature: Skip Scenario
+
+  Scenario: With a passing step
+    Given a file named "features/test.feature" with:
+      """
+      Feature: test
+        Scenario: test
+          Given this step says to skip
+          And this step passes
+      """
+    And the standard step definitions
+    And a file named "features/step_definitions/skippy.rb" with:
+      """
+      Given /skip/ do
+        skip_this_scenario
+      end
+      """
+    When I run `cucumber -q`
+    Then it should pass with exactly:
+      """
+      Feature: test
+
+        Scenario: test
+          Given this step says to skip
+          And this step passes
+
+      1 scenario (1 skipped)
+      2 steps (2 skipped)
+      0m0.012s
+
+      """
+
+  Scenario: Use legacy API from a hook
+    Given a file named "features/test.feature" with:
+      """
+      Feature: test
+        Scenario: test
+          Given this step passes
+          And this step passes
+      """
+    And the standard step definitions
+    And a file named "features/support/hook.rb" with:
+      """
+      Before do |scenario|
+        scenario.skip_invoke!
+      end
+      """
+    When I run `cucumber -q`
+    Then it should pass with:
+      """
+      Feature: test
+
+        Scenario: test
+          Given this step passes
+          And this step passes
+
+      1 scenario (1 skipped)
+      2 steps (2 skipped)
+      0m0.012s
+
+      """
+

data/features/docs/defining_steps/snippets.feature

@@ -0,0 +1,56 @@
+Feature: Snippets
+
+  Cucumber helpfully prints out any undefined step definitions as a code
+  snippet suggestion, which you can then paste into a step definitions
+  file of your choosing.
+
+  Scenario: Snippet for undefined step with a pystring
+    Given a file named "features/undefined_steps.feature" with:
+      """
+      Feature:
+      Scenario: pystring
+        Given a pystring
+        \"\"\"
+          example with <html> entities
+        \"\"\"
+        When a simple when step
+        And another when step
+        Then a simple then step
+      """
+    When I run `cucumber features/undefined_steps.feature -s`
+    Then the output should contain:
+      """
+      Given(/^a pystring$/) do |string|
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+
+      When(/^a simple when step$/) do
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+
+      When(/^another when step$/) do
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+
+      Then(/^a simple then step$/) do
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+      """
+
+  Scenario: Snippet for undefined step with a step table
+    Given a file named "features/undefined_steps.feature" with:
+      """
+      Feature:
+      Scenario: table
+        Given a table
+          | table |
+          |example|
+      """
+    When I run `cucumber features/undefined_steps.feature -s`
+    Then the output should contain:
+      """
+      Given(/^a table$/) do |table|
+        # table is a Cucumber::Core::Ast::DataTable
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+      """

data/{legacy_features → features/docs/defining_steps}/table_diffing.feature

@@ -1,11 +1,11 @@
 Feature: Table diffing
-  In order to more easily compare data in tables
-  step definition writers should be able to diff
-  a table with expected data and see the diff inline
-  
+
+  To allow you to more easily compare data in tables, you are able
+  to easily diff a table with expected data and see the diff in your
+  output.
+
   Scenario: Extra row
-    Given a standard Cucumber project directory structure
-    And a file named "features/tables.feature" with:
+    Given a file named "features/tables.feature" with:
       """
       Feature: Tables
         Scenario: Extra row
@@ -13,33 +13,38 @@ Feature: Table diffing
             | x | y |
             | a | b |
       """
-    And a file named "features/step_definitions/table_steps.rb" with:
+    And a file named "features/step_definitions/steps.rb" with:
       """
       Then /the table should be:/ do |expected| x=1
         expected.diff!(table(%{
-          | x | y | 
+          | x | y |
           | a | c |
         }))
       end
       """
-    When I run cucumber -i features/tables.feature
-    Then it should fail with
+    When I run `cucumber features/tables.feature`
+    Then it should fail with exactly:
       """
       Feature: Tables
-      
+
         Scenario: Extra row         # features/tables.feature:2
-          Then the table should be: # features/step_definitions/table_steps.rb:1
+          Then the table should be: # features/step_definitions/steps.rb:1
             | x | y |
             | a | b |
-            | a | c |
-            Tables were not identical (Cucumber::Ast::Table::Different)
-            ./features/step_definitions/table_steps.rb:2:in `/the table should be:/'
+            Tables were not identical:
+            
+              |     x |     y |
+              | (-) a | (-) b |
+              | (+) a | (+) c |
+             (Cucumber::MultilineArgument::DataTable::Different)
+            ./features/step_definitions/steps.rb:2:in `/the table should be:/'
             features/tables.feature:3:in `Then the table should be:'
-      
+
       Failing Scenarios:
       cucumber features/tables.feature:2 # Scenario: Extra row
 
       1 scenario (1 failed)
       1 step (1 failed)
+      0m0.012s
 
       """

data/features/{transforms.feature → docs/defining_steps/transforms.feature}

@@ -37,7 +37,7 @@ Feature: Transforms
       end
       
       Given /^(a Person aged \d+) with blonde hair$/ do |person|
-        person.age.should == 15
+        expect(person.age).to eq 15
       end
       """
     When I run `cucumber features/foo.feature`
@@ -56,7 +56,7 @@ Feature: Transforms
       end
 
       Given /^(#{A_PERSON}) with blonde hair$/ do |person|
-        person.age.should == 15
+        expect(person.age).to eq 15
       end
       """
     When I run `cucumber features/foo.feature`