Posted 11 months ago. Visible to the public. Repeats.

Rails < 5: How to get after_commit callbacks fired in tests

If you use transactional_fixtures or the database_cleaner gem with strategy :transaction, after_commit callbacks will not be fired in your tests.

Rails 5

Rails 5 has a fix for this issue and no further action is needed.

Rails 3+

Add the gem test_after_commit to your test group in the Gemfile and you are done. You don't need to change the database strategy to deletion (which might lead to longer test runs).


Most often a after_commit is the only right choice. Sending emails, performing async sidekiq workers and many things more are kind of broken with an after_save callback.

If you replace an after_save callback with an after_commit callback this list might help you to fix your code afterwards:

  • attribute_changed? will return true in the after_save callback and false in the after_commit callback. Use something like previous_changes.key?(:attribute) instead.

Once an application no longer requires constant development, it needs periodic maintenance for stable and secure operation. makandra offers monthly maintenance contracts that let you focus on your business while we make sure the lights stay on.

Owner of this card:

Emanuel De
Last edit:
11 months ago
by Besprechungs-PC
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Emanuel De to makandra dev
This website uses cookies to improve usability and analyze traffic.
Accept or learn more