I'm using rails-rspec
gem and I have several specs (models, controllers, etc). When I run:
bundle exec rake
everything is tested. However, I would like to improve my specs by seeding some data (from db/seeds.rb) just after the database is created (in test environment).
My spec/spec_helper.rb file looks like this:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'
require 'capybara/rspec'
require 'ruby-debug'
# Requires supporting ruby files with custom matchers and macros, etc,
# in spec/support/ and its subdirectories.
Dir[Rails.root.join("spec/support/**/*.rb")].each {|f| require f}
RSpec.configure do |config|
config.mock_with :rspec
# Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
config.fixture_path = "#{::Rails.root}/spec/fixtures"
# If you're not using ActiveRecord, or you'd prefer not to run each of your
# examples within a transaction, remove the following line or assign false
# instead of true.
config.use_transactional_fixtures = false
config.include SpecHelper
config.before(:suite) do
DatabaseCleaner.strategy = :truncation
DatabaseCleaner.clean_with(:truncation)
end
config.before(:each) do
DatabaseCleaner.start
stub_xmpp_rest_client!
end
config.after(:each) do
DatabaseCleaner.clean
end
config.include Devise::TestHelpers, :type => :controller
config.include Delorean
config.after(:each) { back_to_the_present }
config.include Factory::Syntax::Methods
config.extend ControllerMacros, :type => :controller
end
What could do the best way to do so? Thanks.
I set up my
rake spec
task to automatically load db/seeds.rb, so I depend on that for setting up the database for a first run. Add this to your Rakefile:Then, on subsequent runs I just call
rspec spec
directly to skip the seed step and avoid unnecessary reloading. I configure database cleaner to ignore the seed tables like this:For scenarios that need committed data, I can add:
This will truncate everything after the example runs, except the seed tables. It's assumed that you never write anything to the seed tables! This is generally a safe assumption, since seed data is typically static.
For all other normal scenarios, I depend on transactions to roll back any inserted records. The database is returned to the original state, with the data in the seed tables intact. It's safe to write to the seed tables here if you need to.
To rebuild the seed tables, you just need to run
rake spec
again.In Rails 4.2.0 and RSpec 3.x, this is how my rails_helper.rb looks.
I think we should use
as before(:all) runs the block one time before all of the examples are run.
So if we use
before :all
, the seed data will be cleared.copy the seed.rb file inside the config/initializers folder.So seed.rb file will be executed on server start.
Run the below command to fill the test db with the seed.rb data
RAILS_ENV=test rake db:seed
Bad idea! Never, ever, seed your test database. Use factories to create, within each test, only the records necessary for that test to pass. Seeding the test database will make your tests less reliable, because you'll be making lots of assumptions that aren't explicitly stated in your tests.
To load seeds in rspec you need to add it after database cleanup in confg.before(:suite) in spec_helper