Databases
StackOverflow2013
Postsdbo
PORSpec + FactoryGirl should_receive failing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORSpec + FactoryGirl should_receive failing
    primarykey
    data
    text
    <p>I can't figure out why this RSpec test fails. Any advice? I'm new-ish to FactoryGirl, RSpec, and TDD in general.</p> <h3>Controller:</h3> <pre><code>def update @vendor = current_user.vendors.find(params[:id]) if @vendor.update_attributes(params[:vendor]) redirect_to vendor_path(@vendor) else render 'edit' end end </code></pre> <h3>Test:</h3> <pre><code>require 'spec_helper' describe VendorsController do login_user before :each do @user = subject.current_user @vendor = FactoryGirl.create(:vendor, :user =&gt; @user) end [...] describe 'POST update' do def do_update post :update, :id =&gt; @vendor.id, :vendor =&gt; FactoryGirl.attributes_for(:vendor) end [...] it 'should update a given vendor' do do_update @vendor.should_receive(:update_attributes).with(FactoryGirl.attributes_for(:vendor)) end end end </code></pre> <h3>Factory:</h3> <pre><code>FactoryGirl.define do factory :vendor do name 'Widget Vendor' user end end </code></pre> <h3>The Failure:</h3> <pre><code>Failures: 1) VendorsController POST update should update a given vendor Failure/Error: @vendor.should_receive(:update_attributes).with(FactoryGirl.attributes_for(:vendor)) (#&lt;Vendor:0x007faeb75e77d0&gt;).update_attributes({:name=&gt;"Widget Vendor"}) expected: 1 time received: 0 times # ./spec/controllers/vendors_controller_spec.rb:108:in `block (3 levels) in &lt;top (required)&gt;' </code></pre> <h3><em>Update:</em></h3> <p>I'm a little closer, now. I changed the test to the following:</p> <pre><code>it 'should update a given vendor' do Vendor.any_instance.should_receive(:update_attributes).with(FactoryGirl.attributes_for(:vendor)) do_update end </code></pre> <p>And the new error is:</p> <pre><code>Failures: 1) VendorsController POST update should update a given vendor Failure/Error: post :update, :id =&gt; @vendor.id, :vendor =&gt; FactoryGirl.attributes_for(:vendor) #&lt;Vendor:0x007ff30d765900&gt; received :update_attributes with unexpected arguments expected: ({:name=&gt;"Widget Vendor"}) got: ({"name"=&gt;"Widget Vendor"}) # ./app/controllers/vendors_controller.rb:33:in `update' # ./spec/controllers/vendors_controller_spec.rb:98:in `do_update' # ./spec/controllers/vendors_controller_spec.rb:108:in `block (3 levels) in &lt;top (required)&gt;' </code></pre> <h3>Answer...?</h3> <p>Well, this worked. There has to be a better way of doing this, though:</p> <p><code>Vendor.any_instance.should_receive(:update_attributes).with(JSON.parse(FactoryGirl.attributes_for(:vendor).to_json)).and_return(true)</code></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USclem
    1. USclem
    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
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORSpec + FactoryGirl should_receive failing
      1. USdutchstrider
      1. VTFavorite
    1. COOn a general note: are you sure that @vendor.should_receive is sufficient as an assertation for "should update a given vendor"? You are always calling update_attributes - so even if it raises an error and your user is not updated, your test will succeed.
      singulars
      1. PORSpec + FactoryGirl should_receive failing
      1. USemrass
    2. COI suppose I could add `and_return(true)` to the end of that line.
      singulars
      1. PORSpec + FactoryGirl should_receive failing
      1. USclem
    3. COThat sounds reasonable (got to admit I'm also no expert in testing with RSpec).
      singulars
      1. PORSpec + FactoryGirl should_receive failing
      1. USemrass
 

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