cucumber 2.0.0.rc.4 → 4.0.0.rc.2

data/features/docs/gherkin/doc_strings.feature

@@ -1,74 +0,0 @@
-Feature: Doc strings
-
-  If you need to specify information in a scenario that won't fit on a single line, 
-  you can use a DocString.
-  
-  A DocString follows a step, and starts and ends with three double quotes, like this:
-  
-  ```gherkin
-  When I ask to reset my password
-  Then I should receive an email with:
-    """
-    Dear bozo,
-    
-    Please click this link to reset your password
-    """
-  ```
-  
-  It's possible to annotate the DocString with the type of content it contains. This is used by
-  formatting tools like http://relishapp.com which will render the contents of the DocString
-  appropriately. You specify the content type after the triple quote, like this:
-  
-  ```gherkin
-  Given there is some Ruby code:
-    """ruby
-    puts "hello world"
-    """
-  ```
-  
-  You can read the content type from the argument passed into your step definition, as shown
-  in the example below.
-
-  Scenario: Plain text Docstring
-    Given a scenario with a step that looks like this:
-      """gherkin
-      Given I have a lot to say:
-       \"\"\"
-       One
-       Two
-       Three
-       \"\"\"
-      """
-    And a step definition that looks like this:
-      """ruby
-      Given /say/ do |text|
-        puts text
-      end
-      """
-    When I run the feature with the progress formatter
-    Then the output should contain:
-      """
-      One
-      Two
-      Three
-      """
-
-  Scenario: DocString with interesting content type
-    Given a scenario with a step that looks like this:
-      """gherkin
-      Given I have some code for you:
-       \"\"\"ruby
-       # hello
-       \"\"\"
-      """
-    And a step definition that looks like this:
-      """ruby
-      Given /code/ do |text|
-        puts text.content_type
-      end
-      """
-    When I run the feature with the progress formatter
-    Then the output should contain:
-      """
-      ruby
-      """

data/features/docs/gherkin/expand_option_for_outlines.feature

@@ -1,46 +0,0 @@
-Feature: Scenario outlines --expand option
-
-  In order to make it easier to write certain editor plugins and also
-  for some people to understand scenarios, Cucumber will expand examples
-  in outlines if you add the `--expand` option when running them.
-
-  Scenario:
-    Given a file named "features/test.feature" with:
-      """
-      Feature:
-        Scenario Outline:
-          Given the secret code is <code>
-          When I guess <guess>
-          Then I am <verdict>
-
-        Examples:
-          | code | guess | verdict |
-          | blue | blue  | right   |
-          | red  | blue  | wrong   |
-      """
-    When I run `cucumber -i -q --expand`
-    Then the stderr should not contain anything
-    And it should pass with:
-      """
-      Feature: 
-
-        Scenario Outline: 
-          Given the secret code is <code>
-          When I guess <guess>
-          Then I am <verdict>
-
-          Examples: 
-
-            Scenario: | blue | blue | right |
-              Given the secret code is blue
-              When I guess blue
-              Then I am right
-
-            Scenario: | red | blue | wrong |
-              Given the secret code is red
-              When I guess blue
-              Then I am wrong
-
-      2 scenarios (2 undefined)
-      6 steps (6 undefined)
-      """

data/features/docs/gherkin/language_from_header.feature

@@ -1,32 +0,0 @@
-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/language_help.feature

@@ -1,37 +0,0 @@
-@needs-many-fonts
-Feature: Language help
-
-  It's possible to ask cucumber which keywords are used for any
-  particular language by running:
-
-  `cucumber --i18n <language code> help`
-
-  This will print a table showing all the different words we use for
-  that language, to allow you to easily write features in any language
-  you choose.
-
-  Scenario: Get help for Portuguese language
-    When I run `cucumber --i18n pt help`
-    Then it should pass with:
-      """
-            | feature          | "Funcionalidade", "Característica", "Caracteristica"                                         |
-            | background       | "Contexto", "Cenário de Fundo", "Cenario de Fundo", "Fundo"                                  |
-            | scenario         | "Cenário", "Cenario"                                                                         |
-            | scenario_outline | "Esquema do Cenário", "Esquema do Cenario", "Delineação do Cenário", "Delineacao do Cenario" |
-            | examples         | "Exemplos", "Cenários", "Cenarios"                                                           |
-            | given            | "* ", "Dado ", "Dada ", "Dados ", "Dadas "                                                   |
-            | when             | "* ", "Quando "                                                                              |
-            | then             | "* ", "Então ", "Entao "                                                                     |
-            | and              | "* ", "E "                                                                                   |
-            | but              | "* ", "Mas "                                                                                 |
-            | given (code)     | "Dado", "Dada", "Dados", "Dadas"                                                             |
-            | when (code)      | "Quando"                                                                                     |
-            | then (code)      | "Então", "Entao"                                                                             |
-            | and (code)       | "E"                                                                                          |
-            | but (code)       | "Mas"                                                                                        |
-
-      """
-
-  Scenario: List languages
-    When I run `cucumber --i18n help`
-    Then cucumber lists all the supported languages

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 }
-      """
-
-  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: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
-
-      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: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)
-
-      """
-
-  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)
-
-      """
-
-  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: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
-
-      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

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

@@ -1,88 +0,0 @@
-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
-
-    """