Hi all,
Having not done any speccing for a few weeks I just spent ages puzzling
over why the following code wasn't working
it "should require a client" do
expect{ }.should raise_error ArgumentError
end
and giving me a
expected ArgumentError, got #<NoMethodError: undefined method `call'
for #<RSpec::Expectations:
A bit of googling pointed to the fact that I should be using `expect{}.to`,
and reminded me that I have made this mistake more than once in the past.
My question/request is, can we have a better error message for this
mistake, something telling us not to use should with expect.
All best
Andrew
--
------------------------
Andrew Premdas
blog.andrew.premdas.org
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
