LearnAI ToolsCareerPractice BuildsPlayContact
Lesson 4416 min read

Testing MongoDB Applications

Test application code that talks to MongoDB using an in-memory server and Mongoose model-level tests.

Why Not Test Against a Real Database?

Running tests against a shared development or production database is slow, risks polluting real data, and makes tests unreliable when run in parallel or by multiple developers at once. An isolated, disposable database per test run avoids all of these problems.

mongodb-memory-server

mongodb-memory-server downloads and spins up a real, temporary MongoDB instance in memory for the duration of a test run — genuine MongoDB behavior, with no separate database server to manage.

npm install --save-dev mongodb-memory-server
import { MongoMemoryServer } from 'mongodb-memory-server';
import mongoose from 'mongoose';


let mongoServer;


beforeAll(async () => {
  mongoServer = await MongoMemoryServer.create();
  await mongoose.connect(mongoServer.getUri());
});


afterAll(async () => {
  await mongoose.disconnect();
  await mongoServer.stop();
});

Testing a Mongoose Model

import { User } from '../models/User.js';


test('creates a user with valid data', async () => {
  const user = await User.create({ name: 'Ada Lovelace', email: 'ada@example.com' });
  expect(user.name).toBe('Ada Lovelace');
});


test('rejects a user without a required email', async () => {
  await expect(User.create({ name: 'No Email' })).rejects.toThrow();
});

Resetting State Between Tests

Clearing collections between tests keeps them independent — one test's data shouldn't affect another's assertions.

afterEach(async () => {
  const collections = await mongoose.connection.db.collections();
  for (const collection of collections) {
    await collection.deleteMany({});
  }
});
Fast, Isolated, Repeatable

This combination — an in-memory server plus resetting state between tests — is exactly what makes database-touching tests fast enough to run constantly in CI without becoming a bottleneck.

FAQs

Very close — it runs an actual MongoDB binary, just as a single, temporary, in-memory-backed instance, so behavior matches production for the vast majority of testing needs.

Yes — testing that a custom validator correctly rejects bad data, or that a pre-save hook actually hashes a password, is just as important as testing basic create/read operations.

Summary

mongodb-memory-server gives you fast, isolated, genuinely accurate database tests without a shared external database. In the final lesson, you'll review best practices and common mistakes that tie this whole course together.

Next Lesson →

Best Practices & Common Mistakes