MongoError differ between mongodb-memory-server and vanilla mongod about mongodb-memory-server

[nodkz]

I think that this difference in error messages depends on mongodb version.

If your testing and production versions of mongodb are the same, then you need to try make storageEngine the same. By default it is in memory.

So if it helps, please put here your solution for future googlers.

PS. You may spin app for some tests regular mongo instance, but for other tests - default in memory for spead.

[lirbank]

Confirming that changing the engine to wiredTiger (same as for production) gives the correct errmsg .

new MongodbMemoryServer({
  binary: {
    version: '4.0.2',
  },
  instance: {
    // Available engines:
    // storageEngines: [ 'devnull', 'ephemeralForTest', 'mmapv1', 'wiredTiger' ],
    storageEngine: 'wiredTiger',
  },
});

[nodkz]

@lirbank wow great!

Please open Pull Request for README.md - add links to your packages under Jest section.
Thanks!

[lirbank]

Ok, cool! I have the same version but not the same engine. I'm going to try that. Keep you posted.

[lirbank]

For future googlers:

I've published a package that enables you to set the storage engine per test file in Jest. It also enables you to keep a single mongodb-memory-server server running between tests when you run Jest in watch mode, and other good stuff.

https://www.npmjs.com/package/jest-environment-mongodb (docs here)
https://www.npmjs.com/package/jest-environment-mongodb-wiredtiger
https://www.npmjs.com/package/jest-environment-mongodb-ephemeral