kotovalexarian-likes-github/database_cleaner
1
0
Fork 0
mirror of https://github.com/DatabaseCleaner/database_cleaner synced 2023-03-27 23:22:03 -04:00
Code Releases Activity

document DatabaseCleaner.cleaning and usage with around filters in cucumber / rspec / minitest

Browse source
This commit is contained in:
Ethan 2014-01-24 23:20:00 -05:00
parent d86e97055c
commit 16f57428bb
1 changed files with 23 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
README.markdown
View file

@ -146,7 +146,7 @@ passed to [`keys`](http://redis.io/commands/keys)).
(I should point out the truncation strategy will never truncate your schema_migrations table.) (I should point out the truncation strategy will never truncate your schema_migrations table.)
Some strategies require that you call `DatabaseCleaner.start` before calling `clean` (for example the `:transaction` one needs to know to open up a transaction). So you would have: Some strategies need to be started before tests are run (for example the `:transaction` strategy needs to know to open up a transaction). This can be accomplished by calling `DatabaseCleaner.start` at the beginning of the run, or by running the tests inside a block to `Database.cleaning`. So you would have:
```ruby ```ruby
require 'database_cleaner' require 'database_cleaner'
@ -158,6 +158,12 @@ DatabaseCleaner.start # usually this is called in setup of a test
dirty_the_db dirty_the_db
DatabaseCleaner.clean # cleanup of the test DatabaseCleaner.clean # cleanup of the test
# OR
DatabaseCleaner.cleaning do
dirty_the_db
end
``` ```
At times you may want to do a single clean with one strategy. At times you may want to do a single clean with one strategy.
@ -196,12 +202,10 @@ RSpec.configure do |config|
DatabaseCleaner.clean_with(:truncation) DatabaseCleaner.clean_with(:truncation)
end end
config.before(:each) do config.around(:each) do |example|
DatabaseCleaner.start DatabaseCleaner.cleaning do
end example.run
end
config.after(:each) do
DatabaseCleaner.clean
end end
end end
@ -221,6 +225,13 @@ class MiniTest::Spec
DatabaseCleaner.clean DatabaseCleaner.clean
end end
end end
# with the minitest-around gem, this may be used instead:
class Minitest::Spec
around do |tests|
DatabaseCleaner.cleaning(&tests)
end
end
``` ```
### Cucumber Example ### Cucumber Example
@ -239,12 +250,8 @@ rescue NameError
raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it." raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it."
end end
Before do Around do |scenario, block|
DatabaseCleaner.start DatabaseCleaner.cleaning(&block)
end
After do |scenario|
DatabaseCleaner.clean
end end
``` ```
@ -358,6 +365,9 @@ If you are using Postgres and have foreign key constraints, the truncation strat
client_min_messages = warning client_min_messages = warning
``` ```
### Nothing happens in JRuby with Sequel using transactions
Due to an inconsistency in JRuby's implementation of Fibers, Sequel gives a different connection to `DatabaseCleaner.start` than is used for tests run between `.start` and `.clean`. This can be worked around by running your tests in a block like `DatabaseCleaner.cleaning { run_my_tests }` instead, which does not use Fibers.
## Debugging ## Debugging