Run each test in there own transaction#223
Closed
sweenu wants to merge 1 commit intofastapi:masterfrom
Closed
Conversation
8a272a3 to
e4ee84d
Compare
Member
|
Thanks for your interest! Yeah, that could be interesting, it probably needs some other changes 🤔 |
alejsdev
pushed a commit
that referenced
this pull request
Dec 19, 2024
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.
This is the first thing I did when I started using the template. It allows me to never have anything really committed to database when running my tests. I don't know how you run your tests but running them each in their own transaction that is then rollbacked and leave no trace whatsoever is to me the cleanest solution when running tests against a database.
I also like the fact that it gives an example of using dependency override.