NoMethodError: undefined method `first' in NegativeExpectationHandler

[rkistner]

In RSpec 2.8.0, I believe the line rspec-expectations-2.8.0/lib/rspec/expectations/handler.rb:42 which contains:

::RSpec::Expectations.fail_with message, matcher.expected.first, matcher.actual

should be:

::RSpec::Expectations.fail_with message, matcher.expected, matcher.actual

Simple check to test this (the test should fail, but not raise this error):

"test".should_not RSpec::Matchers::Eq.new("test")

NoMethodError: undefined method `first' for 1:Fixnum
from /usr/local/lib/ruby/gems/1.9.1/gems/rspec-expectations-2.8.0/lib/rspec/expectations/handler.rb:42:in `handle_matcher'
from /usr/local/lib/ruby/gems/1.9.1/gems/rspec-expectations-2.8.0/lib/rspec/expectations/extensions/kernel.rb:24:in `should_not'
from (irb):28
from /usr/local/bin/irb:12:in `<main>'

[dchelimsky]

There is some unfortunate legacy around matcher.expected.first so it can't just be changed without breaking a bunch of stuff out in the wild. What problem are you experiencing as a result?

[rkistner]

Why is it only matcher.expected.first in NegativeExpectationHandler, but matcher.expected in PositiveExpectationHandler?

My test is a simple

a.should_not equal(b)

However, when the test fails, the above error is spewed instead of a descriptive message.

[e2]

Could you bump Rspec to 1.8.1 to release this? Thanks.

[dchelimsky]

Released 2.9.0.rc2 this morning. 2.9 to follow by the weekend barring any unforeseen issues.

[e2]

Thanks! :)

On Mon, Mar 12, 2012 at 02:15:40PM -0700, David Chelimsky wrote:

Released 2.9.0.rc2 this morning. 2.9 to follow by the weekend barring any unforeseen issues.

---

Reply to this email directly or view it on GitHub:
#115 (comment)

Cezary Baginski