Error in where query about firestore-jest-mock HOT 3 CLOSED

Hi @nosisky

You're right, our where method doesn't actually do any querying against the mock database you create. This was on purpose as rebuilding all the of potential logic firestore has could make this library really hard to maintain and we questioned what the value in reproducing that logic is.

Our thought process was "if the where clause actually filters the filters the mock data and you assert that the right data is returned, then all you've done is tested our code." However, I do understand your point that you have cases where you need to assert that a where returns no results and we should allow a way to test for that.

I don't want to go down the rabbit hole of completely rebuilding everything that where (and other methods) can do. But we should think of a way to test this case 🤔

I am open to suggestions!

from firestore-jest-mock.

Hi @nosisky
I'm facing similar issue and was wondering if you found a work around?
I tried mocking firestore per each test but due to that I ran into other problems

from firestore-jest-mock.

@nosisky & @Foxford13 We added a new optional flag you can pass to mockFirebase in your tests that should allow where to actually return the results of your query:

https://github.com/Upstatement/firestore-jest-mock#simulatequeryfilters

from firestore-jest-mock.