Getting MongooseError: Operation `todos.insertOne()` buffering timed out after 10000ms error message

This is the test,

describe("POST /todos", () => {
  describe("Todos", () => {
    test("return created todo", async () => {
      const _data = {
        _id,
        created,
        status: "pending",
        subtasks: [],
        title: "Todo X"
      };

      Mockingoose(Todo).toReturn(_data, "save");

      const body = { title: "Todo X" };
      const data = await Todo.create(body);

      expect(data).toMatchObject(_data);
    }, 15000);
  });
});

The code I am trying to test,

const data = await Todo.create({
  title: req.body.title
});

[OliverFischer]

Hi all,

starting from 6.x the authors of mongoose decided to shadow the original save function with Model.prototype.$save = Model.prototype.save;,see https://github.com/Automattic/mongoose/compare/5.x…master#diff-305dbcc98ad8fc959dd0c0be51280893962af34c2d8b18abc871cffc2d80c5f9R521 so that mocking save does not work anymore. Modifying the index.js code to include $save for the ops enumeration

const ops = ['find', 'findOne', 'count', 'countDocuments', 'estimatedDocumentCount', 'distinct', 'findOneAndUpdate', 'findOneAndDelete', 'findOneAndRemove', 'findOneAndReplace', 'remove', 'update', 'updateOne', 'updateMany', 'deleteOne', 'deleteMany', 'save', 'aggregate', '$save'];

and extending

if (!mock && op === 'save') {
      mock = this;
    }

    if (!mock && op === '$save') {
      mock = this;
    }
 // or ;-) at least a little bit better
if (!mock && op === op.includes('save')) {
      mock = this;
    } 
    

and in line 243:

const instance = ['remove', 'save', '$save'];

let all tests pass with 5.x and 6.x. May be @alonronin you may change the code to make it work with both versions. Sadly I am stuck to mocha and sinon and searched for a way to depict the functionality of this great project to our needs/libs, so i am not able to provide a pull request.

Btw: @alonronin: The solution provided in https://github.com/alonronin/mockingoose/issues/77#issuecomment-937651045 is imho not correct, it simply infiltrates the original behaviour with a non-sense mock, so that a spied call with a correctly mocked result of the original function is not guaranteed.

Greetings and hope it helps.

Olli

[Parnswir]

I am getting the same error after upgrading to mongoose@^6.0.0. On 5.x your test should work.