Repository navigation
docs: rewrite TESTCONTAINERS-USAGE.md - #176
Merged
Merged
Conversation
magnusp
force-pushed
the
docs/168-testcontainers-usage
branch
from
October 23, 2026 23:35
7473434 to
7be7f6d
Compare
magnusp
force-pushed
the
docs/168-testcontainers-usage
branch
from
October 23, 2026 23:47
7be7f6d to
d444d92
Compare
This was referenced Oct 24, 2026
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
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.
Why
TESTCONTAINERS-USAGE.mddescribed paths, packages, and an endpoint that no longer exist, so contributors could not use it to run the integration tests.What changed
TESTCONTAINERS-USAGE.mdagainst the real module sources.Scope
Tradeoffs
Blast Radius
Verification
turso-java,org.libsql,/v2/pipeline,NetworkToxicityIntegrationIT) in the guide: no matches../mvnw spotless:check: BUILD SUCCESS.