cucumber 1.3.20 → 2.0.0.beta.1

data/features/docs/cli/run_scenarios_matching_name.feature

@@ -0,0 +1,104 @@
+Feature: Run feature elements matching a name with --name/-n
+
+  The `--name NAME` option runs only scenarios which match a certain
+  name. The NAME can be a substring of the names of Features, Scenarios,
+  Scenario Outlines or Example blocks.
+
+  Background:
+    Given a file named "features/first.feature" with:
+      """
+      Feature: first feature
+        Scenario: foo first
+          Given missing
+        Scenario: bar first
+          Given missing
+      """
+    Given a file named "features/second.feature" with:
+      """
+      Feature: second
+        Scenario: foo second
+          Given missing
+        Scenario: bar second
+          Given missing
+      """
+    Given a file named "features/outline.feature" with:
+      """
+      Feature: outline
+        Scenario Outline: baz outline
+          Given outline step <name>
+
+          Examples: quux example
+            | name |
+            | a    |
+            | b    |
+      """
+
+  Scenario: Matching Feature names
+    When I run `cucumber -q --name feature`
+    Then it should pass with:
+      """
+      Feature: first feature
+
+        Scenario: foo first
+          Given missing
+
+        Scenario: bar first
+          Given missing
+
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+      """
+
+  Scenario: Matching Scenario names
+    When I run `cucumber -q --name foo`
+    Then it should pass with:
+      """
+      Feature: first feature
+
+        Scenario: foo first
+          Given missing
+
+      Feature: second
+
+        Scenario: foo second
+          Given missing
+
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+      """
+
+  Scenario: Matching Scenario Outline names
+    When I run `cucumber -q --name baz`
+    Then it should pass with:
+      """
+      Feature: outline
+
+        Scenario Outline: baz outline
+          Given outline step <name>
+
+          Examples: quux example
+            | name |
+            | a    |
+            | b    |
+
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+      """
+
+  Scenario: Matching Example block names
+    When I run `cucumber -q --name quux`
+    Then it should pass with:
+      """
+      Feature: outline
+
+        Scenario Outline: baz outline
+          Given outline step <name>
+
+          Examples: quux example
+            | name |
+            | a    |
+            | b    |
+
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+      """

data/features/docs/cli/run_specific_scenarios.feature

@@ -0,0 +1,113 @@
+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.
+
+  Background:
+    Given the standard step definitions
+
+  Scenario: Two scenarios, run just one of them
+    Given a file named "features/test.feature" with:
+      """
+      Feature: 
+        Scenario:
+          Given this step is undefined
+
+        Scenario: Hit
+          Given this step passes
+      """
+    When I run `cucumber features/test.feature:5 -f progress`
+    Then it should pass with:
+      """
+      1 scenario (1 passed)
+      """
+
+  Scenario: Single example from a scenario outline
+    Given a file named "features/test.feature" with:
+      """
+      Feature:
+        Scenario Outline:
+          Given this step <something>
+
+          Examples:
+            | something    |
+            | is undefined |
+            | fails        |
+
+        Scenario: Miss
+          Given this step passes
+      """
+    When I run `cucumber features/test.feature:8 -f progress`
+    Then it should fail with:
+      """
+      1 scenario (1 failed)
+      """
+
+  @spawn
+  Scenario: Specify 2 line numbers where one is a tag
+    Given a file named "features/test.feature" with:
+      """
+      Feature: Sample
+
+        @two @three
+        Scenario:
+          Given this step passes
+
+        @four
+        Scenario:
+          Given this step passes
+      """
+    When I run `cucumber -q features/test.feature:3:8`
+    Then it should pass with:
+      """
+      2 scenarios (2 passed)
+      2 steps (2 passed)
+      """
+
+  Scenario: Specify the line number of a row
+    Given a file named "features/test.feature" with:
+      """
+      Feature: Sample
+        Scenario: Passing
+          Given this step is a table step
+            | a | b |
+            | c | d |
+
+      """
+    When I run `cucumber -q features/test.feature:4`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        Scenario: Passing
+          Given this step is a table step
+            | a | b |
+            | c | d |
+
+      1 scenario (1 passed)
+      1 step (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)
+      """

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,41 @@
+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
+    """
+
+  Scenario: Fail with --strict
+    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: 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}

@@ -112,16 +112,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:

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,147 @@
+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: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
+        ...
+        """
+