如何在错误的rspec规范之间清理数据库? [英] How can I clean my database between erroneous rspec specs?
问题描述
我已将database_cleaner gem添加到我的rails应用程序中,以便在两次规格之间清理我的数据库.这是我当前在spec/spec_helper.rb
中配置的database_cleaner:
I have added the database_cleaner gem to my rails application in order to clean my database between specs. Here's my current configuration for database_cleaner, located in spec/spec_helper.rb
:
config.before(:suite) do
DatabaseCleaner.strategy = :transaction
DatabaseCleaner.clean_with(:truncation)
DatabaseCleaner.start
DatabaseCleaner.clean
end
config.before(:each) do
DatabaseCleaner.clean
end
config.after(:each) do
DatabaseCleaner.clean
end
config.after(:suite) do
DatabaseCleaner.clean
end
现在,只要运行的每个最后一个规范通过或失败,此配置就可以正常工作.
Now, this configuration works fine, so long as every last spec that is run either passes or fails.
但是,在发生错误的情况下(rspec不会像minitest那样给您一个很好的E
小东西,它会抛出这种事情:
However, in the event of an error (rspec doesn't give you a nice little E
like minitest, it throws this sort of thing:
09:17:32 - INFO - Running: spec
/usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/gems/1.9.1/gems/activerecord-4.0.1/lib/active_record/validations.rb:57:in `save!': Validation failed: Email has already been taken (ActiveRecord::RecordInvalid)
),未清除数据库!错误即将保留在数据库中之前,来自规范的剩余数据.我想这是因为database_cleaner不会认为错误的规范已经完成,因此也不会清理数据库.
), the database isn't cleaned! Residual data from the spec just before the error stays in the database. I suppose this is because database_cleaner doesn't regard the erroneous spec as finishing and so doesn't clean the database.
现在,这不会真正造成任何伤害,除非您再次运行规格.然后,残留数据将导致类似于以下内容的错误:
Now, this doesn't really cause any harm until you run your specs again. The residual data then causes an error analogous to this:
09:17:32 - INFO - Running: spec
/usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/gems/1.9.1/gems/activerecord-4.0.1/lib/active_record/validations.rb:57:in `save!': Validation failed: Email has already been taken (ActiveRecord::RecordInvalid)
解决这个错误很简单;运行rails_env=test rake db:reset
或启动数据库外壳并使用sql语句清空相关表将清除此数据,并使规范运行顺利.
Getting around this error is simple enough; running rails_env=test rake db:reset
or firing up your database shell and emptying the relevant tables with sql statements will clear this data and allow the specs to be run without a hitch.
但是,这变得令人讨厌.我的任何一种规格中的一个错误角色(任何使其错误而不是失败的错误)都会导致我的整个测试工作流程陷入困境,就像自动武器的发射机制一样!
However, this is getting annoying. One wrong character in any of my specs (anything to make it erroneous rather than a failure) causes my whole testing workflow to jam up, almost like the firing mechanism of an automatic weapon!
您对database_cleaner有什么建议?您是否有任何示例配置,即使在测试错误的情况下也可以清理数据库?
What are your suggestions regarding database_cleaner? Do you have any example configurations that allow for the database to be cleaned, even in the event of an erroneous test?
我正在使用警卫来运行我的rspec,并进一步增加了factory-girl:
I'm using guard to run my rspecs that are further augmented with factory-girl:
宝石文件:
source 'https://rubygems.org'
group :development do
gem 'capistrano'
gem 'rb-fsevent'
gem 'debugger'
end
group :development, :test do
gem 'rspec-rails', '~> 2.14.0'
gem 'sqlite3'
gem 'guard-rspec'
gem 'guard-livereload', require: false
gem 'guard-shell'
gem 'webrick', '~> 1.3.1'
end
group :test do
gem 'factory_girl_rails'
gem 'capybara', '~> 2.2.0'
gem 'selenium-webdriver'
# capybara-webkit gem requires an application called 'libqtwebkit-dev' to build. To install 'libqtwebkit-dev' in Ubuntu, run
# sudo apt-get install libqtwebkit-dev
# gem 'capybara-webkit'
gem 'rb-readline'
gem 'launchy'
gem 'database_cleaner'
end
group :production do
gem 'pg'
# gem 'puma'
end
# rails version
gem 'rails', '4.0.1'
# standard library
gem 'sass-rails', '~> 4.0.0'
gem 'uglifier', '>= 1.3.0'
gem 'coffee-rails', '~> 4.0.0'
gem 'jquery-rails'
gem 'turbolinks'
gem 'jbuilder', '~> 1.2'
group :doc do
gem 'sdoc', require: false
end
# custom
gem 'activeadmin', github: 'gregbell/active_admin'
gem 'devise'
gem 'simple_form'
spec/spec_helper:
spec/spec_helper:
# This file is copied to spec/ when you run 'rails generate rspec:install'
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'
require 'capybara/rspec'
# 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 }
# Checks for pending migrations before tests are run.
# If you are not using ActiveRecord, you can remove this line.
ActiveRecord::Migration.check_pending! if defined?(ActiveRecord::Migration)
RSpec.configure do |config|
config.include Capybara::DSL
config.before(:suite) do
DatabaseCleaner.strategy = :transaction
DatabaseCleaner.clean_with(:truncation)
DatabaseCleaner.start
DatabaseCleaner.clean
end
config.before(:each) do
DatabaseCleaner.clean
end
config.after(:each) do
DatabaseCleaner.clean
end
config.after(:suite) do
DatabaseCleaner.clean
end
# Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
config.fixture_path = "#{::Rails.root}/spec/fixtures"
# config.include RSpec::Rails::RequestExampleGroup, type: :feature
# 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 = true
# If true, the base class of anonymous controllers will be inferred
# automatically. This will be the default behavior in future versions of
# rspec-rails.
config.infer_base_class_for_anonymous_controllers = false
# Run specs in random order to surface order dependencies. If you find an
# order dependency and want to debug it, you can fix the order by providing
# the seed, which is printed after each run.
# --seed 1234
config.order = "random"
end
推荐答案
您要更改此内容
config.after(:suite) do
DatabaseCleaner.clean
end
对此:
config.after(:suite) do
DatabaseCleaner.clean_with(:truncation)
end
否则,它将简单地回滚事务,这将保留事务开始之前存在的所有数据.
Otherwise, it will simply roll back the transaction, which will leave any data that existed before the transaction was started.
这篇关于如何在错误的rspec规范之间清理数据库?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!