Databases
StackOverflow2013
Postsdbo
POwhy is before :save callback hook not getting called from FactoryGirl.create()?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POwhy is before :save callback hook not getting called from FactoryGirl.create()?
    primarykey
    data
    text
    <p>This simple example uses DataMapper's <code>before :save</code> callback (aka hook) to increment <code>callback_count</code>. callback_count is initialized to 0 and should be set to 1 by the callback.</p> <p>This callback is invoked when the TestObject is created via:</p> <pre><code>TestObject.create() </code></pre> <p>but the callback is skipped when created by FactoryGirl via:</p> <pre><code>FactoryGirl.create(:test_object) </code></pre> <p>Any idea why? [Note: I'm running ruby 1.9.3, factory_girl 4.2.0, data_mapper 1.2.0]</p> <p>Full details follow...</p> <h2>The DataMapper model</h2> <pre><code># file: models/test_model.rb class TestModel include DataMapper::Resource property :id, Serial property :callback_count, Integer, :default =&gt; 0 before :save do self.callback_count += 1 end end </code></pre> <h2>The FactoryGirl declaration</h2> <pre><code># file: spec/factories.rb FactoryGirl.define do factory :test_model do end end </code></pre> <h2>The RSpec tests</h2> <pre><code># file: spec/models/test_model_spec.rb require 'spec_helper' describe "TestModel Model" do it 'calls before :save using TestModel.create' do test_model = TestModel.create test_model.callback_count.should == 1 end it 'fails to call before :save using FactoryGirl.create' do test_model = FactoryGirl.create(:test_model) test_model.callback_count.should == 1 end end </code></pre> <h2>The test results</h2> <pre><code>Failures: 1) TestModel Model fails to call before :save using FactoryGirl.create Failure/Error: test_model.callback_count.should == 1 expected: 1 got: 0 (using ==) # ./spec/models/test_model_spec.rb:10:in `block (2 levels) in &lt;top (required)&gt;' Finished in 0.00534 seconds 2 examples, 1 failure </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USfearless_fool
    1. USfearless_fool
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POwhy is before :save callback hook not getting called from FactoryGirl.create()?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POwhy is before :save callback hook not getting called from FactoryGirl.create()?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you post the whole thing somewhere? Because `FactoryGirl.create(:stuff)` in my tests goes through `before :save`
      singulars
      1. POwhy is before :save callback hook not getting called from FactoryGirl.create()?
      1. USenthrops
    2. CO@enthrops: done.
      singulars
      1. POwhy is before :save callback hook not getting called from FactoryGirl.create()?
      1. USfearless_fool
    3. CO@enthrops: can you confirm that the above works in your environment, and, if so, version numbers for ruby, FactoryGirl and DataMapper?
      singulars
      1. POwhy is before :save callback hook not getting called from FactoryGirl.create()?
      1. USfearless_fool
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload