> You normally want to use .should be_true (and .should be_false).
Right, I just changed things back but now get this error:
undefined local variable or method `be_true' for #
(NameError)
Now, if I do it with .should == true, I have verified that the problem is
that this test is failing:
user.
David Kahn wrote:
> I have a function that returns the true / false Ruby type. For some
> reason I
> cant get rspec to swallow this.
>
> This errors out:
> user.authorize.should == true
[...]
You normally want to use .should be_true (and .should be_false).
Best,
--
Marnen Laibow-Koser
http://ww
Ok, so it looks like the failure is the failure of the test, but why does
rspec complain so much and not just give me a failed test and the line of
failure instead of crashing? I'm pretty confused.
On Tue, Oct 5, 2010 at 3:03 PM, David Kahn wrote:
> I have a function that returns the true / fals
3 matches
Mail list logo