cucumber 1.3.10 → 2.0.0

data/features/json_formatter.feature

@@ -1,338 +0,0 @@
-Feature: JSON output formatter
-  In order to simplify processing of Cucumber features and results
-  Developers should be able to consume features as JSON
-
-  Background:
-    Given 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
-
-        @c
-        Scenario: Failing
-          Given a failing step
-      """
-    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
-
-      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"
-      end
-      """
-    And a file named "features/embed.feature" with:
-      """
-      Feature: A screenshot feature
-
-        Scenario:
-          Given I embed a screenshot
-
-      """
-
-  # Need to investigate why this won't pass in-process. error_message doesn't get det?
-  @spawn
-  Scenario: one feature, one passing scenario, one failing scenario
-    When I run `cucumber --format json features/one_passing_one_failing.feature`
-    Then it should fail with JSON:
-      """
-      [
-        {
-          "uri": "features/one_passing_one_failing.feature",
-          "keyword": "Feature",
-          "id": "one-passing-scenario,-one-failing-scenario",
-          "name": "One passing scenario, one failing scenario",
-          "line": 2,
-          "description": "",
-          "tags": [
-            {
-              "name": "@a",
-              "line": 1
-            }
-          ],
-          "elements": [
-            {
-              "keyword": "Scenario",
-              "id": "one-passing-scenario,-one-failing-scenario;passing",
-              "name": "Passing",
-              "line": 5,
-              "description": "",
-              "tags": [
-                {
-                  "name": "@b",
-                  "line": 4
-                }
-              ],
-              "type": "scenario",
-              "steps": [
-                {
-                  "keyword": "Given ",
-                  "name": "a passing step",
-                  "line": 6,
-                  "match": {
-                    "location": "features/step_definitions/steps.rb:1"
-                  },
-                  "result": {
-                    "status": "passed",
-                    "duration": 1
-                  }
-                }
-              ]
-            },
-            {
-              "keyword": "Scenario",
-              "id": "one-passing-scenario,-one-failing-scenario;failing",
-              "name": "Failing",
-              "line": 9,
-              "description": "",
-              "tags": [
-                {
-                  "name": "@c",
-                  "line": 8
-                }
-              ],
-              "type": "scenario",
-              "steps": [
-                {
-                  "keyword": "Given ",
-                  "name": "a failing step",
-                  "line": 10,
-                  "match": {
-                    "location": "features/step_definitions/steps.rb:5"
-                  },
-                  "result": {
-                    "status": "failed",
-                    "error_message": " (RuntimeError)\n./features/step_definitions/steps.rb:6:in `/a failing step/'\nfeatures/one_passing_one_failing.feature:10:in `Given a failing step'",
-                    "duration": 1
-                  }
-                }
-              ]
-            }
-          ]
-        }
-      ]
-
-      """
-
-  @spawn
-  Scenario: one feature, one passing scenario, one failing scenario with prettyfied json
-    When I run `cucumber --format json_pretty features/one_passing_one_failing.feature`
-    Then it should fail with JSON:
-      """
-      [
-        {
-          "uri": "features/one_passing_one_failing.feature",
-          "keyword": "Feature",
-          "id": "one-passing-scenario,-one-failing-scenario",
-          "name": "One passing scenario, one failing scenario",
-          "line": 2,
-          "description": "",
-          "tags": [
-            {
-              "name": "@a",
-              "line": 1
-            }
-          ],
-          "elements": [
-            {
-              "keyword": "Scenario",
-              "id": "one-passing-scenario,-one-failing-scenario;passing",
-              "name": "Passing",
-              "line": 5,
-              "description": "",
-              "tags": [
-                {
-                  "name": "@b",
-                  "line": 4
-                }
-              ],
-              "type": "scenario",
-              "steps": [
-                {
-                  "keyword": "Given ",
-                  "name": "a passing step",
-                  "line": 6,
-                  "match": {
-                    "location": "features/step_definitions/steps.rb:1"
-                  },
-                  "result": {
-                    "status": "passed",
-                    "duration": 1
-                  }
-                }
-              ]
-            },
-            {
-              "keyword": "Scenario",
-              "id": "one-passing-scenario,-one-failing-scenario;failing",
-              "name": "Failing",
-              "line": 9,
-              "description": "",
-              "tags": [
-                {
-                  "name": "@c",
-                  "line": 8
-                }
-              ],
-              "type": "scenario",
-              "steps": [
-                {
-                  "keyword": "Given ",
-                  "name": "a failing step",
-                  "line": 10,
-                  "match": {
-                    "location": "features/step_definitions/steps.rb:5"
-                  },
-                  "result": {
-                    "status": "failed",
-                    "error_message": " (RuntimeError)\n./features/step_definitions/steps.rb:6:in `/a failing step/'\nfeatures/one_passing_one_failing.feature:10:in `Given a failing step'",
-                    "duration": 1
-                  }
-                }
-              ]
-            }
-          ]
-        }
-      ]
-
-      """
-
-  @spawn
-  Scenario: DocString
-    Given a file named "features/doc_string.feature" with:
-      """
-      Feature: A DocString feature
-
-        Scenario:
-          Then I should fail with
-            \"\"\"
-            a string
-            \"\"\"
-      """
-    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/doc_string.feature`
-    Then it should fail with JSON:
-      """
-      [
-        {
-          "id": "a-docstring-feature",
-          "uri": "features/doc_string.feature",
-          "keyword": "Feature",
-          "name": "A DocString feature",
-          "line": 1,
-          "description": "",
-          "elements": [
-            {
-              "id": "a-docstring-feature;",
-              "keyword": "Scenario",
-              "name": "",
-              "line": 3,
-              "description": "",
-              "type": "scenario",
-              "steps": [
-                {
-                  "keyword": "Then ",
-                  "name": "I should fail with",
-                  "line": 4,
-                  "doc_string": {
-                    "content_type": "",
-                    "value": "a string",
-                    "line": 5
-                  },
-                  "match": {
-                    "location": "features/step_definitions/doc_string_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'",
-                    "duration": 1
-                  }
-                }
-              ]
-            }
-          ]
-        }
-      ]
-      """
-  @wip-jruby
-  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",
-                  "duration": 1
-                }
-              }
-            ]
-          }
-        ]
-      }
-    ]
-
-    """

data/features/parsing.feature

@@ -1,18 +0,0 @@
-Feature: Scenario Outlines
-
-  Scenario: Scenario Outline requires Example Section
-    Given a file named "features/f.feature" with:
-      """
-      Feature:
-        Scenario Outline:
-          Given I have <opening balance> cucumbers
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^I have (\d+) cucumbers$/ do; end
-      """
-    When I run `cucumber features/f.feature`
-    Then it should fail with:
-      """
-      Missing Example Section for Scenario Outline at features/f.feature:2 (Cucumber::Ast::ScenarioOutline::MissingExamples)
-      """

data/features/pretty_formatter.feature

@@ -1,31 +0,0 @@
-Feature: Pretty output formatter
-
-  Background:
-    Given a file named "features/scenario_outline_with_undefined_steps.feature" with:
-      """
-      Feature:
-
-        Scenario Outline:
-          Given an undefined step
-
-        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...
-    """
-

data/features/rerun_formatter.feature

@@ -1,35 +0,0 @@
-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

@@ -1,47 +0,0 @@
-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)
-      """

data/features/stats_formatters.feature

@@ -1,73 +0,0 @@
-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: C
-          Given <x>
-          And B
-          Examples:
-            |x|
-            |C|
-        Scenario: AC
-          Given A
-          Given C
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /A/ do;end
-      Given /B/ do;end
-      Given /C/ do;end
-      Given /D/ do;end
-      """
-
-  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:3
-        Given A   # features/f.feature:3
-        Given A   # features/f.feature:13
-      /B/         # features/step_definitions/steps.rb:2
-        Given B   # features/f.feature:5
-        And B     # features/f.feature:8
-      /C/         # features/step_definitions/steps.rb:3
-        Given <x> # features/f.feature:7
-        Given C   # features/f.feature:14
-      /D/         # features/step_definitions/steps.rb:4
-        NOT MATCHED BY ANY STEPS
-      
-      3 scenarios (3 skipped)
-      8 steps (8 skipped)
-      0m0.012s
-
-      """
-
-    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
-        
-        3 scenarios (3 skipped)
-        8 steps (8 skipped)
-        0m0.012s
-
-        """