cucumber 1.2.5 → 1.3.0

data/features/assertions.feature

@@ -26,20 +26,24 @@ Feature: Assertions
     end
     """
 
+  @spawn
   Scenario: Test::Unit
     Given a file named "features/step_definitions/assert_steps.rb" with:
       """
+      require 'test/unit/assertions'
+      World(::Test::Unit::Assertions)
+
       Then /^it should pass$/ do
         assert(2 + 2 == 4)
       end
       """
-    When I run `ruby -r./without_rspec -S cucumber`
+    When I run `cucumber`
     Then it should pass with exactly:
       """
       Feature: Assert
 
         Scenario: Passing     # features/assert.feature:2
-          Then it should pass # features/step_definitions/assert_steps.rb:1
+          Then it should pass # features/step_definitions/assert_steps.rb:4
 
       1 scenario (1 passed)
       1 step (1 passed)

data/features/background.feature

@@ -278,6 +278,7 @@ Feature: Background
 
     """
 
+  @spawn
   Scenario: run a feature with a background that fails
     When I run `cucumber -q features/failing_background.feature`
     Then it should fail with exactly:
@@ -307,6 +308,7 @@ Feature: Background
     
     """
 
+  @spawn
   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:
@@ -364,6 +366,7 @@ Feature: Background
     
     """
 
+  @spawn
   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:

data/features/backtraces.feature

@@ -29,8 +29,8 @@ Feature: Backtraces
 
         Scenario: Example # features/failing_hard.feature:2
           Given failing   # features/step_definitions/steps.rb:4
-            java.lang.UnsupportedOperationException: null (NativeException)
-            java/util/AbstractList.java:131:in `add'
-            java/util/AbstractList.java:91:in `add'
+             (Java::JavaLang::UnsupportedOperationException)
+            java.util.AbstractList.add(AbstractList.java:148)
+            java.util.AbstractList.add(AbstractList.java:108)
       """
 

data/features/before_hook.feature

@@ -0,0 +1,43 @@
+Feature: Before Hook
+
+  Scenario: Examine names of elements
+    Given a file named "features/foo.feature" with:
+      """
+      Feature: Feature name
+
+        Scenario: Scenario name
+          Given a step
+
+        Scenario Outline: Scenario Outline name
+          Given a <placeholder>
+
+          Examples: Examples Table name
+            | <placeholder> |
+            | step          |
+      """
+    And a file named "features/support/hook.rb" with:
+      """
+      names = []
+      Before do |scenario|
+        unless scenario.respond_to?(:scenario_outline)
+          names << scenario.feature.name.split("\n").first
+          names << scenario.name.split("\n").first
+        else
+          names << scenario.scenario_outline.feature.name.split("\n").first
+          names << scenario.scenario_outline.name.split("\n").first
+        end
+        if(names.size == 4)
+          raise "NAMES:\n" + names.join("\n") + "\n"
+        end
+      end
+      """
+    When I run `cucumber`
+    Then the output should contain:
+      """
+            NAMES:
+            Feature name
+            Scenario name
+            Feature name
+            Scenario Outline name
+      """
+

data/features/bootstrap.feature

@@ -8,6 +8,18 @@ Feature: Bootstrapping a new project
     When I run `cucumber`
     Then it should fail with:
       """
-      You don't have a 'features' directory.  Please create one to get started.
-      See http://cukes.info/ for more information.
+      No such file or directory - features. Please create a features directory to get started. (Errno::ENOENT)
       """
+
+ Scenario: does not load ruby files in root if features directory is missing
+  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 it should fail with exactly:
+    """
+    No such file or directory - features. Please create a features directory to get started. (Errno::ENOENT)
+
+    """

data/features/custom_formatter.feature

@@ -32,7 +32,7 @@ Feature: Custom Formatter
         end
       end
       """
-    When I run cucumber "features/f.feature --format Ze::Formator"
+    When I run `cucumber features/f.feature --format Ze::Formator`
     Then it should pass with exactly:
       """
       I'LL USE MY OWN

data/features/drb_server_integration.feature

@@ -1,4 +1,4 @@
-@drb
+@drb @wip-jruby @spawn
 Feature: DRb Server Integration
   To prevent waiting for Rails and other large Ruby applications to load their environments
   for each feature run Cucumber ships with a DRb client that can speak to a server which
@@ -48,7 +48,7 @@ Feature: DRb Server Integration
 
   Scenario: Single feature passing with '-r features' option
     Given I am running spork in the background
-    When I run cucumber "features/sample.feature -r features --tags ~@wip"
+    When I run `cucumber features/sample.feature -r features --tags ~@wip`
     And it should pass with:
     """
     1 step (1 passed)
@@ -56,7 +56,7 @@ Feature: DRb Server Integration
 
   Scenario: Single feature passing without '-r features' option
     Given I am running spork in the background
-    When I run cucumber "features/sample.feature --tags ~@wip"
+    When I run `cucumber features/sample.feature --tags ~@wip`
     And it should pass with:
     """
     1 step (1 passed)

data/features/formatter_callbacks.feature

@@ -22,7 +22,7 @@ Feature: Formatter Callback
       Then /^that|there$/ do
       end
       """
-    When I run cucumber "features/f.feature --format debug"
+    When I run `cucumber features/f.feature --format debug`
     Then it should pass with exactly:
       """
       before_features
@@ -117,7 +117,7 @@ Feature: Formatter Callback
       Then /^that|there$/ do
       end
       """
-    When I run cucumber "features/f.feature --format debug --expand"
+    When I run `cucumber features/f.feature --format debug --expand`
     Then it should pass with exactly:
       """
       before_features

data/features/formatter_step_file_colon_line.feature

@@ -35,7 +35,7 @@ Feature: Formatter API: Step file path and line number (Issue #179)
         end
       end
       """
-    When I run cucumber "features/f.feature --format Jb::Formatter"
+    When I run `cucumber features/f.feature --format Jb::Formatter`
     Then it should pass with exactly:
       """
       step result event: features/f.feature:4

data/features/html_formatter.feature

@@ -12,8 +12,59 @@ Feature: HTML output formatter
           |foo|
           |bar|
       """
+    And a file named "features/scenario_outline_with_pending_step.feature" with:
+      """
+      Feature: Outline
+
+        Scenario Outline: Will it blend?
+          Given this hasn't been implemented yet
+          And other step
+          When I do something with <example>
+          Then I should see something
+          Examples:
+            | example |
+            | one     |
+            | two     |
+            | three   |
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this hasn't been implemented yet$/ do
+        pending
+      end
+      """
 
   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 html --expand "
+    When I run `cucumber features/scenario_outline_with_undefined_steps.feature --format html --expand `
+    Then it should pass
+
+  Scenario Outline: an scenario outline, one pending step
+    When I run `cucumber <file> --format html <flag>`
+    Then it should pass
+    And the output should contain:
+    """
+    makeYellow('scenario_1')
+    """
+    And the output should not contain:
+    """
+    makeRed('scenario_1')
+    """
+    Examples:
+      | file                                                   | flag     |
+      | features/scenario_outline_with_pending_step.feature    | --expand |
+      | features/scenario_outline_with_pending_step.feature    |          |
+      | features/scenario_outline_with_undefined_steps.feature | --expand |
+      | features/scenario_outline_with_undefined_steps.feature |          |
+
+  Scenario: when using a profile the html shouldn't include 'Using the default profile...'
+    And a file named "cucumber.yml" with:
+    """
+      default: -r features
+    """
+    When I run `cucumber --profile default --format html`
     Then it should pass
+    And the output should not contain:
+    """
+    Using the default profile...
+    """
 

data/features/json_formatter.feature

@@ -60,8 +60,10 @@ Feature: JSON output formatter
 
       """
 
+  # Need to investigate why this won't pass in-process. error_message doesn't get det?
+  @spawn
   Scenario: one feature, one passing scenario, one failing scenario
-    When I run cucumber "--format json features/one_passing_one_failing.feature"
+    When I run `cucumber --format json features/one_passing_one_failing.feature`
     Then it should fail with JSON:
       """
       [
@@ -142,12 +144,96 @@ Feature: JSON output formatter
 
       """
 
+  @spawn
+  Scenario: one feature, one passing scenario, one failing scenario with prettyfied json
+    When I run `cucumber --format json_pretty features/one_passing_one_failing.feature`
+    Then it should fail with JSON:
+      """
+      [
+        {
+          "uri": "features/one_passing_one_failing.feature",
+          "keyword": "Feature",
+          "id": "one-passing-scenario,-one-failing-scenario",
+          "name": "One passing scenario, one failing scenario",
+          "line": 2,
+          "description": "",
+          "tags": [
+            {
+              "name": "@a",
+              "line": 1
+            }
+          ],
+          "elements": [
+            {
+              "keyword": "Scenario",
+              "id": "one-passing-scenario,-one-failing-scenario;passing",
+              "name": "Passing",
+              "line": 5,
+              "description": "",
+              "tags": [
+                {
+                  "name": "@b",
+                  "line": 4
+                }
+              ],
+              "type": "scenario",
+              "steps": [
+                {
+                  "keyword": "Given ",
+                  "name": "a passing step",
+                  "line": 6,
+                  "match": {
+                    "location": "features/step_definitions/steps.rb:1"
+                  },
+                  "result": {
+                    "status": "passed",
+                    "duration": 1
+                  }
+                }
+              ]
+            },
+            {
+              "keyword": "Scenario",
+              "id": "one-passing-scenario,-one-failing-scenario;failing",
+              "name": "Failing",
+              "line": 9,
+              "description": "",
+              "tags": [
+                {
+                  "name": "@c",
+                  "line": 8
+                }
+              ],
+              "type": "scenario",
+              "steps": [
+                {
+                  "keyword": "Given ",
+                  "name": "a failing step",
+                  "line": 10,
+                  "match": {
+                    "location": "features/step_definitions/steps.rb:5"
+                  },
+                  "result": {
+                    "status": "failed",
+                    "error_message": " (RuntimeError)\n./features/step_definitions/steps.rb:6:in `/a failing step/'\nfeatures/one_passing_one_failing.feature:10:in `Given a failing step'",
+                    "duration": 1
+                  }
+                }
+              ]
+            }
+          ]
+        }
+      ]
+
+      """
+
+  @spawn
   Scenario: DocString
     Given a file named "features/doc_string.feature" with:
       """
       Feature: A DocString feature
 
-        Scenario: 
+        Scenario:
           Then I should fail with
             \"\"\"
             a string
@@ -159,7 +245,7 @@ Feature: JSON output formatter
         raise s
       end
       """
-    When I run cucumber "--format json features/doc_string.feature"
+    When I run `cucumber --format json features/doc_string.feature`
     Then it should fail with JSON:
       """
       [
@@ -184,8 +270,8 @@ Feature: JSON output formatter
                   "name": "I should fail with",
                   "line": 4,
                   "doc_string": {
-                    "content_type": "", 
-                    "value": "a string", 
+                    "content_type": "",
+                    "value": "a string",
                     "line": 5
                   },
                   "match": {
@@ -203,9 +289,9 @@ Feature: JSON output formatter
         }
       ]
       """
-
+  @wip-jruby
   Scenario: embedding screenshot
-    When I run cucumber "-b --format json features/embed.feature"
+    When I run `cucumber -b --format json features/embed.feature`
     Then it should pass with JSON:
     """
     [

data/features/load_path.feature

@@ -0,0 +1,14 @@
+Feature: Set up a default load path
+
+  Scenario: ./lib is included in the $LOAD_PATH
+    Given a file named "features/support/env.rb" with:
+      """
+      require 'something'
+      """
+    And a file named "lib/something.rb" with:
+      """
+      class Something
+      end
+      """
+    When I run `cucumber`
+    Then it should pass

data/features/nested_steps.feature

@@ -49,12 +49,84 @@ Feature: Nested Steps
 
       """
 
-  Scenario: Use deprecated i18n methods
+  Scenario: Use #steps to call a table
+    Given a step definition that looks like this:
+      """ruby
+      Given /turtles:/ do |table|
+        table.hashes.each do |row|
+          puts row[:name]
+        end
+      end
+      """
+    And a step definition that looks like this:
+      """ruby
+      Given /two turtles/ do
+        steps %{
+          Given turtles:
+            | name      |
+            | Sturm     |
+            | Liouville |
+        }
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      Sturm
+
+      Liouville
+
+      """
+
+  Scenario: Use #steps to call a multi-line string
+    Given a step definition that looks like this:
+      """ruby
+        Given /two turtles/ do
+          steps %Q{
+            Given turtles:
+               \"\"\"
+               Sturm
+               Liouville
+               \"\"\"
+          }
+        end
+      """
+    And a step definition that looks like this:
+      """ruby
+      Given /turtles:/ do |string|
+        puts string
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      Sturm
+      Liouville
+      """
+
+  @spawn
+  Scenario: Backtrace doesn't skip nested steps
     Given a step definition that looks like this:
       """ruby
       Given /two turtles/ do
-        Given "a turtle"
+        step "I have a couple turtles"
+      end
+
+      When /I have a couple turtles/ do
+        raise 'error'
       end
       """
     When I run the feature with the progress formatter
-    Then the output should contain "WARNING"
+    Then it should fail with:
+      """
+      error (RuntimeError)
+      ./features/step_definitions/test_steps2.rb:6:in `/I have a couple turtles/'
+      ./features/step_definitions/test_steps2.rb:2:in `/two turtles/'
+      features/test_feature_1.feature:3:in `Given two turtles'
+
+      Failing Scenarios:
+      cucumber features/test_feature_1.feature:2 # Scenario: Test Scenario 1
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+      """