cucumber 2.0.0 → 2.0.1

data/README.md

@@ -1,7 +1,8 @@
-[![Build Status](https://secure.travis-ci.org/cucumber/cucumber.png)](http://travis-ci.org/cucumber/cucumber) [![Code Climate](https://codeclimate.com/github/cucumber/cucumber.png)](https://codeclimate.com/github/cucumber/cucumber) [![Coverage Status](https://coveralls.io/repos/cucumber/cucumber/badge.png?branch=master)](https://coveralls.io/r/cucumber/cucumber?branch=master) [![Dependency Status](https://gemnasium.com/cucumber/cucumber.png)](https://gemnasium.com/cucumber/cucumber)
+[![Join the chat at https://gitter.im/cucumber/cucumber-ruby](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/cucumber/cucumber-ruby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![Build Status](https://secure.travis-ci.org/cucumber/cucumber-ruby.png)](http://travis-ci.org/cucumber/cucumber-ruby) [![Code Climate](https://codeclimate.com/github/cucumber/cucumber-ruby.png)](https://codeclimate.com/github/cucumber/cucumber-ruby) [![Coverage Status](https://coveralls.io/repos/cucumber/cucumber-ruby/badge.png?branch=master)](https://coveralls.io/r/cucumber/cucumber-ruby?branch=master) [![Dependency Status](https://gemnasium.com/cucumber/cucumber-ruby.png)](https://gemnasium.com/cucumber/cucumber-ruby)
 
 # Cucumber
 
+
 Cucumber is a tool for running automated tests written in plain language. Because they're
 written in plain language, they can be read by anyone on your team. Because they can be 
 read by anyone, you can use them to help improve communication, collaboration and trust on
@@ -9,14 +10,15 @@ your team.
 
 Where to get more info:
 
-  * The main website: http://cukes.info/
-  * Documentation: https://wiki.github.com/cucumber/cucumber/
-  * API Documentation: http://cukes.info/api/cucumber/ruby/yardoc/
-  * Support forum: https://groups.google.com/forum/?fromgroups#!forum/cukes
-  * IRC channel: irc://irc.freenode.net/cucumber
+  * The main website: https://cucumber.io/
+  * Documentation: https://github.com/cucumber/cucumber/wiki
+  * Ruby API Documentation: http://www.rubydoc.info/github/cucumber/cucumber/
+  * Support forum: https://groups.google.com/group/cukes
+  * Developer chat: https://gitter.im/cucumber/cucumber-ruby
+  * IRC channel: [irc://irc.freenode.net/cucumber](irc://irc.freenode.net/cucumber)
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for info on contributing to Cucumber.
 
 ## Copyright
 
-Copyright (c) 2008-2013 Aslak Hellesøy and Contributors. See LICENSE for details.
+Copyright (c) 2008-2015 Aslak Hellesøy and Contributors. See LICENSE for details.

data/cucumber.gemspec

@@ -5,7 +5,7 @@ require "cucumber/platform"
 Gem::Specification.new do |s|
   s.name        = 'cucumber'
   s.version     = Cucumber::VERSION
-  s.authors     = ["Aslak Hellesøy"]
+  s.authors     = ["Aslak Hellesøy", "Matt Wynne", "Steve Tooke"]
   s.description = 'Behaviour Driven Development with elegance and joy'
   s.summary     = "cucumber-#{s.version}"
   s.email       = 'cukes@googlegroups.com'
@@ -14,7 +14,7 @@ Gem::Specification.new do |s|
   s.platform    = Gem::Platform::RUBY
   s.required_ruby_version = ">= 1.9.3"
 
-  s.add_dependency 'cucumber-core', '~> 1.1.3'
+  s.add_dependency 'cucumber-core', '~> 1.2.0'
   s.add_dependency 'builder', '>= 2.1.2'
   s.add_dependency 'diff-lcs', '>= 1.1.3'
   s.add_dependency 'gherkin', '~> 2.12'

data/features/docs/cli/dry_run.feature

@@ -23,7 +23,6 @@ Feature: Dry Run
 
       1 scenario (1 skipped)
       1 step (1 skipped)
-      0m0.012s
 
       """
 
@@ -45,7 +44,6 @@ Feature: Dry Run
 
       1 scenario (1 skipped)
       1 step (1 skipped)
-      0m0.012s
 
       """
 
@@ -68,6 +66,5 @@ Feature: Dry Run
 
       1 scenario (1 undefined)
       1 step (1 undefined)
-      0m0.012s
 
       """

data/features/docs/cli/finding_steps.feature

@@ -0,0 +1,28 @@
+Feature: Loading the steps users expect
+  As a User
+  In order to run features in subdirectories without having to pass extra options
+  I want cucumber to load all step files
+
+  Scenario:
+    Given a file named "features/nesting/test.feature" with:
+      """
+      Feature: Feature in Subdirectory
+        Scenario: A step not in the subdirectory
+          Given not found in subdirectory
+      """
+    And a file named "features/step_definitions/steps_no_in_subdirectory.rb" with:
+      """
+      Given(/^not found in subdirectory$/) { }
+      """
+    When I run `cucumber -q features/nesting/test.feature`
+    Then it should pass with:
+      """
+      Feature: Feature in Subdirectory
+
+        Scenario: A step not in the subdirectory
+          Given not found in subdirectory
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+      """
+

data/features/docs/cli/run_specific_scenarios.feature

@@ -24,7 +24,7 @@ Feature: Run specific scenarios
           Given this step passes
       """
     When I run `cucumber features/test.feature:7 --format pretty --quiet`
-    Then it should pass with:
+    Then it should pass with exactly:
       """
       Feature: 
 
@@ -32,6 +32,8 @@ Feature: Run specific scenarios
           Given this step passes
 
       1 scenario (1 passed)
+      1 step (1 passed)
+      
       """
 
   Scenario: Use @-notation to specify a file containing feature file list

data/features/docs/cli/specifying_multiple_formatters.feature

@@ -3,8 +3,9 @@ Feature: Running multiple formatters
 
   When running cucumber, you are able to using multiple different
   formatters and redirect the output to text files.
+  Two formatters cannot both print to the same file (or to STDOUT)
 
-  Scenario: Multiple formatters and outputs
+  Background:
     Given a file named "features/test.feature" with:
     """
     Feature: Lots of undefined
@@ -16,6 +17,8 @@ Feature: Running multiple formatters
         When I stop procrastinating
         And there is world peace
     """
+
+  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
     Then the file "progress.txt" should contain:
@@ -42,3 +45,21 @@ Feature: Running multiple formatters
 
       """
 
+  Scenario: Two formatters to stdout
+    When I run `cucumber -f progress -f pretty features/test.feature`
+    Then it should fail with:
+      """
+      All but one formatter must use --out, only one can print to each stream (or STDOUT) (RuntimeError)
+      """
+
+  Scenario: Two formatters to stdout when using a profile
+    Given the following profiles are defined:
+      """
+      default: -q
+      """
+    When I run `cucumber -f progress -f pretty features/test.feature`
+    Then it should fail with:
+      """
+      All but one formatter must use --out, only one can print to each stream (or STDOUT) (RuntimeError)
+      """
+

data/features/docs/defining_steps/nested_steps.feature

@@ -173,6 +173,5 @@ Feature: Nested Steps
 
       2 scenarios (2 failed)
       2 steps (2 failed)
-      0m0.012s
 
       """

data/features/docs/defining_steps/printing_messages.feature

@@ -137,12 +137,12 @@ Feature: Pretty formatter - Printing messages
         Announce
         
         Me
-        ..-UUUUUU
+        ..UUU
         Announce with fail
-        F--
+        F-
         Line: 1: anno1
-        FFF
+        F
         Line: 2: anno2
-        ...
+        .
         """
 

data/features/docs/defining_steps/skip_scenario.feature

@@ -26,7 +26,6 @@ Feature: Skip Scenario
 
       1 scenario (1 skipped)
       2 steps (2 skipped)
-      0m0.012s
 
       """
 
@@ -56,7 +55,6 @@ Feature: Skip Scenario
 
       1 scenario (1 skipped)
       2 steps (2 skipped)
-      0m0.012s
 
       """
 

data/features/docs/exception_in_around_hook.feature

@@ -41,8 +41,7 @@ Feature: Exceptions in Around Hooks
       
       1 scenario (1 failed)
       0 steps
-      0m0.012s
-
+      
       """
 
   Scenario: Exception after the test case is run
@@ -75,6 +74,5 @@ Feature: Exceptions in Around Hooks
       
       1 scenario (1 failed)
       1 step (1 passed)
-      0m0.012s
 
       """

data/features/docs/formatters/html_formatter.feature

@@ -88,3 +88,4 @@ Feature: HTML output formatter
     """
     makeRed('background_0')
     """
+

data/features/docs/formatters/json_formatter.feature

@@ -131,6 +131,10 @@ Feature: JSON output formatter
               "line": 5,
               "description": "",
               "tags": [
+                {
+                  "name": "@a",
+                  "line": 1
+                },
                 {
                   "name": "@b",
                   "line": 4
@@ -159,6 +163,10 @@ Feature: JSON output formatter
               "line": 9,
               "description": "",
               "tags": [
+                {
+                  "name": "@a",
+                  "line": 1
+                },
                 {
                   "name": "@c",
                   "line": 8
@@ -214,6 +222,10 @@ Feature: JSON output formatter
               "line": 5,
               "description": "",
               "tags": [
+                {
+                  "name": "@a",
+                  "line": 1
+                },
                 {
                   "name": "@b",
                   "line": 4
@@ -242,6 +254,10 @@ Feature: JSON output formatter
               "line": 9,
               "description": "",
               "tags": [
+                {
+                  "name": "@a",
+                  "line": 1
+                },
                 {
                   "name": "@c",
                   "line": 8
@@ -270,7 +286,7 @@ Feature: JSON output formatter
 
       """
 
-  @spawn @wip-jruby
+  @spawn
   Scenario: DocString
     Given a file named "features/doc_string.feature" with:
       """
@@ -285,7 +301,7 @@ Feature: JSON output formatter
     And a file named "features/step_definitions/steps.rb" with:
       """
       Then /I should fail with/ do |s|
-        raise s
+        raise RuntimeError, s
       end
       """
     When I run `cucumber --format json features/doc_string.feature`
@@ -333,7 +349,7 @@ Feature: JSON output formatter
       ]
       """
 
-  @spawn 
+  @spawn
   Scenario: embedding screenshot
     When I run `cucumber -b --format json features/embed.feature`
     Then it should pass with JSON:
@@ -381,6 +397,7 @@ Feature: JSON output formatter
 
     """
 
+  @spawn
   Scenario: scenario outline
     When I run `cucumber --format json features/outline.feature`
     Then it should fail with JSON:
@@ -395,75 +412,69 @@ Feature: JSON output formatter
         "description": "",
         "elements": [
           {
-            "id": "an-outline-feature;outline",
+            "id": "an-outline-feature;outline;examples1;2",
             "keyword": "Scenario Outline",
             "name": "outline",
-            "line": 3,
             "description": "",
-            "type": "scenario_outline",
+            "line": 8,
+            "type": "scenario",
             "steps": [
               {
                 "keyword": "Given ",
-                "name": "this step <status>",
-                "line": 4,
+                "name": "this step passes",
+                "line": 8,
                 "match": {
-                  "location": "features/outline.feature:4"
+                  "location": "features/step_definitions/steps.rb:1"
+                },
+                "result": {
+                  "status": "passed",
+                  "duration": 1
                 }
               }
-            ],
-            "examples": [
+            ]
+          },
+          {
+            "id": "an-outline-feature;outline;examples1;3",
+            "keyword": "Scenario Outline",
+            "name": "outline",
+            "description": "",
+            "line": 9,
+            "type": "scenario",
+            "steps": [
               {
-                "keyword": "Examples", 
-                "name": "examples1", 
-                "line": 6, 
-                "description": "", 
-                "id": "an-outline-feature;outline;examples1", 
-                "rows": [
-                  {
-                    "cells": [
-                      "status"
-                     ], 
-                     "line": 7, 
-                     "id": "an-outline-feature;outline;examples1;1"
-                  }, 
-                  {
-                    "cells": [
-                      "passes"
-                    ], 
-                    "line": 8, 
-                    "id": "an-outline-feature;outline;examples1;2"
-                  }, 
-                  {
-                    "cells": [
-                      "fails"
-                    ], 
-                    "line": 9, 
-                    "id": "an-outline-feature;outline;examples1;3"
-                  }
-                ]
-              },
+                "keyword": "Given ",
+                "name": "this step fails",
+                "line": 9,
+                "match": {
+                  "location": "features/step_definitions/steps.rb:4"
+                },
+                "result": {
+                  "status": "failed",
+                  "error_message": " (RuntimeError)\n./features/step_definitions/steps.rb:4:in `/^this step fails$/'\nfeatures/outline.feature:9:in `Given this step fails'\nfeatures/outline.feature:4:in `Given this step <status>'",
+                  "duration": 1
+                }
+              }
+            ]
+          },
+          {
+            "id": "an-outline-feature;outline;examples2;2",
+            "keyword": "Scenario Outline",
+            "name": "outline",
+            "description": "",
+            "line": 13,
+            "type": "scenario",
+            "steps": [
               {
-                "keyword": "Examples", 
-                "name": "examples2", 
-                "line": 11, 
-                "description": "", 
-                "id": "an-outline-feature;outline;examples2", 
-                "rows": [
-                  {
-                    "cells": [
-                      "status"
-                     ], 
-                     "line": 12, 
-                     "id": "an-outline-feature;outline;examples2;1"
-                  }, 
-                  {
-                    "cells": [
-                      "passes"
-                    ], 
-                    "line": 13, 
-                    "id": "an-outline-feature;outline;examples2;2"
-                  }
-                ]
+                "keyword": "Given ",
+                "name": "this step passes",
+                "line": 13,
+                "match": {
+                  "location": "features/step_definitions/steps.rb:1"
+                },
+                "result": {
+                  "status": "passed",
+                  "duration": 1
+                }
               }
             ]
           }
@@ -735,7 +746,7 @@ Feature: JSON output formatter
         puts "Before hook 2"
         embed "src", "mime_type", "label"
       end
- 
+
       AfterStep do
         puts "AfterStep hook 1"
         embed "src", "mime_type", "label"

data/features/docs/formatters/junit_formatter.feature

@@ -53,9 +53,11 @@ Feature: JUnit output formatter
           Given this step <type>
 
           Examples:
-            | type   |
-            | passes |
-            | fails  |
+            | type         |
+            | passes       |
+            | fails        |
+            | is pending   |
+            | is undefined |
       """
 
   Scenario: one feature, one passing scenario, one failing scenario
@@ -69,8 +71,12 @@ Feature: JUnit output formatter
       <?xml version="1.0" encoding="UTF-8"?>
       <testsuite failures="1" errors="0" skipped="0" tests="2" time="0.05" name="One passing scenario, one failing scenario">
       <testcase classname="One passing scenario, one failing scenario" name="Passing" time="0.05">
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
       <testcase classname="One passing scenario, one failing scenario" name="Failing" time="0.05">
         <failure message="failed Failing" type="failed">
@@ -84,15 +90,13 @@ Feature: JUnit output formatter
 	./features/step_definitions/steps.rb:4:in `/^this step fails$/'
 	features/one_passing_one_failing.feature:7:in `Given this step fails']]>
         </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
         <system-out>
           <![CDATA[]]>
         </system-out>
         <system-err>
           <![CDATA[]]>
         </system-err>
+      </testcase>
       </testsuite>
 
       """
@@ -108,8 +112,12 @@ Feature: JUnit output formatter
       <?xml version="1.0" encoding="UTF-8"?>
       <testsuite failures="1" errors="0" skipped="0" tests="2" time="0.05" name="Subdirectory - One passing scenario, one failing scenario">
       <testcase classname="Subdirectory - One passing scenario, one failing scenario" name="Passing" time="0.05">
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
       <testcase classname="Subdirectory - One passing scenario, one failing scenario" name="Failing" time="0.05">
         <failure message="failed Failing" type="failed">
@@ -123,15 +131,13 @@ Feature: JUnit output formatter
 	./features/step_definitions/steps.rb:4:in `/^this step fails$/'
 	features/some_subdirectory/one_passing_one_failing.feature:7:in `Given this step fails']]>
         </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
         <system-out>
           <![CDATA[]]>
         </system-out>
         <system-err>
           <![CDATA[]]>
         </system-err>
+      </testcase>
       </testsuite>
 
       """
@@ -148,20 +154,22 @@ Feature: JUnit output formatter
       <testsuite failures="0" errors="0" skipped="2" tests="2" time="0.05" name="Pending step">
       <testcase classname="Pending step" name="Pending" time="0.05">
         <skipped/>
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
       <testcase classname="Pending step" name="Undefined" time="0.05">
         <skipped/>
-        <system-out/>
-        <system-err/>
-      </testcase>
         <system-out>
           <![CDATA[]]>
         </system-out>
         <system-err>
           <![CDATA[]]>
         </system-err>
+      </testcase>
       </testsuite>
       
       """
@@ -188,8 +196,12 @@ Feature: JUnit output formatter
       ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
       features/pending.feature:4:in `Given this step is pending']]>
         </failure>
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
       <testcase classname="Pending step" name="Undefined" time="0.05">
         <failure message="undefined Undefined" type="undefined">
@@ -199,18 +211,16 @@ Feature: JUnit output formatter
 
       Message:
       ]]>
-          <![CDATA[Undefined step: "this step is undefined" (Cucumber::Undefined)
+          <![CDATA[Undefined step: "this step is undefined" (Cucumber::Core::Test::Result::Undefined)
       features/pending.feature:7:in `Given this step is undefined']]>
         </failure>
-        <system-out/>
-        <system-err/>
-      </testcase>
         <system-out>
           <![CDATA[]]>
         </system-out>
         <system-err>
           <![CDATA[]]>
         </system-err>
+      </testcase>
       </testsuite>
 
       """
@@ -235,8 +245,8 @@ can't convert .* into String \(TypeError\)
 You *must* specify --out DIR for the junit formatter
       """
 
-  Scenario: one feature, one scenario outline, two examples: one passing, one failing
-    When I run `cucumber --format junit --out tmp/ features/scenario_outline.feature`
+  Scenario: strict mode, one feature, one scenario outline, four examples: one passing, one failing, one pending, one undefined
+    When I run `cucumber --strict --format junit --out tmp/ features/scenario_outline.feature`
     Then it should fail with:
       """
 
@@ -244,10 +254,14 @@ You *must* specify --out DIR for the junit formatter
     And the junit output file "tmp/TEST-features-scenario_outline.xml" should contain:
       """
       <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite failures="1" errors="0" skipped="0" tests="2" time="0.05" name="Scenario outlines">
+      <testsuite failures="3" errors="0" skipped="0" tests="4" time="0.05" name="Scenario outlines">
       <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | passes |)" time="0.05">
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
       <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | fails |)" time="0.05">
         <failure message="failed Using scenario outlines (outline example : | fails |)" type="failed">
@@ -262,21 +276,58 @@ You *must* specify --out DIR for the junit formatter
       features/scenario_outline.feature:9:in `Given this step fails'
       features/scenario_outline.feature:4:in `Given this step <type>']]>
         </failure>
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
+      </testcase>
+      <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | is pending |)" time="0.05">
+        <failure message="pending Using scenario outlines (outline example : | is pending |)" type="pending">
+          <![CDATA[Scenario Outline: Using scenario outlines
+
+      Example row: | is pending |
+
+      Message:
+      ]]>
+          <![CDATA[TODO (Cucumber::Pending)
+      ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+      features/scenario_outline.feature:10:in `Given this step is pending'
+      features/scenario_outline.feature:4:in `Given this step <type>']]>
+        </failure>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
+      <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | is undefined |)" time="0.05">
+        <failure message="undefined Using scenario outlines (outline example : | is undefined |)" type="undefined">
+          <![CDATA[Scenario Outline: Using scenario outlines
+
+      Example row: | is undefined |
+
+      Message:
+      ]]>
+          <![CDATA[Undefined step: "this step is undefined" (Cucumber::Core::Test::Result::Undefined)
+      features/scenario_outline.feature:11:in `Given this step is undefined'
+      features/scenario_outline.feature:4:in `Given this step <type>']]>
+        </failure>
         <system-out>
           <![CDATA[]]>
         </system-out>
         <system-err>
           <![CDATA[]]>
         </system-err>
+      </testcase>
       </testsuite>
 
       """ 
 
-  Scenario: one feature, one scenario outline, two examples: one passing, one failing with --expand option
-    When I run `cucumber --expand --format junit --out tmp/ features/scenario_outline.feature`
+  Scenario: strict mode with --expand option, one feature, one scenario outline, four examples: one passing, one failing, one pending, one undefined
+    When I run `cucumber --strict --expand --format junit --out tmp/ features/scenario_outline.feature`
     Then it should fail with exactly:
       """
 
@@ -284,10 +335,14 @@ You *must* specify --out DIR for the junit formatter
     And the junit output file "tmp/TEST-features-scenario_outline.xml" should contain:
       """
       <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite failures="1" errors="0" skipped="0" tests="2" time="0.05" name="Scenario outlines">
+      <testsuite failures="3" errors="0" skipped="0" tests="4" time="0.05" name="Scenario outlines">
       <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | passes |)" time="0.05">
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
       <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | fails |)" time="0.05">
         <failure message="failed Using scenario outlines (outline example : | fails |)" type="failed">
@@ -302,15 +357,52 @@ You *must* specify --out DIR for the junit formatter
       features/scenario_outline.feature:9:in `Given this step fails'
       features/scenario_outline.feature:4:in `Given this step <type>']]>
         </failure>
-        <system-out/>
-        <system-err/>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
+      </testcase>
+      <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | is pending |)" time="0.05">
+        <failure message="pending Using scenario outlines (outline example : | is pending |)" type="pending">
+          <![CDATA[Scenario Outline: Using scenario outlines
+
+      Example row: | is pending |
+
+      Message:
+      ]]>
+          <![CDATA[TODO (Cucumber::Pending)
+      ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+      features/scenario_outline.feature:10:in `Given this step is pending'
+      features/scenario_outline.feature:4:in `Given this step <type>']]>
+        </failure>
+        <system-out>
+          <![CDATA[]]>
+        </system-out>
+        <system-err>
+          <![CDATA[]]>
+        </system-err>
       </testcase>
+      <testcase classname="Scenario outlines" name="Using scenario outlines (outline example : | is undefined |)" time="0.05">
+        <failure message="undefined Using scenario outlines (outline example : | is undefined |)" type="undefined">
+          <![CDATA[Scenario Outline: Using scenario outlines
+
+      Example row: | is undefined |
+
+      Message:
+      ]]>
+          <![CDATA[Undefined step: "this step is undefined" (Cucumber::Core::Test::Result::Undefined)
+      features/scenario_outline.feature:11:in `Given this step is undefined'
+      features/scenario_outline.feature:4:in `Given this step <type>']]>
+        </failure>
         <system-out>
           <![CDATA[]]>
         </system-out>
         <system-err>
           <![CDATA[]]>
         </system-err>
+      </testcase>
       </testsuite>
 
       """