cucumber 3.0.0.pre.1 → 3.0.0.pre.2

data/features/docs/formatters/rerun_formatter.feature

@@ -18,6 +18,7 @@ Feature: Rerun formatter
   Background:
     Given the standard step definitions
 
+  @todo-windows
   Scenario: Exit code is zero
     Given a file named "features/mixed.feature" with:
       """
@@ -70,6 +71,7 @@ Feature: Rerun formatter
       """
       """
 
+  @todo-windows
   Scenario: Exit code is not zero, regular scenario
     Given a file named "features/mixed.feature" with:
       """

data/features/docs/formatters/summary_formatter.feature

@@ -6,6 +6,7 @@ Feature: Spec formatter
   Background:
     Given the standard step definitions
 
+  @todo-windows
   Scenario: A couple of scenarios
     Given a file named "features/test.feature" with:
     """

data/features/docs/formatters/usage_formatter.feature

@@ -30,6 +30,7 @@ Feature: Usage formatter
       Given(/D/) { }
       """
 
+  @todo-windows
   Scenario: Run with --format usage
     When I run `cucumber -f usage --dry-run`
     Then it should pass with exactly:
@@ -55,6 +56,7 @@ Feature: Usage formatter
 
       """
 
+  @todo-windows
   Scenario: Run with --expand --format usage
     When I run `cucumber -x -f usage --dry-run`
     Then it should pass with exactly:
@@ -80,6 +82,7 @@ Feature: Usage formatter
 
       """
 
+    @todo-windows
     Scenario: Run with --format stepdefs
       When I run `cucumber -f stepdefs --dry-run`
       Then it should pass with exactly:

data/features/docs/getting_started.feature

@@ -3,7 +3,7 @@ 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
+  @spawn @todo-windows
   Scenario: Run Cucumber in an empty directory
     Given a directory without standard Cucumber project directory structure
     When I run `cucumber`
@@ -12,6 +12,7 @@ Feature: Getting started
       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:

data/features/docs/gherkin/background.feature

@@ -295,7 +295,7 @@ Feature: Background
 
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: run a feature with a background that fails
     When I run `cucumber -q features/failing_background.feature`
     Then it should fail with exactly:
@@ -324,7 +324,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: run a feature with scenario outlines that has a background that fails
     When I run `cucumber -q features/scenario_outline_failing_background.feature`
     Then it should fail with exactly:
@@ -383,7 +383,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: background passes with first scenario but fails with second
     When I run `cucumber -q features/failing_background_after_success.feature`
     Then it should fail with exactly:
@@ -412,7 +412,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: background passes with first outline scenario but fails with second
     When I run `cucumber -q features/failing_background_after_success_outline.feature`
     Then it should fail with exactly:
@@ -448,7 +448,7 @@ Feature: Background
     
     """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: background passes with first outline scenario but fails with second (--expand)
     When I run `cucumber -x -q features/failing_background_after_success_outline.feature`
     Then it should fail with exactly:

data/features/docs/gherkin/doc_strings.feature

@@ -29,6 +29,7 @@ Feature: Doc strings
   You can read the content type from the argument passed into your step definition, as shown
   in the example below.
 
+  @todo-windows
   Scenario: Plain text Docstring
     Given a scenario with a step that looks like this:
       """gherkin
@@ -53,6 +54,7 @@ Feature: Doc strings
       Three
       """
 
+  @todo-windows
   Scenario: DocString passed as String
     Given a scenario with a step that looks like this:
       """gherkin

data/features/docs/gherkin/expand_option_for_outlines.feature

@@ -4,6 +4,7 @@ Feature: Scenario outlines --expand option
   for some people to understand scenarios, Cucumber will expand examples
   in outlines if you add the `--expand` option when running them.
 
+  @todo-windows
   Scenario:
     Given a file named "features/test.feature" with:
       """

data/features/docs/gherkin/outlines.feature

@@ -43,6 +43,7 @@ Feature: Scenario outlines
       Given(/^failing without a table$/) { raise RuntimeError }
       """
 
+  @todo-windows
   Scenario: Run scenario outline with filtering on outline name
     When I run `cucumber -q features/outline_sample.feature`
     Then it should fail with:
@@ -76,6 +77,7 @@ Feature: Scenario outlines
       8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
       """
 
+  @todo-windows
   Scenario: Run scenario outline steps only
     When I run `cucumber -q features/outline_sample.feature:7`
     Then it should fail with:
@@ -108,6 +110,7 @@ Feature: Scenario outlines
 
       """
 
+  @todo-windows
   Scenario: Run single failing scenario outline table row
     When I run `cucumber -q features/outline_sample.feature:12`
     Then it should fail with:
@@ -134,6 +137,7 @@ Feature: Scenario outlines
 
       """
 
+  @todo-windows
   Scenario: Run all with progress formatter
     When I run `cucumber -q --format progress features/outline_sample.feature`
     Then it should fail with exactly:

data/features/docs/gherkin/unicode_table.feature

@@ -5,6 +5,7 @@ Feature: Unicode in tables
   ensure that the tables are properly aligned so that your output is as
   readable as possible.
 
+  @todo-windows
   Scenario:
     Given a file named "features/unicode.feature" with:
       """

data/features/docs/gherkin/using_descriptions.feature

@@ -1,3 +1,4 @@
+@todo-windows
 Feature: Using descriptions to give features context
 
   When writing your feature files its very helpful to use description

data/features/docs/gherkin/using_star_notation.feature

@@ -31,7 +31,7 @@ Feature: Using star notation instead of Given/When/Then
       """
       You can implement step definitions for undefined steps with these snippets:
 
-      Given(/^I have some cukes$/) do
+      Given("I have some cukes") do
         pending # Write code here that turns the phrase above into concrete actions
       end
       """

data/features/docs/post_configuration_hook.feature

@@ -8,7 +8,7 @@ Feature: Post Configuration Hook [#423]
     Given a file named "features/support/env.rb" with:
       """
       AfterConfiguration do |config|
-        config.formats << ['html', config.out_stream]
+        config.formats << ['html', {}, config.out_stream]
       end
       """
     When I run `cucumber features`

data/features/docs/rake_task.feature

@@ -16,6 +16,7 @@ Feature: Rake task
           Given I don't want this ran
       """
 
+  @todo-windows
   Scenario: rake task with a defined profile
     Given the following profile is defined:
       """
@@ -41,6 +42,7 @@ Feature: Rake task
       1 step (1 undefined)
       """
 
+  @todo-windows
   Scenario: rake task without a profile
     Given a file named "Rakefile" with:
       """
@@ -65,6 +67,7 @@ Feature: Rake task
       2 steps (2 undefined)
       """
 
+  @todo-windows
   Scenario: rake task with a defined profile and cucumber_opts
     Given the following profile is defined:
       """
@@ -91,6 +94,7 @@ Feature: Rake task
       1 step (1 undefined)
       """
 
+  @todo-windows
   Scenario: respect requires
     Given an empty file named "features/support/env.rb"
     And an empty file named "features/support/dont_require_me.rb"
@@ -114,6 +118,7 @@ Feature: Rake task
         * features/support/dont_require_me.rb
       """
 
+  @todo-windows
   Scenario: feature files with spaces
     Given a file named "features/spaces are nasty.feature" with:
        """

data/features/docs/raketask.feature

@@ -1,4 +1,4 @@
-@spawn
+@spawn @wip-jruby
 Feature: Raketask
 
   In order to use cucumber's rake task
@@ -34,10 +34,12 @@ Feature: Raketask
         end
       """
 
+  @todo-windows
   Scenario: Passing feature
     When I run `bundle exec rake pass`
     Then the exit status should be 0
 
+  @todo-windows
   Scenario: Failing feature
     When I run `bundle exec rake fail`
     Then the exit status should be 1

data/features/docs/work_in_progress.feature

@@ -37,6 +37,7 @@ Feature: Cucumber --work-in-progress switch
             | passes |
       """
 
+  @todo-windows
   Scenario: Pass with Failing Scenarios
     When I run `cucumber -q -w -t @failing features/wip.feature`
     Then the stderr should not contain anything
@@ -63,6 +64,7 @@ Feature: Cucumber --work-in-progress switch
 
       """
 
+  @todo-windows
   Scenario: Pass with Undefined Scenarios
     When I run `cucumber -q -w -t @undefined features/wip.feature`
     Then it should pass with:
@@ -82,6 +84,7 @@ Feature: Cucumber --work-in-progress switch
 
       """
 
+  @todo-windows
   Scenario: Pass with Undefined Scenarios
     When I run `cucumber -q -w -t @pending features/wip.feature`
     Then it should pass with:
@@ -104,6 +107,7 @@ Feature: Cucumber --work-in-progress switch
 
       """
 
+  @todo-windows
   Scenario: Fail with Passing Scenarios
     When I run `cucumber -q -w -t @passing features/wip.feature`
     Then it should fail with:
@@ -124,9 +128,9 @@ Feature: Cucumber --work-in-progress switch
 
       features/wip.feature:15:in `Scenario: Passing'
 
-
       """
 
+  @todo-windows
   Scenario: Fail with Passing Scenario Outline
     When I run `cucumber -q -w features/passing_outline.feature`
     Then it should fail with:
@@ -150,5 +154,4 @@ Feature: Cucumber --work-in-progress switch
 
       features/passing_outline.feature:7:in `Scenario Outline: Passing, Examples (#1)'
 
-
       """

data/features/docs/writing_support_code/after_step_hooks.feature

@@ -12,6 +12,7 @@ Feature: AfterStep Hooks
           Given this step passes
       """
 
+  @todo-windows
   Scenario: Access Test Step object in AfterStep Block
     Given a file named "features/support/env.rb" with:
       """
@@ -32,6 +33,7 @@ Feature: AfterStep Hooks
 
       """
 
+  @todo-windows
   Scenario: An AfterStep with one named argument receives only the result
     Given a file named "features/support/env.rb" with:
       """
@@ -50,4 +52,4 @@ Feature: AfterStep Hooks
       1 scenario (1 passed)
       1 step (1 passed)
 
-      """
+      """

data/features/docs/writing_support_code/around_hooks.feature

@@ -5,6 +5,7 @@ Feature: Around hooks
   that provide only a block syntax for transactions, Cucumber should
   permit definition of Around hooks.
 
+  @todo-windows
   Scenario: A single Around hook
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -38,6 +39,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Multiple Around hooks
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -84,6 +86,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Mixing Around, Before, and After hooks
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -131,6 +134,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Around hooks with tags
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -185,6 +189,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Around hooks with scenario outlines
     Given a file named "features/step_definitions/steps.rb" with:
       """
@@ -228,6 +233,7 @@ Feature: Around hooks
 
       """
 
+  @todo-windows
   Scenario: Around Hooks and the Custom World
     Given a file named "features/step_definitions/steps.rb" with:
       """

data/features/docs/writing_support_code/before_hook.feature

@@ -1,5 +1,6 @@
 Feature: Before Hook
 
+  @todo-windows
   Scenario: Examine names of scenario and feature
     Given a file named "features/foo.feature" with:
       """

data/features/docs/writing_support_code/hook_order.feature

@@ -46,6 +46,7 @@
           Given scenario step
       """
 
+  @todo-windows
   Scenario: Around hooks cover background steps
     When I run `cucumber -o /dev/null features/around_hook_covers_background.feature`
     Then the output should contain:
@@ -53,9 +54,10 @@
       Event order: around_begin background_step scenario_step around_end
       """
 
+  @todo-windows
   Scenario: All hooks execute in expected order
     When I run `cucumber -o /dev/null features/all_hook_order.feature`
     Then the output should contain:
       """
       Event order: around_begin before background_step scenario_step after around_end
-      """
+      """

data/features/docs/writing_support_code/parameter_types.feature

@@ -0,0 +1,75 @@
+Feature: Parameter Types
+
+  Parameter Types allow you to convert primitive string arguments captured in step definitions
+  into more meaningful data types.
+
+  Background:
+    Let's just create a simple feature for testing out parameter types.
+    We also have a Person class that we need to be able to build.
+
+    Given a file named "features/foo.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given Joe has gone home
+          When Sally contacts Joe
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      # It works with Regular Expressions
+      Given /([A-Z]\w+) has gone home/ do |person|
+        expect(person.name).to eq 'Joe'
+      end
+
+      # It works with Cucumber Expressions too
+      When "{person} contacts {person}" do |contacter, contactee|
+        expect(contacter.name).to eq 'Sally'
+        expect(contactee.name).to eq 'Joe'
+      end
+      """
+    And a file named "features/support/env.rb" with:
+      """
+      class Person
+        attr_reader :name
+
+        def initialize(name)
+          @name = name
+        end
+      end
+      """
+
+  Scenario: Parameter type defined with ParameterType method
+    This is the most basic way to use a parameter type.
+
+    Given a file named "features/support/parameter_types.rb" with:
+      """
+      ParameterType(
+        name: 'person',
+        regexp: /[A-Z]\w+/,
+        type: Person,
+        transformer: lambda do |name|
+          Person.new(name)
+        end,
+        use_for_snippets: true,
+        prefer_for_regexp_match: false
+      )
+      """
+    When I run `cucumber features/foo.feature`
+    Then it should pass
+
+  Scenario: Parameter type defined with legacy Transform method
+    This is for backwards compatibility - works with regular expressions,
+    but not with Cucumber Expressions, because no name is specified for the
+    parameter type.
+
+    Given a file named "features/support/transforms.rb" with:
+      """
+      Transform(/[A-Z]\w+/) do |name|
+        Person.new(name)
+      end
+      """
+    When I run `cucumber features/foo.feature`
+    Then it should fail with:
+      """
+      Undefined parameter type {person}
+      """