cucumber 3.0.0.pre.2 → 4.0.0.rc.5

data/features/docs/formatters/pretty_formatter.feature

@@ -1,74 +0,0 @@
-Feature: Pretty output formatter
-
-  Background:
-    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
-      """
-      Feature:
-
-        Scenario Outline:
-          Given this step is undefined
-
-        Examples:
-          |foo|
-          |bar|
-      """
-
-  Scenario: an scenario outline, one undefined step, one random example, expand flag on
-    When I run `cucumber features/scenario_outline_with_undefined_steps.feature --format pretty --expand `
-    Then it should pass
-
-  @todo-windows
-  Scenario: when using a profile the output should include 'Using the default profile...'
-    And a file named "cucumber.yml" with:
-    """
-      default: -r features
-    """
-    When I run `cucumber --profile default --format pretty`
-    Then it should pass
-    And the output should contain:
-    """
-    Using the default profile...
-    """
-  Scenario: Hook output should be printed before hook exception
-    Given the standard step definitions
-    And a file named "features/test.feature" with:
-      """
-      Feature:
-        Scenario:
-          Given this step passes
-      """
-    And a file named "features/step_definitions/output_steps.rb" with:
-      """
-      Before do
-        puts "Before hook"
-       end
-
-      AfterStep do
-        puts "AfterStep hook"
-      end
-
-      After do
-        puts "After hook"
-	raise "error"
-      end
-      """
-    When I run `cucumber -q -f pretty features/test.feature`
-    Then the stderr should not contain anything
-    Then it should fail with:
-      """
-      Feature: 
- 
-        Scenario: 
-            Before hook
-          Given this step passes
-            AfterStep hook
-            After hook
-            error (RuntimeError)
-            ./features/step_definitions/output_steps.rb:11:in `After'
-      
-      Failing Scenarios:
-      cucumber features/test.feature:2
-      
-      1 scenario (1 failed)
-      1 step (1 passed)
-      """

data/features/docs/formatters/progress_formatter.feature

@@ -1,32 +0,0 @@
-Feature: Progress output formatter
-
-  Background:
-    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
-      """
-      Feature:
-
-        Scenario Outline:
-          Given this step is undefined
-
-        Examples:
-          |foo|
-          |bar|
-      """
-
-  Scenario: an scenario outline, one undefined step, one random example, expand flag on
-    When I run `cucumber features/scenario_outline_with_undefined_steps.feature --format progress --expand `
-    Then it should pass
-
-  @todo-windows
-  Scenario: when using a profile the output should include 'Using the default profile...'
-    And a file named "cucumber.yml" with:
-    """
-      default: -r features
-    """
-    When I run `cucumber --profile default --format progress`
-    Then it should pass
-    And the output should contain:
-    """
-    Using the default profile...
-    """
-

data/features/docs/formatters/rerun_formatter.feature

@@ -1,190 +0,0 @@
-Feature: Rerun formatter
-
-  The rerun formatter writes an output that's perfect for
-  passing to Cucumber when you want to rerun only the 
-  scenarios that prevented the exit code to be zero.
-
-  You can save off the rerun output to a file by using it like this:
-
-  `cucumber -f rerun --out .cucumber.rerun`
-
-  Now you can pass that file's content to Cucumber to tell it
-  which scenarios to run:
-
-  `cucumber \`cat .cucumber.rerun\``
-
-  This is useful when debugging in a large suite of features.
-
-  Background:
-    Given the standard step definitions
-
-  @todo-windows
-  Scenario: Exit code is zero
-    Given a file named "features/mixed.feature" with:
-      """
-      Feature: Mixed
-
-        Scenario:
-          Given this step is undefined
-
-        Scenario:
-          Given this step is pending
-
-        Scenario:
-          Given this step passes
-
-      """
-
-    When I run `cucumber -f rerun`
-    Then it should pass with exactly:
-      """
-      """
-
-  Scenario: Exit code is zero in the dry-run mode
-    Given a file named "features/mixed.feature" with:
-      """
-      Feature: Mixed
-
-        Scenario:
-          Given this step fails
-
-        Scenario:
-          Given this step is undefined
-
-        Scenario:
-          Given this step is pending
-
-        Scenario:
-          Given this step passes
-
-      """
-    And a file named "features/all_good.feature" with:
-      """
-      Feature: All good
-
-        Scenario:
-          Given this step passes
-      """
-
-    When I run `cucumber -f rerun --dry-run`
-    Then it should pass with exactly:
-      """
-      """
-
-  @todo-windows
-  Scenario: Exit code is not zero, regular scenario
-    Given a file named "features/mixed.feature" with:
-      """
-      Feature: Mixed
-
-        Scenario:
-          Given this step fails
-
-        Scenario:
-          Given this step is undefined
-
-        Scenario:
-          Given this step is pending
-
-        Scenario:
-          Given this step passes
-
-      """
-    And a file named "features/all_good.feature" with:
-      """
-      Feature: All good
-
-        Scenario:
-          Given this step passes
-      """
-
-    When I run `cucumber -f rerun --strict`
-    Then it should fail with exactly:
-      """
-      features/mixed.feature:3:6:9
-      """
-
-  Scenario: Exit code is not zero, scenario outlines
-    For details see https://github.com/cucumber/cucumber/issues/57
-    Given a file named "features/one_passing_one_failing.feature" with:
-      """
-      Feature: One passing example, one failing example
-
-        Scenario Outline:
-          Given this step <status>
-        
-        Examples:
-          | status |
-          | passes |
-          | fails  |
-
-      """
-    When I run `cucumber -f rerun`
-    Then it should fail with:
-    """
-    features/one_passing_one_failing.feature:9
-    """
-
-  Scenario: Exit code is not zero, failing background
-    Given a file named "features/failing_background.feature" with:
-      """
-      Feature: Failing background sample
-
-        Background:
-          Given this step fails
-
-        Scenario: failing background
-          Then this step passes
-
-        Scenario: another failing background
-          Then this step passes
-      """
-    When I run `cucumber -f rerun`
-    Then it should fail with:
-    """
-    features/failing_background.feature:6:9
-    """
-
-  Scenario: Exit code is not zero, failing background with scenario outline
-    Given a file named "features/failing_background_outline.feature" with:
-      """
-      Feature: Failing background sample with scenario outline
-
-        Background:
-          Given this step fails
-
-        Scenario Outline:
-          Then this step <status>
-
-        Examples:
-          | status |
-          | passes |
-          | passes |
-      """
-    When I run `cucumber features/failing_background_outline.feature -r features -f rerun`
-    Then it should fail with:
-    """
-    features/failing_background_outline.feature:11:12
-    """
-
-  Scenario: Exit code is not zero, scenario outlines with expand
-    For details see https://github.com/cucumber/cucumber/issues/503
-
-    Given a file named "features/one_passing_one_failing.feature" with:
-    """
-      Feature: One passing example, one failing example
-
-        Scenario Outline:
-          Given this step <status>
-
-        Examples:
-          | status |
-          | passes |
-          | fails  |
-
-      """
-    When I run `cucumber --expand -f rerun`
-    Then it should fail with:
-    """
-    features/one_passing_one_failing.feature:9
-    """

data/features/docs/formatters/summary_formatter.feature

@@ -1,35 +0,0 @@
-Feature: Spec formatter
-
-  This formatter mimics the output from tools like RSpec or Mocha, giving an 
-  overview of each feature and scenario but omitting the steps.
-
-  Background:
-    Given the standard step definitions
-
-  @todo-windows
-  Scenario: A couple of scenarios
-    Given a file named "features/test.feature" with:
-    """
-    Feature: Test
-      Scenario: Passing
-        Given this step passes
-
-      Scenario: Failing
-        Given this step fails
-    """
-    When I run `cucumber --format summary`
-    Then it should fail with exactly:
-    """
-    Test
-      Passing ✓
-      Failing ✗
-
-    Failing Scenarios:
-    cucumber features/test.feature:5 # Scenario: Failing
-
-    2 scenarios (1 failed, 1 passed)
-    2 steps (1 failed, 1 passed)
-    0m0.012s
-
-    """
-

data/features/docs/formatters/usage_formatter.feature

@@ -1,101 +0,0 @@
-Feature: Usage formatter
-
-  In order to see where step definitions are used
-  Developers should be able to see a list of step definitions and their use
-
-  Background:
-    Given a file named "features/f.feature" with:
-      """
-      Feature: F
-        Background: A
-          Given A
-        Scenario: B
-          Given B
-        Scenario Outline: CA
-          Given <x>
-          And B
-          Examples:
-            |x|
-            |C|
-            |A|
-        Scenario: AC
-          Given A
-          Given C
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given(/A/) { }
-      Given(/B/) { }
-      Given(/C/) { }
-      Given(/D/) { }
-      """
-
-  @todo-windows
-  Scenario: Run with --format usage
-    When I run `cucumber -f usage --dry-run`
-    Then it should pass with exactly:
-      """
-      -----------
-      
-      /A/       # features/step_definitions/steps.rb:1
-        Given A # features/f.feature:3
-        Given A # features/f.feature:12
-        Given A # features/f.feature:14
-      /B/       # features/step_definitions/steps.rb:2
-        Given B # features/f.feature:5
-        And B   # features/f.feature:11
-        And B   # features/f.feature:12
-      /C/       # features/step_definitions/steps.rb:3
-        Given C # features/f.feature:11
-        Given C # features/f.feature:15
-      /D/       # features/step_definitions/steps.rb:4
-        NOT MATCHED BY ANY STEPS
-      
-      4 scenarios (4 skipped)
-      11 steps (11 skipped)
-
-      """
-
-  @todo-windows
-  Scenario: Run with --expand --format usage
-    When I run `cucumber -x -f usage --dry-run`
-    Then it should pass with exactly:
-      """
-      -----------
-      
-      /A/       # features/step_definitions/steps.rb:1
-        Given A # features/f.feature:3
-        Given A # features/f.feature:12
-        Given A # features/f.feature:14
-      /B/       # features/step_definitions/steps.rb:2
-        Given B # features/f.feature:5
-        And B   # features/f.feature:11
-        And B   # features/f.feature:12
-      /C/       # features/step_definitions/steps.rb:3
-        Given C # features/f.feature:11
-        Given C # features/f.feature:15
-      /D/       # features/step_definitions/steps.rb:4
-        NOT MATCHED BY ANY STEPS
-      
-      4 scenarios (4 skipped)
-      11 steps (11 skipped)
-
-      """
-
-    @todo-windows
-    Scenario: Run with --format stepdefs
-      When I run `cucumber -f stepdefs --dry-run`
-      Then it should pass with exactly:
-        """
-        -----------
-        
-        /A/   # features/step_definitions/steps.rb:1
-        /B/   # features/step_definitions/steps.rb:2
-        /C/   # features/step_definitions/steps.rb:3
-        /D/   # features/step_definitions/steps.rb:4
-          NOT MATCHED BY ANY STEPS
-        
-        4 scenarios (4 skipped)
-        11 steps (11 skipped)
-
-        """

data/features/docs/getting_started.feature

@@ -1,28 +0,0 @@
-Feature: Getting started
-
-  To get started, just open a command prompt in an empty directory and run 
-  `cucumber`. You'll be prompted for what to do next.
-
-  @spawn @todo-windows
-  Scenario: Run Cucumber in an empty directory
-    Given a directory without standard Cucumber project directory structure
-    When I run `cucumber`
-    Then it should fail with:
-      """
-      No such file or directory - features. You can use `cucumber --init` to get started.
-      """
-
-  @todo-windows
-  Scenario: Accidentally run Cucumber in a folder with Ruby files in it.
-    Given a directory without standard Cucumber project directory structure
-    And a file named "should_not_load.rb" with:
-      """
-      puts 'this will not be shown'
-      """
-    When I run `cucumber`
-    Then the exit status should be 2
-    And the output should not contain:
-      """
-      this will not be shown
-
-      """