cucumber 0.8.5 → 0.8.6

data/features/bug_464.feature

@@ -1,16 +0,0 @@
-Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/464
-  Scenario: Limiting with tags which do not exist in the features
-    Given a standard Cucumber project directory structure
-    And a file named "features/f.feature" with:
-      """
-      Feature: Test
-      In order to test
-      As a tester
-      I want to test
-
-        @tag
-        Scenario: Testing
-          Given I'm a test
-      """
-    When I run cucumber -q features/f.feature --tag @i_dont_exist
-    Then it should pass

data/features/bug_475.feature

@@ -1,42 +0,0 @@
-Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/475
-  Scenario: error on pystring in scenario outline with pretty formatter
-    Given a standard Cucumber project directory structure
-    And a file named "features/f.feature" with:
-      """
-      Feature: F
-        Scenario Outline: S
-          Given a multiline string:
-             \"\"\"
-             hello <who>
-             \"\"\"
-        Examples:
-          | who   |
-          | aslak |
-          | david |
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /a multiline string:/ do |s| s.should =~ /hello (\w+)/
-      end
-      """
-    When I run cucumber features/f.feature
-    Then STDERR should be empty
-    And it should pass with
-      """
-      Feature: F
-
-        Scenario Outline: S         # features/f.feature:2
-          Given a multiline string: # features/step_definitions/steps.rb:1
-            \"\"\"
-            hello <who>
-            \"\"\"
-
-          Examples: 
-            | who   |
-            | aslak |
-            | david |
-
-      2 scenarios (2 passed)
-      2 steps (2 passed)
-      
-      """

data/features/bug_585_tab_indentation.feature

@@ -1,22 +0,0 @@
-# Make sure tab indentation is preserved in this feature!
-Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/585
-	Scenario: Tab indentation should work
-    	Given a standard Cucumber project directory structure
-    	And a file named "features/f.feature" with:
-		"""
-		Feature: developer creates a skeleton Ruby application
-			Scenario: create a new application
-				Given a tab indented pystring:
-				\"\"\"
-				I'm tab
-				 and space indented
-				\"\"\"
-			And a file named "features/step_definitions/steps.rb" with:
-				\"\"\"
-				Given /a tab indented pystring:/ do |s| s.should == "I'm tab\n and space indented"
-				end
-				\"\"\"
-		"""
-		When I run cucumber features/f.feature
-		Then STDERR should be empty
-		And it should pass

data/features/bug_600.feature

@@ -1,67 +0,0 @@
-Feature: http://rspec.lighthouseapp.com/projects/16211/tickets/600-inconsistent-order-of-execution-background-and-before-in-070beta2
-
-  Scenario: Background executed twice when scenario follows scenario outline
-    Given a standard Cucumber project directory structure
-    And a file named "features/t.feature" with:
-      """
-      Feature: test
-        Background: 
-          Given I am in the background
-
-        Scenario Outline: test 1
-          Given I am a step
-
-          Examples:
-            | a |
-            | 1 |
-
-        Scenario: test 2
-      """
-    And a file named "features/step_definitions/t_steps.rb" with:
-      """
-      Given "I am in the background" do
-        puts "Within background"
-      end
-
-      Given "I am a step" do
-        # no-op
-      end
-      """
-    And a file named "features/support/env.rb" with:
-      """
-      module TestWorld
-        def before_scenario
-          puts "Before scenario"
-        end
-
-        def after_scenario
-          puts "After scenario"
-        end
-      end
-
-      World(TestWorld)
-
-      Before do
-        before_scenario
-      end
-
-      After do
-        after_scenario
-      end
-      """
-    When I run cucumber -f progress features/t.feature
-    Then it should pass with
-      """
-      Before scenario
-      Within background
-      .--After scenario
-      Before scenario
-      Within background
-      .After scenario
-
-
-      2 scenarios (2 passed)
-      3 steps (3 passed)
-
-      """
-      

data/features/call_steps_from_stepdefs.feature

@@ -1,154 +0,0 @@
-Feature: http://gist.github.com/221223
-  In order to make it easier to extract several steps from
-  a feature file to a step definition I want to be able to
-  copy and paste.
-
-  Background:
-    Given a standard Cucumber project directory structure
-    And a file named "features/f.feature" with:
-      """
-      Feature: Test
-
-        Scenario: Multiline string
-          Given a multiline string:
-             \"\"\"
-             hello
-             world
-             \"\"\"
-
-        Scenario: Call a multiline string
-          Given I call a multiline string with MAMA
-
-        Scenario: Call a table
-          Given I call a table with MAMA
-
-        Scenario: Call a multiline string using keyword
-          Given I use keyword to call a multiline string with BANG
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      And /^a multiline string:$/ do |s| x=1
-        raise "I got multiline:\n#{s}"
-      end
-
-      Given /^a table:$/ do |t| x=1
-        raise "I got table:\n#{t.raw.inspect}"
-      end
-
-      Given /^I call a multiline string with (.*)$/ do |s| x=1
-        steps %Q{
-          And a multiline string:
-            \"\"\"
-            hello
-            #{s}
-            \"\"\"
-        }
-      end
-
-      Given /^I use keyword to call a multiline string with (.*)$/ do |s| x=1
-        Given 'a multiline string:', "Hello\n#{s}"
-      end
-
-      Given /^I call a table with (.*)$/ do |s| x=1
-        steps %Q{
-          Given a table:
-            |a|b|
-            |c|#{s}|
-        }
-      end
-      """
-
-  Scenario: Multiline string
-    When I run cucumber features/f.feature:3
-    Then STDERR should be empty
-    And it should fail with
-      """
-      Feature: Test
-
-        Scenario: Multiline string  # features/f.feature:3
-          Given a multiline string: # features/step_definitions/steps.rb:1
-            \"\"\"
-            hello
-            world
-            \"\"\"
-            I got multiline:
-            hello
-            world (RuntimeError)
-            ./features/step_definitions/steps.rb:2:in `/^a multiline string:$/'
-            features/f.feature:4:in `Given a multiline string:'
-
-      Failing Scenarios:
-      cucumber features/f.feature:3 # Scenario: Multiline string
-      
-      1 scenario (1 failed)
-      1 step (1 failed)
-
-      """
-
-  Scenario: Call multiline string
-    When I run cucumber features/f.feature:10
-    Then STDERR should be empty
-    And it should fail with
-      """
-      Feature: Test
-
-        Scenario: Call a multiline string           # features/f.feature:10
-          Given I call a multiline string with MAMA # features/step_definitions/steps.rb:9
-            I got multiline:
-            hello
-            MAMA (RuntimeError)
-            ./features/step_definitions/steps.rb:2:in `/^a multiline string:$/'
-            features/f.feature:11:in `Given I call a multiline string with MAMA'
-
-      Failing Scenarios:
-      cucumber features/f.feature:10 # Scenario: Call a multiline string
-
-      1 scenario (1 failed)
-      1 step (1 failed)
-
-      """
-
-  Scenario: Call table
-    When I run cucumber features/f.feature:13
-    Then STDERR should be empty
-    And it should fail with
-      """
-      Feature: Test
-
-        Scenario: Call a table           # features/f.feature:13
-          Given I call a table with MAMA # features/step_definitions/steps.rb:23
-            I got table:
-            [["a", "b"], ["c", "MAMA"]] (RuntimeError)
-            ./features/step_definitions/steps.rb:6:in `/^a table:$/'
-            features/f.feature:14:in `Given I call a table with MAMA'
-
-      Failing Scenarios:
-      cucumber features/f.feature:13 # Scenario: Call a table
-
-      1 scenario (1 failed)
-      1 step (1 failed)
-
-      """
-
-  Scenario: Call multiline string with keyword
-    When I run cucumber features/f.feature:16
-    Then STDERR should be empty
-    And it should fail with
-      """
-      Feature: Test
-
-        Scenario: Call a multiline string using keyword            # features/f.feature:16
-          Given I use keyword to call a multiline string with BANG # features/step_definitions/steps.rb:19
-            I got multiline:
-            Hello
-            BANG (RuntimeError)
-            ./features/step_definitions/steps.rb:2:in `/^a multiline string:$/'
-            features/f.feature:17:in `Given I use keyword to call a multiline string with BANG'
-
-      Failing Scenarios:
-      cucumber features/f.feature:16 # Scenario: Call a multiline string using keyword
-
-      1 scenario (1 failed)
-      1 step (1 failed)
-
-      """

data/features/cucumber_cli.feature

@@ -1,591 +0,0 @@
-Feature: Cucumber command line
-  In order to write better software
-  Developers should be able to execute requirements as tests
-
-  Scenario: Run single scenario with missing step definition
-    When I run cucumber -q features/sample.feature:5
-    Then it should pass with      
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """
-
-  Scenario: Fail with --strict
-    When I run cucumber -q features/sample.feature:5 --strict
-    Then it should fail with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-            Undefined step: "missing" (Cucumber::Undefined)
-            features/sample.feature:7:in `Given missing'
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """
-
-  Scenario: Succeed with --strict
-    When I run cucumber -q features/sample.feature:10 --strict
-    Then it should pass with
-    """
-    # Feature comment
-    @one
-    Feature: Sample
-
-      # Scenario comment
-      @three
-      Scenario: Passing
-        Given passing
-          | a | b |
-          | c | d |
-
-    1 scenario (1 passed)
-    1 step (1 passed)
-
-    """
-
-  Scenario: Specify 2 line numbers where one is a tag
-    When I run cucumber -q features/sample.feature:5:16
-    Then it should fail with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        @four
-        Scenario: Failing
-          Given failing
-            \"\"\"
-            hello
-            \"\"\"
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:2:in `flunker'
-            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
-            features/sample.feature:18:in `Given failing'
-      
-      Failing Scenarios:
-      cucumber features/sample.feature:17 # Scenario: Failing
-      
-      2 scenarios (1 failed, 1 undefined)
-      2 steps (1 failed, 1 undefined)
-
-      """
-
-  Scenario: Require missing step definition from elsewhere
-    When I run cucumber -q -r ../../features/step_definitions/extra_steps.rb features/sample.feature:5
-    Then it should pass with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-
-      """
-
-  Scenario: Specify the line number of a row
-    When I run cucumber -q features/sample.feature:12
-    Then it should pass with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-
-      """
-
-  Scenario: Use @-notation to specify a file containing feature file list
-    When I run cucumber -q @list-of-features.txt
-    Then it should pass with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-
-      """
-
-  Scenario: Run all with progress formatter
-    When I run cucumber -q --format progress features/sample.feature
-    Then it should fail with
-      """
-      U.F
-
-      (::) failed steps (::)
-
-      FAIL (RuntimeError)
-      ./features/step_definitions/sample_steps.rb:2:in `flunker'
-      ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
-      features/sample.feature:18:in `Given failing'
-
-      Failing Scenarios:
-      cucumber features/sample.feature:17 # Scenario: Failing
-
-      3 scenarios (1 failed, 1 undefined, 1 passed)
-      3 steps (1 failed, 1 undefined, 1 passed)
-
-      """
-
-  Scenario: --dry-run
-    When I run cucumber --dry-run --no-source features/*.feature --tags ~@lots
-    Then it should pass 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"
-
-      Feature: Failing expectation
-
-        Scenario: Failing expectation
-          Given failing expectation
-
-      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
-
-      Feature: multiline
-
-        Background: I'm a multiline name
-          which goes on and on and on for three lines
-          yawn
-          Given passing without a table
-
-        Scenario: I'm a multiline name
-          which goes on and on and on for three lines
-          yawn
-          Given passing without a table
-
-        Scenario Outline: I'm a multiline name
-          which goes on and on and on for three lines
-          yawn
-          Given <state> without a table
-
-          Examples: 
-            | state   |
-            | passing |
-    
-        Scenario Outline: name
-          Given <state> without a table
-
-          Examples: I'm a multiline name
-            which goes on and on and on for three lines
-            yawn
-            | state   |
-            | passing |
-
-      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     |
-
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-        @four
-        Scenario: Failing
-          Given failing
-            \"\"\"
-            hello
-            \"\"\"
-
-      Feature: search examples
-
-        Background: Hantu Pisang background match
-          Given passing without a table
-
-        Scenario: should match Hantu Pisang
-          Given passing without a table
-
-        Scenario: Ignore me
-          Given failing without a table
-
-        Scenario Outline: Ignore me
-          Given <state> without a table
-
-          Examples: 
-            | state   |
-            | failing |
-
-        Scenario Outline: Hantu Pisang match
-          Given <state> without a table
-
-          Examples: 
-            | state   |
-            | passing |
-
-        Scenario Outline: no match in name but in examples
-          Given <state> without a table
-
-          Examples: Hantu Pisang
-            | state   |
-            | passing |
-
-          Examples: Ignore me
-            | state   |
-            | failing |
-
-      @sample_one
-      Feature: Tag samples
-
-        @sample_two @sample_four
-        Scenario: Passing
-          Given missing
-
-        @sample_three
-        Scenario Outline: 
-          Given <state>
-
-          Examples: 
-            | state   |
-            | missing |
-
-        @sample_three @sample_four
-        Scenario: Skipped
-          Given missing
-
-      Feature: undefined multiline args
-      
-        Scenario: pystring
-          Given a pystring
-            \"\"\"
-              example
-            \"\"\"
-      
-        Scenario: table
-          Given a table
-            | table   |
-            | example |
-
-      26 scenarios (17 skipped, 8 undefined, 1 passed)
-      42 steps (30 skipped, 12 undefined)
-
-      """
-
-  Scenario: Multiple formatters and outputs
-    When I run cucumber --format progress --out tmp/progress.txt --format pretty --out tmp/pretty.txt --no-source --dry-run features/lots_of_undefined.feature
-    Then STDERR should be empty
-    Then "fixtures/self_test/tmp/progress.txt" should contain
-      """
-      UUUUU
-
-      1 scenario (1 undefined)
-      5 steps (5 undefined)
-
-      """
-    And "fixtures/self_test/tmp/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)
-
-      """
-
-  Scenario: Run feature elements which matches a name using --name
-    When I run cucumber --name Pisang -q features/
-    Then it should pass with
-      """
-      Feature: search examples
-
-        Background: Hantu Pisang background match
-          Given passing without a table
-
-        Scenario: should match Hantu Pisang
-          Given passing without a table
-
-        Scenario Outline: Hantu Pisang match
-          Given <state> without a table
-
-          Examples: 
-            | state   |
-            | passing |
-
-        Scenario Outline: no match in name but in examples
-          Given <state> without a table
-
-          Examples: Hantu Pisang
-            | state   |
-            | passing |
-
-      3 scenarios (3 passed)
-      6 steps (6 passed)
-
-      """
-
-  Scenario: Run a single background which matches a name using --name (Useful if there is an error in it)
-    When I run cucumber --name 'Hantu Pisang background' -q features/
-    Then it should pass with
-      """
-      Feature: search examples
-
-        Background: Hantu Pisang background match
-          Given passing without a table
-
-      0 scenarios
-      1 step (1 passed)
-
-      """
-
-
-  Scenario: Run with a tag that exists on 2 scenarios
-    When I run cucumber -q features --tags @three
-    Then it should pass with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      2 scenarios (1 undefined, 1 passed)
-      2 steps (1 undefined, 1 passed)
-
-      """
-
-  Scenario: Run with a tag that exists on 1 feature
-    When I run cucumber -q features --tags @one
-    Then it should fail with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-        @four
-        Scenario: Failing
-          Given failing
-            \"\"\"
-            hello
-            \"\"\"
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:2:in `flunker'
-            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
-            features/sample.feature:18:in `Given failing'
-
-      Failing Scenarios:
-      cucumber features/sample.feature:17 # Scenario: Failing
-
-      3 scenarios (1 failed, 1 undefined, 1 passed)
-      3 steps (1 failed, 1 undefined, 1 passed)
-
-      """
-
-  Scenario: Run with a negative tag
-    When I run cucumber -q features/sample.feature --no-source --dry-run --tags ~@four
-    Then it should pass with
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      2 scenarios (1 skipped, 1 undefined)
-      2 steps (1 skipped, 1 undefined)
-
-      """
-
-  Scenario: Run with limited tag count, blowing it on scenario
-     When I run cucumber -q features/tags_sample.feature --no-source --dry-run --tags @sample_three:1
-     Then it should fail with
-       """
-       @sample_three occurred 2 times, but the limit was set to 1
-         features/tags_sample.feature:11
-         features/tags_sample.feature:16
-       """
-
-   Scenario: Run with limited tag count, blowing it via feature inheritance
-     When I run cucumber -q features/tags_sample.feature --no-source --dry-run --tags @sample_one:1
-     Then it should fail with
-       """
-       @sample_one occurred 3 times, but the limit was set to 1
-         features/tags_sample.feature:5
-         features/tags_sample.feature:11
-         features/tags_sample.feature:16
-       """
-
-   Scenario: Run with limited tag count using negative tag, blowing it via a tag that is not run
-     When I run cucumber -q features/tags_sample.feature --no-source --dry-run --tags ~@sample_one:1
-     Then it should fail with
-       """
-       @sample_one occurred 3 times, but the limit was set to 1
-       """
-
-  Scenario: Reformat files with --autoformat
-    When I run cucumber --autoformat tmp/formatted features
-    Then STDERR should be empty
-    Then "fixtures/self_test/tmp/formatted/features/sample.feature" should contain
-      """
-      # Feature comment
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        # Scenario comment
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-        @four
-        Scenario: Failing
-          Given failing
-            \"\"\"
-            hello
-            \"\"\"
-
-
-      """
-
-  # Fails on 1.9 because of encoding issues.
-  @fails_on_1_9
-  Scenario: Generate PDF with pdf formatter
-    When I run cucumber --format pdf --out tmp/sample.pdf --dry-run features/sample.feature
-    Then STDERR should be empty
-    Then "fixtures/self_test/tmp/sample.pdf" should match "Pages 2"
-
-  Scenario: Run feature elements which match a name using -n
-    When I run cucumber -n Pisang -q features/
-    Then STDERR should be empty
-    Then it should pass with
-      """
-      Feature: search examples
-
-        Background: Hantu Pisang background match
-          Given passing without a table
-
-        Scenario: should match Hantu Pisang
-          Given passing without a table
-
-        Scenario Outline: Hantu Pisang match
-          Given <state> without a table
-
-          Examples: 
-            | state   |
-            | passing |
-
-        Scenario Outline: no match in name but in examples
-          Given <state> without a table
-
-          Examples: Hantu Pisang
-            | state   |
-            | passing |
-
-      3 scenarios (3 passed)
-      6 steps (6 passed)
-
-      """