cucumber 3.0.0 → 3.1.0

data/features/docs/gherkin/outlines.feature

@@ -1,158 +0,0 @@
-@spawn
-Feature: Scenario outlines
-
-  Copying and pasting scenarios to use different values quickly
-  becomes tedious and repetitive. Scenario outlines allow us to more
-  concisely express these examples through the use of a template with
-  placeholders, using Scenario Outline, Examples with tables and < >
-  delimited parameters.
-
-  The Scenario Outline steps provide a template which is never directly
-  run. A Scenario Outline is run once for each row in the Examples section
-  beneath it (not counting the first row).
-
-  The way this works is via placeholders. Placeholders must be contained
-  within < > in the Scenario Outline's steps - see the examples below.
-
-  **IMPORTANT:** Your step definitions will never have to match a
-  placeholder. They will need to match the values that will replace the
-  placeholder.
-
-  Background:
-    Given a file named "features/outline_sample.feature" with:
-      """
-      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     |
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given(/^passing without a table$/) { }
-      Given(/^failing without a table$/) { raise RuntimeError }
-      """
-
-  @todo-windows
-  Scenario: Run scenario outline with filtering on outline name
-    When I run `cucumber -q features/outline_sample.feature`
-    Then it should fail with:
-      """
-      Feature: Outline Sample
-
-        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     |
-            RuntimeError (RuntimeError)
-            ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
-            features/outline_sample.feature:12:in `Given failing without a table'
-            features/outline_sample.feature:6:in `Given <state> without a table'
-
-          Examples: Only passing
-            | state   | other_state |
-            | passing | passing     |
-
-      Failing Scenarios:
-      cucumber features/outline_sample.feature:12
-
-      4 scenarios (1 failed, 1 undefined, 2 passed)
-      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
-      """
-
-  @todo-windows
-  Scenario: Run scenario outline steps only
-    When I run `cucumber -q features/outline_sample.feature:7`
-    Then it should fail with:
-      """
-      Feature: Outline Sample
-
-        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     |
-            RuntimeError (RuntimeError)
-            ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
-            features/outline_sample.feature:12:in `Given failing without a table'
-            features/outline_sample.feature:6:in `Given <state> without a table'
-
-          Examples: Only passing
-            | state   | other_state |
-            | passing | passing     |
-
-      Failing Scenarios:
-      cucumber features/outline_sample.feature:12
-
-      4 scenarios (1 failed, 1 undefined, 2 passed)
-      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
-
-      """
-
-  @todo-windows
-  Scenario: Run single failing scenario outline table row
-    When I run `cucumber -q features/outline_sample.feature:12`
-    Then it should fail with:
-      """
-      Feature: Outline Sample
-
-        Scenario Outline: Test state
-          Given <state> without a table
-          Given <other_state> without a table
-
-          Examples: Rainbow colours
-            | state   | other_state |
-            | failing | passing     |
-            RuntimeError (RuntimeError)
-            ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
-            features/outline_sample.feature:12:in `Given failing without a table'
-            features/outline_sample.feature:6:in `Given <state> without a table'
-
-      Failing Scenarios:
-      cucumber features/outline_sample.feature:12
-
-      1 scenario (1 failed)
-      2 steps (1 failed, 1 skipped)
-
-      """
-
-  @todo-windows
-  Scenario: Run all with progress formatter
-    When I run `cucumber -q --format progress features/outline_sample.feature`
-    Then it should fail with exactly:
-      """
-      U-..F-..
-
-      (::) failed steps (::)
-
-      RuntimeError (RuntimeError)
-      ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
-      features/outline_sample.feature:12:in `Given failing without a table'
-      features/outline_sample.feature:6:in `Given <state> without a table'
-
-      Failing Scenarios:
-      cucumber features/outline_sample.feature:12
-
-      4 scenarios (1 failed, 1 undefined, 2 passed)
-      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
-
-      """

data/features/docs/gherkin/unicode_table.feature

@@ -1,33 +0,0 @@
-@spawn @wip-jruby
-Feature: Unicode in tables
-
-  You are free to use unicode in your tables: we've taken care to
-  ensure that the tables are properly aligned so that your output is as
-  readable as possible.
-
-  @todo-windows
-  Scenario:
-    Given a file named "features/unicode.feature" with:
-      """
-      Feature: Featuring unicode
-
-        Scenario: table with unicode
-          Given passing
-            | Brüno | abc |
-            | Bruno | æøå |
-      """
-    When I run `cucumber -q --dry-run features/unicode.feature`
-    Then it should pass with:
-      """
-      Feature: Featuring unicode
-
-        Scenario: table with unicode
-          Given passing
-            | Brüno | abc |
-            | Bruno | æøå |
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """
-

data/features/docs/gherkin/using_descriptions.feature

@@ -1,83 +0,0 @@
-@todo-windows
-Feature: Using descriptions to give features context
-
-  When writing your feature files its very helpful to use description
-  text at the beginning of the feature file, to write a preamble to the
-  feature describing clearly exactly what the feature does.
-
-  You can also write descriptions attached to individual scenarios - see
-  the examples below for how this can be used.
-
-  It's possible to have your descriptions run over more than one line,
-  and you can have blank lines too. As long as you don't start a line
-  with a Given, When, Then, Background:, Scenario: or similar, you're
-  fine: otherwise Gherkin will start to pay attention.
-
-  Background:
-    Given the standard step definitions
-
-  Scenario: Everything with a description
-    Given a file named "features/test.feature" with:
-    """
-    Feature: descriptions everywhere
-
-      We can put a useful description here of the feature, which can
-      span multiple lines.
-
-      Background:
-
-        We can also put in descriptions showing what the background is
-        doing.
-
-        Given this step passes
-
-      Scenario: I'm a scenario with a description
-
-        You can also put descriptions in front of individual scenarios.
-
-        Given this step passes
-
-      Scenario Outline: I'm a scenario outline with a description
-
-        Scenario outlines can have descriptions.
-
-        Given this step <state>
-        Examples: Examples
-
-          Specific examples for an outline are allowed to have
-          descriptions, too.
-
-          |  state |
-          | passes |
-    """
-    When I run `cucumber -q`
-    Then the stderr should not contain anything
-    Then it should pass with exactly:
-    """
-    Feature: descriptions everywhere
-      We can put a useful description here of the feature, which can
-      span multiple lines.
-
-      Background: 
-        We can also put in descriptions showing what the background is
-        doing.
-        Given this step passes
-
-      Scenario: I'm a scenario with a description
-        You can also put descriptions in front of individual scenarios.
-        Given this step passes
-
-      Scenario Outline: I'm a scenario outline with a description
-        Scenario outlines can have descriptions.
-        Given this step <state>
-
-        Examples: Examples
-          Specific examples for an outline are allowed to have
-          descriptions, too.
-          | state  |
-          | passes |
-
-    2 scenarios (2 passed)
-    4 steps (4 passed)
-
-    """

data/features/docs/gherkin/using_star_notation.feature

@@ -1,37 +0,0 @@
-Feature: Using star notation instead of Given/When/Then
-
-  Cucumber supports the star notation when writing features: instead of
-  using Given/When/Then, you can simply use a star rather like you would
-  use a bullet point.
-
-  When you run the feature for the first time, you still get a nice
-  message showing you the code snippet you need to use to implement the
-  step.
-
-  Scenario: Use some *
-    Given a file named "features/f.feature" with:
-      """
-      Feature: Star-notation feature
-        Scenario: S
-          * I have some cukes
-      """
-    When I run `cucumber features/f.feature`
-    Then the stderr should not contain anything
-    And it should pass with:
-      """
-      Feature: Star-notation feature
-
-        Scenario: S           # features/f.feature:2
-          * I have some cukes # features/f.feature:3
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-      """
-    And it should pass with:
-      """
-      You can implement step definitions for undefined steps with these snippets:
-
-      Given("I have some cukes") do
-        pending # Write code here that turns the phrase above into concrete actions
-      end
-      """

data/features/docs/iso-8859-1.feature

@@ -1,6 +0,0 @@
-# language: no
-# encoding: iso-8859-1
-Egenskap: Alle bruker ikke UTF-8
-  Scenario: Dette b�r g� bra
-    N�r jeg drikker en "�l"
-    S� skal de andre si "sk�l"

data/features/docs/post_configuration_hook.feature

@@ -1,33 +0,0 @@
-Feature: Post Configuration Hook [#423]
-
-  In order to extend Cucumber
-  As a developer
-  I want to manipulate the Cucumber configuration after it has been created
-
-  Scenario: Changing the output format
-    Given a file named "features/support/env.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.formats << ['html', {}, config.out_stream]
-      end
-      """
-    When I run `cucumber features`
-    Then the stderr should not contain anything
-    And the output should contain:
-      """
-      html
-      """
-
-  Scenario: feature directories read from configuration
-    Given a file named "features/support/env.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.out_stream << "AfterConfiguration hook read feature directories: #{config.feature_dirs.join(', ')}"
-      end
-      """
-    When I run `cucumber features`
-    Then the stderr should not contain anything
-    And the output should contain:
-      """
-      AfterConfiguration hook read feature directories: features
-      """

data/features/docs/profiles.feature

@@ -1,120 +0,0 @@
-Feature: Profiles
-
-  In order to save time and prevent carpal tunnel syndrome
-  Cucumber users can save and reuse commonly used cucumber flags in a 'cucumber.yml' file.
-  These named arguments are called profiles and the yml file should be in the root of your project.
-  Any cucumber argument is valid in a profile.  To see all the available flags type 'cucumber --help'
-  For more information about profiles please see the wiki:
-  http://wiki.github.com/cucumber/cucumber/cucumber.yml
-
-  Background: Basic App
-    Given a file named "features/sample.feature" with:
-      """
-      Feature: Sample
-        Scenario: this is a test
-          Given this step raises an error
-      """
-    And an empty file named "features/support/env.rb"
-    And an empty file named "features/support/super_env.rb"
-    And the following profiles are defined:
-      """
-      default: features/sample.feature --require features/support/env.rb -v
-      super: features/sample.feature --require features/support/super_env.rb -v
-      """
-
-  Scenario: Explicitly defining a profile to run
-    When I run `cucumber features/sample.feature --profile super`
-    Then the output should contain:
-      """
-      Using the super profile...
-      """
-    And exactly these files should be loaded: features/support/super_env.rb
-
-  Scenario: Explicitly defining a profile defined in an ERB formatted file
-    Given the following profiles are defined:
-      """
-      <% requires = "--require features/support/super_env.rb" %>
-      super: <%= "features/sample.feature #{requires} -v" %>
-      """
-    When I run `cucumber features/sample.feature --profile super`
-    Then the output should contain:
-      """
-      Using the super profile...
-      """
-    And exactly these files should be loaded: features/support/super_env.rb
-
-  Scenario: Defining multiple profiles to run
-    When I run `cucumber features/sample.feature --profile default --profile super`
-    Then the output should contain:
-      """
-      Using the default and super profiles...
-      """
-    And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
-
-  Scenario: Arguments passed in but no profile specified
-    When I run `cucumber -v`
-    Then the default profile should be used
-    And exactly these files should be loaded: features/support/env.rb
-
-  Scenario: Trying to use a missing profile
-    When I run `cucumber -p foo`
-    Then the stderr should contain:
-      """
-      Could not find profile: 'foo'
-
-      Defined profiles in cucumber.yml:
-        * default
-        * super
-
-      """
-
-  Scenario Outline: Disabling the default profile
-    When I run `cucumber -v features/ <flag>`
-    Then the output should contain:
-      """
-      Disabling profiles...
-      """
-    And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
-
-    Examples:
-      | flag         |
-      | -P           |
-      | --no-profile |
-
-  Scenario: Overriding the profile's features to run
-    Given a file named "features/another.feature" with:
-      """
-      Feature: Just this one should be run
-      """
-    When I run `cucumber -p default features/another.feature`
-    Then exactly these features should be run: features/another.feature
-
-  Scenario: Overriding the profile's formatter
-    You will most likely want to define a formatter in your default formatter.
-    However, you often want to run your features with a different formatter
-    yet still use the other the other arguments in the profile. Cucumber will
-    allow you to do this by giving precedence to the formatter specified on the
-    command line and override the one in the profile.
-
-    Given the following profiles are defined:
-      """
-      default: features/sample.feature --require features/support/env.rb -v --format profile
-      """
-    When I run `cucumber features --format pretty`
-    Then the output should contain:
-      """
-      Feature: Sample
-      """
-
-  Scenario Outline: Showing profiles when listing failing scenarios
-    Given the standard step definitions
-    When I run `cucumber -q -p super -p default -f <format> features/sample.feature --require features/step_definitions/steps.rb`
-    Then it should fail with:
-       """
-       cucumber -p super features/sample.feature:2
-       """
-
-    Examples:
-      | format   |
-      | pretty   |
-      | progress |

data/features/docs/rake_task.feature

@@ -1,146 +0,0 @@
-@spawn
-Feature: Rake task
-  In order to ease the development process
-  As a developer and CI server administrator
-  Cucumber features should be executable via Rake
-
-  Background:
-    And a file named "features/missing_step_definitions.feature" with:
-      """
-      Feature: Sample
-
-        Scenario: Wanted
-          Given I want to run this
-
-        Scenario: Unwanted
-          Given I don't want this ran
-      """
-
-  @todo-windows
-  Scenario: rake task with a defined profile
-    Given the following profile is defined:
-      """
-      foo: --quiet --no-color features/missing_step_definitions.feature:3
-      """
-    And a file named "Rakefile" with:
-      """
-      require 'cucumber/rake/task'
-
-      Cucumber::Rake::Task.new do |t|
-        t.profile = "foo"
-      end
-      """
-    When I run `rake cucumber`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        Scenario: Wanted
-          Given I want to run this
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-      """
-
-  @todo-windows
-  Scenario: rake task without a profile
-    Given a file named "Rakefile" with:
-      """
-      require 'cucumber/rake/task'
-
-      Cucumber::Rake::Task.new do |t|
-        t.cucumber_opts = %w{--quiet --no-color}
-      end
-      """
-    When I run `rake cucumber`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        Scenario: Wanted
-          Given I want to run this
-
-        Scenario: Unwanted
-          Given I don't want this ran
-
-      2 scenarios (2 undefined)
-      2 steps (2 undefined)
-      """
-
-  @todo-windows
-  Scenario: rake task with a defined profile and cucumber_opts
-    Given the following profile is defined:
-      """
-      bar: ['features/missing_step_definitions.feature:3']
-      """
-    And a file named "Rakefile" with:
-      """
-      require 'cucumber/rake/task'
-
-      Cucumber::Rake::Task.new do |t|
-        t.profile = "bar"
-        t.cucumber_opts = %w{--quiet --no-color}
-      end
-      """
-    When I run `rake cucumber`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        Scenario: Wanted
-          Given I want to run this
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-      """
-
-  @todo-windows
-  Scenario: respect requires
-    Given an empty file named "features/support/env.rb"
-    And an empty file named "features/support/dont_require_me.rb"
-    And the following profile is defined:
-      """
-      no_bomb: features/missing_step_definitions.feature:3 --require features/support/env.rb --verbose
-      """
-    And a file named "Rakefile" with:
-      """
-      require 'cucumber/rake/task'
-
-      Cucumber::Rake::Task.new do |t|
-        t.profile = "no_bomb"
-        t.cucumber_opts = %w{--quiet --no-color}
-      end
-      """
-    When I run `rake cucumber`
-    Then it should pass
-    And the output should not contain:
-      """
-        * features/support/dont_require_me.rb
-      """
-
-  @todo-windows
-  Scenario: feature files with spaces
-    Given a file named "features/spaces are nasty.feature" with:
-       """
-       Feature: The futures green
-
-         Scenario: Orange
-           Given this is missing
-       """
-    And a file named "Rakefile" with:
-       """
-       require 'cucumber/rake/task'
-
-       Cucumber::Rake::Task.new do |t|
-         t.cucumber_opts = %w{--quiet --no-color}
-       end
-       """
-    When I run `rake cucumber`
-    Then it should pass with:
-       """
-       Feature: The futures green
-
-         Scenario: Orange
-           Given this is missing
-
-       """

data/features/docs/raketask.feature

@@ -1,46 +0,0 @@
-@spawn @wip-jruby
-Feature: Raketask
-
-  In order to use cucumber's rake task
-  As a Cuker
-  I do not want to see rake's backtraces when it fails
-  Also I want to get zero exit status code on failures
-  And non-zero exit status code when it pases
-
-  Background:
-    Given the standard step definitions
-    Given a file named "features/passing_and_failing.feature" with:
-      """
-      Feature: Sample
-
-        Scenario: Passing
-          Given this step passes
-
-        Scenario: Failing
-          Given this step raises an error
-      """
-    Given a file named "Rakefile" with:
-      """
-        require 'cucumber/rake/task'
-
-        SAMPLE_FEATURE_FILE = 'features/passing_and_failing.feature'
-
-        Cucumber::Rake::Task.new(:pass) do |t|
-          t.cucumber_opts = "#{SAMPLE_FEATURE_FILE}:3"
-        end
-
-        Cucumber::Rake::Task.new(:fail) do |t|
-          t.cucumber_opts = "#{SAMPLE_FEATURE_FILE}:6"
-        end
-      """
-
-  @todo-windows
-  Scenario: Passing feature
-    When I run `bundle exec rake pass`
-    Then the exit status should be 0
-
-  @todo-windows
-  Scenario: Failing feature
-    When I run `bundle exec rake fail`
-    Then the exit status should be 1
-    But the output should not contain "rake aborted!"