cucumber 1.3.10 → 2.0.0

data/legacy_features/default_snippets.feature

@@ -1,43 +0,0 @@
-Feature: Print snippets
-  In order to make it easier to implement step definitions
-  Developers should get a scaffolding for undefined step definitions
-  
-  Scenario: Cucumber doesn't know what language, and defaults to Ruby
-    Given a standard Cucumber project directory structure
-    And a file named "features/x.feature" with:
-      """
-      Feature: X
-        Scenario: Y
-          Given Z
-          Given Q
-      """
-    When I run cucumber features
-    Then STDERR should be empty
-    And it should pass with
-      """
-      Feature: X
-
-        Scenario: Y # features/x.feature:2
-          Given Z   # features/x.feature:3
-          Given Q   # features/x.feature:4
-
-      1 scenario (1 undefined)
-      2 steps (2 undefined)
-
-      You can implement step definitions for undefined steps with these snippets:
-      
-      Given(/^Z$/) do
-        pending # express the regexp above with the code you wish you had
-      end
-
-      Given(/^Q$/) do
-        pending # express the regexp above with the code you wish you had
-      end
-
-      If you want snippets in a different programming language,
-      just make sure a file with the appropriate file extension
-      exists where cucumber looks for step definitions.
-
-
-      """
-  

data/legacy_features/diffing.feature

@@ -1,25 +0,0 @@
-Feature: Cucumber command line
-  In order to write better software
-  Developers should be able to execute requirements as tests
-
-  @rspec2
-  Scenario: Run single failing scenario with default diff enabled
-    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" (using ==) (RSpec::Expectations::ExpectationNotMetError)
-            ./features/step_definitions/sample_steps.rb:63: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/legacy_features/drb_server_integration.feature

@@ -1,174 +0,0 @@
-@spork
-Feature: DRb Server Integration
-  To prevent waiting for Rails and other large Ruby applications to load their environments
-  for each feature run Cucumber ships with a DRb client that can speak to a server which
-  loads up the environment only once.
-
-  Background: App with Spork support
-    Spork is a gem that has a DRb server and the scenarios below illustrate how to use it.
-    However, any DRb server that adheres to the protocol that the client expects would work.
-
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
-      """
-      require 'rubygems'
-      require 'spork'
-
-      Spork.prefork do
-        puts "I'm loading all the heavy stuff..."
-      end
-
-      Spork.each_run do
-        puts "I'm loading the stuff just for this run..."
-      end
-      """
-    And a file named "features/sample.feature" with:
-      """
-      # language: en
-      Feature: Sample
-        Scenario: this is a test
-          Given I am just testing stuff
-      """
-    And a file named "features/essai.feature" with:
-      """
-      # language: fr
-      Fonctionnalité: Essai
-        Scenario: ceci est un test
-          Soit je teste
-      """
-    And a file named "features/step_definitions/all_your_steps_are_belong_to_us.rb" with:
-    """
-    Given /^I am just testing stuff$/ do
-      # no-op
-    end
-
-    Soit /^je teste$/ do
-      # no-op
-    end
-    """
-
-  Scenario: Feature Passing with --drb flag
-    Given I am running spork in the background
-
-    When I run cucumber features --drb
-    Then it should pass
-    And STDERR should be empty
-    And the output should contain
-      """
-      1 step (1 passed)
-      """
-    And the output should contain
-      """
-      I'm loading the stuff just for this run...
-      """
-    And the output should not contain
-      """
-      I'm loading all the heavy stuff...
-      """
-
-  Scenario: Feature Failing with --drb flag
-    Given a file named "features/step_definitions/all_your_steps_are_belong_to_us.rb" with:
-    """
-    Given /^I am just testing stuff$/ do
-      raise "Oh noes!"
-    end
-    """
-    And I am running spork in the background
-
-    When I run cucumber features --drb
-    Then it should fail
-    And the output should contain
-      """
-      1 step (1 failed)
-      """
-    And the output should contain
-      """
-      I'm loading the stuff just for this run...
-      """
-    And the output should not contain
-      """
-      I'm loading all the heavy stuff...
-      """
-
-  Scenario: Feature Run with --drb flag with no DRb server running
-            Cucumber will fall back on running the features locally in this case.
-
-    Given I am not running a DRb server in the background
-
-    When I run cucumber features --drb
-    Then it should pass
-    And STDERR should match
-      """
-      No DRb server is running. Running features locally:
-      """
-    And the output should contain
-      """
-      I'm loading all the heavy stuff...
-      I'm loading the stuff just for this run...
-      """
-    And the output should contain
-      """
-      1 step (1 passed)
-      """
-
-
-  Scenario: Feature Run with --drb flag *defined in a profile* with no DRb server running
-
-    Given I am not running a DRb server in the background
-    And the following profile is defined:
-      """
-      server: --drb features
-      """
-
-    When I run cucumber --profile server
-    Then it should pass
-    And STDERR should match
-      """
-      No DRb server is running. Running features locally:
-      """
-    And the output should contain
-      """
-      I'm loading all the heavy stuff...
-      I'm loading the stuff just for this run...
-      """
-
-  Scenario: Feature Run with --drb specifying a non-standard port
-
-    Given I am running spork in the background on port 9000
-
-    When I run cucumber features --drb --port 9000
-    Then it should pass
-    And STDERR should be empty
-    And the output should contain
-      """
-      1 step (1 passed)
-      """
-    And the output should contain
-      """
-      I'm loading the stuff just for this run...
-      """
-    And the output should not contain
-      """
-      I'm loading all the heavy stuff...
-      """
-
-  Scenario: Feature Run with $CUCUMBER_DRB environment variable
-
-    Given I have environment variable CUCUMBER_DRB set to "9000"
-    And I am running spork in the background on port 9000
-
-    When I run cucumber features/ --drb
-    Then it should pass
-    And STDERR should be empty
-    And the output should contain
-      """
-      1 step (1 passed)
-      """
-    And the output should contain
-      """
-      I'm loading the stuff just for this run...
-      """
-    And the output should not contain
-      """
-      I'm loading all the heavy stuff...
-      """

data/legacy_features/exclude_files.feature

@@ -1,20 +0,0 @@
-Feature: Exclude ruby and feature files from runs
-  Developers should be able to easily exclude files from cucumber runs
-  This is a nice feature to have in conjunction with profiles, so you can exclude
-  certain environment files from certain runs.
-
-  Scenario: exclude ruby files
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/dont_require_me.rb"
-    And a file named "features/step_definitions/fooz.rb"
-    And a file named "features/step_definitions/foof.rb"
-    And a file named "features/step_definitions/foot.rb"
-    And a file named "features/support/require_me.rb"
-
-    When I run cucumber features -q --verbose --exclude features/support/dont --exclude foo[zf]
-
-    Then "features/support/require_me.rb" should be required
-    And "features/step_definitions/foot.rb" should be required
-    And "features/support/dont_require_me.rb" should not be required
-    And "features/step_definitions/foof.rb" should not be required
-    And "features/step_definitions/fooz.rb" should not be required

data/legacy_features/expand.feature

@@ -1,60 +0,0 @@
-Feature: --expand option
-  In order to make it easier to writhe certain editor plugins
-  and also for some people to understand scenarios, Cucumber
-  should expand examples in outlines.
-
-  Background:
-    Given a standard Cucumber project directory structure
-    And a file named "features/expand_me.feature" with:
-      """
-      Feature: submit guess
-
-        Background: 
-          Given the players' names:
-            | maker    | breaker   |
-            | Moriarty | Holmes    |
- 
-        Scenario Outline: submit guess
-          Given the secret code is <code>
-          When I guess <guess>
-          Then the mark should be <mark>
-
-        Examples: all colors correct
-          | code    | guess   | mark |
-          | r g y c | r g y c | bbbb |
-          | r g y c | r g c y | bbww |
-      """
-
-  Scenario: Expand the outline
-    When I run cucumber -i -q --expand features/expand_me.feature
-    Then STDERR should be empty
-    And it should pass with
-      """
-      Feature: submit guess
-
-        Background: 
-          Given the players' names:
-            | maker    | breaker |
-            | Moriarty | Holmes  |
-
-        Scenario Outline: submit guess
-          Given the secret code is <code>
-          When I guess <guess>
-          Then the mark should be <mark>
-
-          Examples: all colors correct
-
-            Scenario: | r g y c | r g y c | bbbb |
-              Given the secret code is r g y c
-              When I guess r g y c
-              Then the mark should be bbbb
-
-            Scenario: | r g y c | r g c y | bbww |
-              Given the secret code is r g y c
-              When I guess r g c y
-              Then the mark should be bbww
-
-      2 scenarios (2 undefined)
-      8 steps (8 undefined)
-      
-      """

data/legacy_features/junit_formatter.feature

@@ -1,214 +0,0 @@
-Feature: JUnit output formatter
-  In order for developers to create test reports with ant
-  Cucumber should be able to output JUnit xml files
-  
-  Background:
-    Given I am in junit
-    And the tmp directory is empty
-  
-  Scenario: one feature, one passing scenario, one failing scenario
-    When I run cucumber --format junit --out tmp/ features/one_passing_one_failing.feature
-    Then it should fail with
-      """
-
-      """
-    And "fixtures/junit/tmp/TEST-features-one_passing_one_failing.xml" with junit duration "0.005" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="1" name="One passing scenario, one failing scenario" skipped="0" tests="2" time="0.005">
-      <testcase classname="One passing scenario, one failing scenario" name="Passing" time="0.005">
-        <system-out/>
-        <system-err/>
-      </testcase>
-      <testcase classname="One passing scenario, one failing scenario" name="Failing" time="0.005">
-        <failure message="failed Failing" type="failed">
-          <![CDATA[Scenario: Failing
-
-      Given a failing scenario
-
-      Message:
-	]]>
-          <![CDATA[ (RuntimeError)
-	features/one_passing_one_failing.feature:7:in `Given a failing scenario']]>
-        </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
-        <system-out>
-          <![CDATA[]]>
-        </system-out>
-        <system-err>
-          <![CDATA[]]>
-        </system-err>
-      </testsuite>
-
-      """
-  
-  Scenario: one feature in a subdirectory, one passing scenario, one failing scenario
-    When I run cucumber --format junit --out tmp/ features/some_subdirectory/one_passing_one_failing.feature --require features
-    Then it should fail with
-      """
-
-      """
-    And "fixtures/junit/tmp/TEST-features-some_subdirectory-one_passing_one_failing.xml" with junit duration "0.005" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="1" name="Subdirectory - One passing scenario, one failing scenario" skipped="0" tests="2" time="0.005">
-      <testcase classname="Subdirectory - One passing scenario, one failing scenario" name="Passing" time="0.005">
-        <system-out/>
-        <system-err/>
-      </testcase>
-      <testcase classname="Subdirectory - One passing scenario, one failing scenario" name="Failing" time="0.005">
-        <failure message="failed Failing" type="failed">
-          <![CDATA[Scenario: Failing
-
-      Given a failing scenario
-
-      Message:
-	]]>
-          <![CDATA[ (RuntimeError)
-	features/some_subdirectory/one_passing_one_failing.feature:7:in `Given a failing scenario']]>
-        </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
-        <system-out>
-          <![CDATA[]]>
-        </system-out>
-        <system-err>
-          <![CDATA[]]>
-        </system-err>
-      </testsuite>
-
-      """
-  
-  Scenario: pending and undefined steps are reported as skipped
-    When I run cucumber --format junit --out tmp/ features/pending.feature
-    Then it should pass with
-      """
-      
-      """
-    And "fixtures/junit/tmp/TEST-features-pending.xml" with junit duration "0.009" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="0" name="Pending step" skipped="2" tests="2" time="0.009">
-      <testcase classname="Pending step" name="Pending" time="0.009">
-        <skipped/>
-        <system-out/>
-        <system-err/>
-      </testcase>
-      <testcase classname="Pending step" name="Undefined" time="0.009">
-        <skipped/>
-        <system-out/>
-        <system-err/>
-      </testcase>
-        <system-out>
-          <![CDATA[]]>
-        </system-out>
-        <system-err>
-          <![CDATA[]]>
-        </system-err>
-      </testsuite>
-      
-      """
-
-  Scenario: pending and undefined steps with strict option should fail
-    When I run cucumber --format junit --out tmp/ features/pending.feature --strict
-    Then it should fail with
-      """
-
-      """
-    And "fixtures/junit/tmp/TEST-features-pending.xml" with junit duration "0.000160" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="2" name="Pending step" skipped="0" tests="2" time="0.000160">
-      <testcase classname="Pending step" name="Pending" time="0.000160">
-        <failure message="pending Pending" type="pending">
-          <![CDATA[Scenario: Pending
-
-      ]]>
-          <![CDATA[TODO (Cucumber::Pending)
-      features/pending.feature:4:in `Given a pending step']]>
-        </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
-      <testcase classname="Pending step" name="Undefined" time="0.000160">
-        <failure message="undefined Undefined" type="undefined">
-          <![CDATA[Scenario: Undefined
-      
-      ]]>
-          <![CDATA[Undefined step: "an undefined step" (Cucumber::Undefined)
-      features/pending.feature:7:in `Given an undefined step']]>
-        </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
-        <system-out>
-          <![CDATA[]]>
-        </system-out>
-        <system-err>
-          <![CDATA[]]>
-        </system-err>
-      </testsuite>
-
-      """
-    
-  Scenario: run all features
-    When I run cucumber --format junit --out tmp/ features
-    Then it should fail with
-      """
-      
-      """
-    And "fixtures/junit/tmp/TEST-features-one_passing_one_failing.xml" should exist
-    And "fixtures/junit/tmp/TEST-features-pending.xml" should exist
-  
-  Scenario: show correct error message if no --out is passed
-    When I run cucumber --format junit features
-    Then STDERR should not match 
-      """
-can't convert .* into String \(TypeError\)
-      """
-    And STDERR should match
-      """
-You \*must\* specify \-\-out DIR for the junit formatter
-      """
-
-  Scenario: one feature, one scenario outline, two examples: one passing, one failing
-    When I run cucumber --format junit --out tmp/ features/scenario_outline.feature
-    Then it should fail with
-      """
-
-      """
-    And "fixtures/junit/tmp/TEST-features-scenario_outline.xml" with junit duration "0.005" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="1" name="Scenario outlines" skipped="0" tests="2" time="0.005">
-      <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | passing |)" time="0.005">
-        <system-out/>
-        <system-err/>
-      </testcase>
-      <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | failing |)" time="0.005">
-        <failure message="failed Using scenario outlines (outline example : | failing |)" type="failed">
-          <![CDATA[Scenario Outline: Using scenario outlines
-      
-      Example row: | failing |
-      
-      Message:
-      ]]>
-          <![CDATA[ (RuntimeError)
-      features/scenario_outline.feature:4:in `Given a <type> scenario']]>
-        </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
-        <system-out>
-          <![CDATA[]]>
-        </system-out>
-        <system-err>
-          <![CDATA[]]>
-        </system-err>
-      </testsuite>
-
-      """
-  

data/legacy_features/language_from_header.feature

@@ -1,30 +0,0 @@
-Feature: Language from header
-  In order to simplify command line and
-  settings in IDEs, Cucumber should pick
-  up parser language from a header.
-  
-  Scenario: LOLCAT
-    Given a standard Cucumber project directory structure
-    And a file named "features/lolcat.feature" with:
-      """
-      # language: en-lol
-      OH HAI: STUFFING
-        B4: HUNGRY
-        MISHUN: CUKES
-          DEN KTHXBAI
-      """
-    When I run cucumber -i features/lolcat.feature
-    Then it should pass with
-      """
-      # language: en-lol
-      OH HAI: STUFFING
-
-        B4: HUNGRY # features/lolcat.feature:3
-
-        MISHUN: CUKES # features/lolcat.feature:4
-          DEN KTHXBAI # features/lolcat.feature:5
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """

data/legacy_features/listener_debugger_formatter.feature

@@ -1,42 +0,0 @@
-Feature: Listener Debugger
-  In order to easily visualise the listener API
-  As a developer
-  I want a formatter that prints the calls to the listener as a feature is run
-
-  Background:
-    Given a standard Cucumber project directory structure
-
-  Scenario: title
-    Given a file named "features/sample.feature" with:
-      """
-      Feature: Sample
-
-        Scenario: Sample
-          Given Sample
-
-      """
-    When I run cucumber -f debug features/sample.feature
-    Then STDERR should be empty
-    Then it should pass with
-      """
-      before_features
-        before_feature
-          before_tags
-          after_tags
-          feature_name
-          before_feature_element
-            before_tags
-            after_tags
-            scenario_name
-            before_steps
-              before_step
-                before_step_result
-                  step_name
-                after_step_result
-              after_step
-            after_steps
-          after_feature_element
-        after_feature
-      after_features
-
-      """

data/legacy_features/multiline_names.feature

@@ -1,44 +0,0 @@
-Feature: Multiline description names
-  In order to accurately document feature elements
-  As a cucumberist
-  I want to have multiline names
-
-  Scenario: multiline scenario
-    When I run cucumber features/multiline_name.feature --no-snippets
-    Then STDERR should be empty
-    Then it should pass with
-    """
-    Feature: multiline
-
-      Background: I'm a multiline name                        # features/multiline_name.feature:3
-                  which goes on and on and on for three lines
-                  yawn
-        Given passing without a table                         # features/step_definitions/sample_steps.rb:12
-
-      Scenario: I'm a multiline name                        # features/multiline_name.feature:8
-                which goes on and on and on for three lines
-                yawn
-        Given passing without a table                       # features/step_definitions/sample_steps.rb:12
-
-      Scenario Outline: I'm a multiline name                        # features/multiline_name.feature:13
-                        which goes on and on and on for three lines
-                        yawn
-        Given <state> without a table                               # features/step_definitions/sample_steps.rb:12
-
-        Examples: 
-          | state   |
-          | passing |
-
-      Scenario Outline: name          # features/multiline_name.feature:21
-        Given <state> without a table # features/step_definitions/sample_steps.rb:12
-
-        Examples: I'm a multiline name
-                  which goes on and on and on for three lines
-                  yawn
-          | state   |
-          | passing |
-
-    3 scenarios (3 passed)
-    6 steps (6 passed)
-
-    """