[rspec-users] Cucumber ".should contain(expected) does but fails anyway
lists at ruby-forum.com
Wed Apr 22 14:45:30 EDT 2009
David Chelimsky wrote:
> The original issue you posted is with the contain matcher, which is in
> webrat, not rspec. Why it's not working, I'm not quite sure, but if
> you're going to throw out the baby with the bath water, you might
> consider figuring out who the parents are :)
Yes, I figured out that #contain was the culprit when I discovered that
Ugly, to me, but it works so the problem is not RSpec. Strangely,
however, this construct also failed:
I am not throwing out RSpec or using it any less. I just had to get
around a specific problem and took the first route I found that worked.
> In the mean time, I'm not sure what better message we can give beyond
> "compared using .equal?" without getting into a long treatise on
> equality in Ruby, which seems out of place in a failure message.
expected "<title>Bank of Canada: Noon Foreign Exchange
got "<title>Bank of Canada: Noon Foreign Exchange
(equal?: expected object is not the object returned, did you mean
Posted via http://www.ruby-forum.com/.
More information about the rspec-users