2014-05-25 65 views
0

我在Rails教程的第9章(这一节在9.2.2节)中被卡住了(再次!)。我越来越Rails教程:未定义的方法

bundle exec rspec spec/ 
................................FFF........................ 

Failures: 

1) Authentication authorization as wrong user submitting a GET request to the Users#edit action 
Failure/Error: before {sign_in user, no_capybara: true} 
NoMethodError: 
    undefined method `new_remember_token' for #<User:0x007f8181815448> 
# ./spec/support/utilities.rb:13:in `sign_in' 
# ./spec/requests/authentication_pages_spec.rb:71:in `block (4 levels) in <top (required)>' 

其他2个错误是相同的类型。

下面是规范导致错误:

describe "as wrong user" do 
     let(:user) {FactoryGirl.create(:user)} 
     let(:wrong_user) {FactoryGirl.create(:user, email: "[email protected]")} 
     before {sign_in user, no_capybara: true} 

     describe "submitting a GET request to the Users#edit action" do 
     before {get edit_user_path(wrong_user)} 
     specify { expect(response.body).not_to match(full_title('Edit user'))} 
     specify { expect(response).to redirect_to(root_url)} 
     end 

     describe "submitting a PATCH request to the Users#update action" do 
     before { patch user_path(wrong_user)} 
     specify { expect(response).to redirect_to(root_url)} 
     end 
    end 

这里是错误消息抱怨的方法(utilities.rb):

def sign_in (user, options={}) 
    if options[:no_capybara] 
    # Sign in when not using Capybara 
    remember_token = User.new_remember_token 
    cookies[:remember_token] 
    user.update_attribute(:remember_token, User.digest(remember_token)) 
    else 
    visit signin_path 
    fill_in "Email", with: user.email 
    fill_in "Password", with: user.password 
    click_button "Sign in" 
    end 
end 

的模型(用户代码。 rb)在这里:

class User < ActiveRecord::Base 
before_save { self.email = email.downcase} 
before_create :create_remember_token 
validates :name, presence: true, length: { maximum: 50 } 
VALID_EMAIL_REGEX = /\A[\w+\-.][email protected][a-z\d\-.]+\.[a-z]+\z/i 
validates :email, presence: true, format: { with: VALID_EMAIL_REGEX }, uniqueness: { case_sensitive: false } 
validates :password, length: {minimum: 6} 
has_secure_password 

def User.new_remember_token 
    SecureRandom.urlsafe_base64 
end 

def User.digest(token) 
    Digest::SHA1.hexdigest(token.to_s) 
end 

private 
    def create_remember_token 
    self.remember_token = User.digest(User.new_remember_token) 
    end 
end 

我以前有与sign_in方法的麻烦,但它miraculously disappeared。我究竟做错了什么?

回答

0

我终于找到了我在这种情况下观察到的不稳定测试结果的罪魁祸首,并且很可能在之前的场合(Failure/Error: sign_in user undefined method `sign_in',Rails named route not recognized)。问题似乎是,rails不会在测试之间默认清除缓存。实际上,这真是令人害怕。看来你不能真正相信测试结果。我通过评论Rail的抱怨和重新运行测试的方法来实现这一点。错误依然存在,这意味着一件事 - rspec只是简单地使用一些缓存版本的文件,因此忽略了我所做的更改。所以即使测试通过了,你也不能确定他们真的这么做了。这真是奇怪。在用google搜索了一下问题后,我发现如何强制rails来清理缓存 - 请检查jaustin的答案:is Rails.cache purged between tests?

+0

也强制Guard轮询可以帮助 - http://stackoverflow.com/questions/11766511/tests-做 - 不运行时,文件的变化,与后卫和-rspec的上窗口 – Nick

相关问题