未能通过 rspec 测试验证来自 Michael Hartl 教程的密码答案

【问题标题】：Failing rspec test to authenticate password from Michael Hartl Tutorial未能通过 rspec 测试验证来自 Michael Hartl 教程的密码
【发布时间】：2014-07-19 16:32:12
【问题描述】：

在 Michael Hartl 教程的第 6 章中，以下测试应该通过，

   describe "with invalid password" do
   let(:user_for_invalid_password) { found_user.authenticate("invalid") }
   it { should_not eq user_for_invalid_password }
   specify { expect(user_for_invalid_password).to be_false }
   end

然而，在 19 次测试中，这是唯一失败的。

我的模型叫做 Utilisateur（用户的法语）

这是完整的规范文件（fund_user 变量设置在同一块中，在文件末尾）

require 'rails_helper'


describe Utilisateur do

  before do
      @user = Utilisateur.new(nom: "Example User", email: "user@example.com",
                       password: "foobar", password_confirmation: "foobar")
    end

  subject { @user }

  it { should respond_to(:nom) }
  it { should respond_to(:email) }
  it { should respond_to(:password_digest) }
  it { should respond_to(:password) }
  it { should respond_to(:password_confirmation) }
  it { should respond_to(:authenticate) }

  it { should be_valid }

  describe "when name is not present" do
      before { @user.nom = " " }
      it { should_not be_valid }
    end

  describe "when email is not present" do
      before { @user.email = " " }
      it { should_not be_valid }
  end

  describe "when name is too long" do
      before { @user.nom = "a" * 51 }
      it { should_not be_valid }
  end

  describe "when email format is invalid" do
      it "should be invalid" do
        addresses = %w[user@foo,com user_at_foo.org example.user@foo.
                       foo@bar_baz.com foo@bar+baz.com]
        addresses.each do |invalid_address|
          @user.email = invalid_address
          expect(@user).not_to be_valid
        end
      end
    end

  describe "when email format is valid" do
      it "should be valid" do
        addresses = %w[user@foo.COM A_US-ER@f.b.org frst.lst@foo.jp a+b@baz.cn]
        addresses.each do |valid_address|
          @user.email = valid_address
          expect(@user).to be_valid
        end
      end
  end

  describe "when email address is already taken" do
      before do
        user_with_same_email = @user.dup
        user_with_same_email.email = @user.email.upcase
        user_with_same_email.save
      end

      it { should_not be_valid }
  end

  describe "when password is not present" do
    before do
      @user = Utilisateur.new(nom: "Example User", email: "user@example.com",
                       password: " ", password_confirmation: " ")
    end
    it { should_not be_valid }
  end

  describe "when password doesn't match confirmation" do
    before { @user.password_confirmation = "mismatch" }
    it { should_not be_valid }
  end

  describe "with a password that's too short" do
     before { @user.password = @user.password_confirmation = "a" * 5 }
     it { should be_invalid }
  end




  describe "return value of authenticate method" do
     before { @user.save }
     let(:found_user) { Utilisateur.find_by(email: @user.email) }

     describe "with valid password" do
       it { should eq found_user.authenticate(@user.password) }
     end

     describe "with invalid password" do
       let(:user_for_invalid_password) { found_user.authenticate("invalid") }

       it { should_not eq user_for_invalid_password }
       specify { expect(user_for_invalid_password).to be_false }
     end
   end

end

还有模型文件：

    class Utilisateur < ActiveRecord::Base

      before_save { self.email = email.downcase }

      validates :nom,  presence: true, length: { maximum: 50 }


      VALID_EMAIL_REGEX = /\A[\w+\-.]+@[a-z\d\-.]+\.[a-z]+\z/i
      validates :email, presence: true, format: { with: VALID_EMAIL_REGEX }, uniqueness: { case_sensitive: false }

      has_secure_password
      validates :password, length: { minimum: 6 }

end

【问题讨论】：

请在此处发布您收到的错误消息。
实际上这不是错误消息，只是以下失败的测试通知：'rspec ./spec/models/utilisateur_spec.rb:125 # Utilisateur return value of authenticate method with invalid password should be false'因为它实际上应该通过
如果您尝试让新用户进行密码测试怎么办？将before { subject.reload } 放在describe "return value of authenticate method" do before { @user.save } 之后或（如果这不起作用）在describe "with invalid password" do 之后。不是“新”用户，最好说“刷新您的用户实例”。
还是一个故障。这很奇怪，因为这是与教程完全相同的代码（用模型名称修改）..

标签： ruby-on-rails-4 rspec-rails

【解决方案1】：

如果您仍然需要答案。你从这个字符串中收到了这个错误：

specify { expect(user_for_invalid_password).to be_false }

你必须使用：

specify { expect(user_for_invalid_password).to be_falsey }

在 rspec echo 中查看相关信息：

1) 密码无效的认证方法的用户返回值应为 false 失败/错误：指定 { expect(user_for_invalid_password).to be_false } 期望 false 回复 false? 或者您的意思是 be false 或 be_falsey

https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers

expect(actual).to be_truthy # 如果实际为真则通过（不是 nil 或假）
expect(actual).to be true # 如果实际 == true 则通过
expect(actual).to be_falsey # 如果实际为假则通过（nil 或假）
expect(actual).to be false # 如果实际 == fals 则通过

【讨论】：