cucumber 3.0.1 → 3.2.0

data/features/docs/cli/backtraces.feature

@@ -1,36 +0,0 @@
-Feature: Backtraces
-
-  In order to discover errors quickly
-  As a cuker
-  I want to see backtraces for failures
-
-  Background:
-    Given a file named "features/failing_hard.feature" with:
-      """
-      Feature: Sample
-        Scenario: Example
-          Given failing
-      """
-
-  @jruby
-  Scenario: Backtraces enabled
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      require 'java'
-      java_import 'java.util.Collections'
-
-      Given /^failing$/ do
-        Collections.empty_list.add 1
-      end
-      """
-    When I run `cucumber features/failing_hard.feature`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        Scenario: Example # features/failing_hard.feature:2
-          Given failing   # features/step_definitions/steps.rb:4
-             (Java::JavaLang::UnsupportedOperationException)
-            java.util.AbstractList.add(java/util/AbstractList.java:
-      """
-

data/features/docs/cli/dry_run.feature

@@ -1,73 +0,0 @@
-Feature: Dry Run
-
-  Dry run gives you a way to quickly scan your features without actually running them.
-
-  - Invokes formatters without executing the steps.
-  - This also omits the loading of your support/env.rb file if it exists.
-
-  Scenario: With a failing step
-    Given a file named "features/test.feature" with:
-      """
-      Feature: test
-        Scenario:
-          Given this step fails
-      """
-    And the standard step definitions
-    When I run `cucumber --dry-run`
-    Then it should pass with exactly:
-      """
-      Feature: test
-
-        Scenario:               # features/test.feature:2
-          Given this step fails # features/step_definitions/steps.rb:4
-
-      1 scenario (1 skipped)
-      1 step (1 skipped)
-
-      """
-
-  Scenario: In strict mode
-    Given a file named "features/test.feature" with:
-      """
-      Feature: test
-        Scenario:
-          Given this step fails
-      """
-    And the standard step definitions
-    When I run `cucumber --dry-run --strict`
-    Then it should pass with exactly:
-      """
-      Feature: test
-
-        Scenario:               # features/test.feature:2
-          Given this step fails # features/step_definitions/steps.rb:4
-
-      1 scenario (1 skipped)
-      1 step (1 skipped)
-
-      """
-
-  Scenario: In strict mode with an undefined step
-    Given a file named "features/test.feature" with:
-      """
-      Feature: test
-        Scenario:
-          Given this step is undefined
-      """
-    When I run `cucumber --dry-run --strict`
-    Then it should fail with:
-      """
-      Feature: test
-
-        Scenario:                      # features/test.feature:2
-          Given this step is undefined # features/test.feature:3
-            Undefined step: "this step is undefined" (Cucumber::Undefined)
-            features/test.feature:3:in `Given this step is undefined'
-
-      Undefined Scenarios:
-      cucumber features/test.feature:2 # Scenario: 
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """

data/features/docs/cli/exclude_files.feature

@@ -1,18 +0,0 @@
-Feature: Excluding ruby and feature files from runs
-
-  Developers are 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 an empty file named "features/support/dont_require_me.rb"
-    And an empty file named "features/step_definitions/fooz.rb"
-    And an empty file named "features/step_definitions/foof.rb"
-    And an empty file named "features/step_definitions/foot.rb"
-    And an empty 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/features/docs/cli/execute_with_tag_filter.feature

@@ -1,119 +0,0 @@
-Feature: Tag logic
-  In order to conveniently run subsets of features
-  As a Cuker
-  I want to select features using logical AND/OR of tags
-
-  Background:
-    Given a file named "features/test.feature" with:
-      """
-      @feature
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @three
-        Scenario: Yet another Example
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-          Given passing
-      """
-
-  Scenario: ANDing tags
-    When I run `cucumber -q -t '@one and @three' features/test.feature`
-    Then it should pass with:
-      """
-      @feature
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """
-
-  Scenario: ORing tags
-    When I run `cucumber -q -t '@one or @three' features/test.feature`
-    Then it should pass with:
-      """
-      @feature
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @three
-        Scenario: Yet another Example
-          Given passing
-
-      3 scenarios (3 undefined)
-      3 steps (3 undefined)
-
-      """
-
-  Scenario: Negative tags
-    When I run `cucumber -q -t 'not @three' features/test.feature`
-    Then it should pass with:
-      """
-      @feature
-      Feature: Sample
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-          Given passing
-
-      2 scenarios (2 undefined)
-      2 steps (2 undefined)
-      """
-
-  Scenario: Run with limited tag count, blowing it on scenario
-     When I run `cucumber -q --no-source --tags @one:1 features/test.feature`
-     Then it fails before running features with:
-       """
-       @one occurred 2 times, but the limit was set to 1
-         features/test.feature:5
-         features/test.feature:9
-       """
-
-  Scenario: Run with limited tag count, blowing it via feature inheritance
-     When I run `cucumber -q --no-source --tags @feature:1 features/test.feature`
-     Then it fails before running features with:
-       """
-       @feature occurred 4 times, but the limit was set to 1
-         features/test.feature:5
-         features/test.feature:9
-         features/test.feature:13
-         features/test.feature:17
-       """
-
-  Scenario: Run with limited tag count using negative tag, blowing it via a tag that is not run
-     When I run `cucumber -q --no-source --tags 'not @one:1' features/test.feature`
-     Then it fails before running features with:
-       """
-       @one occurred 2 times, but the limit was set to 1
-       """
-
-  Scenario: Limiting with tags which do not exist in the features
-    Originally added to check [Lighthouse bug #464](https://rspec.lighthouseapp.com/projects/16211/tickets/464).
-
-    When I run `cucumber -q -t @i_dont_exist features/test.feature`
-    Then it should pass

data/features/docs/cli/fail_fast.feature

@@ -1,48 +0,0 @@
-@spawn
-Feature: Fail fast
-
-  The --fail-fast flag causes Cucumber to exit immediately after the first 
-  scenario fails.
-
-  @todo-windows
-  Scenario: When a scenario fails
-    Given a file named "features/bad.feature" with:
-      """
-      Feature: Bad
-        Scenario: Failing
-          Given this step fails
-      """
-    And a file named "features/good.feature" with:
-    """
-    Feature: Good
-      Scenario: Passing
-        Given this step passes
-    """
-    And the standard step definitions
-    When I run `cucumber --fail-fast`
-    Then it should fail
-    And the output should contain:
-    """
-    1 scenario (1 failed)
-    """
-
-  @todo-windows
-  Scenario: When all the scenarios pass
-    Given a file named "features/first.feature" with:
-      """
-      Feature: first feature
-        Scenario: foo first
-          Given this step passes
-        Scenario: bar first
-          Given this step passes
-      """
-    And a file named "features/second.feature" with:
-      """
-      Feature: second
-        Scenario: foo second
-          Given this step passes
-        Scenario: bar second
-          Given this step passes
-      """
-    When I run `cucumber --fail-fast`
-    Then it should pass

data/features/docs/cli/finding_steps.feature

@@ -1,28 +0,0 @@
-Feature: Loading the steps users expect
-  As a User
-  In order to run features in subdirectories without having to pass extra options
-  I want cucumber to load all step files
-
-  Scenario:
-    Given a file named "features/nesting/test.feature" with:
-      """
-      Feature: Feature in Subdirectory
-        Scenario: A step not in the subdirectory
-          Given not found in subdirectory
-      """
-    And a file named "features/step_definitions/steps_no_in_subdirectory.rb" with:
-      """
-      Given(/^not found in subdirectory$/) { }
-      """
-    When I run `cucumber -q features/nesting/test.feature`
-    Then it should pass with:
-      """
-      Feature: Feature in Subdirectory
-
-        Scenario: A step not in the subdirectory
-          Given not found in subdirectory
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-      """
-

data/features/docs/cli/help.feature

@@ -1,8 +0,0 @@
-Feature: Help
-
-  Running `cucumber --help` shows you command-line options.
-
-  Scenario: Show help
-    When I run `cucumber --help`
-    Then it should pass
-    And I should see the CLI help

data/features/docs/cli/i18n.feature

@@ -1,42 +0,0 @@
-@needs-many-fonts
-Feature: i18n
-
-  It's possible to ask cucumber which keywords are used for any
-  particular language by running:
-
-  `cucumber --i18n-keywords <LANG>`
-
-  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-keywords pt`
-    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-languages`
-    Then cucumber lists all the supported languages
-
-  Scenario: Seek help for invalid language
-    When I run `cucumber --i18n-keywords foo`
-    Then the output includes the message "Invalid language 'foo'"
-    And cucumber lists all the supported languages

data/features/docs/cli/randomize.feature

@@ -1,140 +0,0 @@
-Feature: Randomize
-
-  Use the `--order random` switch to run scenarios in random order.
-
-  This is especially helpful for detecting situations where you have state
-  leaking between scenarios, which can cause flickering or fragile tests.
-
-  If you do find a random run that exposes dependencies between your tests,
-  you can reproduce that run by using the seed that's printed at the end of
-  the test run.
-
-  For a given seed, the order of scenarios is constant, i.e. if step A runs
-  before step B, it will always run before step B even if other steps are
-  skipped.
-
-  Background:
-    Given a file named "features/bad_practice_part_1.feature" with:
-      """
-      Feature: Bad practice, part 1
-        
-        Scenario: Set state
-          Given I set some state
-      
-        Scenario: Depend on state from a preceding scenario
-          When I depend on the state
-      """
-    And a file named "features/bad_practice_part_2.feature" with:
-      """
-      Feature: Bad practice, part 2
-
-        Scenario: Depend on state from a preceding feature
-          When I depend on the state
-      """
-    And a file named "features/unrelated.feature" with:
-      """
-      Feature: Unrelated
-
-        @skipme
-        Scenario: Do something unrelated
-          When I do something
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given(/^I set some state$/) do
-        $global_state = "set"
-      end
-
-      Given(/^I depend on the state$/) do
-        raise "I expect the state to be set!" unless $global_state == "set"
-      end
-
-      Given(/^I do something$/) do
-      end
-      """
-
-  Scenario: Run scenarios in order
-    When I run `cucumber`
-    Then it should pass
-
-  @spawn @todo-windows
-  Scenario: Run scenarios randomized
-    When I run `cucumber --order random:41544 -q`
-    Then it should fail
-    And the stdout should contain exactly:
-      """
-      Feature: Bad practice, part 1
-
-        Scenario: Depend on state from a preceding scenario
-          When I depend on the state
-            I expect the state to be set! (RuntimeError)
-            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
-            features/bad_practice_part_1.feature:7:in `When I depend on the state'
-
-      Feature: Unrelated
-
-        @skipme
-        Scenario: Do something unrelated
-          When I do something
-
-      Feature: Bad practice, part 2
-
-        Scenario: Depend on state from a preceding feature
-          When I depend on the state
-            I expect the state to be set! (RuntimeError)
-            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
-            features/bad_practice_part_2.feature:4:in `When I depend on the state'
-
-      Feature: Bad practice, part 1
-
-        Scenario: Set state
-          Given I set some state
-      
-      Failing Scenarios:
-      cucumber features/bad_practice_part_1.feature:6
-      cucumber features/bad_practice_part_2.feature:3
-
-      4 scenarios (2 failed, 2 passed)
-      4 steps (2 failed, 2 passed)
-
-      Randomized with seed 41544
-
-      """
-
-  @spawn @todo-windows
-  Scenario: Run scenarios randomized with some skipped
-    When I run `cucumber --tags ~@skipme --order random:41544 -q`
-    Then it should fail
-    And the stdout should contain exactly:
-      """
-      Feature: Bad practice, part 1
-
-        Scenario: Depend on state from a preceding scenario
-          When I depend on the state
-            I expect the state to be set! (RuntimeError)
-            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
-            features/bad_practice_part_1.feature:7:in `When I depend on the state'
-
-      Feature: Bad practice, part 2
-
-        Scenario: Depend on state from a preceding feature
-          When I depend on the state
-            I expect the state to be set! (RuntimeError)
-            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
-            features/bad_practice_part_2.feature:4:in `When I depend on the state'
-
-      Feature: Bad practice, part 1
-
-        Scenario: Set state
-          Given I set some state
-
-      Failing Scenarios:
-      cucumber features/bad_practice_part_1.feature:6
-      cucumber features/bad_practice_part_2.feature:3
-
-      3 scenarios (2 failed, 1 passed)
-      3 steps (2 failed, 1 passed)
-
-      Randomized with seed 41544
-
-      """