sinon-mongoose | Extend Sinon stubs for Mongoose methods | Mock library

The primary problem here is that the version of gRPC you are trying to install is not compatible with the version of Node that you are using. That error indicates that you are installing gRPC@1.10.1 with Node 10; the first version of gRPC that supports Node 10 is gRPC@1.11.1. So, in general the solution to this problem would be to either downgrade your Node version, or upgrade your gRPC version.

Your edit seems to indicate that you were able to solve this by downgrading the versions of the firebase, firebase-admin, and firebase-tools packages that you are using. This probably works because the specific versions you tried first pinned the gRPC dependency to the older version, and downgrading got you a version that didn't have the dependency pinned. However, each of those packages also has newer versions that don't pin the gRPC dependency and should give you the newest version.

As a solution to pass the test I update the code to be:

Import the same model in the test as is used in the code under test i.e ../models/model.user and it should work as expected.

Mockgoose runs an in memory copy of MongoDB and once setup, patches mongoose so your app connections go to the test instance.

If a definition has already assigned the Assertion interface to Object.should globally (which it must have if you are told you are making a subsequent declaration)...

And if you have extended the original Assertion interface....

Then you don't need to re-specify the interface in a global declaration.

When you write multiple interface definitions within the same common root, they all contribute to a single type. That means your additions to an interface are included as if they were within the same code block.

If you get the error you mention, or if you can't see the type information you believe you added to the interface it will be because you haven't managed to hit the same common root, i.e. an interface exists in X.Y.Z but you have added it to X.Y.

It's because getUserById is asynchronous function. Even when you've created mock for User model, getUserById is still asynchronous.

To create proper test, you can do the following:

• return promise from getUserById function and create a promise chain it test.
• use supertest module which to send a real http request and validate response.

This is a bit of a tricky scenario. The problem here is that the findOne stub in your test returns the model object - instead, it needs to return an object which contains a property exec which in turn is a promise-returning function that finally resolves into the model value... yeah, as mentioned, it's a bit tricky :)

Something like this:

It took me longer to recreate the missing parts of your example, than to actually find the problem. Below you can find a fixed version of your test scenario.