MongoDB Integration Tests now require Docker

[YasharF]

Checked other resources

• I added a very descriptive title to this issue.
• I searched the LangChain.js documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.
• I am sure that this is a bug in LangChain.js rather than my code.
• The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code

cd ~/langchainjs
yarn
cd langchain-core
yarn build
cd ..
yarn build
cd ~/langchainjs/libs/langchain-mongodb
yarn test:single src/tests...

Error Message and Stack Trace (if applicable)

Error: Jest: Got error running globalSetup - /home/yasharf/langchainjs/libs/langchain-mongodb/src/tests/setup.ts, reason: Could not find a working container runtime strategy
at getContainerRuntimeClient (/home/yasharf/langchainjs/node_modules/testcontainers/build/container-runtime/clients/client.js:66:11)
at async GenericContainer.start (/home/yasharf/langchainjs/node_modules/testcontainers/build/generic-container/generic-container.js:58:24)
at async setup (/home/yasharf/langchainjs/libs/langchain-mongodb/src/tests/setup.ts:65:23)
at async /home/yasharf/langchainjs/node_modules/@jest/core/build/runGlobalHook.js:109:13
at async waitForPromiseWithCleanup (/home/yasharf/langchainjs/node_modules/@jest/transform/build/ScriptTransformer.js:160:5)
at async ScriptTransformer.requireAndTranspileModule (/home/yasharf/langchainjs/node_modules/@jest/transform/build/ScriptTransformer.js:808:16)
at async runGlobalHook (/home/yasharf/langchainjs/node_modules/@jest/core/build/runGlobalHook.js:101:9)
at async runJest (/home/yasharf/langchainjs/node_modules/@jest/core/build/runJest.js:327:5)
at async _run10000 (/home/yasharf/langchainjs/node_modules/@jest/core/build/cli/index.js:343:7)
at async runCLI (/home/yasharf/langchainjs/node_modules/@jest/core/build/cli/index.js:198:3)

Description

The recent PR #8295 for adding more comprehensive MongoDB testing breaks the ability to do integration tests locally without Docker.

@baileympearson @hntrl I am totally onboard with having more comprehensive testing. However, the prior tests had the flexibility to use a container or an actual DB instance outside of a container for testing. With the current setup with the recent PR devs that don't have Docker won't be able to run the tests, and contribute to potential bug fixes or expanding features. Can we have a hybrid test setup that can handle both dev setups like before this PR? Let me know if I can help.

I ran into the issue because the tests I had with #8251 were working last week and now they are broken. So need to figure out a way forward.

System Info

Langchain version: HEAD @ commit 511e473, test(mongodb): add more comprehensive testing to MongoDB integration (#8295)

$ node -v
v22.16.0

WSL Ubuntu 22.04.1 LTS

[YasharF]

Sorry about this issue; it was a false positive. I'm going to add some code in my PR for better messaging regarding local vs container testing.

[baileympearson]

Hey @YasharF , can you clarify the difference between "container testing" and "local testing"? All local tests would in some capacity require a container because they need to run with Atlas local (a standalone mongod/mongos does not suffice).

[hntrl]

I will call out that we have additional context for testing in the README. If either of you feel that doc is not accurate or needs clarification then that's a pretty easy change to make

langchainjs/libs/langchain-mongodb/README.md

Line 61 in 0a6f745

### Run tests

[YasharF]

I have been just setting the MONGODB_ATLAS_URI to a cluster that I have on mongodb.com and have been running the tests on them.

[hntrl]

If you don't want to run tests against production infra then I've found that the test containers work nicely! I think the reason you got this error was because the env var was set differently somehow. That PR shouldn't make any changes to the testing strategy.

[YasharF]

... I think the reason you got this error was because the env var was set differently somehow. That PR shouldn't make any changes to the testing strategy.

Yes you are correct. I had mistakenly set MONGODB_URI in a new session instead of MONGODB_ATLAS_URI, which caused the error, and then I was not patient enough to look at the actual PR to see that it had not changed anything that would cause that issue. To help out, I added some extra messaging for such a case as part of the following PR in case if others make a similar mistake https://github.com/langchain-ai/langchainjs/pull/8251/files#diff-b6084feb46b2abb1c3cdb2f3bd3539d05be79e90bd9519fe698d32f7dbc2160f