mobiusloop 0.1.2

data/features/docs/formatters/pretty_formatter.feature

@@ -0,0 +1,73 @@
+Feature: Pretty output formatter
+
+  Background:
+    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
+      """
+      Feature:
+
+        Scenario Outline:
+          Given this step is undefined
+
+        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...
+    """
+  Scenario: Hook output should be printed before hook exception
+    Given the standard step definitions
+    And a file named "features/test.feature" with:
+      """
+      Feature:
+        Scenario:
+          Given this step passes
+      """
+    And a file named "features/step_definitions/output_steps.rb" with:
+      """
+      Before do
+        puts "Before hook"
+       end
+
+      AfterStep do
+        puts "AfterStep hook"
+      end
+
+      After do
+        puts "After hook"
+	raise "error"
+      end
+      """
+    When I run `cucumber -q -f pretty features/test.feature`
+    Then the stderr should not contain anything
+    Then it should fail with:
+      """
+      Feature: 
+ 
+        Scenario: 
+            Before hook
+          Given this step passes
+            AfterStep hook
+            After hook
+            error (RuntimeError)
+            ./features/step_definitions/output_steps.rb:11:in `After'
+      
+      Failing Scenarios:
+      cucumber features/test.feature:2
+      
+      1 scenario (1 failed)
+      1 step (1 passed)
+      """

data/features/docs/formatters/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 this step is undefined
+
+        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/docs/formatters/rerun_formatter.feature

@@ -0,0 +1,188 @@
+Feature: Rerun formatter
+
+  The rerun formatter writes an output that's perfect for
+  passing to Cucumber when you want to rerun only the 
+  scenarios that prevented the exit code to be zero.
+
+  You can save off the rerun output to a file by using it like this:
+
+  `cucumber -f rerun --out .cucumber.rerun`
+
+  Now you can pass that file's content to Cucumber to tell it
+  which scenarios to run:
+
+  `cucumber \`cat .cucumber.rerun\``
+
+  This is useful when debugging in a large suite of features.
+
+  Background:
+    Given the standard step definitions
+
+  Scenario: Exit code is zero
+    Given a file named "features/mixed.feature" with:
+      """
+      Feature: Mixed
+
+        Scenario:
+          Given this step is undefined
+
+        Scenario:
+          Given this step is pending
+
+        Scenario:
+          Given this step passes
+
+      """
+
+    When I run `cucumber -f rerun`
+    Then it should pass with exactly:
+      """
+      """
+
+  Scenario: Exit code is zero in the dry-run mode
+    Given a file named "features/mixed.feature" with:
+      """
+      Feature: Mixed
+
+        Scenario:
+          Given this step fails
+
+        Scenario:
+          Given this step is undefined
+
+        Scenario:
+          Given this step is pending
+
+        Scenario:
+          Given this step passes
+
+      """
+    And a file named "features/all_good.feature" with:
+      """
+      Feature: All good
+
+        Scenario:
+          Given this step passes
+      """
+
+    When I run `cucumber -f rerun --dry-run`
+    Then it should pass with exactly:
+      """
+      """
+
+  Scenario: Exit code is not zero, regular scenario
+    Given a file named "features/mixed.feature" with:
+      """
+      Feature: Mixed
+
+        Scenario:
+          Given this step fails
+
+        Scenario:
+          Given this step is undefined
+
+        Scenario:
+          Given this step is pending
+
+        Scenario:
+          Given this step passes
+
+      """
+    And a file named "features/all_good.feature" with:
+      """
+      Feature: All good
+
+        Scenario:
+          Given this step passes
+      """
+
+    When I run `cucumber -f rerun --strict`
+    Then it should fail with exactly:
+      """
+      features/mixed.feature:3:6:9
+      """
+
+  Scenario: Exit code is not zero, scenario outlines
+    For details see https://github.com/cucumber/cucumber/issues/57
+    Given a file named "features/one_passing_one_failing.feature" with:
+      """
+      Feature: One passing example, one failing example
+
+        Scenario Outline:
+          Given this step <status>
+        
+        Examples:
+          | status |
+          | passes |
+          | fails  |
+
+      """
+    When I run `cucumber -f rerun`
+    Then it should fail with:
+    """
+    features/one_passing_one_failing.feature:9
+    """
+
+  Scenario: Exit code is not zero, failing background
+    Given a file named "features/failing_background.feature" with:
+      """
+      Feature: Failing background sample
+
+        Background:
+          Given this step fails
+
+        Scenario: failing background
+          Then this step passes
+
+        Scenario: another failing background
+          Then this step passes
+      """
+    When I run `cucumber -f rerun`
+    Then it should fail with:
+    """
+    features/failing_background.feature:6:9
+    """
+
+  Scenario: Exit code is not zero, failing background with scenario outline
+    Given a file named "features/failing_background_outline.feature" with:
+      """
+      Feature: Failing background sample with scenario outline
+
+        Background:
+          Given this step fails
+
+        Scenario Outline:
+          Then this step <status>
+
+        Examples:
+          | status |
+          | passes |
+          | passes |
+      """
+    When I run `cucumber features/failing_background_outline.feature -r features -f rerun`
+    Then it should fail with:
+    """
+    features/failing_background_outline.feature:11:12
+    """
+
+  Scenario: Exit code is not zero, scenario outlines with expand
+    For details see https://github.com/cucumber/cucumber/issues/503
+
+    Given a file named "features/one_passing_one_failing.feature" with:
+    """
+      Feature: One passing example, one failing example
+
+        Scenario Outline:
+          Given this step <status>
+
+        Examples:
+          | status |
+          | passes |
+          | fails  |
+
+      """
+    When I run `cucumber --expand -f rerun`
+    Then it should fail with:
+    """
+    features/one_passing_one_failing.feature:9
+    """

data/features/docs/formatters/usage_formatter.feature

@@ -0,0 +1,98 @@
+Feature: Usage formatter
+
+  In order to see where step definitions are used
+  Developers should be able to see a list of step definitions and their use
+
+  Background:
+    Given a file named "features/f.feature" with:
+      """
+      Feature: F
+        Background: A
+          Given A
+        Scenario: B
+          Given B
+        Scenario Outline: CA
+          Given <x>
+          And B
+          Examples:
+            |x|
+            |C|
+            |A|
+        Scenario: AC
+          Given A
+          Given C
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given(/A/) { }
+      Given(/B/) { }
+      Given(/C/) { }
+      Given(/D/) { }
+      """
+
+  Scenario: Run with --format usage
+    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:12
+        Given A # features/f.feature:14
+      /B/       # features/step_definitions/steps.rb:2
+        Given B # features/f.feature:5
+        And B   # features/f.feature:11
+        And B   # features/f.feature:12
+      /C/       # features/step_definitions/steps.rb:3
+        Given C # features/f.feature:11
+        Given C # features/f.feature:15
+      /D/       # features/step_definitions/steps.rb:4
+        NOT MATCHED BY ANY STEPS
+      
+      4 scenarios (4 skipped)
+      11 steps (11 skipped)
+
+      """
+
+  Scenario: Run with --expand --format usage
+    When I run `cucumber -x -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:12
+        Given A # features/f.feature:14
+      /B/       # features/step_definitions/steps.rb:2
+        Given B # features/f.feature:5
+        And B   # features/f.feature:11
+        And B   # features/f.feature:12
+      /C/       # features/step_definitions/steps.rb:3
+        Given C # features/f.feature:11
+        Given C # features/f.feature:15
+      /D/       # features/step_definitions/steps.rb:4
+        NOT MATCHED BY ANY STEPS
+      
+      4 scenarios (4 skipped)
+      11 steps (11 skipped)
+
+      """
+
+    Scenario: Run with --format stepdefs
+      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
+        /C/   # features/step_definitions/steps.rb:3
+        /D/   # features/step_definitions/steps.rb:4
+          NOT MATCHED BY ANY STEPS
+        
+        4 scenarios (4 skipped)
+        11 steps (11 skipped)
+
+        """

data/features/docs/getting_started.feature

@@ -0,0 +1,27 @@
+Feature: Getting started
+
+  To get started, just open a command prompt in an empty directory and run 
+  `cucumber`. You'll be prompted for what to do next.
+
+  @spawn
+  Scenario: Run Cucumber in an empty directory
+    Given a directory without standard Cucumber project directory structure
+    When I run `cucumber`
+    Then it should fail with:
+      """
+      No such file or directory - features. You can use `cucumber --init` to get started.
+      """
+
+  Scenario: Accidentally run Cucumber in a folder with Ruby files in it.
+    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 the exit status should be 2
+    And the output should not contain:
+      """
+      this will not be shown
+
+      """

data/features/docs/gherkin/background.feature

@@ -0,0 +1,548 @@
+Feature: Background
+
+  Often you find that several scenarios in the same feature start with 
+  a common context.
+  
+  Cucumber provides a mechanism for this, by providing a `Background` keyword
+  where you can specify steps that should be run before each scenario in the
+  feature. Typically these will be `Given` steps, but you can use any steps
+  that you need to.
+  
+  **Hint:** if you find that some of the scenarios don't fit the background,
+  consider splitting them into a separate feature.
+  
+  Background:
+    Given a file named "features/passing_background.feature" with:
+      """
+      Feature: Passing background sample
+
+        Background:
+          Given '10' cukes
+
+        Scenario: passing background
+          Then I should have '10' cukes    
+
+        Scenario: another passing background
+          Then I should have '10' cukes
+      """
+    And a file named "features/scenario_outline_passing_background.feature" with:
+      """
+      Feature: Passing background with scenario outlines sample
+
+        Background:
+          Given '10' cukes
+
+        Scenario Outline: passing background
+          Then I should have '<count>' cukes
+          Examples:
+            |count|
+            | 10  |
+
+        Scenario Outline: another passing background
+          Then I should have '<count>' cukes
+          Examples:
+            |count|
+            | 10  |
+      """
+    And a file named "features/background_tagged_before_on_outline.feature" with:
+      """
+      @background_tagged_before_on_outline
+      Feature: Background tagged Before on Outline
+
+        Background: 
+          Given this step passes
+
+        Scenario Outline: passing background
+          Then I should have '<count>' cukes
+
+          Examples: 
+            | count |
+            | 888   |
+      """
+    And a file named "features/failing_background.feature" with:
+      """
+      Feature: Failing background sample
+
+        Background:
+          Given this step raises an error
+          And '10' cukes
+
+        Scenario: failing background
+          Then I should have '10' cukes
+
+        Scenario: another failing background
+          Then I should have '10' cukes
+      """
+    And a file named "features/scenario_outline_failing_background.feature" with:
+      """
+      Feature: Failing background with scenario outlines sample
+
+        Background:
+          Given this step raises an error
+
+        Scenario Outline: failing background
+          Then I should have '<count>' cukes
+          Examples:
+            |count|
+            | 10  |
+
+        Scenario Outline: another failing background
+          Then I should have '<count>' cukes
+          Examples:
+            |count|
+            | 10  |
+      """
+    And a file named "features/pending_background.feature" with:
+      """
+      Feature: Pending background sample
+
+        Background:
+          Given this step is pending
+
+        Scenario: pending background
+          Then I should have '10' cukes
+
+        Scenario: another pending background
+          Then I should have '10' cukes
+      """
+    And a file named "features/failing_background_after_success.feature" with:
+      """
+      Feature: Failing background after previously successful background sample
+
+        Background:
+          Given this step passes
+          And '10' global cukes
+
+        Scenario: passing background
+          Then I should have '10' global cukes
+
+        Scenario: failing background
+          Then I should have '10' global cukes
+      """
+    And a file named "features/failing_background_after_success_outline.feature" with:
+      """
+      Feature: Failing background after previously successful background sample
+
+        Background:
+          Given this step passes
+          And '10' global cukes
+
+        Scenario Outline: passing background
+          Then I should have '<count>' global cukes
+
+          Examples: 
+            | count |
+            | 10    |
+
+        Scenario Outline: failing background
+          Then I should have '<count>' global cukes
+
+          Examples: 
+            | count |
+            | 10    |
+
+      """
+    And a file named "features/multiline_args_background.feature" with:
+      """
+      Feature: Passing background with multiline args
+
+        Background:
+          Given table
+            |a|b|
+            |c|d|
+          And multiline string
+            \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+            \"\"\"
+
+        Scenario: passing background
+          Then the table should be
+            |a|b|
+            |c|d|
+          Then the multiline string should be
+            \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+            \"\"\"
+
+        Scenario: another passing background
+          Then the table should be
+            |a|b|
+            |c|d|
+          Then the multiline string should be
+            \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+            \"\"\"
+      """
+    And the standard step definitions
+    And a file named "features/step_definitions/cuke_steps.rb" with:
+      """
+      Given /^'(.+)' cukes$/ do |cukes| x=1
+        raise "We already have #{@cukes} cukes!" if @cukes
+        @cukes = cukes
+      end
+
+      Given /^'(.+)' global cukes$/ do |cukes| x=1
+        $scenario_runs ||= 0
+        raise 'FAIL' if $scenario_runs >= 1
+        $cukes = cukes
+        $scenario_runs += 1
+      end
+
+      Then /^I should have '(.+)' global cukes$/ do |cukes| x=1
+        expect($cukes).to eq cukes
+      end
+
+      Then /^I should have '(.+)' cukes$/ do |cukes| x=1
+        expect(@cukes).to eq cukes
+      end
+
+      Before('@background_tagged_before_on_outline') do
+        @cukes = '888'
+      end
+
+      After('@background_tagged_before_on_outline') do
+        expect(@cukes).to eq '888'
+      end
+      """
+
+  Scenario: run a specific scenario with a background
+    When I run `cucumber -q features/passing_background.feature:9`
+    Then it should pass with exactly:
+    """
+    Feature: Passing background sample
+    
+      Background: 
+        Given '10' cukes
+
+      Scenario: another passing background
+        Then I should have '10' cukes
+
+    1 scenario (1 passed)
+    2 steps (2 passed)
+
+    """
+  
+  Scenario: run a feature with a background that passes
+    When I run `cucumber -q features/passing_background.feature`
+    Then it should pass with exactly:
+    """
+    Feature: Passing background sample
+
+      Background: 
+        Given '10' cukes
+
+      Scenario: passing background
+        Then I should have '10' cukes
+
+      Scenario: another passing background
+        Then I should have '10' cukes
+
+    2 scenarios (2 passed)
+    4 steps (4 passed)
+
+    """
+
+  Scenario: run a feature with scenario outlines that has a background that passes
+    When I run `cucumber -q features/scenario_outline_passing_background.feature`
+    Then it should pass with exactly:
+    """
+    Feature: Passing background with scenario outlines sample
+
+      Background: 
+        Given '10' cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+      Scenario Outline: another passing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+    2 scenarios (2 passed)
+    4 steps (4 passed)
+
+    """
+
+  Scenario: run a feature with scenario outlines that has a background that passes
+    When I run `cucumber -q features/background_tagged_before_on_outline.feature`
+    Then it should pass with exactly:
+    """
+    @background_tagged_before_on_outline
+    Feature: Background tagged Before on Outline
+
+      Background: 
+        Given this step passes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 888   |
+
+    1 scenario (1 passed)
+    2 steps (2 passed)
+
+    """
+
+  @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:
+    """
+    Feature: Failing background sample
+
+      Background: 
+        Given this step raises an error
+          error (RuntimeError)
+          ./features/step_definitions/steps.rb:2:in `/^this step raises an error$/'
+          features/failing_background.feature:4:in `Given this step raises an error'
+        And '10' cukes
+
+      Scenario: failing background
+        Then I should have '10' cukes
+
+      Scenario: another failing background
+        Then I should have '10' cukes
+
+    Failing Scenarios:
+    cucumber features/failing_background.feature:7
+    cucumber features/failing_background.feature:10
+    
+    2 scenarios (2 failed)
+    6 steps (2 failed, 4 skipped)
+    
+    """
+
+  @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:
+    """
+    Feature: Failing background with scenario outlines sample
+
+      Background: 
+        Given this step raises an error
+          error (RuntimeError)
+          ./features/step_definitions/steps.rb:2:in `/^this step raises an error$/'
+          features/scenario_outline_failing_background.feature:4:in `Given this step raises an error'
+
+      Scenario Outline: failing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+      Scenario Outline: another failing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+    Failing Scenarios:
+    cucumber features/scenario_outline_failing_background.feature:10
+    cucumber features/scenario_outline_failing_background.feature:16
+
+    2 scenarios (2 failed)
+    4 steps (2 failed, 2 skipped)
+    
+    """
+
+  Scenario: run a feature with a background that is pending
+    When I run `cucumber -q features/pending_background.feature`
+    Then it should pass with exactly:
+    """
+    Feature: Pending background sample
+
+      Background: 
+        Given this step is pending
+          TODO (Cucumber::Pending)
+          ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+          features/pending_background.feature:4:in `Given this step is pending'
+
+      Scenario: pending background
+        Then I should have '10' cukes
+
+      Scenario: another pending background
+        Then I should have '10' cukes
+
+    2 scenarios (2 pending)
+    4 steps (2 skipped, 2 pending)
+    
+    """
+
+  @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:
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given this step passes
+        And '10' global cukes
+
+      Scenario: passing background
+        Then I should have '10' global cukes
+
+      Scenario: failing background
+        And '10' global cukes
+          FAIL (RuntimeError)
+          ./features/step_definitions/cuke_steps.rb:8:in `/^'(.+)' global cukes$/'
+          features/failing_background_after_success.feature:5:in `And '10' global cukes'
+        Then I should have '10' global cukes
+
+    Failing Scenarios:
+    cucumber features/failing_background_after_success.feature:10
+
+    2 scenarios (1 failed, 1 passed)
+    6 steps (1 failed, 1 skipped, 4 passed)
+    
+    """
+
+  @spawn
+  Scenario: background passes with first outline scenario but fails with second
+    When I run `cucumber -q features/failing_background_after_success_outline.feature`
+    Then it should fail with exactly:
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given this step passes
+        And '10' global cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+      Scenario Outline: failing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+          | count |
+          | 10    |
+          FAIL (RuntimeError)
+          ./features/step_definitions/cuke_steps.rb:8:in `/^'(.+)' global cukes$/'
+          features/failing_background_after_success_outline.feature:5:in `And '10' global cukes'
+
+    Failing Scenarios:
+    cucumber features/failing_background_after_success_outline.feature:19
+
+    2 scenarios (1 failed, 1 passed)
+    6 steps (1 failed, 1 skipped, 4 passed)
+    
+    """
+
+  @spawn
+  Scenario: background passes with first outline scenario but fails with second (--expand)
+    When I run `cucumber -x -q features/failing_background_after_success_outline.feature`
+    Then it should fail with exactly:
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given this step passes
+        And '10' global cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+ 
+          Scenario: | 10 |
+            Then I should have '10' global cukes
+
+      Scenario Outline: failing background
+        Then I should have '<count>' global cukes
+
+        Examples: 
+
+          Scenario: | 10 |
+            And '10' global cukes
+          FAIL (RuntimeError)
+          ./features/step_definitions/cuke_steps.rb:8:in `/^'(.+)' global cukes$/'
+          features/failing_background_after_success_outline.feature:5:in `And '10' global cukes'
+            Then I should have '10' global cukes
+
+    Failing Scenarios:
+    cucumber features/failing_background_after_success_outline.feature:19
+
+    2 scenarios (1 failed, 1 passed)
+    6 steps (1 failed, 1 skipped, 4 passed)
+    
+    """
+
+  Scenario: background with multline args
+    Given a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^table$/ do |table| x=1
+        @table = table
+      end
+
+      Given /^multiline string$/ do |string| x=1
+        @multiline = string
+      end
+
+      Then /^the table should be$/ do |table| x=1
+        expect(@table.raw).to eq table.raw
+      end
+
+      Then /^the multiline string should be$/ do |string| x=1
+        expect(@multiline).to eq string
+      end
+      """
+    When I run `cucumber -q features/multiline_args_background.feature`
+    Then it should pass with exactly:
+      """
+      Feature: Passing background with multiline args
+
+        Background: 
+          Given table
+            | a | b |
+            | c | d |
+          And multiline string
+            \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+            \"\"\"
+
+        Scenario: passing background
+          Then the table should be
+            | a | b |
+            | c | d |
+          Then the multiline string should be
+            \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+            \"\"\"
+
+        Scenario: another passing background
+          Then the table should be
+            | a | b |
+            | c | d |
+          Then the multiline string should be
+            \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+            \"\"\"
+
+      2 scenarios (2 passed)
+      8 steps (8 passed)
+    
+      """
+