stefl-cucumber 0.10.1

data/features/step_definitions/cucumber_steps.rb

@@ -0,0 +1,8 @@
+When /^I run cucumber "([^"]*)"$/ do |cmd|
+  run_simple(unescape("cucumber #{cmd}"), false)
+end
+
+Then /^it should (pass|fail) with JSON:$/ do |pass_fail, json|
+  JSON.parse(all_stdout).should == JSON.parse(json)
+  assert_exiting_with(pass_fail == 'pass')
+end

data/features/support/env.rb

@@ -0,0 +1,31 @@
+require 'aruba/api'
+
+# Monkey patch aruba to filter out some stuff
+module Aruba::Api
+  alias _all_stdout all_stdout
+  
+  def all_stdout
+    out = _all_stdout
+
+    # Remove absolute paths
+    out.gsub!(/#{Dir.pwd}\/tmp\/aruba/, '.') 
+    # Make duration predictable
+    out.gsub!(/^\d+m\d+\.\d+s$/, '0m0.012s')
+    # Remove SimpleCov message
+    out.gsub!(/Coverage report generated for Cucumber Features to #{Dir.pwd}\/coverage\n$/, '')
+    
+    out
+  end
+end
+
+require 'aruba/cucumber'
+
+Before do |scenario|
+  @scenario = scenario
+
+  # Make sure bin/cucumber runs with SimpleCov enabled
+  set_env('SIMPLECOV', 'true')
+  
+  # Set a longer timeout for aruba
+  @aruba_timeout_seconds = 5
+end

data/features/tagged_hooks.feature

@@ -0,0 +1,217 @@
+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: Before hooks ORing
+    Given a file named "features/support/hooks.rb" with:
+      """
+      Before('@one,@three') do
+        raise 'boom'
+      end
+      """
+    When I run "cucumber -q features/tagulicious.feature"
+    Then it should fail with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+       boom (RuntimeError)
+       ./features/support/hooks.rb:2:in `Before'
+          Given passing
+
+        @one
+        Scenario: Another Example
+       boom (RuntimeError)
+       ./features/support/hooks.rb:2:in `Before'
+          Given passing
+
+        @three
+        Scenario: Yet another Example
+       boom (RuntimeError)
+       ./features/support/hooks.rb:2:in `Before'
+          Given passing
+
+        @ignore
+        Scenario: And yet another Example
+
+      Failing Scenarios:
+      cucumber features/tagulicious.feature:4 # Scenario: Example
+      cucumber features/tagulicious.feature:8 # Scenario: Another Example
+      cucumber features/tagulicious.feature:12 # Scenario: Yet another Example
+
+      4 scenarios (3 failed, 1 passed)
+      3 steps (3 undefined)
+
+      """
+
+  Scenario: Before hooks ANDing
+    Given a file named "features/support/hooks.rb" with:
+      """
+      Before('@one','@three') do
+        raise 'boom'
+      end
+      """
+    When I run "cucumber -q features/tagulicious.feature"
+    Then it should fail with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+       boom (RuntimeError)
+       ./features/support/hooks.rb:2:in `Before'
+          Given passing
+
+        @one
+        Scenario: Another Example
+          Given passing
+
+        @three
+        Scenario: Yet another Example
+          Given passing
+
+        @ignore
+        Scenario: And yet another Example
+
+      Failing Scenarios:
+      cucumber features/tagulicious.feature:4 # Scenario: Example
+
+      4 scenarios (1 failed, 2 undefined, 1 passed)
+      3 steps (3 undefined)
+
+      """
+
+  Scenario: Before hooks ANDing with a bad hook matching nothing
+    Given a file named "features/support/hooks.rb" with:
+      """
+      Before('@one','@notused') do
+        raise 'boom'
+      end
+      """
+    When I run "cucumber -q 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
+
+        @ignore
+        Scenario: And yet another Example
+
+      4 scenarios (3 undefined, 1 passed)
+      3 steps (3 undefined)
+
+      """
+
+  Scenario: After hooks ORing
+    Given a file named "features/support/hooks.rb" with:
+      """
+      After('@one,@three') do
+        raise 'boom'
+      end
+      """
+    When I run "cucumber -q features/tagulicious.feature"
+    Then it should fail with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+          Given passing
+            boom (RuntimeError)
+            ./features/support/hooks.rb:2:in `After'
+
+        @one
+        Scenario: Another Example
+          Given passing
+            boom (RuntimeError)
+            ./features/support/hooks.rb:2:in `After'
+
+        @three
+        Scenario: Yet another Example
+          Given passing
+            boom (RuntimeError)
+            ./features/support/hooks.rb:2:in `After'
+
+        @ignore
+        Scenario: And yet another Example
+
+      Failing Scenarios:
+      cucumber features/tagulicious.feature:4 # Scenario: Example
+      cucumber features/tagulicious.feature:8 # Scenario: Another Example
+      cucumber features/tagulicious.feature:12 # Scenario: Yet another Example
+
+      4 scenarios (3 failed, 1 passed)
+      3 steps (3 undefined)
+
+      """
+
+  Scenario: After hooks ANDing
+    Given a file named "features/support/hooks.rb" with:
+      """
+      After('@one','@three') do
+        raise 'boom'
+      end
+      """
+    When I run "cucumber -q features/tagulicious.feature"
+    Then it should fail with:
+      """
+      Feature: Sample
+
+        @one @three
+        Scenario: Example
+          Given passing
+            boom (RuntimeError)
+            ./features/support/hooks.rb:2:in `After'
+
+        @one
+        Scenario: Another Example
+          Given passing
+
+        @three
+        Scenario: Yet another Example
+          Given passing
+
+        @ignore
+        Scenario: And yet another Example
+
+      Failing Scenarios:
+      cucumber features/tagulicious.feature:4 # Scenario: Example
+
+      4 scenarios (1 failed, 2 undefined, 1 passed)
+      3 steps (3 undefined)
+
+      """

data/fixtures/json/features/background.feature

@@ -0,0 +1,7 @@
+Feature: Feature with background
+  
+  Background:
+    Given a passing step
+
+  Scenario: 
+    Given a failing step

data/fixtures/json/features/embed.feature

@@ -0,0 +1,4 @@
+Feature: A screenshot feature
+
+  Scenario:
+    Given I embed a screenshot

data/fixtures/json/features/one_passing_one_failing.feature

@@ -0,0 +1,11 @@
+@a
+Feature: One passing scenario, one failing scenario
+
+  @b
+  Scenario: Passing
+    Given a passing step
+
+  @c
+  Scenario: Failing
+    Given a failing step
+

data/fixtures/json/features/step_definitions/steps.rb

@@ -0,0 +1,32 @@
+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("tmp/screenshot.png", "w") { |file| file << "foo" }
+  embed "tmp/screenshot.png", "image/png"
+end

data/fixtures/json/features/tables.feature

@@ -0,0 +1,13 @@
+Feature: A scenario outline
+
+  Scenario Outline:
+    Given I add <a> and <b>
+    When I pass a table argument
+      | foo | bar |
+      | bar | baz |
+    Then I the result should be <c>
+
+    Examples:
+      | a   | b   | c |
+      | 1   | 2   | 3 |
+      | 2   | 3   | 4 |

data/fixtures/junit/features/one_passing_one_failing.feature

@@ -0,0 +1,8 @@
+Feature: One passing scenario, one failing scenario
+
+  Scenario: Passing
+    Given a passing scenario
+    
+  Scenario: Failing
+    Given a failing scenario
+    

data/fixtures/junit/features/pending.feature

@@ -0,0 +1,5 @@
+Feature: Pending step
+
+  Scenario: Pending
+    Given a pending step
+    

data/fixtures/junit/features/step_definitions/steps.rb

@@ -0,0 +1,11 @@
+Given /a passing scenario/ do
+  #does nothing
+end
+
+Given /a failing scenario/ do
+  fail
+end
+
+Given /a pending step/ do
+  pending
+end

data/fixtures/self_test/.gitignore

@@ -0,0 +1 @@
+tmp

data/fixtures/self_test/README.textile

@@ -0,0 +1,6 @@
+h1. Self Test
+
+Cucumber's own features (ROOT_DIR/features) run the features in this directory and look at the output.
+
+Note that several of these fail intentionally. The purpose is to verify actual output against expected
+output.

data/fixtures/self_test/Rakefile

@@ -0,0 +1,6 @@
+$:.unshift(File.dirname(__FILE__) + '/../../lib')
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new(:features)
+
+task :default => :features

data/fixtures/self_test/features/call_undefined_step_from_step_def.feature

@@ -0,0 +1,7 @@
+Feature: Calling undefined step
+  
+  Scenario: Call directly
+    Given a step definition that calls an undefined step
+    
+  Scenario: Call via another
+    Given call step "a step definition that calls an undefined step"

data/fixtures/self_test/features/failing_expectation.feature

@@ -0,0 +1,4 @@
+Feature: Failing expectation
+
+  Scenario: Failing expectation
+    Given failing expectation

data/fixtures/self_test/features/lots_of_undefined.feature

@@ -0,0 +1,8 @@
+Feature: Lots of undefined
+
+  Scenario: Implement me
+    Given it snows in Sahara
+    Given it's 40 degrees in Norway
+    And it's 40 degrees in Norway
+    When I stop procrastinating
+    And there is world peace

data/fixtures/self_test/features/multiline_name.feature

@@ -0,0 +1,27 @@
+Feature: multiline
+
+  Background: I'm a multiline name
+              which goes on and on and on for three lines
+              yawn
+    Given passing without a table
+
+  Scenario: I'm a multiline name
+            which goes on and on and on for three lines
+            yawn
+    Given passing without a table
+
+  Scenario Outline: I'm a multiline name
+                    which goes on and on and on for three lines
+                    yawn
+    Given <state> without a table 
+    Examples:
+      | state |
+      |passing|
+
+  Scenario Outline: name
+    Given <state> without a table 
+    Examples: I'm a multiline name
+              which goes on and on and on for three lines
+              yawn
+      | state |
+      |passing|

data/fixtures/self_test/features/outline_sample.feature

@@ -0,0 +1,15 @@
+Feature: Outline Sample
+
+  Scenario: I have no steps
+
+  Scenario Outline: Test state
+    Given <state> without a table
+    Given <other_state> without a table
+  Examples: Rainbow colours
+    |  state   | other_state |
+    | missing |  passing|
+    | passing| passing |
+| failing | passing |
+Examples:Only passing
+|  state   | other_state |
+| passing  | passing |