jest-mongo | Unit Testing library

As I'm introducing authentication for my MongoDB instance in Docker, I ran into problems which are probably related to the way agenda.js tries to connect to MongoDB, as the connection string invokes successful logs for mongoose connecting to the DB, therefore I assume the string should be valid.

Everything worked until I changed the connection string to use authentication. I verified the users are properly created in the database and also tried variations of the connection string and deleting/installing node modules.

Following output I get upon running docker-compose up:

I am building tests for my node/express controller methods and using @shelf/jest-mongodb. I am creating a document first, and then when I try to find that I have to run find twice from model in order to get the results. It should get the results in the first find instead.

test.js

i have a project that uses jest, i can run jest with npm test and it works if i dont set a preset.

I need the preset @shelf/jest-mongodb, and i get the error that is in the title of this post.

Here is my jest.config.js:

I’m learning to create RestAPI’s using NodeJS and MongoDB from this tutorial, and from the repo they have provided[which has quite a lot of updates from the post], I further modified it to do UnitTesting of my Mongo server with Jest and SuperTest.

The major changes I’ve made to the repo before adding mine is:

Move the listen logic to a start.js, while in package.json make this the main file

start.js

I am making my first tentative steps into modern JS development, and to do so, I am writing an app, with the intention of running it on Mongo Stitch. I am trying to stick to TDD-ish development, partly because it is good practice, and partly because it is much easier to run things locally than in the Stitch environment.

I have a working Docker/Alpine environment, and it runs unit tests against Stitch functions fine using Jest. However, I am now writing functions where the conditionals/logic are in Mongo, so unit tests are not enough to protect against regressions.

My original plan was to spin up a MongoDB 4.0 instance in Docker Compose, and then work out how to connect to it in Jest. However, the Jest docs have pointed me to an in-memory MongoDB, which sounds pretty good. Unfortunately it seems non-trivial to set up, and I am bumping into a number of errors.

I am using Yarn to pull dependencies. Since this appears to compile some binaries, I wondered if my being on Alpine was complicating things (BusyBox builds tend to be a bit trickier). I have therefore swapped to Ubuntu. My Dockerfile is pretty simple: