Skip to main content

Rails: seeds.rb and rake db:test:prepare

Rails has a new feature that allows you to put "seed" data into db/seeds.rb. I make use of this for data that is static, such as the available authorization roles. I also make use of Factory Girl for test data. I consider the two things to be very different. Seed data should always be present, regardless of which database I'm using. My Factory Girl data is only for tests.

I noticed that lib/tasks/cucumber.rake now requires db:test:prepare:{:ok => 'db:test:prepare'}, 'Run features that should pass') do |t|
This broke many of my tests because it wiped out my seed data. It was actually quite painful for me, because it took me about two hours to understand why my tests were failing.

Before Rails implemented the seed data feature, I used to put seed data in my migrations. Yeah, I know--naughty. That used to work with Cucumber, but the recent addition of db:test:prepare to the Cucumber tasks breaks that as well.

I tried to hack the Cucumber tasks to also require db:seed, but I was met with another surprise. When it ran the seed file, the RAILS_ENV was set to development! I would have expected test or cucumber, but definitely not development.

I brought the issue up on the Cucumber mailing list, so hopefully they'll set me or the code straight. In my own code, I decided to update the Cucumber tasks to not use rake db:test:prepare.

rake db:test:prepare has always given me problems since schema.rb doesn't accurately represent everything I put in my migrations. For instance, sometimes I have to make use of custom MySQL features using custom SQL. By the way, I still like foreigner for foreign key constraints.


Unknown said…
make a file called local.rb in your /features/support directory

put this in it...

seed_file = File.join(Rails.root, "db", "seeds.rb")

This will let you keep the seed data in that one spot and still load it into cuke.
jjinux said…
Maybe Cucumber should do that by default now that Rails has this new seeds feature.
appworks said…
Had a similar situation. I came with two options:

Either drop the following code in any .rb file inside 'features/support/' directory

require "#{Rails.root}/db/seeds.rb"

(this will load seed data into test env)


Create the following task in cucumber.rake (inside :cucumber namespace)

task :load_seed_data => :environment do

and modify the existing tasks to include this task;
such as :{:ok => 'db:test:prepare','cucumber:load_seed_data'}

Hope that helps someone.
jjinux said…
Thanks, nEo.X.
Unknown said…
I have been trying for some time now to get this to work. I tried all 3 "solutions" as indicated by bleonard and nEo.X and still no luck. Is the additional clarification?
jjinux said…
Are you using the newest version of Rails? What exactly is the problem? Does "rake db:seed" exist? Are you trying to get it to run before your tests or something?
Dennis Burton said…
thanks for this post. I was having trouble tracking this behavior down

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…