cucumber 1.3.20 → 2.0.0.beta.1

data/legacy_features/README.md

@@ -1,14 +0,0 @@
-# Please do not add to the tests in this folder
-
-This folder contains the acceptance tests that were written for Cucumber
-before [Aruba](https://github.com/cucumber/aruba) existed.
-
-These tests are currently run as part of the build, but should not be added to.
-
-New acceptance tests should be added in the `features` directory. If you find a test
-in here that you want to modify, please do the work to migrate it into the `features`
-directory.
-
-There is a ticket [#408](https://github.com/cucumber/cucumber/issues/408) to track 
-the effort to migrate all these tests into the `features` directory. We aim to have this
-completed for the release of Cucumber 2.0

data/legacy_features/announce.feature

@@ -1,152 +0,0 @@
-Feature: Delayed message
-
-  Background:
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^I use puts with text "(.*)"$/ do |ann| x=1
-        puts(ann)
-      end
-
-      Given /^I use multiple putss$/ do x=1
-        puts("Multiple")
-        puts("Announce","Me")
-      end
-
-      Given /^I use message (.+) in line (.+) (?:with result (.+))$/ do |ann, line, result| x=1
-        puts("Last message") if line == "3"
-        puts("Line: #{line}: #{ann}")
-        fail if result =~ /fail/i
-      end
-
-      Given /^I use puts and step fails$/ do x=1
-        puts("Announce with fail")
-        fail
-      end
-
-      Given /^this step works$/ do x=1
-      end
-
-      Given /^I puts the world$/ do x=1
-        puts(self)
-      end
-      """
-    And a file named "features/f.feature" with:
-      """
-      Feature: F
-
-        Scenario: S
-          Given I use puts with text "Ann"
-          And this step works
-
-        Scenario: S2
-          Given I use multiple putss
-          And this step works
-
-        Scenario Outline: S3
-          Given I use message <ann> in line <line>
-
-          Examples:
-            | line | ann |
-            | 1 | anno1 |
-            | 2 | anno2 |
-            | 3 | anno3 |
-
-        Scenario: S4
-          Given I use puts and step fails
-          And this step works
-
-        Scenario Outline: s5
-          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
-      """
-
-    Scenario: Delayed messages feature
-      When I run cucumber --format pretty features/f.feature
-      Then STDERR should be empty
-      And the output should contain
-      """
-      Feature: F
-
-        Scenario: S                        # features/f.feature:3
-          Given I use puts with text "Ann" # features/step_definitions/steps.rb:1
-            Ann
-          And this step works              # features/step_definitions/steps.rb:21
-
-        Scenario: S2                 # features/f.feature:7
-          Given I use multiple putss # features/step_definitions/steps.rb:5
-            Multiple
-            Announce
-            Me
-          And this step works        # features/step_definitions/steps.rb:21
-
-        Scenario Outline: S3                       # features/f.feature:11
-          Given I use message <ann> in line <line> # features/f.feature:12
-
-          Examples: 
-            | line | ann   |
-            | 1    | anno1 |
-            | 2    | anno2 |
-            | 3    | anno3 |
-
-        Scenario: S4                      # features/f.feature:20
-          Given I use puts and step fails # features/step_definitions/steps.rb:16
-            Announce with fail
-             (RuntimeError)
-            ./features/step_definitions/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 works             # features/step_definitions/steps.rb:21
-
-        Scenario Outline: s5                                            # features/f.feature:24
-          Given I use message <ann> in line <line> with result <result> # features/step_definitions/steps.rb:10
-
-          Examples: 
-            | line | ann   | result |
-            | 1    | anno1 | fail   |  Line: 1: anno1
-             (RuntimeError)
-            ./features/step_definitions/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
-        ...
-        """
-
-    @rspec2
-    Scenario: puts world
-      When I run cucumber --format progress features/puts_world.feature
-      Then the output should contain "RSpec::Matchers"
-      And the output should contain "Cucumber::RbSupport::RbWorld"
-
-    @rspec1
-    Scenario: puts world
-      When I run cucumber --format progress features/puts_world.feature
-      Then the output should contain "Spec::Matchers"
-      And the output should contain "Cucumber::RbSupport::RbWorld"

data/legacy_features/bug_371.feature

@@ -1,32 +0,0 @@
-Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/371
-  Scenario: Before runs once
-    Given a standard Cucumber project directory structure
-    And a file named "features/f.feature" with:
-      """
-      Feature: F
-        Scenario: S
-          Given G
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Before do
-        puts "B"
-      end
-      Given /G/ do
-        puts "G"
-      end
-      """
-    When I run cucumber -q --format pretty --format progress --out progress.txt features/f.feature
-    Then it should pass with
-      """
-      Feature: F
-
-        Scenario: S
-          Given G
-            B
-            G
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-
-      """

data/legacy_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/legacy_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/legacy_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/legacy_features/bug_600.feature

@@ -1,73 +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/legacy_features/cucumber_cli.feature

@@ -1,584 +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
-      
-      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 ../../legacy_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
-
-      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 with <html> entities
-            \"\"\"
-      
-        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 --no-snippets 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
-
-      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
-            \"\"\"
-
-
-      """
-
-  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)
-
-      """