|connection_info = YAML.load_file("config/database.yml")["test"]|
|RSpec.configure do |config||
|config.around do |example||
|class Coderetreat < ActiveRecord::Base|
|describe Coderetreat do|
|describe ".running_today" do|
|it "returns a coderetreat scheduled for today" do|
|coderetreat = Coderetreat.create! city: "Chicago", scheduled_on: Date.today|
|Coderetreat.running_today.all.should =~ [coderetreat]|
|it "does not return a coderetreat not scheduled for today" do|
|coderetreat = Coderetreat.create! city: "Chicago", scheduled_on: Date.today.advance(:days => -1)|
|#Some databases get upset if you try to start a new transaction while a transaction is already in play, so running the whole spec suite chokes when rspec is trying to start a transaction. You need to update your spec_helper to rely on active_record_spec_helper to do this for you.|
|#Replace this line|
|config.use_transactional_fixtures = true|
Dec 28, 2012
What happens with a class with a lot of relations? We may end up manually requiring a lot of things, won't we? Or is there a catch that I'm not seeing?
@brandonhilkert that's cool! But if you use
capybara-webkit for example, this doesn't work :(
@brandonhilkert I mean, unless you workaround https://gist.github.com/4469873
Jan 8, 2013
Two things I've noticed:
- I had to require the model like this
- When loading the full stack I had an
ActiveModel::MassAssignmentSecurity::Errorwhich passed with this approach
Not sure if I'm doing anything wrong. The idea is awesome though.
Jan 30, 2013
@zamith, I had the same problem. Were you sure to add the
-I app line to your
.rspec file? Then you
require 'models/coderetreat'. That fixed it for me.
Sep 7, 2013
If you are using Rails 4 with SQLite and database_cleaner 1.1.1 you get this error
undefined local variable or method `postgresql_version'
to solve the problem downgrade to database_cleaner 1.0.1
Thank you @coreyhaines for sharing this.
Nov 22, 2014
I had to add
require "yaml" to the top of
active_record_spec_helper to get this to work. RSpec 3.1.7, Rails 4.1.8.
Nov 26, 2014
I love this idea, and I really want to implement it more in my test suites. But I'm having the problem that my ActiveRecord models just have too damn many dependencies, and I have to add so many "requires" at the top of my spec file that I might as well just require
Of course, the obvious solution here is to reduce the number of dependencies. And in some cases this is pretty easy, but it's often not, because a lot of the dependencies are due to my associations.
E.g. say I have an model
User that looks like this:
class Comment < ActiveRecord::Base belongs_to :design end
If I set up my spec like this:
require 'active_record_spec_helper' require "comment" describe Comment do ... whatever end
... then it will fail, because when it tries to load "comment.rb", it hits the line
belongs_to :design, and starts looking for a
Design class - which hasn't been required, so the whole thing crashes with
uninitialized constant Comment::Design.
So I add
require 'design' to the top of my spec - but within my
Design class I have the line
belongs_to :user, which crashes with
uninitialized constant Design::User... so I add
require 'user' to the top of my spec, which hits the line
has_many :posts and raises
uninitialized constant User::Post... and so on until I've required almost my entire
Is there something conceptual I'm missing? How do I get around this? Basic Rails associations don't seem like something I should be refactoring out into a separate class or module, and stubbing out the associations feels a bit icky too (plus I'm not entirely sure how to do it anyway.)
Anyone have any pointers?
Dec 16, 2014
Sorry, me again. StackOverflow bounty is available to anyone who can help me out with the above question:
Jul 8, 2015
Did anyone came up with a solution to the question of georgemillo? I also struggle with the idea of loading all dependent models, which is undesireable to me.
@brandonhilkert Thanks. I'm going to try that.