Need help with mongomock?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

619 Stars 260 Forks Other 1.0K Commits 58 Opened issues


Small library for mocking pymongo collection objects for testing purposes

Services available


Need anything else?

Contributors list

|travis| |pypiversion| |pypilicense| |pypi_wheel|

.. image:: :target:

What is this?

Mongomock is a small library to help testing Python code that interacts with MongoDB via Pymongo.

To understand what it's useful for, we can take the following code:

.. code-block:: python

def increasevotes(collection): for document in collection.find(): collection.updateone(document, {'$set': {'votes': document['votes'] + 1}})

The above code can be tested in several ways:

  1. It can be tested against a real mongodb instance with pymongo.
  2. It can receive a record-replay style mock as an argument. In this manner we record the expected calls (find, and then a series of updates), and replay them later.
  3. It can receive a carefully hand-crafted mock responding to find() and update() appropriately.

Option number 1 is obviously the best approach here, since we are testing against a real mongodb instance. However, a mongodb instance needs to be set up for this, and cleaned before/after the test. You might want to run your tests in continuous integration servers, on your laptop, or other bizarre platforms - which makes the mongodb requirement a liability.

We are left with #2 and #3. Unfortunately they are very high maintenance in real scenarios, since they replicate the series of calls made in the code, violating the DRY rule. Let's see

2 in action - we might write our test like so:

.. code-block:: python

def testincreasevotes(): objects = [dict(...), dict(...), ...] collectionmock = myfavoritemocklibrary.createmock(Collection) record() collectionmock.find().AndReturn(objects) for obj in objects: collectionmock.updateone(obj, {'$set': {'votes': obj['votes']}}) replay() increasevotes(collectionmock) verify()

Let's assume the code changes one day, because the author just learned about the '$inc' instruction:

.. code-block:: python

def increasevotes(collection): collection.updatemany({}, {'$inc': {'votes': 1}})

This breaks the test, although the end result being tested is just the same. The test also repeats large portions of the code we already wrote.

We are left, therefore, with option #3 -- you want something to behave like a mongodb database collection, without being one. This is exactly what this library aims to provide. With mongomock, the test simply becomes:

.. code-block:: python

def testincreasevotes(): collection = mongomock.MongoClient().db.collection objects = [dict(votes=1), dict(votes=2), ...] for obj in objects: obj['id'] = collection.insertone(obj).insertedid increasevotes(collection) for obj in objects: storedobj = collection.findone({'id': obj['id']}) storedobj['votes'] -= 1 assert storedobj == obj # by comparing all fields we make sure only votes changed

This code checks increase_votes with respect to its functionality, not syntax or algorithm, and therefore is much more robust as a test.

If the code to be tested is creating the connection itself with pymongo, you can use mongomock.patch (NOTE: you should use :code:

rather than :code:
from pymongo import MongoClient
, as shown below):

.. code-block:: python

@mongomock.patch(servers=(('', 27017),)) def testincreatevotesendpoint(): objects = [dict(votes=1), dict(votes=2), ...] client = pymongo.MongoClient('') client.db.collection.insertmany(objects) call_endpoint('/votes') ... verify client.db.collection

Important Note About Project Status & Development

MongoDB is complex. This library aims at a reasonably complete mock of MongoDB for testing purposes, not a perfect replica. This means some features are not likely to make it in any time soon.

Also, since many corner cases are encountered along the way, our goal is to try and TDD our way into completeness. This means that every time we encounter a missing or broken (incompatible) feature, we write a test for it and fix it. There are probably lots of such issues hiding around lurking, so feel free to open issues and/or pull requests and help the project out!

NOTE: We don't include pymongo functionality as "stubs" or "placeholders". Since this library is used to validate production code, it is unacceptable to behave differently than the real pymongo implementation. In such cases it is better to throw

than implement a modified version of the original behavior.


When submitting a PR, please make sure that:

  1. You include tests for the feature you are adding or bug you are fixing. Preferably, the test should compare against the real MongoDB engine (see
    examples in tests
    _ for reference).
  2. No existing test got deleted or unintentionally castrated
  3. The travis build passes on your PR.

To download, setup and perfom tests, run the following commands on Mac / Linux:

.. code-block:: bash

git clone [email protected]:mongomock/mongomock.git pip install tox cd mongomock tox

Alternatively, docker-compose can be used to simplify dependency management for local development:

.. code-block:: bash

git clone [email protected]:mongomock/mongomock.git cd mongomock docker-compose build docker-compose run --rm mongomock

If you need/want tox to recreate its environments, you can override the container command by running:

.. code-block:: bash

docker-compose run --rm mongomock tox -r

Similarly, if you'd like to run tox against a specific environment in the container:

.. code-block:: bash

docker-compose run --rm mongomock tox -e py38-pymongo-pyexecjs

NOTE: If the MongoDB image was updated, or you want to try a different MongoDB version in docker-compose, you'll have to issue a

docker-compose down
before you do anything else to ensure you're running against the intended version.

utcnow ~~~~

When developing features that need to make use of "now," please use the libraries :code:

helper method in the following way:

.. code-block:: python

import mongomock # Awesome code! now_reference = mongomock.utcnow()

This provides users a consistent way to mock the notion of "now" in mongomock if they so choose. Please see

utcnow docstring for more details 

Branching model ~~~~~~~~~~~~~~~

The branching model used for this project follows the

gitflow workflow
_. This means that pull requests should be issued against the
branch and not the
branch. If you want to contribute to the legacy 2.x branch then your pull request should go into the


Mongomock has originally been developed by

Rotem Yaari 
, then by
Martin Domke 
. It is currently being developed and maintained by
Pascal Corpet 

Also, many thanks go to the following people for helping out, contributing pull requests and fixing bugs:

  • Alec Perkins
  • Alexandre Viau
  • Austin W Ellis
  • Andrey Ovchinnikov
  • Arthur Hirata
  • Baruch Oxman
  • Corey Downing
  • Craig Hobbs
  • Daniel Murray
  • David Fischer
  • Diego Garcia
  • Dmitriy Kostochko
  • Drew Winstel
  • Eddie Linder
  • Edward D'Souza
  • Emily Rosengren
  • Eugene Chernyshov
  • Grigoriy Osadchenko
  • Israel Teixeira
  • Jacob Perkins
  • Jason Burchfield
  • Jason Sommer
  • Jeff Browning
  • Jeff McGee
  • Joël Franusic
  • Jonathan Hedén 
  • Julian Hille
  • Krzysztof Płocharz
  • Lyon Zhang
  • Lucas Rangel Cezimbra 
  • Marc Prewitt
  • Marcin Barczynski
  • Marian Galik
  • Michał Albrycht
  • Mike Ho
  • Nigel Choi
  • Omer Gertel
  • Omer Katz
  • Papp Győző
  • Paul Glass
  • Scott Sexton
  • Srinivas Reddy Thatiparthy
  • Taras Boiko
  • Todd Tomkinson
  • Xinyan Lu 
  • Zachary Carter
  • catty (ca77y at
  • emosenkis
  • hthieu1110
  • יppetlinskiy
  • pacud
  • tipok
  • waskew (waskew at
  • jmsantorum (jmsantorum [at] gmail [dot] com)
  • lidongyong
  • Juan Gutierrez 

.. examples in tests:

.. _gitflow workflow:

.. |travis| image:: :target: :alt: Travis CI build

.. |pypi_version| image:: :target: :alt: PyPI package

.. |pypi_license| image:: :alt: PyPI license

.. |pypi_wheel| image:: :alt: PyPI wheel status

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.