cucumber 0.4.3 → 0.4.4

data/History.txt

@@ -1,3 +1,27 @@
+== 0.4.4 2009-11-13
+
+What a bad day to make a release, but here goes.
+
+=== New features
+* Cucumber should use ActiveSupport::Callbacks for fixtures (#516 Adam Salter)
+* Make 'I' optional in all webrat steps. (Gavin Hughes)
+* Make generated cucumber.rake work with a vendored gem (Alex Rothenberg)
+* Native support for ANSIColor on IronRuby via the iron-term-ansicolor gem (Will Green)
+* Call a bunch of steps from step definitions - also with tables or pystrings. Copy-paste friendly (Bodaniel Jeanes, Jack Chen, Aslak Hellesøy) TODO - WIKI DOCUMENTATION BEFORE RELEASE
+
+=== Bugfixes
+* Pretty printer fails when expanding scenario outlines with -x when the background includes a table (#515 Mike Sassak)
+* Ensure tags used with Before/After hooks always get parsed (#520 Joseph Wilk)
+* Define IRONRUBY correctly on Ruby 1.9 (Joe Van Dyk)
+* RbStepDefinition#invoke calls #backtrace_line on self rather than @proc (#503 Mike Sassak)
+* Avoid duplicate cucumber entries in database.yml (Daniel Hofstetter)
+* Added respond_to? when checking config.cache_classes for older Rails versions (Jeremy Durham)
+
+=== Changed Features
+* The code for Czech has changed from cz to cs. (deepj)
+* $cucumber_interrupted is now Cucumber.wants_to_quit - avoid global variable, which gives warnings. (Aslak Hellesøy)
+* Examples keyword without a colon is deprecated loudly. Gherkin will not recognize it at all. (Gherkin #30 Mike Sassak)
+
 == 0.4.3 2009-10-28
 
 The exciting thing about this release is that the wire protocol is starting to take shape. This means you can
@@ -16,6 +40,9 @@ As usual there are several small features and bug fixes.
 * Show scenario and step summary in HTML formatter (#285 Joseph Wilk)
 * Ast::Table can now be constructed with an Array of Hash. (Aslak Hellesøy)
 
+=== Changed features
+* The #announce method will no longer escape HTML if the html formatter is used. Escaping must be done manually. (Aslak Hellesøy)
+
 === Bugfixes
 * Fixed incorrect rendering of step arguments with UTF8 characters (Aslak Hellesøy)
 * "--format rerun", with a Scenario Outline, kills cucumber (#492 Aslak Hellesøy)

data/VERSION.yml

@@ -1,4 +1,5 @@
 --- 
-:minor: 4
-:patch: 3
+:patch: 4
 :major: 0
+:minor: 4
+:build: 

data/cucumber.gemspec

@@ -1,15 +1,15 @@
 # Generated by jeweler
-# DO NOT EDIT THIS FILE
-# Instead, edit Jeweler::Tasks in Rakefile, and run `rake gemspec`
+# DO NOT EDIT THIS FILE DIRECTLY
+# Instead, edit Jeweler::Tasks in Rakefile, and run the gemspec command
 # -*- encoding: utf-8 -*-
 
 Gem::Specification.new do |s|
   s.name = %q{cucumber}
-  s.version = "0.4.3"
+  s.version = "0.4.4"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Aslak Helles\303\270y"]
-  s.date = %q{2009-10-28}
+  s.date = %q{2009-11-13}
   s.default_executable = %q{cucumber}
   s.description = %q{A BDD tool written in Ruby}
   s.email = %q{cukes@googlegroups.com}
@@ -319,6 +319,7 @@ Gem::Specification.new do |s|
      "features/bug_371.feature",
      "features/bug_464.feature",
      "features/bug_475.feature",
+     "features/call_many_steps.feature",
      "features/cucumber_cli.feature",
      "features/cucumber_cli_diff_disabled.feature",
      "features/cucumber_cli_outlines.feature",
@@ -430,10 +431,14 @@ Gem::Specification.new do |s|
      "lib/cucumber/language_support/language_methods.rb",
      "lib/cucumber/languages.yml",
      "lib/cucumber/parser.rb",
+     "lib/cucumber/parser/common.rb",
+     "lib/cucumber/parser/common.tt",
      "lib/cucumber/parser/feature.rb",
      "lib/cucumber/parser/feature.tt",
      "lib/cucumber/parser/i18n.tt",
      "lib/cucumber/parser/natural_language.rb",
+     "lib/cucumber/parser/py_string.rb",
+     "lib/cucumber/parser/py_string.tt",
      "lib/cucumber/parser/table.rb",
      "lib/cucumber/parser/table.tt",
      "lib/cucumber/parser/treetop_ext.rb",
@@ -542,7 +547,7 @@ Gem::Specification.new do |s|
 
                      (::)   U P G R A D I N G    (::)
 
-Thank you for installing cucumber-0.4.3.
+Thank you for installing cucumber-0.4.4.
 Please be sure to read http://wiki.github.com/aslakhellesoy/cucumber/upgrading
 for important information about this release. Happy cuking!
 
@@ -742,3 +747,4 @@ for important information about this release. Happy cuking!
     s.add_dependency(%q<spork>, ["= 0.7.3"])
   end
 end
+

data/examples/watir/features/support/screenshots.rb

@@ -11,8 +11,7 @@ module Screenshots
     embed("#{id}.png", "image/png")
   end
 
-  if `which screencapture` =~ /screencapture/
-    # OS X
+  if Cucumber::OS_X
     def take_screenshot(id)
       `screencapture -t png #{id}.png`
     end

data/features/call_many_steps.feature

@@ -0,0 +1,124 @@
+Feature: http://gist.github.com/221223
+  In order to make it easier to extract several steps from
+  a feature file to a step definition I want to be able to
+  copy and paste.
+
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/f.feature" with:
+      """
+      Feature: Test
+
+        Scenario: Multiline string
+          Given a multiline string:
+             \"\"\"
+             hello
+             world
+             \"\"\"
+
+        Scenario: Call a multiline string
+          Given I call a multiline string with MAMA
+
+        Scenario: Call a table
+          Given I call a table with MAMA
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^a multiline string:$/ do |s|
+        raise "I got multiline:\n#{s}"
+      end
+
+      Given /^a table:$/ do |t|
+        raise "I got table:\n#{t.raw.inspect}"
+      end
+
+      Given /^I call a multiline string with (.*)$/ do |s|
+        steps %Q{
+          Given a multiline string:
+            \"\"\"
+            hello
+            #{s}
+            \"\"\"
+        }
+      end
+
+      Given /^I call a table with (.*)$/ do |s|
+        steps %Q{
+          Given a table:
+            |a|b|
+            |c|#{s}|
+        }
+      end
+      """
+
+  Scenario: Multiline string
+    When I run cucumber features/f.feature:6
+    Then STDERR should be empty
+    And it should fail with
+      """
+      Feature: Test
+
+        Scenario: Multiline string  # features/f.feature:3
+          Given a multiline string: # features/step_definitions/steps.rb:1
+            \"\"\"
+            hello
+            world
+            \"\"\"
+            I got multiline:
+            hello
+            world (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^a multiline string:$/'
+            features/f.feature:4:in `Given a multiline string:'
+
+      Failing Scenarios:
+      cucumber features/f.feature:3 # Scenario: Multiline string
+      
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+
+  Scenario: Call multiline string
+    When I run cucumber features/f.feature:10
+    Then STDERR should be empty
+    And it should fail with
+      """
+      Feature: Test
+
+        Scenario: Call a multiline string           # features/f.feature:10
+          Given I call a multiline string with MAMA # features/step_definitions/steps.rb:9
+            I got multiline:
+            hello
+            MAMA (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^a multiline string:$/'
+            features/f.feature:11:in `Given I call a multiline string with MAMA'
+
+      Failing Scenarios:
+      cucumber features/f.feature:10 # Scenario: Call a multiline string
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+
+  Scenario: Call table
+    When I run cucumber features/f.feature:13
+    Then STDERR should be empty
+    And it should fail with
+      """
+      Feature: Test
+
+        Scenario: Call a table           # features/f.feature:13
+          Given I call a table with MAMA # features/step_definitions/steps.rb:19
+            I got table:
+            [["a", "b"], ["c", "MAMA"]] (RuntimeError)
+            ./features/step_definitions/steps.rb:6:in `/^a table:$/'
+            features/f.feature:14:in `Given I call a table with MAMA'
+
+      Failing Scenarios:
+      cucumber features/f.feature:13 # Scenario: Call a table
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """

data/features/default_snippets.feature

@@ -27,11 +27,11 @@ Feature: Print snippets
       You can implement step definitions for undefined steps with these snippets:
       
       Given /^Z$/ do
-        pending
+        pending # express the regexp above with the code you wish you had
       end
 
       Given /^Q$/ do
-        pending
+        pending # express the regexp above with the code you wish you had
       end
 
       If you want snippets in a different programming language, just make sure a file

data/features/expand.feature

@@ -8,6 +8,12 @@ Feature: --expand option
     And a file named "features/expand_me.feature" with:
       """
       Feature: submit guess
+
+        Background: 
+          Given the players' names:
+            | maker    | breaker   |
+            | Moriarty | Holmes    |
+ 
         Scenario Outline: submit guess
           Given the secret code is <code>
           When I guess <guess>
@@ -26,6 +32,11 @@ Feature: --expand option
       """
       Feature: submit guess
 
+        Background: 
+          Given the players' names:
+            | maker    | breaker |
+            | Moriarty | Holmes  |
+
         Scenario Outline: submit guess
           Given the secret code is <code>
           When I guess <guess>
@@ -44,6 +55,6 @@ Feature: --expand option
               Then the mark should be bbww
 
       2 scenarios (2 undefined)
-      6 steps (6 undefined)
+      8 steps (8 undefined)
       
-      """
+      """

data/features/language_help.feature

@@ -29,8 +29,8 @@ Feature: Language help
       | ar      | Arabic                 | العربية              |
       | bg      | Bulgarian              | български            |
       | cat     | Catalan                | català               |
+      | cs      | Czech                  | Česky                |
       | cy      | Welsh                  | Cymraeg              |
-      | cz      | Czech                  | Česky                |
       | da      | Danish                 | dansk                |
       | de      | German                 | Deutsch              |
       | en      | English                | English              |

data/features/report_called_undefined_steps.feature

@@ -26,7 +26,7 @@ Feature: Cucumber command line
       You can implement step definitions for undefined steps with these snippets:
 
       Given /^this does not exist$/ do
-        pending
+        pending # express the regexp above with the code you wish you had
       end
 
 

data/features/snippet.feature

@@ -8,7 +8,7 @@ Feature: Snippets
     Then the output should contain
       """
       Given /^a pystring$/ do |string|
-        pending
+        pending # express the regexp above with the code you wish you had
       end
       """
   Scenario: Snippet for undefined step with a step table
@@ -17,6 +17,6 @@ Feature: Snippets
       """
       Given /^a table$/ do |table|
         # table is a Cucumber::Ast::Table
-        pending
+        pending # express the regexp above with the code you wish you had
       end
       """

data/features/support/env.rb

@@ -111,14 +111,12 @@ class CucumberWorld
         exec cmd
       end
     end
-    sleep 1.0
+    sleep (ENV["RUN_CODE_RUN"] ? 5.0 : 1.0)
   end
 
   def terminate_background_jobs
-    if @background_jobs
-      @background_jobs.each do |pid|
-        Process.kill(Signal.list['TERM'], pid)
-      end
+    background_jobs.each do |pid|
+      Process.kill(Signal.list['TERM'], pid)
     end
   end
 

data/features/tag_logic.feature

@@ -145,6 +145,38 @@ Feature: Tag logic
 
       """
 
+  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:
       """

data/features/wire_protocol.feature

@@ -31,7 +31,7 @@ Feature: Wire Protocol
     And a file named "features/step_definitions/some_remote_place.wire" with:
       """
       host: localhost
-      port: 98989
+      port: 54321
 
       """
 
@@ -45,7 +45,7 @@ Feature: Wire Protocol
   # be invoked for the given step name.
 
   Scenario: Dry run finds no step match
-    Given there is a wire server running on port 98989 which understands the following protocol:
+    Given 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"}] | ["step_matches",[]] |
     When I run cucumber --dry-run -f progress features
@@ -65,7 +65,7 @@ Feature: Wire Protocol
   # The step match also contains any argument values as parsed out by the wire end's own regular
   # expression or other argument matching process.
   Scenario: Dry run finds a step match
-    Given there is a wire server running on port 98989 which understands the following protocol:
+    Given 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"}] | ["step_matches",[{"id":"1", "args":[]}]] |
     When I run cucumber --dry-run -f progress features
@@ -90,7 +90,7 @@ Feature: Wire Protocol
   # The wire end will reply with either a step_failed or a success message.
 
   Scenario: Invoke a step definition which passes
-    Given there is a wire server running on port 98989 which understands the following protocol:
+    Given 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"}] | ["step_matches",[{"id":"1", "args":[]}]] |
       | ["begin_scenario",null]                              | ["success",null]                         |
@@ -110,7 +110,7 @@ Feature: Wire Protocol
   # will then be passed by Cucumber to the formatters for display to the user.
   #
   Scenario: Invoke a step definition which fails
-    Given there is a wire server running on port 98989 which understands the following protocol:
+    Given 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"}] | ["step_matches",[{"id":"1", "args":[]}]]         |
       | ["begin_scenario",null]                              | ["success",null]                                 |
@@ -148,7 +148,7 @@ Feature: Wire Protocol
   #   * pos : the position within the step name that the argument was matched (used for formatter highlighting)
   #
   Scenario: Invoke a step definition which takes arguments (and passes)
-    Given there is a wire server running on port 98989 which understands the following protocol:
+    Given 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"}] | ["step_matches",[{"id":"1", "args":[{"val":"wired", "pos":10}]}]] |
       | ["begin_scenario",null]                              | ["success",null]                                                  |
@@ -167,7 +167,7 @@ Feature: Wire Protocol
 
 
   Scenario: Unexpected response
-    Given there is a wire server running on port 98989 which understands the following protocol:
+    Given there is a wire server running on port 54321 which understands the following protocol:
       | request                                              | response   |
       | ["begin_scenario",null]                              | ["yikes"]  |
     When I run cucumber -f progress features

data/lib/cucumber.rb

@@ -7,3 +7,9 @@ require 'cucumber/parser'
 require 'cucumber/step_mother'
 require 'cucumber/cli/main'
 require 'cucumber/broadcaster'
+
+module Cucumber
+  class << self
+    attr_accessor :wants_to_quit
+  end
+end