cucumber 1.2.5 → 1.3.0

data/features/nested_steps_i18n.feature

@@ -0,0 +1,36 @@
+@fails_on_1_8_7
+Feature: Nested Steps in I18n
+
+
+  Background:
+    Given a scenario with a step that looks like this in japanese:
+      """gherkin
+      前提 two turtles
+      """
+    And a step definition that looks like this:
+      """ruby
+      # -*- coding: utf-8 -*-
+      前提 /a turtle/ do
+        puts "turtle!"
+      end
+      """
+
+  Scenario: Use #steps to call several steps at once
+    Given a step definition that looks like this:
+      """ruby
+      # -*- coding: utf-8 -*-
+      前提 /two turtles/ do
+        steps %{
+          前提 a turtle
+          かつ a turtle
+        }
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      turtle!
+
+      turtle!
+
+      """

data/features/pretty_formatter.feature

@@ -0,0 +1,31 @@
+Feature: Pretty output formatter
+
+  Background:
+    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
+      """
+      Feature:
+
+        Scenario Outline:
+          Given an undefined step
+
+        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
+
+  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...
+    """
+

data/features/progress_formatter.feature

@@ -0,0 +1,31 @@
+Feature: Progress output formatter
+
+  Background:
+    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
+      """
+      Feature:
+
+        Scenario Outline:
+          Given an undefined step
+
+        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
+
+  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/raketask.feature

@@ -0,0 +1,51 @@
+@spawn
+Feature: Raketask
+  In order to use cucumber's rake task
+  As a Cuker
+  I do not want to see rake's backtraces when it fails
+  Also I want to get zero exit status code on failures
+  And non-zero exit status code when is pases
+
+  Background:
+    Given a file named "features/passing_and_failing.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Passing
+          Given passing
+
+        Scenario: Failing
+          Given failing
+      """
+    Given a file named "features/step_definitions/steps.rb" with:
+      """
+      Given(/^passing$/) do
+      end
+
+      Given /^failing$/ do
+        raise "FAIL"
+      end
+      """
+    Given a file named "Rakefile" with:
+      """
+        require 'cucumber/rake/task'
+
+        SAMPLE_FEATURE_FILE = 'features/passing_and_failing.feature'
+
+        Cucumber::Rake::Task.new(:pass) do |t|
+          t.cucumber_opts = "#{SAMPLE_FEATURE_FILE}:3"
+        end
+
+        Cucumber::Rake::Task.new(:fail) do |t|
+          t.cucumber_opts = "#{SAMPLE_FEATURE_FILE}:6"
+        end
+      """
+
+  Scenario: Passing feature
+    When I run `bundle exec rake pass`
+    Then the exit status should be 0
+
+  Scenario: Failing feature
+    When I run `bundle exec rake fail`
+    Then the exit status should not be 0
+    And the output should not contain "rake aborted!"

data/features/rerun_formatter.feature

@@ -27,7 +27,7 @@ Feature: Rerun formatter
       """
 
   Scenario: Handle examples with the rerun formatter
-    When I run cucumber "features/one_passing_one_failing.feature -r features -f rerun"
+    When I run `cucumber features/one_passing_one_failing.feature -r features -f rerun`
     Then it should fail with:
     """
     features/one_passing_one_failing.feature:9

data/features/stats_formatters.feature

@@ -12,6 +12,7 @@ Feature: Usage formatter
           Given B
         Scenario Outline: C
           Given <x>
+          And B
           Examples:
             |x|
             |C|
@@ -31,22 +32,24 @@ Feature: Usage formatter
     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:3
-        Given A # features/f.feature:3
-        Given A # features/f.feature:12
-      /B/       # features/step_definitions/steps.rb:2
-        Given B # features/f.feature:5
-      /C/       # features/step_definitions/steps.rb:3
-        Given C # features/f.feature:13
-      /D/       # features/step_definitions/steps.rb:4
+      /A/         # features/step_definitions/steps.rb:1
+        Given A   # features/f.feature:3
+        Given A   # features/f.feature:3
+        Given A   # features/f.feature:3
+        Given A   # features/f.feature:13
+      /B/         # features/step_definitions/steps.rb:2
+        Given B   # features/f.feature:5
+        And B     # features/f.feature:8
+      /C/         # features/step_definitions/steps.rb:3
+        Given <x> # features/f.feature:7
+        Given C   # features/f.feature:14
+      /D/         # features/step_definitions/steps.rb:4
         NOT MATCHED BY ANY STEPS
       
       3 scenarios (3 skipped)
-      7 steps (7 skipped)
+      8 steps (8 skipped)
       0m0.012s
 
       """
@@ -55,7 +58,7 @@ Feature: Usage formatter
       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
@@ -64,7 +67,7 @@ Feature: Usage formatter
           NOT MATCHED BY ANY STEPS
         
         3 scenarios (3 skipped)
-        7 steps (7 skipped)
+        8 steps (8 skipped)
         0m0.012s
 
         """

data/features/step_definitions/cucumber_steps.rb

@@ -1,7 +1,3 @@
-When /^I run cucumber "(.+)"$/ do |cmd|
-  run_simple(unescape("cucumber #{cmd}"), false)
-end
-
 Then 'it should pass' do
   assert_exit_status 0
 end
@@ -43,6 +39,12 @@ Given /^a scenario with a step that looks like this:$/ do |string|
   end
 end
 
+Given(/^a scenario with a step that looks like this in japanese:$/) do |string|
+  create_feature_ja do
+    create_scenario_ja { string }
+  end
+end
+
 Given /^a step definition that looks like this:$/ do |string|
   create_step_definition { string }
 end

data/features/support/env.rb

@@ -1,28 +1,55 @@
 ENV['FORCE_COLOR'] = 'true'
+
+require 'aruba'
 require 'aruba/api'
 require 'aruba/cucumber'
+require 'aruba/in_process'
+require 'aruba/spawn_process'
+require 'cucumber/rspec/disable_option_parser'
+require 'cucumber/cli/main'
 
 # Monkey patch aruba to filter out some stuff
 module Aruba::Api
   alias __all_stdout all_stdout
-  
+
   def all_stdout
     unrandom(__all_stdout)
   end
 
+  alias __all_stderr all_stderr
+  def all_stderr
+    err = __all_stderr
+    if Cucumber::JRUBY
+      # TODO: this actually a workaround for cucumber/gherkin#238
+      err = err.gsub(/^.*java_package_module_template.rb:\d+ warning: `eval' should not be aliased.*\n/, '')
+    end
+    err
+  end
+
   def unrandom(out)
     out = out.gsub(/#{Dir.pwd}\/tmp\/aruba/, '.') # Remove absolute paths
+    out = out.gsub(/tmp\/aruba\//, '')            # Fix aruba path
+    out = out.gsub(/^.*cucumber_process\.rb.*$\n/, '')
     out = out.gsub(/^\d+m\d+\.\d+s$/, '0m0.012s') # Make duration predictable
     out = out.gsub(/Coverage report generated for Cucumber Features to #{Dir.pwd}\/coverage.*\n$/, '') # Remove SimpleCov message
   end
 end
 
+Before('@spawn') do
+  Aruba.process = Aruba::SpawnProcess
+end
+
+Before('~@spawn') do
+  Aruba::InProcess.main_class = Cucumber::Cli::Main
+  Aruba.process = Aruba::InProcess
+end
+
 Before do
   # Make sure bin/cucumber runs with SimpleCov enabled
   # set_env('SIMPLECOV', 'true')
-  
-  # Set a longer timeout for aruba
-  @aruba_timeout_seconds = 15
+
+  # Set a longer timeout for aruba, and a really long one if running on JRuby
+  @aruba_timeout_seconds = Cucumber::JRUBY ? 35 : 15
 end
 
 After do

data/features/support/feature_factory.rb

@@ -1,3 +1,4 @@
+# -*- coding: utf-8 -*-
 module FeatureFactory
   def create_feature(name = generate_feature_name)
     gherkin = <<-GHERKIN
@@ -7,6 +8,15 @@ Feature: #{name}
     write_file filename(name), gherkin
   end
 
+  def create_feature_ja(name = generate_feature_name)
+    gherkin = <<-GHERKIN
+# language: ja
+機能: #{name}
+#{yield}
+    GHERKIN
+    write_file filename(name), gherkin
+  end
+
   def create_scenario(name = generate_scenario_name)
     <<-GHERKIN
   Scenario: #{name}
@@ -14,6 +24,13 @@ Feature: #{name}
     GHERKIN
   end
 
+  def create_scenario_ja(name = generate_scenario_name)
+    <<-GHERKIN
+  シナリオ: #{name}
+  #{yield}
+    GHERKIN
+  end
+
   def create_step_definition
     write_file generate_step_definition_filename, yield
   end

data/features/tagged_hooks.feature

@@ -1,217 +1,59 @@
-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
+Feature: Tagged hooks
 
   Background:
-    Given a file named "features/tagulicious.feature" with:
+    Given a file named "features/step_definitions/steps.rb" with:
       """
-      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: Before hooks ORing
-    Given a file named "features/support/hooks.rb" with:
-      """
-      Before('@one,@three') do
-        raise 'boom'
-      end
-      """
-    When I run `cucumber -q features/tagulicious.feature`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-       boom (RuntimeError)
-       ./features/support/hooks.rb:2:in `Before'
-          Given passing
-
-        @one
-        Scenario: Another Example
-       boom (RuntimeError)
-       ./features/support/hooks.rb:2:in `Before'
-          Given passing
-
-        @three
-        Scenario: Yet another Example
-       boom (RuntimeError)
-       ./features/support/hooks.rb:2:in `Before'
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-
-      Failing Scenarios:
-      cucumber features/tagulicious.feature:4
-      cucumber features/tagulicious.feature:8
-      cucumber features/tagulicious.feature:12
-
-      4 scenarios (3 failed, 1 passed)
-      3 steps (3 undefined)
-
-      """
-
-  Scenario: Before hooks ANDing
-    Given a file named "features/support/hooks.rb" with:
-      """
-      Before('@one','@three') do
-        raise 'boom'
-      end
-      """
-    When I run `cucumber -q features/tagulicious.feature`
-    Then it should fail with:
-      """
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-       boom (RuntimeError)
-       ./features/support/hooks.rb:2:in `Before'
-          Given passing
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @three
-        Scenario: Yet another Example
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-
-      Failing Scenarios:
-      cucumber features/tagulicious.feature:4
-
-      4 scenarios (1 failed, 2 undefined, 1 passed)
-      3 steps (3 undefined)
-
+      Given /^this step works$/ do; end
       """
-
-  Scenario: Before hooks ANDing with a bad hook matching nothing
-    Given a file named "features/support/hooks.rb" with:
+    And a file named "features/support/hooks.rb" with:
       """
-      Before('@one','@notused') do
+      Before('~@no-boom') do 
         raise 'boom'
       end
       """
-    When I run `cucumber -q features/tagulicious.feature`
-    Then it should pass with:
-      """
-      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
-
-      4 scenarios (3 undefined, 1 passed)
-      3 steps (3 undefined)
-
+    And a file named "features/f.feature" with:
       """
+      Feature: With and without hooks
+        Scenario: using hook
+          Given this step works
 
-  Scenario: After hooks ORing
-    Given a file named "features/support/hooks.rb" with:
-      """
-      After('@one,@three') do
-        raise 'boom'
-      end
+        @no-boom
+        Scenario: omitting hook
+          Given this step works
       """
-    When I run `cucumber -q features/tagulicious.feature`
+  @spawn
+  Scenario: omit tagged hook
+    When I run `cucumber features/f.feature:2`
     Then it should fail with:
       """
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-            boom (RuntimeError)
-            ./features/support/hooks.rb:2:in `After'
-
-        @one
-        Scenario: Another Example
-          Given passing
-            boom (RuntimeError)
-            ./features/support/hooks.rb:2:in `After'
-
-        @three
-        Scenario: Yet another Example
-          Given passing
-            boom (RuntimeError)
-            ./features/support/hooks.rb:2:in `After'
-
-        @ignore
-        Scenario: And yet another Example
-
+      Feature: With and without hooks
+      
+        Scenario: using hook    # features/f.feature:2
+        boom (RuntimeError)
+        ./features/support/hooks.rb:2:in `Before'
+          Given this step works # features/step_definitions/steps.rb:1
+      
       Failing Scenarios:
-      cucumber features/tagulicious.feature:4
-      cucumber features/tagulicious.feature:8
-      cucumber features/tagulicious.feature:12
-
-      4 scenarios (3 failed, 1 passed)
-      3 steps (3 undefined)
+      cucumber features/f.feature:2 # Scenario: using hook
+      
+      1 scenario (1 failed)
+      1 step (1 skipped)
 
       """
 
-  Scenario: After hooks ANDing
-    Given a file named "features/support/hooks.rb" with:
-      """
-      After('@one','@three') do
-        raise 'boom'
-      end
-      """
-    When I run `cucumber -q features/tagulicious.feature`
-    Then it should fail with:
-      """
-      Feature: Sample
+    Scenario: omit tagged hook
+      When I run `cucumber features/f.feature:6`
+      Then it should pass with:
+        """
+        Feature: With and without hooks
 
-        @one @three
-        Scenario: Example
-          Given passing
-            boom (RuntimeError)
-            ./features/support/hooks.rb:2:in `After'
+          @no-boom
+          Scenario: omitting hook # features/f.feature:6
+            Given this step works # features/step_definitions/steps.rb:1
 
-        @one
-        Scenario: Another Example
-          Given passing
+        1 scenario (1 passed)
+        1 step (1 passed)
 
-        @three
-        Scenario: Yet another Example
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-
-      Failing Scenarios:
-      cucumber features/tagulicious.feature:4
+        """
 
-      4 scenarios (1 failed, 2 undefined, 1 passed)
-      3 steps (3 undefined)
 
-      """