On Nov 22, 12:02 am, David Chelimsky wrote:
> On Nov 20, 2010, at 9:49 PM, Doug E. wrote:
>
> > Problem discovered, but not solved. It isn't an rspec problem. It's
> > caused by nifty-authentication's use of Mocha's any_instance.
> > users_controller_spec.rb's last test calls:
>
> > User.any_
On Nov 20, 2010, at 9:49 PM, Doug E. wrote:
> Problem discovered, but not solved. It isn't an rspec problem. It's
> caused by nifty-authentication's use of Mocha's any_instance.
> users_controller_spec.rb's last test calls:
>
>User.any_instance.stubs(:valid?).and_returns(true)
>
> This is fi
Problem discovered, but not solved. It isn't an rspec problem. It's
caused by nifty-authentication's use of Mocha's any_instance.
users_controller_spec.rb's last test calls:
User.any_instance.stubs(:valid?).and_returns(true)
This is fine if the tests are run singly, but with autotest the call
On Nov 20, 8:43 pm, "Doug E." wrote:
> Hi,
> I'm trying to run autotest and I'm using ryanb's nifty authentication
> with Rails 3 and Rpec 2. When I run autotest, the user model spec
> fails all its validation tests with the "error_on" matcher.
>
> If I run the spec by itself, it passes. If I'm ru
Hi,
I'm trying to run autotest and I'm using ryanb's nifty authentication
with Rails 3 and Rpec 2. When I run autotest, the user model spec
fails all its validation tests with the "error_on" matcher.
If I run the spec by itself, it passes. If I'm running autotest and
make a trivial change to the s
