cucumber 0.8.5 → 0.8.6

data/features/junit_formatter.feature

@@ -1,88 +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-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" tests="2" time="0.005">
-      <testcase classname="One passing scenario, one failing scenario.Passing" name="Passing" time="0.005">
-      </testcase>
-      <testcase classname="One passing scenario, one failing scenario.Failing" name="Failing" time="0.005">
-        <failure message="failed Failing" type="failed">
-      Scenario: Failing
-
-      Given a failing scenario
-
-      Message:
-       (RuntimeError)
-      features/one_passing_one_failing.feature:7:in `Given a failing scenario'  </failure>
-      </testcase>
-      </testsuite>
-
-      """
-  
-  Scenario: pending steps are simply skipped
-    When I run cucumber --format junit --out tmp/ features/pending.feature
-    Then it should pass with
-      """
-      
-      """
-    And "fixtures/junit/tmp/TEST-pending.xml" with junit duration "0.009" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="0" name="Pending step" tests="0" time="0.009">
-      </testsuite>
-      
-      """
-
-  Scenario: pending step 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-pending.xml" with junit duration "0.000160" should contain
-      """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" failures="1" name="Pending step" tests="1" time="0.000160">
-      <testcase classname="Pending step.Pending" name="Pending" time="0.000160">
-        <failure message="pending Pending" type="pending">
-      Scenario: Pending
-
-      TODO (Cucumber::Pending)
-      features/pending.feature:4:in `Given a pending step'  </failure>
-      </testcase>
-      </testsuite>
-
-      """
-    
-  Scenario: run all features
-    When I run cucumber --format junit --out tmp/ features
-    Then it should fail with
-      """
-      
-      """
-    And "fixtures/junit/tmp/TEST-one_passing_one_failing.xml" should exist
-    And "fixtures/junit/tmp/TEST-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
-      """

data/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/features/language_help.feature

@@ -1,78 +0,0 @@
-@needs-many-fonts
-Feature: Language help
-  In order to figure out the keywords to use for a language
-  I want to be able to get help on the language from the CLI
-
-  Scenario: Get help for Portuguese language
-    When I run cucumber --i18n pt help
-    Then it should pass with
-      """
-            | feature          | "Funcionalidade"                           |
-            | background       | "Contexto"                                 |
-            | scenario         | "Cenário", "Cenario"                       |
-            | scenario_outline | "Esquema do Cenário", "Esquema do Cenario" |
-            | examples         | "Exemplos"                                 |
-            | given            | "* ", "Dado "                              |
-            | when             | "* ", "Quando "                            |
-            | then             | "* ", "Então ", "Entao "                   |
-            | and              | "* ", "E "                                 |
-            | but              | "* ", "Mas "                               |
-            | given (code)     | "Dado"                                     |
-            | when (code)      | "Quando"                                   |
-            | then (code)      | "Então", "Entao"                           |
-            | and (code)       | "E"                                        |
-            | but (code)       | "Mas"                                      |
-
-      """
-  Scenario: List languages
-    When I run cucumber --i18n help
-    Then STDERR should be empty
-    Then it should pass with
-      """
-            | ar        | Arabic                 | العربية              |
-            | bg        | Bulgarian              | български            |
-            | ca        | Catalan                | català               |
-            | cs        | Czech                  | Česky                |
-            | cy-GB     | Welsh                  | Cymraeg              |
-            | da        | Danish                 | dansk                |
-            | de        | German                 | Deutsch              |
-            | en        | English                | English              |
-            | en-Scouse | Scouse                 | Scouse               |
-            | en-au     | Australian             | Australian           |
-            | en-lol    | LOLCAT                 | LOLCAT               |
-            | en-pirate | Pirate                 | Pirate               |
-            | en-tx     | Texan                  | Texan                |
-            | eo        | Esperanto              | Esperanto            |
-            | es        | Spanish                | español              |
-            | et        | Estonian               | eesti keel           |
-            | fi        | Finnish                | suomi                |
-            | fr        | French                 | français             |
-            | he        | Hebrew                 | עברית                |
-            | hr        | Croatian               | hrvatski             |
-            | hu        | Hungarian              | magyar               |
-            | id        | Indonesian             | Bahasa Indonesia     |
-            | it        | Italian                | italiano             |
-            | ja        | Japanese               | 日本語                  |
-            | ko        | Korean                 | 한국어                  |
-            | lt        | Lithuanian             | lietuvių kalba       |
-            | lu        | Luxemburgish           | Lëtzebuergesch       |
-            | lv        | Latvian                | latviešu             |
-            | nl        | Dutch                  | Nederlands           |
-            | no        | Norwegian              | norsk                |
-            | pl        | Polish                 | polski               |
-            | pt        | Portuguese             | português            |
-            | ro        | Romanian               | română               |
-            | ro-RO     | Romanian (diacritical) | română (diacritical) |
-            | ru        | Russian                | русский              |
-            | sk        | Slovak                 | Slovensky            |
-            | sr-Cyrl   | Serbian                | Српски               |
-            | sr-Latn   | Serbian (Latin)        | Srpski (Latinica)    |
-            | sv        | Swedish                | Svenska              |
-            | tr        | Turkish                | Türkçe               |
-            | uk        | Ukrainian              | Українська           |
-            | uz        | Uzbek                  | Узбекча              |
-            | vi        | Vietnamese             | Tiếng Việt           |
-            | zh-CN     | Chinese simplified     | 简体中文                 |
-            | zh-TW     | Chinese traditional    | 繁體中文                 |
-
-      """

data/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/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)
-
-    """

data/features/negative_tagged_hooks.feature

@@ -1,60 +0,0 @@
-Feature: Tagged hooks
-
-  Background:
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^this step works$/ do; end
-      """
-    And a file named "features/support/hooks.rb" with:
-      """
-      Before('~@no-boom') do 
-        raise 'boom'
-      end
-      """
-    And a file named "features/f.feature" with:
-      """
-      Feature: With and without hooks
-        Scenario: using hook
-          Given this step works
-
-        @no-boom
-        Scenario: omitting hook
-          Given this step works
-      """
-
-  Scenario: omit tagged hook
-    When I run cucumber features/f.feature:2
-    Then it should fail with
-      """
-      Feature: With and without hooks
-      
-        Scenario: using hook    # features/f.feature:2
-        boom (RuntimeError)
-        ./features/support/hooks.rb:2:in `Before'
-          Given this step works # features/step_definitions/steps.rb:1
-      
-      Failing Scenarios:
-      cucumber features/f.feature:2 # Scenario: using hook
-      
-      1 scenario (1 failed)
-      1 step (1 skipped)
-
-      """
-
-    Scenario: omit tagged hook
-      When I run cucumber features/f.feature:6
-      Then it should pass with
-        """
-        Feature: With and without hooks
-
-          @no-boom
-          Scenario: omitting hook # features/f.feature:6
-            Given this step works # features/step_definitions/steps.rb:1
-
-        1 scenario (1 passed)
-        1 step (1 passed)
-
-        """
-
-

data/features/post_configuration_hook.feature

@@ -1,37 +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: configuration modified to use HTML formatter
-
-    Given a standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
-      """
-      AfterConfiguration do |config|
-        config.options[:formats] << ['html', config.out_stream]
-      end
-      """
-    When I run cucumber features
-    Then STDERR should be empty
-    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:
-      """
-      AfterConfiguration do |config|
-        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
-      """
-      AfterConfiguration hook read feature directories: features
-      """

data/features/profiles.feature

@@ -1,126 +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/aslakhellesoy/cucumber/cucumberyml
-
-  Background: Basic App
-    Given a standard Cucumber project directory structure
-    And a file named "features/sample.feature" with:
-      """
-      Feature: Sample
-        Scenario: this is a test
-          Given I am just testing stuff
-      """
-    And a file named "features/support/env.rb"
-    And a 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 STDERR should be
-      """
-      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 ran
-      """
-      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.
-    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
-    And 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
-       """
-       cucumber -p super features/sample.feature:2 # Scenario: this is a test
-       """
-    Examples:
-      | format  |
-      | pretty  |
-      | progress|