On Feb 28, 2012, at 9:43 PM, Mohamad El-Husseini wrote:

> I ran this scenario in the console and it works as expected. But RSpec keeps 
> failing the test and I can't understand why.
> 
> describe User do
> 
>   before do
>     @user = User.new(name: "Mickey Mouse", email: "mic...@disney.com", 
> password: "m1ckey", password_confirmation: "m1ckey")
>   end
> 
>     # Password
>     describe "when password is not present" do
>       before { @user.password = @user.password_confirmation = " " }
>       it { should_not be_valid }
>     end
> end
> 
> --> expected valid? to return false, got true
> 
> If I take out the @user.password_confirmation from the assignment, it works:
> 
>       before { @user.password = " " }
>       it { should_not be_valid }
> 
> But, as I said, using the console I can verify that everything works as 
> expected. Why does adding @password_confirmation break the test?
> 
> Here's my user model:
> 
> class User < ActiveRecord::Base
>   attr_accessible :name, :email, :password, :password_confirmation
>   has_secure_password
>   validates :password,  length: { minimum: 6 }
> end
> _______________________________________________
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

Can't reproduce. What versions are you using? Ruby, Rails, RSpec

Also, do you have a `subject` set? 
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users

Reply via email to