cucumber 1.3.20 → 2.0.0.beta.1

data/features/{custom_formatter.feature → docs/extending_cucumber/custom_formatter.feature}

@@ -6,19 +6,14 @@ Feature: Custom Formatter
       Feature: I'll use my own
         because I'm worth it
         Scenario: just print me
-          Given this step works
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^this step works$/ do
-      end
+          Given this step passes
       """
+    And the standard step definitions
     And a file named "features/support/ze/formator.rb" with:
       """
       module Ze
         class Formator
-          def initialize(step_mother, io, options)
-            @step_mother = step_mother
+          def initialize(runtime, io, options)
             @io = io
           end
 

data/features/{formatter_callbacks.feature → docs/extending_cucumber/formatter_callbacks.feature}

@@ -17,10 +17,8 @@ Feature: Formatter Callback
       """
     And a file named "features/step_definitions/steps.rb" with:
       """
-      Given /^.+ step works$/ do
-      end
-      Then /^that|there$/ do
-      end
+      Given(/^.+ step works$/) { }
+      Then(/^that|there$/)     { }
       """
     When I run `cucumber features/f.feature --format debug`
     Then it should pass with exactly:
@@ -95,6 +93,7 @@ Feature: Formatter Callback
 
       """
 
+
   Scenario: callback if expanded
     Given a file named "features/f.feature" with:
       """
@@ -187,3 +186,185 @@ Feature: Formatter Callback
       after_features
 
       """
+
+  Scenario: callback with background if not expanded
+    Given a file named "features/f.feature" with:
+      """
+      Feature: I'll use my own
+        because I'm worth it
+        Background:
+          Given this step works
+        Scenario Outline: outline
+          Given <x> step works
+          Then <y>
+          Examples:
+          |x|y|
+          |this|that|
+          |here|there|
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given(/^.+ step works$/) { }
+      Then(/^that|there$/)     { }
+      """
+    When I run `cucumber features/f.feature --format debug`
+    Then it should pass with exactly:
+      """
+      before_features
+        before_feature
+          before_tags
+          after_tags
+          feature_name
+          before_background
+            background_name
+            before_steps
+              before_step
+                before_step_result
+                  step_name
+                after_step_result
+              after_step
+            after_steps
+          after_background
+          before_feature_element
+            before_tags
+            after_tags
+            scenario_name
+            before_steps
+              before_step
+                before_step_result
+                  step_name
+                after_step_result
+              after_step
+              before_step
+                before_step_result
+                  step_name
+                after_step_result
+              after_step
+            after_steps
+            before_examples_array
+              before_examples
+                examples_name
+                before_outline_table
+                  before_table_row
+                    before_table_cell
+                      table_cell_value
+                    after_table_cell
+                    before_table_cell
+                      table_cell_value
+                    after_table_cell
+                  after_table_row
+                  before_table_row
+                    before_table_cell
+                      table_cell_value
+                    after_table_cell
+                    before_table_cell
+                      table_cell_value
+                    after_table_cell
+                  after_table_row
+                  before_table_row
+                    before_table_cell
+                      table_cell_value
+                    after_table_cell
+                    before_table_cell
+                      table_cell_value
+                    after_table_cell
+                  after_table_row
+                after_outline_table
+              after_examples
+            after_examples_array
+          after_feature_element
+        after_feature
+      after_features
+
+      """
+
+  Scenario: callback with background if expanded
+    Given a file named "features/f.feature" with:
+      """
+      Feature: I'll use my own
+        because I'm worth it
+        Background:
+          Given this step works
+        Scenario Outline: outline
+          Given <x> step works
+          Then <y>
+          Examples:
+          |x|y|
+          |this|that|
+          |here|there|
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^.+ step works$/ do
+      end
+      Then /^that|there$/ do
+      end
+      """
+    When I run `cucumber features/f.feature --format debug --expand`
+    Then it should pass with exactly:
+      """
+      before_features
+        before_feature
+          before_tags
+          after_tags
+          feature_name
+          before_background
+            background_name
+            before_steps
+              before_step
+                before_step_result
+                  step_name
+                after_step_result
+              after_step
+            after_steps
+          after_background
+          before_feature_element
+            before_tags
+            after_tags
+            scenario_name
+            before_steps
+              before_step
+                before_step_result
+                  step_name
+                after_step_result
+              after_step
+              before_step
+                before_step_result
+                  step_name
+                after_step_result
+              after_step
+            after_steps
+            before_examples_array
+              before_examples
+                examples_name
+                before_outline_table
+                  scenario_name
+                  before_step
+                    before_step_result
+                      step_name
+                    after_step_result
+                  after_step
+                  before_step
+                    before_step_result
+                      step_name
+                    after_step_result
+                  after_step
+                  scenario_name
+                  before_step
+                    before_step_result
+                      step_name
+                    after_step_result
+                  after_step
+                  before_step
+                    before_step_result
+                      step_name
+                    after_step_result
+                  after_step
+                after_outline_table
+              after_examples
+            after_examples_array
+          after_feature_element
+        after_feature
+      after_features
+
+      """

data/{legacy_features/listener_debugger_formatter.feature → features/docs/formatters/debug_formatter.feature}

@@ -1,23 +1,22 @@
-Feature: Listener Debugger
-  In order to easily visualise the listener API
-  As a developer
-  I want a formatter that prints the calls to the listener as a feature is run
+Feature: Debug formatter
+
+  In order to help you easily visualise the listener API, you can use
+  the `debug` formatter that prints the calls to the listener as a
+  feature is run.
 
   Background:
-    Given a standard Cucumber project directory structure
+    Given the standard step definitions
 
   Scenario: title
-    Given a file named "features/sample.feature" with:
+    Given a file named "features/test.feature" with:
       """
-      Feature: Sample
-
-        Scenario: Sample
-          Given Sample
-
+      Feature:
+        Scenario:
+          Given this step passes
       """
-    When I run cucumber -f debug features/sample.feature
-    Then STDERR should be empty
-    Then it should pass with
+    When I run `cucumber -f debug`
+    Then the stderr should not contain anything
+    Then it should pass with:
       """
       before_features
         before_feature
@@ -38,5 +37,4 @@ Feature: Listener Debugger
           after_feature_element
         after_feature
       after_features
-
       """

data/features/{formatter_step_file_colon_line.feature → docs/formatters/formatter_step_file_colon_line.feature}

@@ -13,15 +13,13 @@ Feature: Formatter API: Step file path and line number (Issue #179)
       """
     And a file named "features/step_definitions/steps.rb" with:
       """
-      Given /^step at line (.*)$/ do |line|
-      end
+      Given(/^step at line (.*)$/) {|line| }
       """
     And a file named "features/support/jb/formatter.rb" with:
       """
       module Jb
         class Formatter
-          def initialize(step_mother, io, options)
-            @step_mother = step_mother
+          def initialize(runtime, io, options)
             @io = io
           end
 

data/features/{html_formatter.feature → docs/formatters/html_formatter.feature}

@@ -1,13 +1,14 @@
 Feature: HTML output formatter
 
   Background:
-    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
+    Given the standard step definitions
+    And a file named "features/scenario_outline_with_undefined_steps.feature" with:
       """
       Feature:
 
         Scenario Outline:
-          Given an undefined step
-        
+          Given this step is undefined
+
         Examples:
           |foo|
           |bar|
@@ -17,7 +18,7 @@ Feature: HTML output formatter
       Feature: Outline
 
         Scenario Outline: Will it blend?
-          Given this hasn't been implemented yet
+          Given this step is pending
           And other step
           When I do something with <example>
           Then I should see something
@@ -32,21 +33,12 @@ Feature: HTML output formatter
       Feature: Feature with failing background step
 
         Background:
-          Given this fails
+          Given this step fails
 
         Scenario:
           When I do something
           Then I should see something
       """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^this fails$/ do
-        fail 'This step should fail'
-      end
-      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 `
@@ -63,10 +55,14 @@ Feature: HTML output formatter
     """
     makeRed('scenario_1')
     """
+
     Examples:
       | file                                                   | flag     |
       | features/scenario_outline_with_pending_step.feature    | --expand |
       | features/scenario_outline_with_pending_step.feature    |          |
+
+    Examples:
+      | file                                                   | flag     |
       | features/scenario_outline_with_undefined_steps.feature | --expand |
       | features/scenario_outline_with_undefined_steps.feature |          |
 

data/features/{json_formatter.feature → docs/formatters/json_formatter.feature}

@@ -3,49 +3,22 @@ Feature: JSON output formatter
   Developers should be able to consume features as JSON
 
   Background:
-    Given a file named "features/one_passing_one_failing.feature" with:
+    Given the standard step definitions
+    And a file named "features/one_passing_one_failing.feature" with:
       """
       @a
       Feature: One passing scenario, one failing scenario
 
         @b
         Scenario: Passing
-          Given a passing step
+          Given this step passes
 
         @c
         Scenario: Failing
-          Given a failing step
+          Given this step fails
       """
-    And a file named "features/step_definitions/steps.rb" with:
+    And a file named "features/step_definitions/json_steps.rb" with:
       """
-      Given /a passing step/ do
-        #does nothing
-      end
-
-      Given /a failing step/ do
-        fail
-      end
-
-      Given /a pending step/ do
-        pending
-      end
-
-      Given /^I add (\d+) and (\d+)$/ do |a,b|
-        @result = a.to_i + b.to_i
-      end
-
-      Then /^I the result should be (\d+)$/ do |c|
-        @result.should == c.to_i
-      end
-
-      Then /^I should see/ do |string|
-
-      end
-
-      Given /^I pass a table argument/ do |table|
-
-      end
-
       Given /^I embed a screenshot/ do
         File.open("screenshot.png", "w") { |file| file << "foo" }
         embed "screenshot.png", "image/png"
@@ -54,11 +27,6 @@ Feature: JSON output formatter
       Given /^I print from step definition/ do
         puts "from step definition"
       end
-
-      Given /^I embed data directly/ do
-        data = "YWJj"
-        embed data, "mime-type;base64"
-      end
       """
     And a file named "features/embed.feature" with:
       """
@@ -67,47 +35,39 @@ Feature: JSON output formatter
         Scenario:
           Given I embed a screenshot
 
-      """
-    And a file named "features/print_from_step_definition.feature" with:
-      """
-      Feature: A print from step definition feature
-
-        Scenario:
-          Given I print from step definition
-          And I print from step definition
-
       """
     And a file named "features/outline.feature" with:
       """
       Feature: An outline feature
 
         Scenario Outline: outline
-          Given a <type> step
+          Given this step <status>
 
           Examples: examples1
-            |  type   |
-            | passing |
-            | failing |
+            | status |
+            | passes |
+            | fails  |
 
           Examples: examples2
-            |  type   |
-            | passing |
-
+            | status |
+            | passes |
       """
-    And a file named "features/embed_data_directly.feature" with:
+    And a file named "features/print_from_step_definition.feature" with:
       """
-      Feature: An embed data directly feature
+      Feature: A print from step definition feature
 
-        Scenario Outline:
-          Given I embed data directly
+        Scenario:
+          Given I print from step definition
+          And I print from step definition
 
-	  Examples:
-	  | dummy |
-	  |   1   |
-	  |   2   |
+      """
+    And a file named "features/print_from_step_definition.feature" with:
+      """
+      Feature: A print from step definition feature
 
         Scenario:
-          Given I embed data directly
+          Given I print from step definition
+          And I print from step definition
 
       """
 
@@ -148,7 +108,7 @@ Feature: JSON output formatter
               "steps": [
                 {
                   "keyword": "Given ",
-                  "name": "a passing step",
+                  "name": "this step passes",
                   "line": 6,
                   "match": {
                     "location": "features/step_definitions/steps.rb:1"
@@ -176,14 +136,14 @@ Feature: JSON output formatter
               "steps": [
                 {
                   "keyword": "Given ",
-                  "name": "a failing step",
+                  "name": "this step fails",
                   "line": 10,
                   "match": {
-                    "location": "features/step_definitions/steps.rb:5"
+                    "location": "features/step_definitions/steps.rb:4"
                   },
                   "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'",
+                    "error_message": " (RuntimeError)\n./features/step_definitions/steps.rb:4:in `/^this step fails$/'\nfeatures/one_passing_one_failing.feature:10:in `Given this step fails'",
                     "duration": 1
                   }
                 }
@@ -231,7 +191,7 @@ Feature: JSON output formatter
               "steps": [
                 {
                   "keyword": "Given ",
-                  "name": "a passing step",
+                  "name": "this step passes",
                   "line": 6,
                   "match": {
                     "location": "features/step_definitions/steps.rb:1"
@@ -259,14 +219,14 @@ Feature: JSON output formatter
               "steps": [
                 {
                   "keyword": "Given ",
-                  "name": "a failing step",
+                  "name": "this step fails",
                   "line": 10,
                   "match": {
-                    "location": "features/step_definitions/steps.rb:5"
+                    "location": "features/step_definitions/steps.rb:4"
                   },
                   "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'",
+                    "error_message": " (RuntimeError)\n./features/step_definitions/steps.rb:4:in `/^this step fails$/'\nfeatures/one_passing_one_failing.feature:10:in `Given this step fails'",
                     "duration": 1
                   }
                 }
@@ -278,7 +238,7 @@ Feature: JSON output formatter
 
       """
 
-  @spawn
+  @spawn @wip-jruby
   Scenario: DocString
     Given a file named "features/doc_string.feature" with:
       """
@@ -290,7 +250,7 @@ Feature: JSON output formatter
             a string
             \"\"\"
       """
-    And a file named "features/step_definitions/doc_string_steps.rb" with:
+    And a file named "features/step_definitions/steps.rb" with:
       """
       Then /I should fail with/ do |s|
         raise s
@@ -326,11 +286,11 @@ Feature: JSON output formatter
                     "line": 5
                   },
                   "match": {
-                    "location": "features/step_definitions/doc_string_steps.rb:1"
+                    "location": "features/step_definitions/steps.rb:1"
                   },
                   "result": {
                     "status": "failed",
-                    "error_message": "a string (RuntimeError)\n./features/step_definitions/doc_string_steps.rb:2:in `/I should fail with/'\nfeatures/doc_string.feature:4:in `Then I should fail with'",
+                    "error_message": "a string (RuntimeError)\n./features/step_definitions/steps.rb:2:in `/I should fail with/'\nfeatures/doc_string.feature:4:in `Then I should fail with'",
                     "duration": 1
                   }
                 }
@@ -340,6 +300,8 @@ Feature: JSON output formatter
         }
       ]
       """
+
+  @spawn 
   Scenario: embedding screenshot
     When I run `cucumber -b --format json features/embed.feature`
     Then it should pass with JSON:
@@ -372,7 +334,7 @@ Feature: JSON output formatter
                   }
                 ],
                 "match": {
-                  "location": "features/step_definitions/steps.rb:29"
+                  "location": "features/step_definitions/json_steps.rb:1"
                 },
                 "result": {
                   "status": "passed",
@@ -386,167 +348,7 @@ Feature: JSON output formatter
     ]
 
     """
-  Scenario: print from step definition
-    When I run `cucumber --format json features/print_from_step_definition.feature`
-    Then it should pass with JSON:
-    """
-    [
-      {
-        "uri": "features/print_from_step_definition.feature",
-        "id": "a-print-from-step-definition-feature",
-        "keyword": "Feature",
-        "name": "A print from step definition feature",
-        "line": 1,
-        "description": "",
-        "elements": [
-          {
-            "id": "a-print-from-step-definition-feature;",
-            "keyword": "Scenario",
-            "name": "",
-            "line": 3,
-            "description": "",
-            "type": "scenario",
-            "steps": [
-              {
-                "keyword": "Given ",
-                "name": "I print from step definition",
-                "line": 4,
-                "output": [
-		  "from step definition"
-                ],
-                "match": {
-                  "location": "features/step_definitions/steps.rb:34"
-                },
-                "result": {
-                  "status": "passed",
-                  "duration": 1
-                }
-              },
-              {
-                "keyword": "And ",
-                "name": "I print from step definition",
-                "line": 5,
-                "output": [
-		  "from step definition"
-                ],
-                "match": {
-                  "location": "features/step_definitions/steps.rb:34"
-                },
-                "result": {
-                  "status": "passed",
-                  "duration": 1
-                }
-              }
-            ]
-          }
-        ]
-      }
-    ]
-
-    """
-  Scenario: embedding data directly
-    When I run `cucumber -b --format json -x features/embed_data_directly.feature`
-    Then it should pass with JSON:
-    """
-    [
-      {
-        "uri": "features/embed_data_directly.feature",
-        "id": "an-embed-data-directly-feature",
-        "keyword": "Feature",
-        "name": "An embed data directly feature",
-        "line": 1,
-        "description": "",
-        "elements": [
-          {
-            "keyword": "Scenario Outline",
-            "name": "",
-            "line": 8,
-            "description": "",
-            "id": "an-embed-data-directly-feature;;;2",
-            "type": "scenario",
-            "steps": [
-              {
-                "keyword": "Given ",
-                "name": "I embed data directly",
-                "line": 4,
-                "embeddings": [
-                  {
-                    "mime_type": "mime-type",
-                    "data": "YWJj"
-                  }
-                ],
-                "match": {
-                  "location": "features/step_definitions/steps.rb:38"
-                },
-                "result": {
-                  "status": "passed",
-                  "duration": 1
-                }
-              }
-            ]
-          },
-          {
-            "keyword": "Scenario Outline",
-            "name": "",
-            "line": 9,
-            "description": "",
-            "id": "an-embed-data-directly-feature;;;3",
-            "type": "scenario",
-            "steps": [
-              {
-                "keyword": "Given ",
-                "name": "I embed data directly",
-                "line": 4,
-                "embeddings": [
-                  {
-                    "mime_type": "mime-type",
-                    "data": "YWJj"
-                  }
-                ],
-                "match": {
-                  "location": "features/step_definitions/steps.rb:38"
-                },
-                "result": {
-                  "status": "passed",
-                  "duration": 1
-                }
-              }
-            ]
-	  },
-          {
-            "id": "an-embed-data-directly-feature;",
-            "keyword": "Scenario",
-            "name": "",
-            "line": 11,
-            "description": "",
-            "type": "scenario",
-            "steps": [
-              {
-                "keyword": "Given ",
-                "name": "I embed data directly",
-                "line": 12,
-                "embeddings": [
-                  {
-		    "mime_type": "mime-type",
-		    "data": "YWJj"
-                  }
-                ],
-                "match": {
-                  "location": "features/step_definitions/steps.rb:38"
-                },
-                "result": {
-                  "status": "passed",
-                  "duration": 1
-                }
-              }
-            ]
-          }
-        ]
-      }
-    ]
 
-    """
-  @spawn
   Scenario: scenario outline
     When I run `cucumber --format json features/outline.feature`
     Then it should fail with JSON:
@@ -570,10 +372,10 @@ Feature: JSON output formatter
             "steps": [
               {
                 "keyword": "Given ",
-                "name": "a <type> step",
+                "name": "this step <status>",
                 "line": 4,
                 "match": {
-                  "location": "features/step_definitions/steps.rb:1"
+                  "location": "features/outline.feature:4"
                 }
               }
             ],
@@ -587,21 +389,21 @@ Feature: JSON output formatter
                 "rows": [
                   {
                     "cells": [
-                      "type"
+                      "status"
                      ], 
                      "line": 7, 
                      "id": "an-outline-feature;outline;examples1;1"
                   }, 
                   {
                     "cells": [
-                      "passing"
+                      "passes"
                     ], 
                     "line": 8, 
                     "id": "an-outline-feature;outline;examples1;2"
                   }, 
                   {
                     "cells": [
-                      "failing"
+                      "fails"
                     ], 
                     "line": 9, 
                     "id": "an-outline-feature;outline;examples1;3"
@@ -617,14 +419,14 @@ Feature: JSON output formatter
                 "rows": [
                   {
                     "cells": [
-                      "type"
+                      "status"
                      ], 
                      "line": 12, 
                      "id": "an-outline-feature;outline;examples2;1"
                   }, 
                   {
                     "cells": [
-                      "passing"
+                      "passes"
                     ], 
                     "line": 13, 
                     "id": "an-outline-feature;outline;examples2;2"
@@ -638,6 +440,66 @@ Feature: JSON output formatter
     ]
 
     """
+
+  Scenario: print from step definition
+    When I run `cucumber --format json features/print_from_step_definition.feature`
+    Then it should pass with JSON:
+    """
+    [
+      {
+        "uri": "features/print_from_step_definition.feature",
+        "id": "a-print-from-step-definition-feature",
+        "keyword": "Feature",
+        "name": "A print from step definition feature",
+        "line": 1,
+        "description": "",
+        "elements": [
+          {
+            "id": "a-print-from-step-definition-feature;",
+            "keyword": "Scenario",
+            "name": "",
+            "line": 3,
+            "description": "",
+            "type": "scenario",
+            "steps": [
+              {
+                "keyword": "Given ",
+                "name": "I print from step definition",
+                "line": 4,
+                "output": [
+                  "from step definition"
+                ],
+                "match": {
+                  "location": "features/step_definitions/json_steps.rb:6"
+                },
+                "result": {
+                  "status": "passed",
+                  "duration": 1
+                }
+              },
+              {
+                "keyword": "And ",
+                "name": "I print from step definition",
+                "line": 5,
+                "output": [
+                  "from step definition"
+                ],
+                "match": {
+                  "location": "features/step_definitions/json_steps.rb:6"
+                },
+                "result": {
+                  "status": "passed",
+                  "duration": 1
+                }
+              }
+            ]
+          }
+        ]
+      }
+    ]
+
+    """
+
   @spawn
   Scenario: scenario outline expanded
     When I run `cucumber --expand --format json features/outline.feature`
@@ -662,7 +524,7 @@ Feature: JSON output formatter
             "steps": [
               {
                 "keyword": "Given ",
-                "name": "a passing step",
+                "name": "this step passes",
                 "line": 4,
                 "match": {
                   "location": "features/step_definitions/steps.rb:1"
@@ -684,14 +546,14 @@ Feature: JSON output formatter
             "steps": [
               {
                 "keyword": "Given ",
-                "name": "a failing step",
+                "name": "this step fails",
                 "line": 4,
                 "match": {
-                  "location": "features/step_definitions/steps.rb:5"
+                  "location": "features/step_definitions/steps.rb:4"
                 },
                 "result": {
                   "status": "failed",
-                  "error_message" : " (RuntimeError)\n./features/step_definitions/steps.rb:6:in `/a failing step/'\nfeatures/outline.feature:4:in `Given a <type> step'",
+                  "error_message" : " (RuntimeError)\n./features/step_definitions/steps.rb:4:in `/^this step fails$/'\nfeatures/outline.feature:4:in `Given this step <status>'",
 		  "duration": 1
                 }
               }
@@ -707,7 +569,7 @@ Feature: JSON output formatter
             "steps": [
               {
                 "keyword": "Given ",
-                "name": "a passing step",
+                "name": "this step passes",
                 "line": 4,
                 "match": {
                   "location": "features/step_definitions/steps.rb:1"