ruby on rails - Rspec and testing instance methods -


here rspec file:

require 'spec_helper'  describe classroom, focus: true    describe "associations"     { should belong_to(:user) }   end    describe "validations"     { should validate_presence_of(:user) }   end    describe "instance methods"      describe "archive!"       before(:each)         @classroom = build_stubbed(:classroom)       end        context "when classroom active"         "should mark classroom inactive"           @classroom.archive!           @classroom.active.should_be == false         end       end      end    end  end

here classroom factory:

factorygirl.define    factory :classroom     name "hello world"     active true      trait :archive       active false     end   end  end

when instance method test runs above, receive following error: stubbed models not allowed access database

i understand why happening (but lack of test knowledge/being newb testing) can't figure out how stub out model doesn't hit database

working rspec tests:

require 'spec_helper'  describe classroom, focus: true    let(:classroom) { build(:classroom) }    describe "associations"     { should belong_to(:user) }   end    describe "validations"     { should validate_presence_of(:user) }   end    describe "instance methods"      describe "archive!"        context "when classroom active"         "should mark classroom inactive"           classroom.archive!           classroom.active == false         end       end      end    end  end

your archive! method trying save model database. , since created stubbed model, doesn't know how this. have 2 possible solutions this:

  • change method archive, don't save database, , call method in spec instead.
  • don't use stubbed model in test.

thoughtbot provides example of stubbing dependencies here. subject under test (orderprocessor) bona fide object, while items passed through stubbed efficiency.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more