casecumber 1.0.2.1

data/features/bootstrap.feature

@@ -0,0 +1,13 @@
+Feature: Bootstrapping a new project
+  In order to have the best chances of getting up and running with cucumber
+  As a new cucumber user
+  I want cucumber to give helpful error messages in basic situations
+
+ Scenario: running cucumber against a non-existing feature file
+  Given a directory without standard Cucumber project directory structure
+    When I run `cucumber`
+    Then it should fail with:
+      """
+      You don't have a 'features' directory.  Please create one to get started.
+      See http://cukes.info/ for more information.
+      """

data/features/custom_formatter.feature

@@ -0,0 +1,41 @@
+Feature: Custom Formatter
+
+  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 me
+          Given this step works
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step works$/ do
+      end
+      """
+    And a file named "features/support/ze/formator.rb" with:
+      """
+      module Ze
+        class Formator
+          def initialize(step_mother, io, options)
+            @step_mother = step_mother
+            @io = io
+          end
+
+          def before_feature(feature)
+            @io.puts feature.short_name.upcase
+          end
+
+          def scenario_name(keyword, name, file_colon_line, source_indent)
+            @io.puts "  #{name.upcase}"
+          end
+        end
+      end
+      """
+    When I run cucumber "features/f.feature --format Ze::Formator"
+    Then it should pass with exactly:
+      """
+      I'LL USE MY OWN
+        JUST PRINT ME
+
+      """

data/features/execute_with_tag_filter.feature

@@ -0,0 +1,63 @@
+Feature: Tag logic
+  In order to conveniently run subsets of features
+  As a Cuker
+  I want to select features using logical AND/OR of tags
+
+  Background:
+    Given a file named "features/tagulicious.feature" with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+          Given passing
+
+        @one
+        Scenario: Another Example
+          Given passing
+
+        @three
+        Scenario: Yet another Example
+          Given passing
+
+        @ignore
+        Scenario: And yet another Example
+      """
+
+  Scenario: ANDing tags
+    When I run `cucumber -q -t @one -t @three features/tagulicious.feature`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+          Given passing
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """
+
+  Scenario: ORing tags
+    When I run `cucumber -q -t @one,@three features/tagulicious.feature`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+          Given passing
+
+        @one
+        Scenario: Another Example
+          Given passing
+
+        @three
+        Scenario: Yet another Example
+          Given passing
+
+      3 scenarios (3 undefined)
+      3 steps (3 undefined)
+
+      """

data/features/hooks.feature

@@ -0,0 +1,59 @@
+Feature: Tagged hooks
+
+  Background:
+    Given a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step works$/ do; end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Before('~@no-boom') do 
+        raise 'boom'
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: With and without hooks
+        Scenario: using hook
+          Given this step works
+
+        @no-boom
+        Scenario: omitting hook
+          Given this step works
+      """
+
+  Scenario: omit tagged hook
+    When I run `cucumber features/f.feature:2`
+    Then it should fail with:
+      """
+      Feature: With and without hooks
+      
+        Scenario: using hook    # features/f.feature:2
+        boom (RuntimeError)
+        ./features/support/hooks.rb:2:in `Before'
+          Given this step works # features/step_definitions/steps.rb:1
+      
+      Failing Scenarios:
+      cucumber features/f.feature:2 # Scenario: using hook
+      
+      1 scenario (1 failed)
+      1 step (1 skipped)
+
+      """
+
+    Scenario: omit tagged hook
+      When I run `cucumber features/f.feature:6`
+      Then it should pass with:
+        """
+        Feature: With and without hooks
+
+          @no-boom
+          Scenario: omitting hook # features/f.feature:6
+            Given this step works # features/step_definitions/steps.rb:1
+
+        1 scenario (1 passed)
+        1 step (1 passed)
+
+        """
+
+

data/features/iso-8859-1.feature

@@ -0,0 +1,6 @@
+# language: no
+# encoding: iso-8859-1
+Egenskap: Alle bruker ikke UTF-8
+  Scenario: Dette b�r g� bra
+    N�r jeg drikker en "�l"
+    S� skal de andre si "sk�l"

data/features/json_formatter.feature

@@ -0,0 +1,248 @@
+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
+
+      """
+
+  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
+                  }
+                ],
+                "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:
+      """
+      Feature: A pystring feature
+
+        Scenario: 
+          Then I should fail with
+            \"\"\"
+            a string
+            \"\"\"
+      """
+    And a file named "features/step_definitions/pystring_steps.rb" with:
+      """
+      Then /I should fail with/ do |s|
+        raise s
+      end
+      """
+    When I run cucumber "--format json features/pystring.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": [
+        {
+          "keyword": "Feature",
+          "name": "A screenshot feature",
+          "line": 1,
+          "description": "",
+          "elements": [
+            {
+              "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/stats_formatters.feature

@@ -0,0 +1,70 @@
+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>
+          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:12
+      /B/       # features/step_definitions/steps.rb:2
+        Given B # features/f.feature:5
+      /C/       # features/step_definitions/steps.rb:3
+        Given C # features/f.feature:13
+      /D/       # features/step_definitions/steps.rb:4
+        NOT MATCHED BY ANY STEPS
+      
+      3 scenarios (3 skipped)
+      7 steps (7 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)
+        7 steps (7 skipped)
+        0m0.012s
+
+        """