移除User模型的:email唯一性验证后仍出现唯一性验证失败？

Hey there, let’s work through this test issue you’re hitting while following Rails Crash Course by Anthony Lewis. I’ve been in this spot before—double-checking code line by line and still seeing failures can be frustrating, but let’s break it down step by step.

First, Let’s Clarify the Context #

You removed the uniqueness: true line from your User.rb model to troubleshoot, then ran rake test test/models/user_test.rb and got errors. Chances are, the test suite is explicitly expecting that uniqueness validation to be present, so removing it breaks the test’s core expected behavior.

Step 1: Check Your Test Case for Uniqueness Expectations #

First, open up test/models/user_test.rb and look for a test that verifies email uniqueness. It almost certainly looks something like this:

test "email should be unique" do
  duplicate_user = @user.dup
  duplicate_user.email = @user.email.upcase
  @user.save
  assert_not duplicate_user.valid?
end

This test expects that creating a duplicate email user will fail—but since you removed the uniqueness: true validation from the model, the duplicate user is now considered valid. That’s exactly why the test is failing.

Step 2: Fix the Test (or Restore the Validation) #

If your goal is to get the test passing as per the book:

1. Restore the uniqueness: true validation in User.rb. Your validations block should look something like this:

class User < ApplicationRecord
  # Add back the uniqueness validation here
  validates :email, presence: true, uniqueness: true
  # Other validations and code from the book...
end

2. Reset your test database to ensure no leftover data is skewing results:
   • For older Rails versions: rake db:test:prepare
   • For newer Rails versions: rails db:test:prepare (or rails db:reset RAILS_ENV=test)
3. Re-run the test: rake test test/models/user_test.rb

If you removed the validation intentionally to debug something else:

• Temporarily comment out the uniqueness test in user_test.rb so it doesn’t run until you restore the validation. Wrap the test in # comments like this:

# test "email should be unique" do
#   duplicate_user = @user.dup
#   duplicate_user.email = @user.email.upcase
#   @user.save
#   assert_not duplicate_user.valid?
# end

Step 3: If the Test Still Fails After Restoring Validation #

If bringing back the uniqueness: true line doesn’t fix the issue, check these common pitfalls:

• Database Case Sensitivity: Some databases (like PostgreSQL) treat emails as case-sensitive by default. The book might expect case-insensitive uniqueness, so update your validation to:

  validates :email, presence: true, uniqueness: { case_sensitive: false }
  

  You’ll also need a case-insensitive index on the email column. Run this migration:

  def change
    add_index :users, :email, unique: true, using: :btree, expression: 'lower(email)'
  end
  

• Leftover Test Data: Make sure your test database is completely fresh. Run rake db:test:purge then rake db:test:prepare to wipe and rebuild it from scratch.

内容的提问来源于stack exchange，提问作者Christopher Agnus Lam