Control after-commit calls in tests with a setting#23
Merged
Conversation
By default, in (non transaction testcase) tests, we simulate the execution of after-commit callbacks, to reproduce Django's normal behaviour when outside of tests. To allow projects to migrate their existing code over to this new paradigm gradually, we allow this behaviour to be disabled. This was previously controlled by monkey-patching a module scoped value in tests, but is now exposed with a Django setting: `SUBATOMIC_RUN_AFTER_COMMIT_CALLBACKS_IN_TESTS`. Co-authored-by: Samuel Searles-Bryant <sam.searles-bryant@kraken.tech>
samueljsb
approved these changes
Sep 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
By default, in (non transaction testcase) tests, we simulate the execution of after-commit callbacks, to reproduce Django's normal behaviour when outside of tests.
To allow projects to migrate their existing code over to this new paradigm gradually, we allow this behaviour to be disabled. This was previously controlled by monkey-patching a module scoped value in tests, but is now exposed with a Django setting:
SUBATOMIC_RUN_AFTER_COMMIT_CALLBACKS_IN_TESTS.Fixes #9.