UnitTest testSqlQueryCount for GetEntity and GetCollection #3602
Conversation
This file contains 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
manuelmeister
approved these changes
Aug 15, 2023
pmattmann
force-pushed
the
feature/unittest-number-of-database-queries
branch
4 times, most recently
from
0f028dd
to
f93695d
Compare
pmattmann
force-pushed
the
feature/unittest-number-of-database-queries
branch
from
f93695d
to
ced6075
Compare
pmattmann
changed the title
BacLuc
approved these changes
Aug 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR shows an example how we could write UnitTests testing the number of required database queries.
This should prevent us form adding an N+1 performance problem by accident.
What do you think about?