rspec 1.3.0 → 2.0.0

data/features/matchers/define_matcher.feature

@@ -1,179 +0,0 @@
-Feature: define matcher
-
-  In order to express my domain clearly in my code examples
-  As an RSpec user
-  I want a shortcut to define custom matchers
-
-  Scenario: define a matcher with default messages
-    Given a file named "matcher_with_default_message_spec.rb" with:
-      """
-      Spec::Matchers.define :be_a_multiple_of do |expected|
-        match do |actual|
-          actual % expected == 0
-        end
-      end
-
-      describe 9 do
-        it {should be_a_multiple_of(3)}
-      end
-
-      describe 9 do
-        it {should_not be_a_multiple_of(4)}
-      end
-
-      # fail intentionally to generate expected output
-      describe 9 do
-        it {should be_a_multiple_of(4)}
-      end
-
-      # fail intentionally to generate expected output
-      describe 9 do
-        it {should_not be_a_multiple_of(3)}
-      end
-
-      """
-    When I run "spec matcher_with_default_message_spec.rb --format specdoc"
-    Then the exit code should be 256
-
-    And the stdout should include "should be a multiple of 3"
-    And the stdout should include "should not be a multiple of 4"
-    And the stdout should include "should be a multiple of 4 (FAILED - 1)"
-    And the stdout should include "should not be a multiple of 3 (FAILED - 2)"
-
-    And the stdout should include "4 examples, 2 failures"
-    And the stdout should include "expected 9 to be a multiple of 4"
-    And the stdout should include "expected 9 not to be a multiple of 3"
-
-  Scenario: overriding the failure_message_for_should
-    Given a file named "matcher_with_failure_message_spec.rb" with:
-      """
-      Spec::Matchers.define :be_a_multiple_of do |expected|
-        match do |actual|
-          actual % expected == 0
-        end
-        failure_message_for_should do |actual|
-          "expected that #{actual} would be a multiple of #{expected}"
-        end
-      end
-
-      # fail intentionally to generate expected output
-      describe 9 do
-        it {should be_a_multiple_of(4)}
-      end
-      """
-    When I run "spec matcher_with_failure_message_spec.rb"
-    Then the exit code should be 256
-    And the stdout should include "1 example, 1 failure"
-    And the stdout should include "expected that 9 would be a multiple of 4"
-
-  Scenario: overriding the failure_message_for_should_not
-    Given a file named "matcher_with_failure_for_message_spec.rb" with:
-      """
-      Spec::Matchers.define :be_a_multiple_of do |expected|
-        match do |actual|
-          actual % expected == 0
-        end
-        failure_message_for_should_not do |actual|
-          "expected that #{actual} would not be a multiple of #{expected}"
-        end
-      end
-
-      # fail intentionally to generate expected output
-      describe 9 do
-        it {should_not be_a_multiple_of(3)}
-      end
-      """
-    When I run "spec matcher_with_failure_for_message_spec.rb"
-    Then the exit code should be 256
-    And the stdout should include "1 example, 1 failure"
-    And the stdout should include "expected that 9 would not be a multiple of 3"
-
-  Scenario: overriding the description
-    Given a file named "matcher_overriding_description_spec.rb" with:
-      """
-      Spec::Matchers.define :be_a_multiple_of do |expected|
-        match do |actual|
-          actual % expected == 0
-        end
-        description do
-          "be multiple of #{expected}"
-        end
-      end
-
-      describe 9 do
-        it {should be_a_multiple_of(3)}
-      end
-
-      describe 9 do
-        it {should_not be_a_multiple_of(4)}
-      end
-      """
-    When I run "spec matcher_overriding_description_spec.rb --format specdoc"
-    Then the exit code should be 0
-    And the stdout should include "2 examples, 0 failures"
-    And the stdout should include "should be multiple of 3"
-    And the stdout should include "should not be multiple of 4"
-
-  Scenario: with no args
-    Given a file named "matcher_with_no_args_spec.rb" with:
-      """
-      Spec::Matchers.define :have_7_fingers do
-        match do |thing|
-          thing.fingers.length == 7
-        end
-      end
-
-      class Thing
-        def fingers; (1..7).collect {"finger"}; end
-      end
-
-      describe Thing do
-        it {should have_7_fingers}
-      end
-      """
-    When I run "spec matcher_with_no_args_spec.rb --format specdoc"
-    Then the exit code should be 0
-    And the stdout should include "1 example, 0 failures"
-    And the stdout should include "should have 7 fingers"
-
-  Scenario: with multiple args
-    Given a file named "matcher_with_multiple_args_spec.rb" with:
-      """
-      Spec::Matchers.define :be_the_sum_of do |a,b,c,d|
-        match do |sum|
-          a + b + c + d == sum
-        end
-      end
-
-      describe 10 do
-        it {should be_the_sum_of(1,2,3,4)}
-      end
-      """
-    When I run "spec matcher_with_multiple_args_spec.rb --format specdoc"
-    Then the exit code should be 0
-    And the stdout should include "1 example, 0 failures"
-    And the stdout should include "should be the sum of 1, 2, 3, and 4"
-    
-  Scenario: with helper methods
-    Given a file named "matcher_with_internal_helper_spec.rb" with:
-      """
-      Spec::Matchers.define :have_same_elements_as do |sample|
-        match do |actual|
-          similar?(sample, actual)
-        end
-        
-        def similar?(a, b)
-          a.sort == b.sort
-        end
-      end
-      
-      describe "these two arrays" do
-        specify "should be similar" do
-          [1,2,3].should have_same_elements_as([2,3,1])
-        end
-      end
-      """
-    When I run "spec matcher_with_internal_helper_spec.rb"
-    Then the exit code should be 0
-    And the stdout should include "1 example, 0 failures"
-

data/features/matchers/define_matcher_outside_rspec.feature

@@ -1,38 +0,0 @@
-Feature: define matcher outside rspec
-
-  In order to express my domain clearly in my code examples
-  As a non-rspec user
-  I want a shortcut to define custom matchers
-
-  Scenario: define a matcher with default messages
-    Given a file named "test_multiples.rb" with:
-      """
-      require 'test/unit'
-      require 'spec/expectations'
-      
-      Spec::Matchers.define :be_a_multiple_of do |expected|
-        match do |actual|
-          actual % expected == 0
-        end
-      end
-      
-      class Test::Unit::TestCase
-        include Spec::Matchers
-      end
-      
-      class TestMultiples < Test::Unit::TestCase
-      
-        def test_9_should_be_a_multiple_of_3
-          9.should be_a_multiple_of(3)
-        end
-
-        def test_9_should_be_a_multiple_of_4
-          9.should be_a_multiple_of(4)
-        end
-        
-      end
-      """
-    When I run "ruby test_multiples.rb"
-    Then the exit code should be 256
-    And the stdout should include "expected 9 to be a multiple of 4"
-    And the stdout should include "2 tests, 0 assertions, 1 failures, 0 errors"

data/features/matchers/define_matcher_with_fluent_interface.feature

@@ -1,48 +0,0 @@
-Feature: define matcher
-
-  In order to express my domain clearly in my code examples
-  As an RSpec user
-  I want to define matchers with fluent interfaces
-  
-  Scenario: one additional method
-    Given a file named "between_spec.rb" with:
-      """
-      Spec::Matchers.define :be_bigger_than do |first|
-        def but_smaller_than(second)
-          @second = second
-          self
-        end
-        
-        match do |actual|
-          (actual > first) && (actual < @second)
-        end
-      end
-
-      describe 5 do
-        it { should be_bigger_than(4).but_smaller_than(6) }
-      end
-      """
-    When I run "spec between_spec.rb --format specdoc"
-    Then the stdout should include "1 example, 0 failures"
-    And  the stdout should include "should be bigger than 4"
-
-  Scenario: generate method using dsl
-    Given a file named "between_spec.rb" with:
-      """
-      Spec::Matchers.define :be_bigger_than do |first|
-        chain :but_smaller_than do |limit|
-          @limit = limit
-        end
-        
-        match do |actual|
-          (actual > first) && (actual < @limit)
-        end
-      end
-
-      describe 5 do
-        it { should be_bigger_than(4).but_smaller_than(6) }
-      end
-      """
-    When I run "spec between_spec.rb --format specdoc"
-    Then the stdout should include "1 example, 0 failures"
-    And  the stdout should include "should be bigger than 4"

data/features/matchers/define_wrapped_matcher.feature

@@ -1,56 +0,0 @@
-Feature: define wrapped matcher
-
-  In order to reuse existing matchers
-  As an RSpec user
-  I want to define matchers that wrap other matchers
-
-  When the wrapped matcher passes, the wrapping matcher returns true.
-  When the wrapped matcher fails, the wrapping matcher returns false.
-  
-  Scenario: wrap a matcher using should
-    Given a file named "new_model_spec.rb" with:
-      """
-      Spec::Matchers.define :have_tag do |tag|
-        match do |markup|
-          markup =~ /<#{tag}>.*<\/#{tag}>/
-        end
-      end
-      
-      Spec::Matchers.define :have_button do
-        match do |markup|
-          markup.should have_tag('button')
-        end
-      end
-      
-      describe "some markup" do
-        it "has a button" do
-          "<button>Label</button>".should have_button
-        end
-      end
-      """
-    When I run "spec new_model_spec.rb --format specdoc"
-    Then the stdout should include "1 example, 0 failures"
-
-  Scenario: wrap a matcher using should_not
-    Given a file named "new_model_spec.rb" with:
-      """
-      Spec::Matchers.define :have_tag do |tag|
-        match do |markup|
-          markup =~ /<#{tag}>.*<\/#{tag}>/
-        end
-      end
-      
-      Spec::Matchers.define :have_button do
-        match do |markup|
-          markup.should have_tag('button')
-        end
-      end
-      
-      describe "some markup" do
-        it "has no buttons" do
-          "<p>Label</p>".should_not have_button
-        end
-      end
-      """
-    When I run "spec new_model_spec.rb --format specdoc"
-    Then the stdout should include "1 example, 0 failures"

data/features/matchers/match_unless_raises.feature

@@ -1,60 +0,0 @@
-Feature: match unless raises
-
-  In order, primarily, to reuse existing test/unit assertions
-  As an RSpec user
-  I want to define matchers that wrap a statement that raises an error on failure
-
-  Background:
-    Given a file named "example.rb" with:
-      """
-      require 'test/unit/assertions'
-
-      Spec::Matchers.define :be_the_same_as do |expected|
-        extend Test::Unit::Assertions
-        match_unless_raises Test::Unit::AssertionFailedError do |actual|
-          assert_equal expected, actual
-        end
-      end
-      """
-  
-  Scenario: passing examples
-    Given a file named "match_unless_raises_spec.rb" with:
-      """
-      require 'example.rb'
-
-      describe 4 do
-        it "is 4" do
-          4.should be_the_same_as(4)
-        end
-      end
-
-      describe 5 do
-        it "is not 4" do
-          5.should_not be_the_same_as(4)
-        end
-      end
-      """
-    When I run "spec match_unless_raises_spec.rb"
-    Then the stdout should include "2 examples, 0 failures"
-
-  Scenario: failing examples
-    Given a file named "match_unless_raises_spec.rb" with:
-      """
-      require 'example.rb'
-
-      describe 4 do
-        it "is 4" do
-          # intentionally fail
-          4.should_not be_the_same_as(4)
-        end
-      end
-
-      describe 5 do
-        it "is not 4" do
-          # intentionally fail
-          5.should be_the_same_as(4)
-        end
-      end
-      """
-    When I run "spec match_unless_raises_spec.rb"
-    Then the stdout should include "2 examples, 2 failures"

data/features/matchers/match_unless_raises_unexpected_error.feature

@@ -1,39 +0,0 @@
-Feature: match unless raises with an unexpected error
-
-  In order to know when a match_unless_raises block raises an unexpected error
-  As an RSpec user
-  I want the error to bubble up
-
-  Background:
-    Given a file named "example.rb" with:
-      """
-      Spec::Matchers.define :be_the_same_as do |expected|
-        match_unless_raises SyntaxError do |actual|
-          raise "unexpected error"
-        end
-      end
-      """
-  
-  Scenario: failing examples
-    Given a file named "match_unless_raises_spec.rb" with:
-      """
-      require 'example.rb'
-
-      describe 4 do
-        it "is 4" do
-          # intentionally fail
-          4.should_not be_the_same_as(4)
-        end
-      end
-
-      describe 5 do
-        it "is not 4" do
-          # intentionally fail
-          5.should be_the_same_as(4)
-        end
-      end
-      """
-    When I run "spec match_unless_raises_spec.rb"
-    Then the stdout should include "2 examples, 2 failures"
-    Then the stdout should include "unexpected error"
-  

data/features/mock_framework_integration/use_flexmock.feature

@@ -1,27 +0,0 @@
-Feature: mock with flexmock
-
-  As an RSpec user who prefers flexmock
-  I want to be able to use flexmock without rspec mocks interfering
-
-  Scenario: Mock with flexmock
-    Given a file named "flexmock_example_spec.rb" with:
-      """
-      Spec::Runner.configure do |config|
-        config.mock_with :flexmock
-      end
-
-      describe "plugging in flexmock" do
-        it "allows flexmock to be used" do
-          target = Object.new
-          flexmock(target).should_receive(:foo).once
-          target.foo
-        end
-
-        it "does not include rspec mocks" do
-          Spec.const_defined?(:Mocks).should be_false
-        end
-      end
-      """
-    When I run "spec flexmock_example_spec.rb"
-    Then the exit code should be 0
-    And the stdout should include "2 examples, 0 failures"

data/features/mock_framework_integration/use_mocha.feature

@@ -1,27 +0,0 @@
-Feature: mock with mocha
-
-  As an RSpec user who prefers mocha
-  I want to be able to use mocha without rspec mocks interfering
-
-  Scenario: Mock with mocha
-    Given a file named "mocha_example_spec.rb" with:
-      """
-      Spec::Runner.configure do |config|
-        config.mock_with :mocha
-      end
-
-      describe "plugging in mocha" do
-        it "allows mocha to be used" do
-          target = Object.new
-          target.expects(:foo).once
-          target.foo
-        end
-
-        it "does not include rspec mocks" do
-          Spec.const_defined?(:Mocks).should be_false
-        end
-      end
-      """
-    When I run "spec mocha_example_spec.rb"
-    Then the exit code should be 0
-    And the stdout should include "2 examples, 0 failures"

data/features/mock_framework_integration/use_rr.feature

@@ -1,27 +0,0 @@
-Feature: mock with rr
-
-  As an RSpec user who prefers rr
-  I want to be able to use rr without rspec mocks interfering
-
-  Scenario: Mock with rr
-    Given a file named "rr_example_spec.rb" with:
-      """
-      Spec::Runner.configure do |config|
-        config.mock_with :rr
-      end
-
-      describe "plugging in rr" do
-        it "allows rr to be used" do
-          target = Object.new
-          mock(target).foo
-          target.foo
-        end
-
-        it "does not include rspec mocks" do
-          Spec.const_defined?(:Mocks).should be_false
-        end
-      end
-      """
-    When I run "spec rr_example_spec.rb"
-    Then the exit code should be 0
-    And the stdout should include "2 examples, 0 failures"

data/features/mocks/block_local_expectations.feature

@@ -1,62 +0,0 @@
-Feature: block local expectations
-
-  In order to set message expectations on ...
-  As an RSpec user
-  I want to configure the evaluation context
-
-  Background:
-    Given a file named "account.rb" with:
-      """
-      class Account
-        def self.create
-          yield new
-        end
-
-        def opening_balance(amount, currency)
-        end
-      end
-      """
-
-  Scenario: passing example
-    Given a file named "account_dsl.rb" with:
-      """
-      require 'spec_helper'
-      require 'account'
-
-      describe "account DSL" do
-        it " .... " do
-          account = Account.new
-          Account.should_receive(:create).and_yield do |account|
-            account.should_receive(:opening_balance).with(100, :USD)
-          end
-          Account.create do
-            opening_balance 100, :USD
-          end
-        end
-      end
-      """
-    When I run "spec account_dsl.rb"
-    Then the stdout should include "1 example, 0 failures"
-    
-  Scenario: failing example
-    
-    Given a file named "account_dsl.rb" with:
-      """
-      require 'spec_helper'
-      require 'account'
-
-      describe "account DSL" do
-        it " .... " do
-          account = Account.new
-          Account.should_receive(:create).and_yield do |account|
-            account.should_receive(:opening_balance).with(100, :USD)
-          end
-          Account.create do
-            # opening_balance is not called here
-          end
-        end
-      end
-      """
-
-    When I run "spec account_dsl.rb"
-    Then the stdout should include "1 example, 1 failure"

data/features/mocks/mix_stubs_and_mocks.feature

@@ -1,22 +0,0 @@
-Feature: stub and mock together
-
-  As an RSpec user
-  I want to use stubs and mocks together
-
-  Scenario: stub in before
-    Given a file named "stub_and_mocks_spec.rb" with:
-      """
-      describe "a stub in before" do
-        before(:each) do
-          @messenger = mock('messenger').as_null_object
-        end
-
-        it "a" do
-          @messenger.should_receive(:foo).with('first')
-          @messenger.foo('second')
-          @messenger.foo('third')
-        end
-      end
-      """
-    When I run "spec stub_and_mocks_spec.rb --format nested"
-    Then the stdout should include "received :foo with unexpected arguments\n  expected: (\"first\")\n       got: ([\"second\"], [\"third\"])"

data/features/mocks/stub_implementation.feature

@@ -1,26 +0,0 @@
-Feature: stub implementation
-
-  As an rspec user, I want to stub a complete implementation, not just a
-  return value.
-  
-  Scenario: stub implementation
-    Given a file named "stub_implementation.rb" with:
-      """
-      describe "a stubbed implementation" do
-        it "works" do
-          object = Object.new
-          object.stub(:foo) do |arg|
-            if arg == :this
-              "got this"
-            elsif arg == :that
-              "got that"
-            end
-          end
-          
-          object.foo(:this).should == "got this"
-          object.foo(:that).should == "got that"
-        end
-      end
-      """
-    When I run "spec stub_implementation.rb"
-    Then the stdout should include "1 example, 0 failures"