cucumber 1.3.20 → 2.0.0.beta.1

data/features/docs/gherkin/language_from_header.feature

@@ -0,0 +1,32 @@
+Feature: Choosing the language from the feature file header
+
+  In order to simplify command line and settings in IDEs, Cucumber picks
+  up the parser language from a `# language` comment at the beginning of
+  any feature file. See the examples below for the exact syntax.
+
+  Scenario: LOLCAT
+    Given a file named "features/lolcat.feature" with:
+      """
+      # language: en-lol
+      OH HAI: STUFFING
+        B4: HUNGRY
+          I CAN HAZ EMPTY BELLY
+        MISHUN: CUKES
+          DEN KTHXBAI
+      """
+    When I run `cucumber -i features/lolcat.feature -q`
+    Then it should pass with:
+      """
+      # language: en-lol
+      OH HAI: STUFFING
+
+        B4: HUNGRY
+          I CAN HAZ EMPTY BELLY
+
+        MISHUN: CUKES
+          DEN KTHXBAI
+
+      1 scenario (1 undefined)
+      2 steps (2 undefined)
+
+      """

data/features/docs/gherkin/outlines.feature

@@ -0,0 +1,154 @@
+@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 }
+      """
+
+  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: 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     |
+            RuntimeError (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^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
+
+      5 scenarios (1 failed, 1 undefined, 3 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+      """
+
+  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: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)
+
+      """
+
+  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: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)
+
+      """
+
+  Scenario: Run all with progress formatter
+    When I run `cucumber -q --format progress features/outline_sample.feature`
+    Then it should fail with exactly:
+      """
+      --UU..FF..
+
+      (::) failed steps (::)
+
+      RuntimeError (RuntimeError)
+      ./features/step_definitions/steps.rb:2:in `/^failing without a table$/'
+      features/outline_sample.feature:6:in `Given <state> without a table'
+
+      Failing Scenarios:
+      cucumber features/outline_sample.feature:12
+
+      5 scenarios (1 failed, 1 undefined, 3 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+      0m0.012s
+
+      """
+

data/features/docs/gherkin/unicode_table.feature

@@ -0,0 +1,32 @@
+@spawn
+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.
+
+  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

@@ -0,0 +1,88 @@
+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)
+    0m0.012s
+
+    """

data/features/docs/gherkin/using_star_notation.feature

@@ -0,0 +1,37 @@
+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/{legacy_features → features/docs}/post_configuration_hook.feature

@@ -4,47 +4,46 @@ Feature: Post Configuration Hook [#423]
   As a developer
   I want to manipulate the Cucumber configuration after it has been created
 
+  # Fails on Travis under JRuby
+  @spawn
+  @wip-jruby
   Scenario: Using options directly gets a deprecation warning
-
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
+    Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
         config.options[:blah]
       end
       """
-    When I run cucumber features
-    Then STDERR should match
+    When I run `cucumber features`
+    Then the stderr should contain:
       """
       Deprecated
       """
 
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
+  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 STDERR should be empty
-    And the output should contain
+    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 standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
+    Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
-        config.out_stream << "AfterConfiguration hook read feature directories: #{config.feature_dirs.join(', ')}" 
+        config.out_stream << "AfterConfiguration hook read feature directories: #{config.feature_dirs.join(', ')}"
       end
       """
-    When I run cucumber features
-    Then STDERR should be empty
-    And the output should contain
+    When I run `cucumber features`
+    Then the stderr should not contain anything
+    And the output should contain:
       """
       AfterConfiguration hook read feature directories: features
-      """
+      """

data/{legacy_features → features/docs}/profiles.feature

@@ -1,4 +1,5 @@
 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.
@@ -7,15 +8,14 @@ Feature: Profiles
   http://wiki.github.com/cucumber/cucumber/cucumber.yml
 
   Background: Basic App
-    Given a standard Cucumber project directory structure
-    And a file named "features/sample.feature" with:
+    Given a file named "features/sample.feature" with:
       """
       Feature: Sample
         Scenario: this is a test
-          Given I am just testing stuff
+          Given this step raises an error
       """
-    And a file named "features/support/env.rb"
-    And a file named "features/support/super_env.rb"
+    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
@@ -23,8 +23,8 @@ Feature: Profiles
       """
 
   Scenario: Explicitly defining a profile to run
-    When I run cucumber features/sample.feature --profile super
-    Then the output should contain
+    When I run `cucumber features/sample.feature --profile super`
+    Then the output should contain:
       """
       Using the super profile...
       """
@@ -36,29 +36,29 @@ Feature: Profiles
       <% 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
+    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
+    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
+    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 STDERR should be
+    When I run `cucumber -p foo`
+    Then the stderr should contain:
       """
       Could not find profile: 'foo'
 
@@ -69,26 +69,25 @@ Feature: Profiles
       """
 
   Scenario Outline: Disabling the default profile
-    When I run cucumber -v features/ <Flag>
-    Then the output should contain
+    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    |
-
+      | 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 ran
       """
-      When I run cucumber -p default features/another.feature
-      Then exactly these features should be ran: features/another.feature
+    When I run `cucumber -p default features/another.feature`
+    Then exactly these features should be ran: features/another.feature
 
   Scenario: Overriding the profile's formatter
     You will most likely want to define a formatter in your default formatter.
@@ -101,26 +100,21 @@ Feature: Profiles
       """
       default: features/sample.feature --require features/support/env.rb -v --format profile
       """
-    When I run cucumber features --format pretty
-    And the output should contain
+    When I run `cucumber features --format pretty`
+    Then the output should contain:
       """
       Feature: Sample
       """
 
   Scenario Outline: Showing profiles when listing failing scenarios
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^I am just testing stuff$/ do
-        raise 'BANG'
-      end
-      """
-    When I run cucumber -q -p super -p default -f <format> features/sample.feature --require features/step_definitions/steps.rb
-    Then it should fail
-    And the output should contain
+    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|
+      | format   |
+      | pretty   |
+      | progress |