Skip to main content

Mongo database mocking with fixtures

Project description

https://img.shields.io/pypi/v/humongous.svg https://travis-ci.org/mdomke/humongous.svg?branch=master https://img.shields.io/pypi/l/humongous.svg

What is this?

This is a pytest plugin, that enables you to test your code that relies on a database connection to a MongoDB and expectes certain data to be present. It allows you to specify fixtures for database collections in JSON/BSON or YAML format. Under the hood we use the mongomock library, that you should consult for documentation on how to use MongoDB mock objects. If suitable you can also use a real MongoDb server.

Configuration

If you don’t want to put your fixtures on the top-level directory of your package you have to specify a directory where humongous looks for your data definitions.

To do so put a line like the following under the pytest section of your pytest.ini-file put a

[pytest]
humongous_basedir =
  tests/unit/fixtures

humongous would then look for files ending in .yaml or .json in that directory.

You can also choose to use a real MongoDB server for your tests. In that case you might also want to configure the hostname and/or the credentials if you don’t want to stick with the default (localhost and no credentials). Use the following configuration values in your pytest.ini to adapt the settings to your needs:

[pytest]
humongous_engine = pymongo
humongous_host = mongodb://user:passwd@server.tld
humongous_dbname = mydbname

Basic usage

After you configured humongous so that it can find your fixtures you’re ready to specify some data. Regardless of the markup language you choose, the data is provided as a list of documents (dicts). The collection that these documents are being inserted into is given by the filename of your fixutre-file. E.g.: If you had a file named players.yaml with the following content:

-
  name: Mario
  surname: Götze
  position: striker

-
  name: Manuel
  surname: Neuer
  position: keeper

you’d end up with a collection players that has the above player definitions inserted. If your fixture file is in JSON/BSON format you can also use BSON specific types like $oid, $date, etc.

You get ahold of the database in you test-function by using the humongous fixture like so:

def test_players(humongous):
    assert "players" in humongous.collection_names()
    manuel = humongous.players.find_one({"name": "Manuel"})
    assert manuel["surname"] == "Neuer"

For further information refer to the mongomock documentation.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

humongous-1.3.0-py2.py3-none-any.whl (6.6 kB view details)

Uploaded Python 2Python 3

File details

Details for the file humongous-1.3.0-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for humongous-1.3.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 7c1b3fc6dbfe7d10a21d9cb1f55f0f1e2d40d30370ac4c024c64cd4bf31fb127
MD5 55fc8a671237a17a2a7bf6d18c2d16c9
BLAKE2b-256 ee7c0f5abc7027b3a02a0358baccfb7b0b59cf5602a9c5d15a9be296e11c93a0

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page