#database_cleaner

Hay muchisimos sitios donde dicen como configurar esto, no diré porque exactamente pero esto es lo que a mi me funciona:

En el spec_helper  dentro del RSpec.configure do |config|

config.before(:suite) do

DatabaseCleaner.clean_with(:truncation) end

config.before(:each) do DatabaseCleaner.strategy = :transaction end

config.before(:each, :js => true) do DatabaseCleaner.strategy = :truncation end

config.before(:each) do DatabaseCleaner.start end

config.after(:each) do DatabaseCleaner.clean end

Esto es para el rspec, para el cucumber nos creamos un archibo llamado database_cleaner.rb en la carpeta features/support

begin require 'database_cleaner' require 'database_cleaner/cucumber'

DatabaseCleaner.strategy = :truncation DatabaseCleaner.clean_with(:truncation) rescue NameError raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it." end

Before do DatabaseCleaner.start end

Please also see this blog post on tweaking your ruby GC settings.

I use and love DatabaseCleaner, although historically I had never paid too much attention on the performance of its varies cleaning strategies - I'd always used truncation.

We use Postgres, and after digging around and finding out the difference between DELETE and TRUNCATE, I ended up improving our test suite speed by about 30-40% simply by tweaking the cleaning strategies.

http://stackoverflow.com/questions/5308307/rails-3-tutorial-chapter-11-validation-failed-email-has-already-been-taken-er

But it might be better to level up...