Logo: Relish

  1. Sign in

Project: Bogus 0.1.2


Instances of ActiveRecord::Base subclasses are different then most of the objects you might encounter because the field access on those classes is done by taking advantage of Ruby's method_missing functionality.

Unfortunately, in order to create a fake, Bogus has to examine all of the methods that are defined on a given class and herein lies the problem, the methods that you would expect to have on your ActiveRecord models do not exist:

class BlogPost < ActiveRecord::Base

blog_post = BlogPost.new
blog_post.respond_to?(:name) # => true
blog_post.method(:name) # raises NameError

Normally, this would prevent Bogus from being able to fake those methods, but in the case of ActiveRecord we can figure out those fields by looking at the BlogPost.columns property. Based on that we can define those accessors on the created fake. If you wish to take advantage of that, you just need to flip a configuration switch:

Bogus.configure do |c|
  c.fake_ar_attributes = true
Adding missing accessors to AR classes
a file named "blog_post.rb" with:
require 'active_record'
require 'nulldb'

ActiveRecord::Schema.verbose = false
ActiveRecord::Base.establish_connection :adapter => :nulldb

ActiveRecord::Schema.define do
  create_table :blog_posts do |t|
    t.string :name
    t.string :tags

class BlogPost < ActiveRecord::Base

Bogus.configure do |c|
  c.fake_ar_attributes = true
the following test should pass:
require_relative 'blog_post'

post = fake(:blog_post, name: "the name")
stub(post).tags { "foo, bar" }

post.name.should == "the name"
post.tags.should == "foo, bar"

Last published over 7 years ago by Adam Pohorecki.