PaulBarry.com - Displaying error messages in RSpec failures

Displaying error messages in RSpec failures

2008-04-23T18:30:13-04:00

@something.errors.should be_empty

When that fails, you get a report that says:

expected empty? to return true, got false

That's not very helpful because it doesn't tell you what the errors are. If you do this:

@something.errors.full_messages.should == []

You get a more informative failure message:

expected: [],
got: ["Whatever can't be blank"] (using ==)

Comment on "Displaying error messages in RSpec failures" by nicholas a. evans

2008-04-24T13:39:33-04:00

Or you could use my ValidationSpecHelper module, which could be called like so:

<pre>
@it.should accept("blah").for(:firstname)
@it.should accept(:firstname).of("foobar")
@it.should reject(:firstname).of("")
@it.should reject(:firstname).of("chunky").with("reason")
</pre>

and return failure messages like so:

<pre>
expected validation to accept "" for firstname
but firstname had the following errors:
- firstname: can't be blank

expected validation to reject "a name" for firstname
but firstname was valid
</pre>

and so on...

http://svn.ekenosen.net/public/rspec_validation_matcher/

There are other validation spec matchers out there, but I like mine the best. ;-)

Comment on "Displaying error messages in RSpec failures" by nicholas a. evans

2008-04-24T13:40:15-04:00

Oh well, I guess the <pre> tags didn't work. Preview buttons are nice things for blog comments. ;-)

Comment on "Displaying error messages in RSpec failures" by bryanl

2008-04-25T06:58:31-04:00

Or you just give up on rspec and its spaghetti mess of code and start using shoulda.

should_not_allow_values_for :email, "blah", "b lah"
should_allow_values_for :email, "a@b.com", "asdf@asdf.com"