cucumber 2.0.0.rc.5 → 4.0.0.rc.3

data/features/docs/api/list_step_defs_as_json.feature

@@ -1,50 +0,0 @@
-@spawn
-Feature: List step defs as json
-
-  In order to build tools on top of Cucumber
-  As a tool developer
-  I want to be able to query a features directory for all the step definitions it contains
-
-  Background:
-    Given a directory named "features"
-
-  Scenario: Two Ruby step definitions, in the same file
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      Given(/foo/i)  { }
-      Given(/b.r/xm) { }
-      """
-    When I run the following Ruby code:
-      """
-      require 'cucumber'
-      puts Cucumber::StepDefinitions.new.to_json
-      
-      """
-    Then it should pass with JSON:
-      """
-      [
-        {"source": "foo", "flags": "i"},
-        {"source": "b.r", "flags": "mx"}
-      ]
-      """
-
-  Scenario: Non-default directory structure
-    Given a file named "my_weird/place/steps.rb" with:
-      """
-      Given(/foo/)  { }
-      Given(/b.r/x) { }
-      """
-    When I run the following Ruby code:
-      """
-      require 'cucumber'
-      puts Cucumber::StepDefinitions.new(:autoload_code_paths => ['my_weird']).to_json
-      
-      """
-    Then it should pass with JSON:
-      """
-      [
-        {"source": "foo", "flags": ""},
-        {"source": "b.r", "flags": "x"}
-      ]
-      
-      """

data/features/docs/api/run_cli_main_with_existing_runtime.feature

@@ -1,29 +0,0 @@
-@spawn
-Feature: Run Cli::Main with existing Runtime
-
-  This is the API that Spork uses. It creates an existing runtime then
-  calls load_programming_language('rb') on it to load the RbDsl.
-  When the process forks, Spork them passes the runtime to Cli::Main to 
-  run it.
-
-    Scenario: Run a single feature
-      Given the standard step definitions
-      Given a file named "features/success.feature" with:
-        """
-        Feature: 
-          Scenario: 
-            Given this step passes
-        """
-      When I run the following Ruby code:
-        """
-        require 'cucumber'
-        runtime = Cucumber::Runtime.new
-        runtime.load_programming_language('rb')
-        Cucumber::Cli::Main.new([]).execute!(runtime)
-        
-        """
-      Then it should pass
-      And the output should contain:
-        """
-        Given this step passes
-        """

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,68 +0,0 @@
-Feature: Dry Run
-  - 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)
-      0m0.012s
-
-      """
-  Scenario: In the 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)
-      0m0.012s
-
-      """
-  Scenario: In the 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'
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-      0m0.012s
-
-      """

data/features/docs/cli/exclude_files.feature

@@ -1,19 +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,117 +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
-      """
-
-  Scenario: ANDing tags
-    When I run `cucumber -q -t @one -t @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,@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 ~@three features/test.feature`
-    Then it should pass with:
-      """
-      @feature
-      Feature: Sample
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-
-      2 scenarios (1 undefined, 1 passed)
-      1 step (1 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 ~@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/randomize.feature

@@ -1,46 +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 randmon 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.
-
-  Background:
-    Given a file named "features/bad_practice.feature" with:
-      """
-      Feature: Bad practice
-        
-        Scenario: Set state
-          Given I set some state
-      
-        Scenario: Depend on state
-          When I depend on the state
-      """
-    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
-      """
-
-  Scenario: Run scenarios in order
-    When I run `cucumber`
-    Then it should pass
-
-  @spawn
-  Scenario: Run scenarios randomized
-    When I run `cucumber --order random:41515`
-    Then it should fail
-    And the stdout should contain:
-      """
-      Randomized with seed 41515
-      """
-

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