refactor: improve test structure and performance by utilizing fixtures #157
+416
−321
Conversation
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
SebastienDegodez
force-pushed
the
refactor/increase-performance-testing
branch
from
9b89731 to
8020377
Compare
Signed-off-by: SebastienDegodez <[email protected]>
SebastienDegodez
force-pushed
the
refactor/increase-performance-testing
branch
from
8020377 to
464a7d7
Compare
lbroudoux
added
kind/enhancement
lbroudoux
approved these changes
Nov 28, 2025
Member
lbroudoux
left a comment
lbroudoux
left a comment
There was a problem hiding this comment.
Looks all good to me! Thanks!
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.
Pull Request
Proposed Changes
Reuse Testcontainers across tests to drastically reduce test runtime and flakiness by switching per-test lifecycle to shared fixtures / collections where appropriate.
Replace per-test container creation/destruction with IClassFixture (or test collections when multiple test classes must share resources), move fixtures close to tests (inner class where requested), and update tests to use the fixtures.
Sample: 3 tests KAFKA + Microcks, Before: 69 seconds, After: 44 seconds.
Readiness Checklist
Author/Contributor
dotnet testand ensure you have test coverage for the lines you are introducingdotnet husky runand fix any issues that you have introducedReviewer
feature,fix,documentation,enhancement,maintenanceorbreaking#158