Use Couchbase SDK readiness waits in tests#1371
Merged
Merged
Conversation
✅ Deploy Preview for testcontainers-node ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
Verification
npm run formatnpm run lintnpm run check-compilesnpm run test -- packages/modules/couchbase/src/couchbase-container.test.ts -t "should create and use a bucket with KV service only"Test results
The focused KV-only Couchbase test passes. A full sequential Couchbase test-file run reached 8/9 passing locally; the remaining failure was a Docker port-bind timeout before Couchbase startup logic, not a failure in the SDK readiness path.
Breaking change evidence
This is not breaking. The change updates a test-only dev dependency and test/example code only; it does not change the published module API or runtime behavior.