casecumber 1.0.2.1 → 1.2.1.cb2

data/features/doc_strings.feature

@@ -0,0 +1,73 @@
+Feature: Doc strings
+
+  If you need to specify information in a scenario that won't fit on a single line, 
+  you can use a DocString.
+  
+  A DocString follows a step, and starts and ends with three double quotes, like this:
+  
+  ```gherkin
+  When I ask to reset my password
+  Then I should receive an email with:
+    """
+    Dear bozo,
+    
+    Please click this link to reset your password
+    """
+  ```
+  
+  It's possible to annotate the DocString with the type of content it contains. This is used by
+  formatting tools like http://relishapp.com which will render the contents of the DocString
+  appropriately. You specify the content type after the triple quote, like this:
+  
+  ```gherkin
+  Given there is some Ruby code:
+    """ruby
+    puts "hello world"
+    """
+  
+  You can read the content type from the argument passed into your step definition, as shown
+  in the example below.
+
+  Scenario: Plain text Docstring
+    Given a scenario with a step that looks like this:
+      """gherkin
+      Given I have a lot to say:
+       \"\"\"
+       One
+       Two
+       Three
+       \"\"\"
+      """
+    And a step definition that looks like this:
+      """ruby
+      Given /say/ do |text|
+        puts text
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      One
+      Two
+      Three
+      """
+
+  Scenario: DocString with interesting content type
+    Given a scenario with a step that looks like this:
+      """gherkin
+      Given I have some code for you:
+       \"\"\"ruby
+       # hello
+       \"\"\"
+      """
+    And a step definition that looks like this:
+      """ruby
+      Given /code/ do |text|
+        puts text.content_type
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      ruby
+      """

data/features/drb_server_integration.feature

@@ -0,0 +1,63 @@
+@drb
+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
+  loads up the environment only once.
+
+  This regression test highlights bug related to DRb server arguments processing, for more
+  details see https://github.com/cucumber/cucumber/issues/117
+
+  Background: App with Spork support
+    Spork is a gem that has a DRb server and the scenarios below illustrate how to use it.
+    However, any DRb server that adheres to the protocol that the client expects would work.
+
+    Given a directory without standard Cucumber project directory structure
+    And a file named "features/support/env.rb" with:
+      """
+      require 'rubygems'
+      require 'spork'
+
+      Spork.prefork do
+        puts "I'm loading all the heavy stuff..."
+      end
+
+      Spork.each_run do
+        puts "I'm loading the stuff just for this run..."
+      end
+      """
+    And a file named "config/cucumber.yml" with:
+      """
+      <%
+      std_opts = "--format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} --strict --tags ~@wip"
+      %>
+      default: --drb <%= std_opts %> features
+      """
+    And a file named "features/sample.feature" with:
+      """
+      # language: en
+      Feature: Sample
+        Scenario: this is a test
+          Given I am just testing stuff
+      """
+    And a file named "features/step_definitions/all_your_steps_are_belong_to_us.rb" with:
+    """
+    Given /^I am just testing stuff$/ do
+      # no-op
+    end
+    """
+
+  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"
+    And it should pass with:
+    """
+    1 step (1 passed)
+    """
+
+  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"
+    And it should pass with:
+    """
+    1 step (1 passed)
+    """

data/features/formatter_step_file_colon_line.feature

@@ -0,0 +1,46 @@
+Feature: Formatter API: Step file path and line number (Issue #179)
+  To all reporter to understand location of current executing step let's fetch this information
+  from step/step_invocation and pass to reporters
+
+  Scenario: my own formatter
+    Given a file named "features/f.feature" with:
+      """
+      Feature: I'll use my own
+        because I'm worth it
+        Scenario: just print step current line and feature file name
+          Given step at line 4
+          Given step at line 5
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^step at line (.*)$/ do |line|
+      end
+      """
+    And a file named "features/support/jb/formatter.rb" with:
+      """
+      module Jb
+        class Formatter
+          def initialize(step_mother, io, options)
+            @step_mother = step_mother
+            @io = io
+          end
+
+          def before_step_result(keyword, step_match, multiline_arg, status, exception, source_indent, background, file_colon_line)
+            @io.puts "step result event: #{file_colon_line}"
+          end
+
+          def step_name(keyword, step_match, status, source_indent, background, file_colon_line)
+            @io.puts "step name event: #{file_colon_line}"
+          end
+        end
+      end
+      """
+    When I run cucumber "features/f.feature --format Jb::Formatter"
+    Then it should pass with exactly:
+      """
+      step result event: features/f.feature:4
+      step name event: features/f.feature:4
+      step result event: features/f.feature:5
+      step name event: features/f.feature:5
+
+      """

data/features/json_formatter.feature

@@ -60,92 +60,90 @@ Feature: JSON output formatter
 
       """
 
-  Scenario: one feature, one passing scenario, one failing scenario
-    When I run cucumber "--format json features/one_passing_one_failing.feature"
-    Then the output should match /^\{"features":\[/
-
   Scenario: one feature, one passing scenario, one failing scenario
     When I run cucumber "--format json features/one_passing_one_failing.feature"
     Then it should fail with JSON:
       """
-      {
-        "features": [
-          {
-            "keyword": "Feature",
-            "name": "One passing scenario, one failing scenario",
-            "line": 2,
-            "description": "",
-            "tags": [
-              {
-                "name": "@a",
-                "line": 1
-              }
-            ],
-            "elements": [
-              {
-                "keyword": "Scenario",
-                "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"
-                    }
-                  }
-                ]
-              },
-              {
-                "keyword": "Scenario",
-                "name": "Failing",
-                "line": 9,
-                "description": "",
-                "tags": [
-                  {
-                    "name": "@c",
-                    "line": 8
+      [
+        {
+          "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"
                   }
-                ],
-                "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'"
-                    }
+                }
+              ]
+            },
+            {
+              "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'"
                   }
-                ]
-              }
-            ]
-          }
-        ]
-      }
+                }
+              ]
+            }
+          ]
+        }
+      ]
 
       """
 
-  Scenario: pystring
-    Given a file named "features/pystring.feature" with:
+  Scenario: DocString
+    Given a file named "features/doc_string.feature" with:
       """
-      Feature: A pystring feature
+      Feature: A DocString feature
 
         Scenario: 
           Then I should fail with
@@ -153,68 +151,26 @@ Feature: JSON output formatter
             a string
             \"\"\"
       """
-    And a file named "features/step_definitions/pystring_steps.rb" with:
+    And a file named "features/step_definitions/doc_string_steps.rb" with:
       """
       Then /I should fail with/ do |s|
         raise s
       end
       """
-    When I run cucumber "--format json features/pystring.feature"
+    When I run cucumber "--format json features/doc_string.feature"
     Then it should fail with JSON:
       """
-      {
-        "features": [
-          {
-            "keyword": "Feature",
-            "name": "A pystring feature",
-            "line": 1,
-            "description": "",
-            "elements": [
-              {
-                "keyword": "Scenario",
-                "name": "",
-                "line": 3,
-                "description": "",
-                "type": "scenario",
-                "steps": [
-                  {
-                    "keyword": "Then ",
-                    "name": "I should fail with",
-                    "line": 4,
-                    "multiline_arg": {
-                      "value": "a string",
-                      "line": 5,
-                      "type": "doc_string"
-                    },
-                    "match": {
-                      "location": "features/step_definitions/pystring_steps.rb:1"
-                    },
-                    "result": {
-                      "status": "failed",
-                      "error_message": "a string (RuntimeError)\n./features/step_definitions/pystring_steps.rb:2:in `/I should fail with/'\nfeatures/pystring.feature:4:in `Then I should fail with'"
-                    }
-                  }
-                ]
-              }
-            ]
-          }
-        ]
-      }
-      """
-
-  Scenario: embedding screenshot
-    When I run cucumber "-b --format json features/embed.feature"
-    Then it should pass with JSON:
-    """
-    {
-      "features": [
+      [
         {
+          "id": "a-docstring-feature",
+          "uri": "features/doc_string.feature",
           "keyword": "Feature",
-          "name": "A screenshot feature",
+          "name": "A DocString feature",
           "line": 1,
           "description": "",
           "elements": [
             {
+              "id": "a-docstring-feature;",
               "keyword": "Scenario",
               "name": "",
               "line": 3,
@@ -222,20 +178,20 @@ Feature: JSON output formatter
               "type": "scenario",
               "steps": [
                 {
-                  "keyword": "Given ",
-                  "name": "I embed a screenshot",
+                  "keyword": "Then ",
+                  "name": "I should fail with",
                   "line": 4,
-                  "embeddings": [
-                    {
-                      "mime_type": "image/png",
-                      "data": "Zm9v"
-                    }
-                  ],
+                  "doc_string": {
+                    "content_type": "", 
+                    "value": "a string", 
+                    "line": 5
+                  },
                   "match": {
-                    "location": "features/step_definitions/steps.rb:29"
+                    "location": "features/step_definitions/doc_string_steps.rb:1"
                   },
                   "result": {
-                    "status": "passed"
+                    "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'"
                   }
                 }
               ]
@@ -243,6 +199,50 @@ Feature: JSON output formatter
           ]
         }
       ]
-    }
+      """
 
-    """
+  Scenario: embedding screenshot
+    When I run cucumber "-b --format json features/embed.feature"
+    Then it should pass with JSON:
+    """
+    [
+      {
+        "uri": "features/embed.feature",
+        "id": "a-screenshot-feature",
+        "keyword": "Feature",
+        "name": "A screenshot feature",
+        "line": 1,
+        "description": "",
+        "elements": [
+          {
+            "id": "a-screenshot-feature;",
+            "keyword": "Scenario",
+            "name": "",
+            "line": 3,
+            "description": "",
+            "type": "scenario",
+            "steps": [
+              {
+                "keyword": "Given ",
+                "name": "I embed a screenshot",
+                "line": 4,
+                "embeddings": [
+                  {
+                    "mime_type": "image/png",
+                    "data": "Zm9v"
+                  }
+                ],
+                "match": {
+                  "location": "features/step_definitions/steps.rb:29"
+                },
+                "result": {
+                  "status": "passed"
+                }
+              }
+            ]
+          }
+        ]
+      }
+    ]
+
+    """

data/features/nested_steps.feature

@@ -0,0 +1,60 @@
+Feature: Nested Steps
+
+
+  Background:
+    Given a scenario with a step that looks like this:
+      """gherkin
+      Given two turtles
+      """
+    And a step definition that looks like this:
+      """ruby
+      Given /a turtle/ do
+        puts "turtle!"
+      end
+      """
+
+  Scenario: Use #steps to call several steps at once
+    Given a step definition that looks like this:
+      """ruby
+      Given /two turtles/ do
+        steps %{
+          Given a turtle
+          And a turtle
+        }
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      turtle!
+
+      turtle!
+
+      """
+
+  Scenario: Use #step to call a single step
+    Given a step definition that looks like this:
+      """ruby
+      Given /two turtles/ do
+        step "a turtle"
+        step "a turtle"
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain:
+      """
+      turtle!
+
+      turtle!
+
+      """
+
+  Scenario: Use deprecated i18n methods
+    Given a step definition that looks like this:
+      """ruby
+      Given /two turtles/ do
+        Given "a turtle"
+      end
+      """
+    When I run the feature with the progress formatter
+    Then the output should contain "WARNING"

data/features/rerun_formatter.feature

@@ -0,0 +1,35 @@
+Feature: Rerun formatter
+  For details see https://github.com/cucumber/cucumber/issues/57
+
+  Background:
+    Given a file named "features/one_passing_one_failing.feature" with:
+      """
+      Feature: One passing example, one failing example
+
+        Scenario Outline:
+          Given a <certain> step
+        
+        Examples:
+          |certain|
+          |passing|
+          |failing|
+
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /a passing step/ do
+        #does nothing
+      end
+
+      Given /a failing step/ do
+        fail
+      end
+      """
+
+  Scenario: Handle examples with the rerun formatter
+    When I run cucumber "features/one_passing_one_failing.feature -r features -f rerun"
+    Then it should fail with:
+    """
+    features/one_passing_one_failing.feature:9
+    """
+

data/features/run_specific_scenarios.feature

@@ -0,0 +1,47 @@
+Feature: Run specific scenarios
+
+  You can choose to run a specific scenario using the file:line format
+
+  Background:
+    Given a file named "features/step_definitions/steps.rb" with:
+      """
+      Given(/pass/) {}
+      Given(/fail/) { raise "Failed" }
+      """
+
+  Scenario: Two scenarios, run just one of them
+    Given a file named "features/test.feature" with:
+      """
+      Feature: 
+        Scenario:
+          Given this is undefined
+
+        Scenario: Hit
+          Given this passes
+      """
+    When I run `cucumber features/test.feature:5 -f progress`
+    Then it should pass with:
+      """
+      1 scenario (1 passed)
+      """
+
+  Scenario: Single example from a scenario outline
+    Given a file named "features/test.feature" with:
+      """
+      Feature:
+        Scenario Outline:
+          Given this <something>
+
+          Examples:
+            | something    |
+            | is undefined |
+            | fails        |
+
+        Scenario: Miss
+          Given this passes
+      """
+    When I run `cucumber features/test.feature:8 -f progress`
+    Then it should fail with:
+      """
+      1 scenario (1 failed)
+      """