ファクトリー・ガール、InvalidRecordエラー

Question

の問題、私はエラーに問題があります。

let(:ind2){ build(:ind2) } 

RSpecのテスト：

describe '#client_free_time_validation' do 
    let(:ind) { build(:ind).tap {|e| p e.valid?; p e.errors}} 
    let(:ind2){ build(:ind2).tap {|e| p e.valid?; p e.errors} } 

    context 'when training is during another training' do 
     it 'raises an error' do 
     expect(ind.valid?).to be_truthy 
     expect(ind2.valid?).to be_falsey 
     # expect(ind2.errors.count).to eq 1 
     # expect(ind2.errors[:base]).to eq(['Masz w tym czasie inny trening.']) 
     end 
    end 

工場：

このによって引き起こさ

ActiveRecord::RecordInvalid 

を

FactoryGirl.define do 
    factory :individual_training do 
    date_of_training { Date.today.next_week.advance(days: 1) } 
    association :client, factory: :client 
    association :trainer, factory: :trainer 
    start_on Time.parse('12:30') 
    end_on Time.parse('13:30') 
    association :training_cost, factory: :tc2 

    factory :ind do 
     start_on Time.parse('11:00') 
     end_on Time.parse('12:00') 
    end 

    factory :ind2 do 
     start_on Time.parse('10:30') 
     end_on Time.parse('11:30') 
    end 
    end 
end 

同様のletが別のテストで動作しているので、私は混乱しています。私はtapメソッドを使ってデバッグしようとしましたが、エラーメッセージを表示しません。

私はいくつかの追加データ（モデルの見た目など）を書いてください。

私が最初のletまたは2番目にコメントすれば、テストに合格することが分かりました。 2つのlet（indとind2）のような状況を一緒に扱うことはできませんでした。属性の 例値は、テストによって生成：

#<ActiveModel::Errors:0x00000001f4ade8 @base=#<IndividualTraining id: nil, date_of_training: "2016-08-23", client_id: 28, trainer_id: 29, start_on: "2016-08-20 11:00:00", end_on: "2016-08-20 12:00:00", training_cost_id: 4>, @messages={}> 

あなたは無効であるものを記録デバッグする方法の提案を持っていますか？

更新：

完全なエラーメッセージ：

Failure/Error: let(:ind2){ build(:ind2).tap {|e| p e.valid?; p e.errors} } 

ActiveRecord::RecordInvalid: 
    Nieprawidłowy rekord 

# /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/validations.rb:79:in `raise_record_invalid' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/validations.rb:43:in `save!' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/attribute_methods/dirty.rb:29:in `save!' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:291:in `block in save!' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:220:in `transaction' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:348:in `with_transaction_returning_status' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activerecord-4.2.5.1/lib/active_record/transactions.rb:291:in `save!' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/configuration.rb:18:in `block in initialize' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/evaluation.rb:15:in `create' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/strategy/create.rb:12:in `block in result' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/strategy/create.rb:9:in `tap' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/strategy/create.rb:9:in `result' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/factory.rb:42:in `run' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/factory_runner.rb:29:in `block in run' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:166:in `instrument' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/factory_runner.rb:28:in `run' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/strategy/build.rb:5:in `association' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/evaluator.rb:31:in `association' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute/association.rb:19:in `block in to_proc' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/evaluator.rb:75:in `instance_exec' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/evaluator.rb:75:in `block in define_attribute' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute_assigner.rb:56:in `get' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute_assigner.rb:16:in `block (2 levels) in object' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute_assigner.rb:15:in `each' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute_assigner.rb:15:in `block in object' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute_assigner.rb:14:in `tap' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/attribute_assigner.rb:14:in `object' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/evaluation.rb:12:in `object' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/strategy/build.rb:9:in `result' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/factory.rb:42:in `run' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/factory_runner.rb:29:in `block in run' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:166:in `instrument' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/factory_runner.rb:28:in `run' 
    # /home/lukas/.rvm/gems/ruby-2.3.1/gems/factory_girl-4.7.0/lib/factory_girl/strategy_syntax_method_registrar.rb:20:in `block in define_singular_strategy_method' 
    # ./spec/models/individual_training_spec.rb:60:in `block (3 levels) in <top (required)>' 
    # ./spec/models/individual_training_spec.rb:65:in `block (4 levels) in <top (required)>' 

アップデート2：

私は工場でdate_of_training Date.todayを設定する際にエラーが消えます。また、2016-08-23のように手動で日付を設定しようとしましたが、まだInvalidRecordです。また、Date.today + 1.dayは機能しません。何が間違っているのでしょうか？たぶんdate_of_trainingは直接の問題ではないでしょう。

アップデート3： IndividualTrainingモデルの検証：

private 

    def date_and_start_on_validation 
    unless start_on.blank? 
     if date_of_training < Date.today 
     errors.add(:base, 'You cannot set individual training before today.') 
     elsif date_of_training == Date.today 
     if start_on <= Time.now 
      errors.add(:base, 'Time of today training is before current time.') 
     end 
     end 
    end 
    end 

    # check if trainer work while will be individual_training 
    def date_of_training_validation 
    unless start_on.blank? 
     trainer.work_schedules.each_with_index do |ti, ind| 
     if ti.day_of_week == BackendController.helpers.translate_date(date_of_training) 
      if (start_on.strftime('%H:%M')..end_on.strftime('%H:%M')) 
      .overlaps?(ti.start_time.strftime('%H:%M')..ti.end_time.strftime('%H:%M')) 
      break 
      else 
      errors.add(:base, 'Training is outside of trainer work schedule.') 
      end 
     elsif ind == trainer.work_schedules.size - 1 
      errors.add(:base, 'In this day trainer doesn't work.') 
     end 
     end 
    end 
    end 

    # check if client doesn't have another training or activity 
    def client_free_time_validation 
    unless start_on.blank? 
     client.individual_trainings_as_client.where(date_of_training: date_of_training) 
      .where('id != ?', id).each do |ci| 
     if (start_on...end_on).overlaps?(ci.start_on...ci.end_on) 
      errors.add(:base, 'You have another training.') 
     end 
     end 
     client.activities.where(day_of_week: BackendController.helpers.translate_date(date_of_training)) 
      .each do |ca| 
     if (start_on...end_on).overlaps?(ca.start_on...end_on) 
      errors.add(:base, 'You have another activity.') 
     end 
     end 
    end 
    end 

更新4： 私が最初にind.valid実行するとことに気づきましたか？ - それは真でind2はRecordInvalidになります。しかし、私が読み込んで、ind2.validをチェックしたら？ - 今は真実であり、虚偽である。

更新5： 私は同じletを別のコンテキストで別々に使用し、rspecは成功しました。私は同じコンテキストで2つを使用することはできません理由は何ですか？

IndividualTraining団体

belongs_to :trainer, class_name: 'Person', foreign_key: 'trainer_id' 
    belongs_to :client, class_name: 'Person', foreign_key: 'client_id' 
    belongs_to :training_cost 

クライアントとトレーナー工場

FactoryGirl.define do 
    factory :person do 
    pesel { Faker::Number.number(11) } 
    first_name 'Thomas' 
    last_name 'Owel' 
    date_of_birth { Faker::Time.between('1970-01-01', '2000-12-31') } 
    email { Faker::Internet.email } 
    password { Faker::Internet.password } 
    type 'Person' 
    end 

    factory :client, parent: :person, class: 'Client' do 
    first_name { Faker::Name.first_name } 
    last_name { Faker::Name.last_name } 
    type 'Client' 
    end 
    factory :trainer, parent: :person, class: 'Trainer' do 
    first_name { Faker::Name.first_name } 
    last_name { Faker::Name.last_name } 
    type 'Trainer' 
    salary { Faker::Number.decimal(4, 2) } 
    hiredate { Faker::Time.between('2016-01-01', '2016-04-30') } 
    end 
end 

更新6：私はこれを聞かせてい別の文脈では ：

let(:individual_training) { build :individual_training, trainer_id: work_schedule[:person_id] } 
let(:ind2) do 
    build :individual_training, 
     trainer_id: work_schedule[:person_id], 
     date_of_training: Date.today.next_week.advance(days: 0), 
     start_on: Time.now - 1.hour, 
     end_on: Time.now 
end 

この素敵な作品。エラーがない：RecordInvalid

Answer 1

これらは「不正なレコードエラー」の背後にある理由かもしれない - まず

Reason - It usually happens when you use "create" and "build" together. 
create method persists the instance while the build method keeps it only in memory. 

が、私はあなたのビルド方法を使用することをお勧めし、それに関連した検証をご確認くださいます。あなたのバリデーションに何か問題があります。