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

data/features/docs/cli/fail_fast.feature

@@ -4,6 +4,7 @@ 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:
       """
@@ -25,6 +26,7 @@ Feature: Fail fast
     1 scenario (1 failed)
     """
 
+  @todo-windows
   Scenario: When all the scenarios pass
     Given a file named "features/first.feature" with:
       """

data/features/docs/{gherkin/language_help.feature → cli/i18n.feature}

@@ -1,17 +1,17 @@
 @needs-many-fonts
-Feature: Language help
+Feature: i18n
 
   It's possible to ask cucumber which keywords are used for any
   particular language by running:
 
-  `cucumber --i18n <language code> help`
+  `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 pt help`
+    When I run `cucumber --i18n-keywords pt`
     Then it should pass with:
       """
         | feature          | "Funcionalidade", "Característica", "Caracteristica"                                         |
@@ -33,10 +33,10 @@ Feature: Language help
       """
 
   Scenario: List languages
-    When I run `cucumber --i18n help`
+    When I run `cucumber --i18n-languages`
     Then cucumber lists all the supported languages
 
   Scenario: Seek help for invalid language
-    When I run `cucumber --i18n foo`
+    When I run `cucumber --i18n-keywords foo`
     Then the output includes the message "Invalid language 'foo'"
-    And cucumber lists all the supported languages
+    And cucumber lists all the supported languages

data/features/docs/cli/randomize.feature

@@ -57,7 +57,7 @@ Feature: Randomize
     When I run `cucumber`
     Then it should pass
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Run scenarios randomized
     When I run `cucumber --order random:41544 -q`
     Then it should fail
@@ -101,7 +101,7 @@ Feature: Randomize
 
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Run scenarios randomized with some skipped
     When I run `cucumber --tags ~@skipme --order random:41544 -q`
     Then it should fail

data/features/docs/cli/retry_failing_tests.feature

@@ -14,13 +14,14 @@ Feature: Retry failing tests
     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
 
+  @todo-windows
   Scenario: Retry once, so Fails-once starts to pass
+    Given a scenario "Fails-forever" that fails
     When I run `cucumber -q --retry 1 --format summary`
     Then it should fail with:
       """
-      7 scenarios (5 failed, 2 passed)
+      4 scenarios (2 failed, 1 flaky, 1 passed)
       """
     And it should fail with:
       """
@@ -40,11 +41,13 @@ Feature: Retry failing tests
         Fails-twice ✗
       """
 
+  @todo-windows
   Scenario: Retry twice, so Fails-twice starts to pass too
+    Given a scenario "Fails-forever" that fails
     When I run `cucumber -q --retry 2 --format summary`
     Then it should fail with:
       """
-      9 scenarios (6 failed, 3 passed)
+      4 scenarios (1 failed, 2 flaky, 1 passed)
       """
     And it should fail with:
       """
@@ -65,3 +68,25 @@ Feature: Retry failing tests
         Fails-twice ✗
         Fails-twice ✓
       """
+
+  @todo-windows
+  Scenario: Flaky scenarios gives exit code zero in non-strict mode
+    When I run `cucumber -q --retry 2 --format summary`
+    Then it should pass with:
+      """
+
+
+      3 scenarios (2 flaky, 1 passed)
+      """
+
+  @todo-windows
+  Scenario: Flaky scenarios gives non-zero exit code in strict mode
+    When I run `cucumber -q --retry 2 --format summary --strict`
+    Then it should fail with:
+      """
+      Flaky Scenarios:
+      cucumber features/fails_once.feature:2
+      cucumber features/fails_twice.feature:2
+
+      3 scenarios (2 flaky, 1 passed)
+      """

data/features/docs/cli/run_scenarios_matching_name.feature

@@ -33,6 +33,7 @@ Feature: Run feature elements matching a name with --name/-n
             | b    |
       """
 
+  @todo-windows
   Scenario: Matching Feature names
     When I run `cucumber -q --name feature`
     Then it should pass with:

data/features/docs/cli/specifying_multiple_formatters.feature

@@ -18,6 +18,7 @@ Feature: Running multiple formatters
         And there is world peace
     """
 
+  @todo-windows
   Scenario: Multiple formatters and outputs
     When I run `cucumber --no-color --format progress --out progress.txt --format pretty --out pretty.txt --no-source --dry-run --no-snippets features/test.feature`
     Then the stderr should not contain anything
@@ -45,6 +46,7 @@ Feature: Running multiple formatters
 
       """
 
+  @todo-windows
   Scenario: Two formatters to stdout
     When I run `cucumber -f progress -f pretty features/test.feature`
     Then it should fail with:
@@ -52,6 +54,7 @@ Feature: Running multiple formatters
       All but one formatter must use --out, only one can print to each stream (or STDOUT) (RuntimeError)
       """
 
+  @todo-windows
   Scenario: Two formatters to stdout when using a profile
     Given the following profiles are defined:
       """

data/features/docs/cli/strict_mode.feature

@@ -28,6 +28,9 @@ Feature: Strict mode
             Undefined step: "this step passes" (Cucumber::Undefined)
             features/missing.feature:3:in `Given this step passes'
 
+      Undefined Scenarios:
+      cucumber features/missing.feature:2
+
       1 scenario (1 undefined)
       1 step (1 undefined)
       """
@@ -45,6 +48,9 @@ Feature: Strict mode
             ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
             features/pending.feature:3:in `Given this step is pending'
 
+      Pending Scenarios:
+      cucumber features/pending.feature:2
+
       1 scenario (1 pending)
       1 step (1 pending)
       """

data/features/docs/defining_steps/nested_steps.feature

@@ -12,6 +12,7 @@ Feature: Nested Steps
       end
       """
 
+  @todo-windows
   Scenario: Use #steps to call several steps at once
     Given a step definition that looks like this:
       """ruby
@@ -31,6 +32,7 @@ Feature: Nested Steps
 
       """
 
+  @todo-windows
   Scenario: Use #step to call a single step
     Given a step definition that looks like this:
       """ruby
@@ -48,6 +50,7 @@ Feature: Nested Steps
 
       """
 
+  @todo-windows
   Scenario: Use #steps to call a table
     Given a step definition that looks like this:
       """ruby
@@ -77,6 +80,7 @@ Feature: Nested Steps
 
       """
 
+  @todo-windows
   Scenario: Use #steps to call a multi-line string
     Given a step definition that looks like this:
       """ruby
@@ -103,7 +107,7 @@ Feature: Nested Steps
       Liouville
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Backtrace doesn't skip nested steps
     Given a step definition that looks like this:
       """ruby

data/features/docs/defining_steps/nested_steps_i18n.feature

@@ -14,6 +14,7 @@ Feature: Nested Steps in I18n
       end
       """
 
+  @todo-windows
   Scenario: Use #steps to call several steps at once
     Given a step definition that looks like this:
       """ruby

data/features/docs/defining_steps/nested_steps_with_second_arg.feature

@@ -6,6 +6,7 @@ Feature: Nested Steps with either table or doc string
       Given two turtles
       """
 
+  @todo-windows
   Scenario: Use #step with table
     Given a step definition that looks like this:
       """ruby
@@ -34,6 +35,7 @@ Feature: Nested Steps with either table or doc string
 
       """
 
+  @todo-windows
   Scenario: Use #step with Doc String
     Given a step definition that looks like this:
       """ruby

data/features/docs/defining_steps/printing_messages.feature

@@ -76,7 +76,7 @@ Feature: Pretty formatter - Printing messages
       """
 
     # Don't know why, but we need to spawn this for JRuby otherwise it gives wierd errors
-    @spawn
+    @spawn @todo-windows
     Scenario: Delayed messages feature
       When I run `cucumber --quiet --format pretty features/f.feature`
       Then the stderr should not contain anything

data/features/docs/defining_steps/skip_scenario.feature

@@ -1,5 +1,6 @@
 Feature: Skip Scenario
 
+  @todo-windows
   Scenario: With a passing step
     Given a file named "features/test.feature" with:
       """

data/features/docs/defining_steps/snippets.feature

@@ -4,35 +4,35 @@ Feature: Snippets
   snippet suggestion, which you can then paste into a step definitions
   file of your choosing.
 
-  Scenario: Snippet for undefined step with a pystring
+  Scenario: Snippet for undefined step with a Doc String
     Given a file named "features/undefined_steps.feature" with:
       """
       Feature:
-      Scenario: pystring
-        Given a pystring
-        \"\"\"
-          example with <html> entities
-        \"\"\"
-        When a simple when step
-        And another when step
-        Then a simple then step
+        Scenario: Doc String
+          Given a Doc String
+          \"\"\"
+            example with <html> entities
+          \"\"\"
+          When 1 simple when step
+          And another "when" step
+          Then a simple then step
       """
     When I run `cucumber features/undefined_steps.feature -s`
     Then the output should contain:
       """
-      Given(/^a pystring$/) do |string|
+      Given("a Doc String") do |string|
         pending # Write code here that turns the phrase above into concrete actions
       end
 
-      When(/^a simple when step$/) do
+      When("{int} simple when step") do |int|
         pending # Write code here that turns the phrase above into concrete actions
       end
 
-      When(/^another when step$/) do
+      When("another {string} step") do |string|
         pending # Write code here that turns the phrase above into concrete actions
       end
 
-      Then(/^a simple then step$/) do
+      Then("a simple then step") do
         pending # Write code here that turns the phrase above into concrete actions
       end
       """
@@ -41,15 +41,15 @@ Feature: Snippets
     Given a file named "features/undefined_steps.feature" with:
       """
       Feature:
-      Scenario: table
-        Given a table
-          | table |
-          |example|
+        Scenario: table
+          Given a table
+            | table |
+            |example|
       """
     When I run `cucumber features/undefined_steps.feature -s`
     Then the output should contain:
       """
-      Given(/^a table$/) do |table|
+      Given("a table") do |table|
         # table is a Cucumber::MultilineArgument::DataTable
         pending # Write code here that turns the phrase above into concrete actions
       end

data/features/docs/events/gherkin_source_read_event.feature

@@ -0,0 +1,43 @@
+Feature: Gherkin Source Read Event
+
+  This event is fired when Cucumber reads a Gherkin document.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/GherkinSourceRead)
+  for more information about the data available on this event.
+
+  @todo-windows
+  Scenario: Read two documents
+    Given a file named "features/one.feature" with:
+      """
+      Feature: One
+        This is the first feature
+
+      """
+    And a file named "features/two.feature" with:
+      """
+      Feature: Two
+        This is the other feature
+
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.on_event :gherkin_source_read do |event|
+          config.out_stream.puts "path: #{event.path}"
+          config.out_stream.puts "body:\n#{event.body}"
+        end
+      end
+      """
+    When I run `cucumber --dry-run`
+    Then it should pass with:
+      """
+      path: features/one.feature
+      body:
+      Feature: One
+        This is the first feature
+      path: features/two.feature
+      body:
+      Feature: Two
+        This is the other feature
+      """
+

data/features/docs/events/step_activated_event.feature

@@ -0,0 +1,36 @@
+Feature: Step Activated Event
+
+  This event is fired when Cucumber finds a matching definition for a Gherkin step.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/StepActivated)
+  for more information about the data available on this event.
+
+  Scenario: Activate a step
+    Given a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /a step/ do
+        # automation goes here
+      end
+      """
+    And a file named "features/test.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given a step
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.on_event :step_activated do |event|
+          config.out_stream.puts "The step: #{event.test_step.location}"
+          config.out_stream.puts "The step definition: #{event.step_match.location}"
+        end
+      end
+      """
+    When I run `cucumber`
+    Then it should pass with:
+      """
+      The step: features/test.feature:3
+      The step definition: features/step_definitions/steps.rb:1
+      """
+

data/features/docs/events/step_definition_registered_event.feature

@@ -0,0 +1,29 @@
+Feature: Step definition registered
+
+  This event is fired when Cucumber loads the user's step definitions. Typically, this is
+  when the `Given /^my step$/ do` methods are called.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/StepDefinitionRegistered) for more information about the data available on this event.
+
+  Scenario: Register a new step definition
+    Given the standard step definitions
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /a step/ do
+        # automation goes here
+      end
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.on_event :step_definition_registered do |event|
+          config.out_stream.puts "The step definition: #{event.step_definition.location}"
+        end
+      end
+      """
+    When I run `cucumber`
+    Then it should pass with:
+      """
+      The step definition: features/step_definitions/steps.rb:1
+      """
+

data/features/docs/events/test_case_finished_event.feature

@@ -0,0 +1,35 @@
+Feature: Test Case Finished Event
+
+  This event is fired after each scenario or examples table row (generally named a 
+  Test Case) has finished executing. You can use the event to learn about the 
+  result of the test case.
+
+  See [the API documentation](http://www.rubydoc.info/github/cucumber/cucumber-ruby/Cucumber/Events/TestCaseFinished) for more information about the data available on this event.
+
+  Scenario: Test case passes
+    Given the standard step definitions
+    And a file named "features/passing.feature" with:
+      """
+      Feature: A feature
+        Scenario: A scenario
+          Given this step passes
+      """
+    And a file named "features/support/events.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.on_event :test_case_finished do |event|
+          config.out_stream.puts "Results"
+          config.out_stream.puts "-------"
+          config.out_stream.puts "Test case: #{event.test_case.name}"
+          config.out_stream.puts "The result is: #{event.result}"
+        end
+      end
+      """
+    When I run `cucumber`
+    Then it should pass with:
+      """
+      Results
+      -------
+      Test case: A scenario
+      The result is: ✓
+      """