stefl-cucumber 0.10.1

data/legacy_features/wire_protocol_tags.feature

@@ -0,0 +1,87 @@
+@wire
+Feature: Wire protocol tags
+  In order to use Before and After hooks in a wire server, we send tags with the 
+  scenario in the begin_scenario and end_scenario messages
+
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/some_remote_place.wire" with:
+      """
+      host: localhost
+      port: 54321
+
+      """
+
+  Scenario: Run a scenario
+    Given a file named "features/wired.feature" with:
+      """
+        @foo @bar
+        Feature: Wired
+        
+          @baz
+          Scenario: Everybody's Wired
+            Given we're all wired
+
+      """
+    And there is a wire server running on port 54321 which understands the following protocol:
+      | request                                              | response                            |
+      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
+      | ["begin_scenario", {"tags":["bar","baz","foo"]}]     | ["success"]                         |
+      | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
+      | ["end_scenario", {"tags":["bar","baz","foo"]}]       | ["success"]                         |
+    When I run cucumber -f pretty -q
+    Then STDERR should be empty
+    And it should pass with
+      """
+      @foo @bar
+      Feature: Wired
+      
+        @baz
+        Scenario: Everybody's Wired
+          Given we're all wired
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Run a scenario outline example
+  Given a file named "features/wired.feature" with:
+    """
+      @foo @bar
+      Feature: Wired
+      
+        @baz
+        Scenario Outline: Everybody's Wired
+          Given we're all <something>
+          
+        Examples:
+          | something |
+          | wired     |
+
+    """
+  And there is a wire server running on port 54321 which understands the following protocol:
+    | request                                              | response                            |
+    | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[]}]] |
+    | ["begin_scenario", {"tags":["bar","baz","foo"]}]     | ["success"]                         |
+    | ["invoke",{"id":"1","args":[]}]                      | ["success"]                         |
+    | ["end_scenario", {"tags":["bar","baz","foo"]}]       | ["success"]                         |
+  When I run cucumber -f pretty -q
+  Then STDERR should be empty
+  And it should pass with
+    """
+    @foo @bar
+    Feature: Wired
+    
+      @baz
+      Scenario Outline: Everybody's Wired
+        Given we're all <something>
+
+        Examples: 
+          | something |
+          | wired     |
+
+    1 scenario (1 passed)
+    1 step (1 passed)
+
+    """

data/legacy_features/wire_protocol_timeouts.feature

@@ -0,0 +1,63 @@
+@wire
+Feature: Wire protocol timeouts
+  We don't want Cucumber to hang forever on a wire server that's not even there,
+  but equally we need to give the user the flexibility to allow step definitions
+  to take a while to execute, if that's what they need.
+
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/wired.feature" with:
+      """
+      Feature: Telegraphy
+        Scenario: Wired
+          Given we're all wired
+
+      """
+
+  Scenario: Try to talk to a server that's not there
+    Given a file named "features/step_definitions/some_remote_place.wire" with:
+      """
+      host: localhost
+      port: 54321
+
+      """
+    When I run cucumber -f progress
+    Then STDERR should match
+      """
+      Unable to contact the wire server at localhost:54321
+      """
+
+  Scenario: Invoke a step definition that takes longer than its timeout
+    Given a file named "features/step_definitions/some_remote_place.wire" with:
+      """
+      host: localhost
+      port: 54321
+      timeout:
+        invoke: 0.1
+
+      """
+    And there is a wire server on port 54321 which understands the following protocol:
+      | request                                              | response                                                     |
+      | ["step_matches",{"name_to_match":"we're all wired"}] | ["success",[{"id":"1", "args":[{"val":"wired", "pos":10}]}]] |
+      | ["begin_scenario"]                                   | ["success"]                                                  |
+      | ["invoke",{"id":"1","args":["wired"]}]               | ["success"]                                                  |
+      | ["end_scenario"]                                     | ["success"]                                                  |
+    And the wire server takes 0.2 seconds to respond to the invoke message
+    When I run cucumber -f pretty
+    Then STDERR should be empty
+    And it should fail with
+      """
+      Feature: Telegraphy
+
+        Scenario: Wired         # features/wired.feature:2
+          Given we're all wired # Unknown
+            Timed out calling wire server with message 'invoke' (Timeout::Error)
+            features/wired.feature:3:in `Given we're all wired'
+
+      Failing Scenarios:
+      cucumber features/wired.feature:2 # Scenario: Wired
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """

data/legacy_features/work_in_progress.feature

@@ -0,0 +1,156 @@
+Feature: Cucumber --work-in-progress switch
+  In order to ensure that feature scenarios do not pass until they are expected to
+  Developers should be able to run cucumber in a mode that
+            - will fail if any scenario passes completely
+            - will not fail otherwise
+
+  Background: A passing and a pending feature
+    Given a standard Cucumber project directory structure
+    Given a file named "features/wip.feature" with:
+      """
+      Feature: WIP
+        @failing
+        Scenario: Failing
+          Given a failing step
+
+        @undefined
+        Scenario: Undefined
+          Given an undefined step
+
+        @pending
+        Scenario: Pending
+          Given a pending step
+
+        @passing
+        Scenario: Passing
+          Given a passing step
+      """
+    And a file named "features/passing_outline.feature" with:
+      """
+      Feature: Not WIP
+        Scenario Outline: Passing
+          Given a <what> step
+          
+          Examples:
+            | what    |
+            | passing |
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^a failing step$/ do
+        raise "I fail"
+      end
+
+      Given /^a passing step$/ do
+      end
+
+      Given /^a pending step$/ do
+        pending
+      end
+      """
+
+  Scenario: Pass with Failing Scenarios
+    When I run cucumber -q -w -t @failing features/wip.feature
+    Then STDERR should be empty
+    Then it should pass with
+      """
+      Feature: WIP
+
+        @failing
+        Scenario: Failing
+          Given a failing step
+            I fail (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^a failing step$/'
+            features/wip.feature:4:in `Given a failing step'
+      
+      Failing Scenarios:
+      cucumber features/wip.feature:3 # Scenario: Failing
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      The --wip switch was used, so the failures were expected. All is good.
+
+      """
+
+  Scenario: Pass with Undefined Scenarios
+    When I run cucumber -q -w -t @undefined features/wip.feature
+    Then it should pass with
+      """
+      Feature: WIP
+
+        @undefined
+        Scenario: Undefined
+          Given an undefined step
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      The --wip switch was used, so the failures were expected. All is good.
+
+      """
+
+  Scenario: Pass with Undefined Scenarios
+    When I run cucumber -q -w -t @pending features/wip.feature
+    Then it should pass with
+      """
+      Feature: WIP
+
+        @pending
+        Scenario: Pending
+          Given a pending step
+            TODO (Cucumber::Pending)
+            ./features/step_definitions/steps.rb:9:in `/^a pending step$/'
+            features/wip.feature:12:in `Given a pending step'
+
+      1 scenario (1 pending)
+      1 step (1 pending)
+
+      The --wip switch was used, so the failures were expected. All is good.
+
+      """
+
+  Scenario: Fail with Passing Scenarios
+    When I run cucumber -q -w -t @passing features/wip.feature
+    Then it should fail with
+      """
+      Feature: WIP
+
+        @passing
+        Scenario: Passing
+          Given a passing step
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
+      (::) passed scenarios (::)
+
+      features/wip.feature:15:in `Scenario: Passing'
+
+
+      """
+
+  Scenario: Fail with Passing Scenario Outline
+    When I run cucumber -q -w features/passing_outline.feature
+    Then it should fail with
+      """
+      Feature: Not WIP
+
+        Scenario Outline: Passing
+          Given a <what> step
+      
+          Examples: 
+            | what    |
+            | passing |
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
+      (::) passed scenarios (::)
+
+      features/passing_outline.feature:7:in `| passing |'
+
+
+      """

data/lib/README.rdoc

@@ -0,0 +1,12 @@
+= Cucumber API
+
+This is the public API of Cucumber. The public API includes the classes, modules
+and methods you can use if you are a user of Cucumber. It also applies to you if
+you're developing a 3rd party tool that integrates with Cucumber.
+
+== Internal API
+
+Cucumber has more classes, modules and methods than what you can see in the public
+API. If you decide to dive into the source code and make use of an API that isn't
+part of this documentation - beware that this API might change at any time. If you
+want a particular internal API to be promoted to the public API - let us know.

data/lib/autotest/cucumber.rb

@@ -0,0 +1,6 @@
+require 'autotest'
+require 'autotest/cucumber_mixin'
+
+class Autotest::Cucumber < Autotest
+  include CucumberMixin
+end

data/lib/autotest/cucumber_mixin.rb

@@ -0,0 +1,135 @@
+require 'autotest'
+require 'tempfile'
+require 'cucumber'
+require 'cucumber/cli/profile_loader'
+
+module Autotest::CucumberMixin
+  def self.included(receiver)
+    receiver::ALL_HOOKS << [:run_features, :ran_features]
+  end
+  
+  attr_accessor :features_to_run
+  
+  def initialize
+    super
+    reset_features
+  end
+  
+  def run
+    hook :initialize
+    reset
+    reset_features
+    add_sigint_handler
+
+    self.last_mtime = Time.now if $f
+
+    loop do # ^c handler
+      begin
+        get_to_green
+        if self.tainted then
+          rerun_all_tests
+          rerun_all_features if all_good
+        else
+          hook :all_good
+        end
+        wait_for_changes
+        # Once tests and features are green, reset features every
+        # time a file is changed to see if anything breaks.
+        reset_features
+      rescue Interrupt
+        break if self.wants_to_quit
+        reset
+        reset_features
+      end
+    end
+    hook :quit
+  end
+  
+  def all_features_good
+    features_to_run == ""
+  end
+  
+  def get_to_green
+    begin
+      super
+      run_features
+      wait_for_changes unless all_features_good
+    end until all_features_good
+  end
+  
+  def rerun_all_features
+    reset_features
+    run_features
+  end
+  
+  def reset_features
+    self.features_to_run = :all
+  end
+    
+  def run_features
+    hook :run_features
+    Tempfile.open('autotest-cucumber') do |dirty_features_file|
+      cmd = self.make_cucumber_cmd(self.features_to_run, dirty_features_file.path)
+      return if cmd.empty?
+      puts cmd unless $q
+      old_sync = $stdout.sync
+      $stdout.sync = true
+      self.results = []
+      line = []
+      begin
+        open("| #{cmd}", "r") do |f|
+          until f.eof? do
+            c = f.getc or break
+            if RUBY_VERSION >= "1.9" then
+              print c
+            else
+              putc c
+            end
+            line << c
+            if c == ?\n then
+              self.results << if RUBY_VERSION >= "1.9" then
+                                line.join
+                              else
+                                line.pack "c*"
+                              end
+              line.clear
+            end
+          end
+        end
+      ensure
+        $stdout.sync = old_sync
+      end
+      self.features_to_run = dirty_features_file.read.strip
+      self.tainted = true unless self.features_to_run == ''
+    end
+    hook :ran_features
+  end
+  
+  def make_cucumber_cmd(features_to_run, dirty_features_filename)
+    return '' if features_to_run == ''
+    
+    profile_loader = Cucumber::Cli::ProfileLoader.new
+    
+    profile ||= "autotest-all" if profile_loader.has_profile?("autotest-all") && features_to_run == :all
+    profile ||= "autotest"     if profile_loader.has_profile?("autotest")
+    profile ||= nil
+    
+    if profile
+      args = ["--profile", profile]
+    else
+      args = %w{--format} << (features_to_run == :all ? "progress" : "pretty")
+    end
+    # No --color option as some IDEs (Netbeans) don't output them very well (1 failed step)
+    args += %w{--format rerun --out} << dirty_features_filename
+    args << (features_to_run == :all ? "" : features_to_run)
+    
+    # Unless I do this, all the steps turn up undefined during the rerun...
+    unless features_to_run == :all
+      args << 'features/step_definitions' << 'features/support'
+    end
+    
+    args = args.join(' ')
+
+    return "#{Cucumber::RUBY_BINARY} #{Cucumber::BINARY} #{args}"
+  end
+end