Rails 3到4迁移唯一性验证问题

Question

上下文

我们正在从Rails 3.2.12迁移到4.0.2和Ruby 1.9.3到2.1.8。

我们有很多测试覆盖率来完成RSpec形式的迁移。

问题

一说检查是在卡模型验证的唯一失败的规范的。

validates :mobile, uniqueness: {scope: :program_member_id, message: I18n.t('models.card.error.cardholder_already_has_mobile')}, if: :mobile 

凡program_member可能只有一个mobile: true卡。

该规范会为会员创建2张卡片，将其中一张转换为移动卡片，然后期待第二张卡片这样做时的验证消息。

let(:program) { FactoryGirl.create(:program) } 
let(:card) { FactoryGirl.create(:card, program: program) } 

context 'when cardholder already has a mobile card' do 
    it 'fails validation' do 
    card2 = FactoryGirl.create(:card, program: program) 
    program_member_user = FactoryGirl.create(:program_member_user, card_number: card2.cardnumber) 
    program_member = program_member_user.program_members.first 

    program_member.cards << card2 
    card2.update_attributes(:mobile => true) 

    program_member.cards << card 
    card.update_attributes(:mobile => true) 

    expect(card.errors.messages).to include(:mobile=>[I18n.t('models.card.error.cardholder_already_has_mobile')]) 
    end 
end 

后市展望：

expected {} to include {:mobile=>["Cardholder already has a mobile card"]} 

当我去我们master分支，该规范通过。

从这个规范工作到失败的唯一因素是Rails 3到4的迁移。

尝试在控制台中运行规范代码才发现该成员有两个移动卡，并且对两个实例都做了card.valid?返回true。

问题

有没有什么Rails中4改变了问候的唯一性验证或验证生命周期？

Answer 1

好吧，我正在做点什么。

我使用相同的Ruby和Rails版本创建了一个测试项目。

https://github.com/frank184/test_uniquness

在这个项目中，我将有一个具有admin列具有类似验证的一个boolean User模型。

validates_uniqueness_of :admin, if: :admin? 

我用shoulda-matchers和rspec来描述期望的结果。

require 'rails_helper' 

RSpec.describe User, type: :model do 
    let(:user) { build :user } 
    subject { user } 

    describe 'validations' do 
    context 'when admin = true' do 
     before(:each) { user.admin = true } 
     it { is_expected.to validate_uniqueness_of(:admin) } 
    end 
    end 
end 

该规范失败，出现以下的输出：

Failures: 

    1) User validations when admin = true should validate that :admin is case-sensitively unique 
    Failure/Error: it { is_expected.to validate_uniqueness_of(:admin) } 

     User did not properly validate that :admin is case-sensitively unique. 
     After taking the given User, whose :admin is ‹true›, and saving it as 
     the existing record, then making a new User and setting its :admin to 
     ‹true› as well, the matcher expected the new User to be invalid, but 
     it was valid instead. 
    # ./spec/models/user_spec.rb:10:in `block (4 levels) in <top (required)>' 

Finished in 0.11435 seconds (files took 0.79997 seconds to load) 
1 example, 1 failure 

我决定，该代码是好的，碰到的Rails 4.1.0，以准确。

规范通过！

bundle update 
rspec 
. 

Finished in 0.09538 seconds (files took 1.28 seconds to load) 
1 example, 0 failures