fix: Postpone exception in DbContainerFixture to match the behavior of ContainerFixture
#1310
+6
−6
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
…of ContainerFixture
✅ Deploy Preview for testcontainers-dotnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
HofmeisterAn
changed the title
DbContainerFixture to match the behavior of ContainerFixture
HofmeisterAn
approved these changes
Dec 1, 2024
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.
What does this PR do?
This pull request fixes a discrepancy between
ContainerFixtureandDbContainerFixture. Accessing theConnectionStringproperty in theTestcontainers.Xunit.DbContainerFixture<TBuilderEntity,TContainerEntity>.InitializeAsyncmethod might throw. Using aLazy<string>instead makes it throw when the fixture is actually used.Why is it important?
To make
ContainerFixtureandDbContainerFixturehave a consistent behaviour.Related issues
I discovered this issue while helping someone here: xunit/xunit#3066