mocha 4+ doesn't exit when using mockgoose in tests

[deployable]

Mocha 4+ changed behaviour to "no longer force the process to exit once all tests complete".

Mockgoose runs into this behaviour change due to the child process for mongod stopping mocha from exiting.

[deployable]

I've submitted a PR to mongodb-prebuilt to add the helper functions to enable this: mongodb-js/mongodb-prebuilt#49

[bbruneau]

+1, any word on this?

[pgerlach]

Until #72 is merged, I use this code in my after() function in mocha 4+.

  after(async function() {
    await mockgoose.helper.reset();
    await mongoose.disconnect();
    mockgoose.mongodHelper.mongoBin.childProcess.kill('SIGTERM');
  });

[j3ko]

adding the above code works when there is one test file in mocha 5, but when there are 2+ test files (ie. multiple after's) it still seems to hang. Is there a better workaround for that?

[gsikorski]

@j3ko Something like this works for me:

// mongomock.js
const mongoose = require('mongoose'),
    Mockgoose = require('mockgoose').Mockgoose,
    mockgoose = new Mockgoose(mongoose);

module.exports = {
    setup: async function setup() {
        await mockgoose.prepareStorage();
        await mongoose.connect('mongodb://test');
    },

    teardown: async function teardown() {
        await mockgoose.helper.reset();
        await mongoose.disconnect();
        let retval = new Promise(resolve => {
            mockgoose.mongodHelper.mongoBin.childProcess.on('exit', resolve);
        });
        mockgoose.mongodHelper.mongoBin.childProcess.kill('SIGTERM');
        return retval;
    }
};

Then in your tests you can do:

const mongomock = require('mongomock');

    before(async () => {
        await mongomock.setup();
    });
    ...

    after(async () => {
        await mongomock.teardown();
    });