当我运行bundle exec rspec spec /时，我得到21个例子和3个故障。这些故障是：Hartl教程第7章中出现故障的问题
失败：
1）用户has_password？如果密码匹配 故障/错误的方法应该是真实的：？@ user.has_password（@ ATTR [：密码]）。应该be_true NoMethodError： 未定义的方法在'has_password?' for nil:NilClass # ./spec/models/user_spec.rb:47:in块（3级）
2）用户has_password？方法应该是假的，如果密码不匹配 故障/错误：@ user.has_password（“无效”）应be_false NoMethodError：在“
3）用户 未定义的方法has_password?' for nil:NilClass # ./spec/models/user_spec.rb:51:in块（3级）密码验证应该接受有效的电子邮件地址 故障/错误：它“应该拒绝无效的电子邮件地址”做 NoMethodError： 未定义的方法it' for #<RSpec::Core::ExampleGroup::Nested_3::Nested_3:0x00000102eb38b0> # ./spec/models/user_spec.rb:97:in块（3级）的“
我会后我的user_spec.rb文件BC我认为它几乎是正确的，但不完全。注意到注释结束，我曾经玩过这些游戏，但认为它们是错误的，因此将它们评论出来。
require 'spec_helper'
describe User do
before(:each) do
@attr = {
:name => "Example User",
:email => "[email protected]",
:password => "foobar",
:password_confirmation => "foobar" }
end
it "should create a new instance given valid attributes" do
User.create!(@attr)
end
describe "password encryption" do
before(:each) do
@user = User.create!(@attr)
end
it "should have an encrypted password attribute" do
@user.should respond_to(:encrypted_password)
end
it "should set the encrypted password" do
@user.encrypted_password.should_not be_blank
end
end
describe "has_password? method" do
it "should be true if the passwords match" do
@user.has_password?(@attr[:password]).should be_true
end
it "should be false if the passwords don't match" do
@user.has_password?("invalid").should be_false
end
end
describe "password validations" do
it "should require a password" do
User.new(@attr.merge(:password => "", :password_confirmation => "")).
should_not be_valid
end
it "should require a matching password confirmation" do
User.new(@attr.merge(:password_confirmation => "invalid")).
should_not be_valid
end
it "should reject short passwords" do
short = "a" * 5
hash = @attr.merge(:password => short, :password_confirmation => short)
User.new(hash).should_not be_valid
end
it "should reject long passwords" do
short = "a" * 5
hash = @attr.merge(:password => short, :password_confirmation => short)
User.new(hash).should_not be_valid
end
it "should require a name" do
no_name_user = User.new(@attr.merge(:name => ""))
no_name_user.should_not be_valid
end
it "should require an email address" do
no_email_user = User.new(@attr.merge(:email => ""))
no_email_user.should_not be_valid
end
it "should accept valid email addresses" do
addresses = %w[[email protected] [email protected] [email protected]]
addresses.each do |address|
valid_email_user = User.new(@attr.merge(:email => address))
valid_email_user.should be_valid
end
#end
it "should reject invalid email addresses" do
addresses = %w[[email protected],com user_at_foo.org [email protected]]
addresses.each do |address|
invalid_email_user = User.new(@attr.merge(:email => address))
invalid_email_user.should_not be_valid
end
#end
it "should reject duplicate email addresses" do
# Put a user with given email address into the database.
User.create!(@attr)
user_with_duplicate_email = User.new(@attr)
user_with_duplicate_email.should_not be_valid
end
it "should reject email addresses identical up to case" do
upcased_email = @attr[:email].upcase
User.create!(@attr.merge(:email => upcased_email))
user_with_duplicate_email = User.new(@attr)
user_with_duplicate_email.should_not be_valid
end
it "should reject names that are too long" do
long_name = "a" * 51
long_name_user = User.new(@attr.merge(:name => long_name))
long_name_user.should_not be_valid
end
end
end
end
end
我的user.rb文件很好，我认为。
因此，3次失败的事情是我的问题的一个方面，但真正让我担心的事情是下面的命令：
束的exec rspec的规格/型号/ user_spec.rb -e“？has_password \法”
结果在终端是这样的：
否例子匹配{：full_description => /（ - 混合物：？has_password \\？\方法）/}。
成品在0.00003秒 0实施例中，0失败
根据Hartl的我应该有2个实施例中，和0故障。想法？任何输入赞赏:)你的user_spec.rb文件中的