cucumber 3.0.0.pre.1 → 4.0.0.rc.4

data/features/docs/cli/fail_fast.feature

@@ -1,46 +0,0 @@
-@spawn
-Feature: Fail fast
-
-  The --fail-fast flag causes Cucumber to exit immediately after the first 
-  scenario fails.
-
-  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)
-    """
-
-  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/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
-  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
-  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
-
-      """

data/features/docs/cli/require.feature

@@ -1,27 +0,0 @@
-Feature: Requiring extra step files
-
-  Cucumber allows you to require extra files using the `-r` option.
-
-  Scenario:
-    Given a file named "features/test.feature" with:
-      """
-      Feature: Sample
-        Scenario: Sample
-          Given found in extra file
-      """
-    And a file named "tmp/extras.rb" with:
-      """
-      Given(/^found in extra file$/) { }
-      """
-    When I run `cucumber -q -r tmp/extras.rb features/test.feature`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        Scenario: Sample
-          Given found in extra file
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-      """
-

data/features/docs/cli/retry_failing_tests.feature

@@ -1,67 +0,0 @@
-Feature: Retry failing tests
-
-  Retry gives you a way to get through flaky tests that usually pass after a few runs.
-  This gives a development team a way forward other than disabling a valuable test.
-
-  - Specify max retry count in option
-  - Output information to the screen
-  - Output retry information in test report
-
-  Questions:
-  use a tag for flaky tests?  Global option to retry any test that fails?
-
-  Background:
-    Given a scenario "Fails-once" that fails once, then passes
-    And a scenario "Fails-twice" that fails twice, then passes
-    And a scenario "Solid" that passes
-    And a scenario "Fails-forever" that fails
-
-  Scenario: Retry once, so Fails-once starts to pass
-    When I run `cucumber -q --retry 1 --format summary`
-    Then it should fail with:
-      """
-      7 scenarios (5 failed, 2 passed)
-      """
-    And it should fail with:
-      """
-      Fails-forever
-        Fails-forever ✗
-        Fails-forever ✗
-
-      Solid
-        Solid ✓
-
-      Fails-once feature
-        Fails-once ✗
-        Fails-once ✓
-
-      Fails-twice feature
-        Fails-twice ✗
-        Fails-twice ✗
-      """
-
-  Scenario: Retry twice, so Fails-twice starts to pass too
-    When I run `cucumber -q --retry 2 --format summary`
-    Then it should fail with:
-      """
-      9 scenarios (6 failed, 3 passed)
-      """
-    And it should fail with:
-      """
-      Fails-forever
-        Fails-forever ✗
-        Fails-forever ✗
-        Fails-forever ✗
-
-      Solid
-        Solid ✓
-
-      Fails-once feature
-        Fails-once ✗
-        Fails-once ✓
-
-      Fails-twice feature
-        Fails-twice ✗
-        Fails-twice ✗
-        Fails-twice ✓
-      """

data/features/docs/cli/run_scenarios_matching_name.feature

@@ -1,104 +0,0 @@
-Feature: Run feature elements matching a name with --name/-n
-
-  The `--name NAME` option runs only scenarios which match a certain
-  name. The NAME can be a substring of the names of Features, Scenarios,
-  Scenario Outlines or Example blocks.
-
-  Background:
-    Given a file named "features/first.feature" with:
-      """
-      Feature: first feature
-        Scenario: foo first
-          Given missing
-        Scenario: bar first
-          Given missing
-      """
-    Given a file named "features/second.feature" with:
-      """
-      Feature: second
-        Scenario: foo second
-          Given missing
-        Scenario: bar second
-          Given missing
-      """
-    Given a file named "features/outline.feature" with:
-      """
-      Feature: outline
-        Scenario Outline: baz outline
-          Given outline step <name>
-
-          Examples: quux example
-            | name |
-            | a    |
-            | b    |
-      """
-
-  Scenario: Matching Feature names
-    When I run `cucumber -q --name feature`
-    Then it should pass with:
-      """
-      Feature: first feature
-
-        Scenario: foo first
-          Given missing
-
-        Scenario: bar first
-          Given missing
-
-      2 scenarios (2 undefined)
-      2 steps (2 undefined)
-      """
-
-  Scenario: Matching Scenario names
-    When I run `cucumber -q --name foo`
-    Then it should pass with:
-      """
-      Feature: first feature
-
-        Scenario: foo first
-          Given missing
-
-      Feature: second
-
-        Scenario: foo second
-          Given missing
-
-      2 scenarios (2 undefined)
-      2 steps (2 undefined)
-      """
-
-  Scenario: Matching Scenario Outline names
-    When I run `cucumber -q --name baz`
-    Then it should pass with:
-      """
-      Feature: outline
-
-        Scenario Outline: baz outline
-          Given outline step <name>
-
-          Examples: quux example
-            | name |
-            | a    |
-            | b    |
-
-      2 scenarios (2 undefined)
-      2 steps (2 undefined)
-      """
-
-  Scenario: Matching Example block names
-    When I run `cucumber -q --name quux`
-    Then it should pass with:
-      """
-      Feature: outline
-
-        Scenario Outline: baz outline
-          Given outline step <name>
-
-          Examples: quux example
-            | name |
-            | a    |
-            | b    |
-
-      2 scenarios (2 undefined)
-      2 steps (2 undefined)
-      """

data/features/docs/cli/run_specific_scenarios.feature

@@ -1,77 +0,0 @@
-Feature: Run specific scenarios
-
-  You can choose to run a specific scenario using the file:line format,
-  or you can pass in a file with a list of scenarios using @-notation.
-
-  The line number can fall anywhere within the body of a scenario, including
-  steps, tags, comments, description, data tables or doc strings.
-
-  For scenario outlines, if the line hits one example row, just that one
-  will be run. Otherwise all examples in the table or outline will be run.
-
-  Background:
-    Given the standard step definitions
-
-  Scenario: Two scenarios, run just one of them
-    Given a file named "features/test.feature" with:
-      """
-      Feature: 
-
-        Scenario: Miss
-          Given this step is undefined
-
-        Scenario: Hit
-          Given this step passes
-      """
-    When I run `cucumber features/test.feature:7 --format pretty --quiet`
-    Then it should pass with exactly:
-      """
-      Feature: 
-
-        Scenario: Hit
-          Given this step passes
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-      
-      """
-
-  Scenario: Use @-notation to specify a file containing feature file list
-    Given a file named "features/test.feature" with:
-      """
-      Feature: Sample
-        Scenario: Passing
-          Given this step passes
-      """
-    And a file named "list-of-features.txt" with:
-      """
-      features/test.feature:2
-      """
-    When I run `cucumber -q @list-of-features.txt`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        Scenario: Passing
-          Given this step passes
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-      """
-
-  Scenario: Specify order of scenarios
-    Given a file named "features/test.feature" with:
-      """
-      Feature: 
-        Scenario:
-          Given this step passes
-
-        Scenario:
-          Given this step fails
-      """
-    When I run `cucumber features/test.feature:5 features/test.feature:3 -f progress`
-    Then it should fail with:
-      """
-      F.
-      """
-