Rails 5, Rspec: Environment data not found in the schema
After upgrading a Rails app to Rails 5, running RSpec tests gives me the following error:
rails aborted!
ActiveRecord::NoEnvironmentInSchemaError:
Environment data not found in the schema. To resolve this issue, run:
bin/rails db:environment:set RAILS_ENV=test
However, that bin does not exist and I can't seem to generate it with bundle binstubs rails or with rake rails:update:bin.
I have also tried:
rails db:environment:set RAILS_ENV=test
rake db:environment:set RAILS_ENV=test
There is a related issue on Github here.
How can I address this error?
env RAILS_ENV={{whatever}} bin/rake db:migrate spec used to work just fine
New Rails 5 command to generate binstubs:
rails app:update:bin
Allows me to run the solution as the error suggested:
bin/rails db:environment:set RAILS_ENV=test
Tip from @max comment: If you are using database_cleaner and this error keeps popping up then change your config to:
DatabaseCleaner.clean_with(
:truncation,
except: %w(ar_internal_metadata)
)
For me, this error was followed by a similar one asking for a migration.
This did the trick: rails db:migrate RAILS_ENV=test
fix for jenkins before you drop database you should execute db:environment:set with || true, so the command doesn't abort:
bin/rails db:environment:set RAILS_ENV=test || true
All of the above answers are correct, however, if you're in a more unique project such as developing a rails engine with a concept of a schema (hacky, I know) and your migration fails for some reason, you can re-run it without the check that throws this exception. Example:
rake environment db:{drop,create,migrate} DISABLE_DATABASE_ENVIRONMENT_CHECK=1
For me, I had to do a mixture of things:
bin/rails db:environment:set RAILS_ENV=test
bin/rails db:migrate RAILS_ENV=test
This would make things work, and then I had to review my migrations, I was adding a null:false into a relationship and that added a bug, the migration was cancelled and didn't finish
I had to drop my database for tests and create it again:
psql DROP DATABASE your_db_name_test; bundle exec rake db:create RAILS_ENV=test
After that the warning bin/rails db:environment:set RAILS_ENV=test disappeared.
bundle exec rake db:migrate RAILS_ENV=test
If you happen to see this error while using parallel_tests gem then you need to run below command for each DB. Just increase TEST_ENV_NUMBER.
TEST_ENV_NUMBER=1 bin/rails db:environment:set RAILS_ENV=test
TEST_ENV_NUMBER=2 bin/rails db:environment:set RAILS_ENV=test
This helped me fix the problem when I was testing parallel_tests with knapsack_pro gem https://github.com/KnapsackPro/knapsack_pro-ruby#parallel_tests-with-knapsack_pro-on-single-ci-machine
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- Understanding the Rails Authenticity Token
- How do I get the current absolute URL in Ruby on Rails?
- Rspec, shoulda and spork does not work together
- How do I prepare test database(s) for Rails rspec tests without running rake spec?
- Rails 3.1, RSpec: testing model validations
- Rails 3.1 plugin gem, dummy test app, rspec
- Why am I asked to run 'rake db:migrate RAILS_ENV=test'?
database_cleanerand this error keeps popping up then change your config toDatabaseCleaner.clean_with :truncation, except: %w(ar_internal_metadata)- github.com/DatabaseCleaner/database_cleaner/issues/445database_cleaner >= 1.6.2must have fixed the issue. Do note that if you're running CI tests on a server, all projects that are build there should havedatabase_cleaner >= 1.6.2.%w(ar_internal_metadata)workaround did not work for me. (Rails 6, cucumber-rails 2.0.0, mysql). Any other ideas?