#database_cleaner

[agilizandome]

Configurando el database cleaner para que funcione con cucumber capybara y selenium

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

After do |scenario| DatabaseCleaner.clean end

[ifredwu]

Protip: Faster Ruby Tests with DatabaseCleaner and DatabaseRewinder

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.

RSpec.configure do |config| config.before :suite do DatabaseCleaner.clean_with :truncation DatabaseCleaner.strategy = :transaction end config.before do if example.metadata[:js] || example.metadata[:type] == :feature DatabaseCleaner.strategy = :deletion else DatabaseCleaner.strategy = :transaction DatabaseCleaner.start end end config.after do DatabaseCleaner.clean end end

Essentially, we want to truncate the DB only once before the whole suite runs to ensure a clean slate DB, then we only want to use deletion on Capybara tests, everything else should just use transaction which is the fastest strategy.

Now, as a bonus, I have just discovered @amatsuda's DatabaseRewinder which is a lightweight alternative that supports only ActiveRecord. It offers comparable performance with a much similar API.

RSpec.configure do |config| config.before :suite do DatabaseRewinder.clean_all end config.after do DatabaseRewinder.clean end end

By the way, we also use parallel_tests to scale our test suite to multiple processes, even on Travis CI and Wercker.

Hooray to faster tests! :)

[servzin]

Failing RSpec tests on PostgreSQL while using DatabaseCleaner

Yesterday I decided to move my practice application from SQLite to some other database due to some issues with speed and geofencing. I successfully shifted to PostgreSQL, but when I launched `rspec spec` I saw this terrible picture:  Whoops, looks like my database cleans up before it is required. So I dug in deeper and found out that this issue happens due to a race condition on pg adapter using shared connection hack. So according to [this comment](https://github.com/bmabey/database_cleaner/issues/117#issuecomment-8024824) I modified my `database_cleaner.rb` this way: RSpec.configure do |config| config.before do DatabaseCleaner.strategy = if example.metadata[:type] == :request :truncation else :transaction end DatabaseCleaner.start end config.after do DatabaseCleaner.clean end end Now everything works as charm and all my tests are up and running.

[codefolly-blog]

Getting validation "something has been taken" errors in Rails?

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...

https://github.com/bmabey/database_cleaner