app works, but in rSpec test fails - ruby-on-rails

Question

In User model I have following methods:
def generate_and_set_new_password!
password = random_pronouncable_token
self.password_hash = encrypt(password)
self.password_reset_sent_at = Time.now
if self.save!
password
else
nil
end
end
private
def encrypt(string)
# Some code that encrypts string
# ...
end
def random_pronouncable_token(size = 4)
# Some code that generates new password
# ...
end
rSpec test:
describe "New password generation" do
it "should generate new password" do
user = #user
old_pwd_hash = user.password_hash
pwd = user.generate_and_set_new_password!
pwd.should_not be_nil
user.password_hash.should_not == old_pwd_hash
end
end
This test gives me such output:
1) User password encryption New password generation should generate new password
Failure/Error: user.password_hash.should_not == old_pwd_hash
expected not: == "966abfff742d73c71fc87a1928b90aec"
got: "966abfff742d73c71fc87a1928b90aec"
' generate_and_set_new_password! ' method correctly works in app, here is example from console:
ruby-1.8.7-p249 :014 > user.password_hash
=> "ef10fb44dfceeaca05ca78030c1d8cb5"
ruby-1.8.7-p249 :015 > user.generate_and_set_new_password!
=> "quispopeho"
ruby-1.8.7-p249 :016 > user.password_hash
=> "a0b7605d5d6ca2152f7e019b4896fef4"
ruby-1.8.7-p249 :017 >
As we can see, it gives new password_hash for user, so it works correctly.
I decided that this is some bug in rSpec. I've made such experiment:
Here is some changes in test's code:
describe "New password generation" do
it "should generate new password" do
user = #user
old_pwd_hash = user.password_hash
p "old_password = ", user.password
p "old_pwd_hash = ", old_pwd_hash
pwd = user.generate_and_set_new_password!
p "received new password = #{pwd}"
p "SHOULD BE a new_pwd_hash, but it isn't! ", user.password_hash
p "SHOULD BE a new_password, but it isn't! ", user.password
pwd.should_not be_nil
# There I am tring to set this new password explicitly :)
user.password = pwd
user.save
p "NOW it is other password hash = ", user.password_hash
user.password_hash.should_not == old_pwd_hash
end
end
Now test is passed!
And the debugging output is the following:
"old_password = foobar"
"old_pwd_hash = c251e8a9bcc4fba1199181b1f2c1430c"
"received new password = kongibyty"
"SHOULD BE a new_pwd_hash, but it isn't! c251e8a9bcc4fba1199181b1f2c1430c"
"SHOULD BE a new_password, but it isn't! foobar"
"NOW it is other password hash = e2b53133b796bcb212a0c1fa1d2a1cfa"
As I can see from this debugging output, user object get it's new password_hash ONLY after it was EXPLICITLY set up in test's code. Seems like 'generate_and_set_new_password!' method can't change object that was created in test environment.
Why I am getting such weird rSpec's behaviour?
Any suggestions will be useful.
Some additional info about my development envoroment:
I am using:
ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]
Rails 3.0.9
rvm
Gemfile snippet:
group :development, :test do
gem "rspec-rails", "~> 2.6"
gem 'webrat', '0.7.1'
gem 'spork', '0.9.0.rc9'
gem 'autotest-standalone'
gem 'autotest', '4.4.6'
gem 'autotest-rails-pure', '4.1.2'
gem 'factory_girl_rails', '1.0'
end
Udpates:
Code that creates #user
require 'spec_helper'
describe User do
# attributes for user object
before(:each) do
#attr = {
:email => "user#example.com",
:password => "foobar",
:password_confirmation => "foobar",
:first_name => "Example",
:last_name => "Examploid",
:dob => Date.new(1980,07,03),
:relationships_status => "Single",
:sex => "male",
:sexual_orientaion => "Woman",
:about_me => "All about me",
:school_id => 1,
:education_id => 1,
:occupation_id => 1,
:web_site => "example.com"
}
end
# Some other tests...
# ...
describe "password encryption" do
# create user
before(:each) do
#user = User.create!(#attr)
end
# Some other tests...
# ...
# Here is shown the same test code as above.
describe "New password generation" do
it "should generate new password" do
# I even tried to use factory_girl's method
# #user = Factory(:device_user)
user = #user
old_pwd_hash = user.password_hash
pwd = user.generate_and_set_new_password!
pwd.should_not be_nil
user.password_hash.should_not == old_pwd_hash
end
end
end
end
Some clarification:
I am not using stubbing of #user's methods in any of my tests.
I tried to do the same with factory_girl, and got the same test's fail.
Here user's Factory definition:
Factory.define :device_user, :class => User do |user|
user.password "password"
user.password_confirmation "password"
user.email "device_user#example.com"
user.first_name "Device"
user.last_name "User"
user.dob Date.new(2011,10,03)
user.relationships_status "Single"
user.sex "male"
user.sexual_orientaion "Woman"
user.about_me "All about Device User"
user.school_id 1
user.education_id 1
user.occupation_id 1
user.web_site "device.example.com"
user.facebook_id "face_test_id"
end