CODEWITHSUNDEEP
ruby-on-railsrails-migrationsruby-on-rails-4
Peeja
Peeja

Reputation: 14264

Why am I asked to run 'rake db:migrate RAILS_ENV=test'?

On Rails 4.0.0.rc1, Ruby 2.0.0, after I run a migration, I see the following error when I try to run a test through rspec:

/Users/peeja/.rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/activerecord-4.0.0.rc1/lib/active_record/migration.rb:376:in `check_pending!': Migrations are pending; run 'rake db:migrate RAILS_ENV=test' to resolve this issue. (ActiveRecord::PendingMigrationError)

That doesn't seem right. No one migrates their test database, do they? They db:test:prepare it, which—to be fair—I've forgotten to do. So I run rake db:test:prepare and run my rspec command again…and see the same error.

If I actually rake db:migrate RAILS_ENV=test, the error does in fact go away.

What's going on? Is this new in Rails 4?

Upvotes: 71

Views: 130065

Answers (7)

x-yuri
x-yuri

Reputation: 18843

It's hard to provide an answer for your case given the information you provided.

In my case it failed to "maintain the schema" (spec/rails_helper.rb, ActiveRecord::Migration.maintain_test_schema!). Because I used the postgres database (running in a docker container). In this case there are 2 solutions:

  • switch to a separate database (something other than postgres)
  • use bin/rails db:migrate RAILS_ENV=test

To give you some more details, what maintain_test_schema! does is it runs bin/rails db:test:prepare if there are pending migrations.

Upvotes: 0

Unkas
Unkas

Reputation: 3710

You can try to set variable BEFORE command, like this. This statement solved my problem:

RAILS_ENV=test rake db:migrate

Upvotes: 0

Jesse Brown
Jesse Brown

Reputation: 709

I've found I have this problem when using chruby to manage my ruby versions. Rails calls bin/rails db:test:prepare via the system command. This doesn't take advantage of chrubys $PATH env var, so it runs as whatever the system ruby is, and fails because of missing gems typically. Unfortunately, I don't currently have a good solution for this.

Upvotes: 3

SilasOtoko
SilasOtoko

Reputation: 132

I still have trouble sometimes in sorting this problem out when I just follow one person's answer so I have thrown a couple together to get better results. Here are the steps I take, not sure which ones are unnecessary, but it works in the end.

  1. add ActiveRecord::Migration.maintain_test_schema! to the top of the test_helper.rb file.
  2. rake test:prepare
  3. rake db:migrate
  4. rake db:migrate RAILS_ENV=test

Then when I run bundle exec rake test I get clean results every time with no pending migrations. (This is what I do right after generating the scaffold the first time). Someone feel free to correct me if you know for sure that one of these steps is absolutely not necessary, but this is how I make sure it works every time.

Upvotes: 11

Peeja
Peeja

Reputation: 14264

As of Rails 4.1, the rake db:test:* tasks are deprecated. Instead, your (test|spec)_helper.rb should include:

ActiveRecord::Migration.maintain_test_schema!

This means that your test database will get the correct schema every time your tests run, whether you run them from a Rake task or not.

Upvotes: 79

meejoe
meejoe

Reputation: 265

You can also try 

rake db:migrate RAILS_ENV=test

which works as

db:test:prepare

does:)

Upvotes: 24

Kris
Kris

Reputation: 19938

Looks like rake test:prepare works, not sure what db:test:prepare now does.

Upvotes: 31

Related Questions