rspec 1.3.2 → 2.0.0.a2

data/lib/spec/example/subject.rb

@@ -1,114 +0,0 @@
-module Spec
-  module Example
-    module Subject
-      module ExampleGroupMethods
-        # Defines an explicit subject for an example group which can then be the
-        # implicit receiver (through delegation) of calls to +should+.
-        #
-        # == Examples
-        #
-        #   describe CheckingAccount, "with $50" do
-        #     subject { CheckingAccount.new(:amount => 50, :currency => :USD) }
-        #     it { should have_a_balance_of(50, :USD) }
-        #     it { should_not be_overdrawn }
-        #     its(:currency) { should == :USD }
-        #   end
-        #
-        # See +ExampleMethods#should+ for more information about this approach.
-        def subject(&block)
-          block.nil? ?
-            explicit_subject || implicit_subject : @explicit_subject_block = block
-        end
-        
-        def its(attribute, &block)
-          describe(attribute) do
-            example do
-              self.class.class_eval do
-                define_method(:subject) do
-                  super().send(attribute)
-                end
-              end
-              instance_eval(&block)
-            end
-          end
-        end
-
-        attr_reader :explicit_subject_block # :nodoc:
-
-      private
-
-        def explicit_subject
-          group = self
-          while group.respond_to?(:explicit_subject_block)
-            return group.explicit_subject_block if group.explicit_subject_block
-            group = group.superclass
-          end
-        end
-
-        def implicit_subject
-          (described_class ? proc {described_class.new} : proc {description_args.first})
-        end
-      end
-
-      module ExampleMethods
-
-        alias_method :__should_for_example_group__,     :should
-        alias_method :__should_not_for_example_group__, :should_not
-
-        # Returns the subject defined in ExampleGroupMethods#subject. The
-        # subject block is only executed once per example, the result of which
-        # is cached and returned by any subsequent calls to +subject+.
-        #
-        # If a class is passed to +describe+ and no subject is explicitly
-        # declared in the example group, then +subject+ will return a new
-        # instance of that class.
-        #
-        # == Examples
-        #
-        #   # explicit subject defined by the subject method
-        #   describe Person do
-        #     subject { Person.new(:birthdate => 19.years.ago) }
-        #     it "should be eligible to vote" do
-        #       subject.should be_eligible_to_vote
-        #     end
-        #   end
-        #
-        #   # implicit subject => { Person.new }
-        #   describe Person do
-        #     it "should be eligible to vote" do
-        #       subject.should be_eligible_to_vote
-        #     end
-        #   end
-        def subject
-          @subject ||= instance_eval(&self.class.subject)
-        end
-
-        # When +should+ is called with no explicit receiver, the call is
-        # delegated to the object returned by +subject+. Combined with
-        # an implicit subject (see +subject+), this supports very concise
-        # expressions.
-        #
-        # == Examples
-        #
-        #   describe Person do
-        #     it { should be_eligible_to_vote }
-        #   end
-        def should(matcher=nil, message=nil)
-          self == subject ? self.__should_for_example_group__(matcher) : subject.should(matcher,message)
-        end
-
-        # Just like +should+, +should_not+ delegates to the subject (implicit or
-        # explicit) of the example group.
-        #
-        # == Examples
-        #
-        #   describe Person do
-        #     it { should_not be_eligible_to_vote }
-        #   end
-        def should_not(matcher=nil, message=nil)
-          self == subject ? self.__should_not_for_example_group__(matcher) : subject.should_not(matcher,message)
-        end
-      end
-    end
-  end
-end

data/lib/spec/expectations.rb

@@ -1,35 +0,0 @@
-require 'spec/matchers'
-require 'spec/expectations/fail_with'
-require 'spec/expectations/errors'
-require 'spec/expectations/extensions'
-require 'spec/expectations/handler'
-
-module Spec
-  
-  # Spec::Expectations lets you set expectations on your objects.
-  #
-  #   result.should == 37
-  #   team.should have(11).players_on_the_field
-  #
-  # == How Expectations work.
-  #
-  # Spec::Expectations adds two methods to Object:
-  #
-  #   should(matcher=nil)
-  #   should_not(matcher=nil)
-  #
-  # Both methods take an optional Expression Matcher (See Spec::Matchers).
-  #
-  # When +should+ receives an Expression Matcher, it calls <tt>matches?(self)</tt>. If
-  # it returns +true+, the spec passes and execution continues. If it returns
-  # +false+, then the spec fails with the message returned by <tt>matcher.failure_message</tt>.
-  #
-  # Similarly, when +should_not+ receives a matcher, it calls <tt>matches?(self)</tt>. If
-  # it returns +false+, the spec passes and execution continues. If it returns
-  # +true+, then the spec fails with the message returned by <tt>matcher.negative_failure_message</tt>.
-  #
-  # RSpec ships with a standard set of useful matchers, and writing your own
-  # matchers is quite simple. See Spec::Matchers for details.
-  module Expectations
-  end
-end

data/lib/spec/expectations/errors.rb

@@ -1,12 +0,0 @@
-module Spec
-  module Expectations
-    # If Test::Unit is loaed, we'll use its error as baseclass, so that Test::Unit
-    # will report unmet RSpec expectations as failures rather than errors.
-    superclass = ['Test::Unit::AssertionFailedError', '::StandardError'].map do |c|
-      eval(c) rescue nil
-    end.compact.first
-    
-    class ExpectationNotMetError < superclass
-    end
-  end
-end

data/lib/spec/expectations/extensions.rb

@@ -1 +0,0 @@
-require 'spec/expectations/extensions/kernel'

data/lib/spec/expectations/extensions/kernel.rb

@@ -1,52 +0,0 @@
-module Kernel
-  # :call-seq:
-  #   should(matcher)
-  #   should == expected
-  #   should === expected
-  #   should =~ expected
-  #
-  #   receiver.should(matcher)
-  #     => Passes if matcher.matches?(receiver)
-  #
-  #   receiver.should == expected #any value
-  #     => Passes if (receiver == expected)
-  #
-  #   receiver.should === expected #any value
-  #     => Passes if (receiver === expected)
-  #
-  #   receiver.should =~ regexp
-  #     => Passes if (receiver =~ regexp)
-  #
-  # See Spec::Matchers for more information about matchers
-  #
-  # == Warning
-  #
-  # NOTE that this does NOT support receiver.should != expected.
-  # Instead, use receiver.should_not == expected
-  def should(matcher=nil, message=nil, &block)
-    Spec::Expectations::PositiveExpectationHandler.handle_matcher(self, matcher, message, &block)
-  end
-  
-  # :call-seq:
-  #   should_not(matcher)
-  #   should_not == expected
-  #   should_not === expected
-  #   should_not =~ expected
-  #
-  #   receiver.should_not(matcher)
-  #     => Passes unless matcher.matches?(receiver)
-  #
-  #   receiver.should_not == expected
-  #     => Passes unless (receiver == expected)
-  #
-  #   receiver.should_not === expected
-  #     => Passes unless (receiver === expected)
-  #
-  #   receiver.should_not =~ regexp
-  #     => Passes unless (receiver =~ regexp)
-  #
-  # See Spec::Matchers for more information about matchers
-  def should_not(matcher=nil, message=nil, &block)
-    Spec::Expectations::NegativeExpectationHandler.handle_matcher(self, matcher, message, &block)
-  end
-end

data/lib/spec/expectations/fail_with.rb

@@ -1,45 +0,0 @@
-module Spec
-  module Expectations
-    class << self
-      attr_accessor :differ
-      
-      # raises a Spec::Expectations::ExpectationNotMetError with message
-      #
-      # When a differ has been assigned and fail_with is passed
-      # <code>expected</code> and <code>target</code>, passes them
-      # to the differ to append a diff message to the failure message.
-      def fail_with(message, expected=nil, target=nil) # :nodoc:
-        if message.nil?
-          raise ArgumentError, "Failure message is nil. Does your matcher define the " +
-                               "appropriate failure_message_for_* method to return a string?"
-        end
-        if (Array === message) & (message.length == 3)
-          ::Spec.warn(<<-NOTICE
-
-*****************************************************************
-DEPRECATION WARNING: you are using deprecated behaviour that will
-be removed from a future version of RSpec.
-
-* Support for matchers that return arrays from failure message
-methods is deprecated.
-* Instead, the matcher should return a string, and expose methods
-for the expected() and actual() values.
-*****************************************************************
-NOTICE
-          )
-          message, expected, target = message[0], message[1], message[2]
-        end
-        unless (differ.nil? || expected.nil? || target.nil?)
-          if expected.is_a?(String)
-            message << "\n\n Diff:" << self.differ.diff_as_string(target.to_s, expected)
-          elsif expected.is_a?(Hash) && target.is_a?(Hash)
-            message << "\n\n Diff:" << self.differ.diff_as_hash(target, expected)
-          elsif !target.is_a?(Proc)
-            message << "\n\n Diff:" << self.differ.diff_as_object(target, expected)
-          end
-        end
-        Kernel::raise(Spec::Expectations::ExpectationNotMetError.new(message))
-      end
-    end
-  end
-end

data/lib/spec/expectations/handler.rb

@@ -1,50 +0,0 @@
-module Spec
-  module Expectations
-    class InvalidMatcherError < ArgumentError; end        
-    
-    class PositiveExpectationHandler        
-      def self.handle_matcher(actual, matcher, message=nil, &block)
-        ::Spec::Matchers.last_should = :should
-        ::Spec::Matchers.last_matcher = matcher
-        return ::Spec::Matchers::PositiveOperatorMatcher.new(actual) if matcher.nil?
-
-        match = matcher.matches?(actual, &block)
-        return match if match
-        
-        message ||= matcher.respond_to?(:failure_message_for_should) ?
-                    matcher.failure_message_for_should :
-                    matcher.failure_message
-        
-        if matcher.respond_to?(:diffable?) && matcher.diffable?
-          ::Spec::Expectations.fail_with message, matcher.expected.first, matcher.actual
-        else
-          ::Spec::Expectations.fail_with message
-        end
-      end
-    end
-
-    class NegativeExpectationHandler
-      def self.handle_matcher(actual, matcher, message=nil, &block)
-        ::Spec::Matchers.last_should = :should_not
-        ::Spec::Matchers.last_matcher = matcher
-        return ::Spec::Matchers::NegativeOperatorMatcher.new(actual) if matcher.nil?
-        
-        match = matcher.respond_to?(:does_not_match?) ?
-                !matcher.does_not_match?(actual, &block) :
-                matcher.matches?(actual, &block)
-        return match unless match
-        
-        message ||= matcher.respond_to?(:failure_message_for_should_not) ?
-                    matcher.failure_message_for_should_not :
-                    matcher.negative_failure_message
-
-        if matcher.respond_to?(:diffable?) && matcher.diffable?
-          ::Spec::Expectations.fail_with message, matcher.expected.first, matcher.actual
-        else
-          ::Spec::Expectations.fail_with message
-        end
-      end
-    end
-  end
-end
-

data/lib/spec/extensions/instance_exec.rb

@@ -1,31 +0,0 @@
-module Spec
-  module Matchers
-    module InstanceExec
-      unless respond_to?(:instance_exec)
-        # based on Bounded Spec InstanceExec (Mauricio Fernandez)
-        # http://eigenclass.org/hiki/bounded+space+instance_exec
-        # - uses singleton_class of matcher instead of global
-        #   InstanceExecHelper module
-        # - this keeps it scoped to this class only, which is the
-        #   only place we need it
-        # - only necessary for ruby 1.8.6
-        def instance_exec(*args, &block)
-          singleton_class = (class << self; self; end)
-          begin
-            orig_critical, Thread.critical = Thread.critical, true
-            n = 0
-            n += 1 while respond_to?(method_name="__instance_exec#{n}")
-            singleton_class.module_eval{ define_method(:__instance_exec, &block) }
-          ensure
-            Thread.critical = orig_critical
-          end
-          begin
-            return send(:__instance_exec, *args)
-          ensure
-            singleton_class.module_eval{ remove_method(:__instance_exec) } rescue nil
-          end
-        end
-      end
-    end
-  end
-end

data/lib/spec/interop/test.rb

@@ -1,44 +0,0 @@
-require 'spec'
-
-if Spec::Ruby.version.to_f >= 1.9
-  gem 'test-unit','= 1.2.3'
-end
-
-require 'test/unit'
-
-if Spec::Ruby.version.to_f >= 1.9
-  require 'test/unit/version'
-  if Test::Unit::VERSION > '1.2.3'
-    raise <<-MESSAGE
-#{'*' * 50}
-Required: test-unit-1.2.3
-Loaded:   test-unit-#{Test::Unit::VERSION}
-
-With ruby-1.9, rspec-#{Spec::VERSION::STRING} requires test-unit-1.2.3, and
-tries to force it with "gem 'test-unit', '= 1.2.3'" in:
-
-  #{__FILE__}
-  
-Unfortunately, test-unit-#{Test::Unit::VERSION} was loaded anyway. While we are
-aware of this bug we have not been able to track down its source.
-Until we do, you have two alternatives:
-
-* uninstall test-unit-#{Test::Unit::VERSION}
-* use 'script/spec' instead of 'rake spec'
-#{'*' * 50}
-MESSAGE
-  end
-end
-
-
-require 'test/unit/testresult'
-
-require 'spec/interop/test/unit/testcase'
-require 'spec/interop/test/unit/testsuite_adapter'
-require 'spec/interop/test/unit/autorunner'
-require 'spec/interop/test/unit/testresult'
-require 'spec/interop/test/unit/ui/console/testrunner'
-
-Spec::Example::ExampleGroupFactory.default(Test::Unit::TestCase)
-
-Test::Unit.run = true

data/lib/spec/interop/test/unit/autorunner.rb

@@ -1,6 +0,0 @@
-class Test::Unit::AutoRunner
-  remove_method :process_args
-  def process_args(argv)
-    true
-  end
-end

data/lib/spec/interop/test/unit/testcase.rb

@@ -1,56 +0,0 @@
-require 'test/unit/testcase'
-
-module Test
-  module Unit
-    # This extension of the standard Test::Unit::TestCase makes RSpec
-    # available from within, so that you can do things like:
-    #
-    # require 'spec/test/unit'
-    #
-    # class MyTest < Test::Unit::TestCase
-    #   it "should work with Test::Unit assertions" do
-    #     assert_equal 4, 2+1
-    #   end
-    #
-    #   def test_should_work_with_rspec_expectations
-    #     (3+1).should == 5
-    #   end
-    # end
-    #
-    # See also Spec::Example::ExampleGroup
-    class TestCase
-      extend Spec::Example::ExampleGroupMethods
-      include Spec::Example::ExampleMethods
-
-      def self.suite
-        Test::Unit::TestSuiteAdapter.new(self)
-      end
-
-      def self.example_method?(method_name)
-        should_method?(method_name) || test_method?(method_name)
-      end
-
-      def self.test_method?(method_name)
-        method_name =~ /^test./ && (
-          instance_method(method_name).arity == 0 ||
-          instance_method(method_name).arity == -1
-        )
-      end
-
-      before(:each) {setup}
-      after(:each) {teardown}
-
-      def initialize(description, &implementation)
-        super
-        # Some Test::Unit extensions depend on @method_name being present.
-        @method_name = description.description
-        @_result = ::Test::Unit::TestResult.new
-      end
-
-      def run(ignore_this_argument=nil)
-        super()
-      end
-
-    end
-  end
-end