TIL Rails: Errors In Test Cases Creates Floating Test Data #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If an exception is thrown when running your test cases, the test data
created will NOT be rolled back.
This creates "floating" test data in your test database will may impact
other test cases.
The most common solution is to use the gem database_cleaner which
basically clears out the entire test database
whenever you start the test cases.
However, this makes your test cases run slower!
Furthermore, database_cleaner gem also don't address any test data
leakage in your test cases.
The easiest solution is to run
rake db:test:prepare
in your terminal.This resets the entire test database so that there are no more floating
test data in your test database.
Every time you have a floating test data issue, you should run
rake db:test:prepare
instead of using a slow solution like database_cleaner.