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

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p