If you need your tests to perform where queries on mock database data, you can set simulateQueryFilters to true when calling mockFirebase. PRs welcome! simulateQueryFiltersīy default, query filters (read: where clauses) pass through all mock Firestore data without applying the requested filters.
#Jest reset all mocks update
Note: not all APIs that update the database are supported yet. This can make your tests less predictable, as they may need to be run in the same order. set() on a document or collection would update the mock database you created. If you need your tests to update the mock database, you can set mutable to true when calling mockFirebase.Ĭalling. This means it doesn't update, even when you call things like set or add, as the result isn't typically important for your tests. mutableīy default, the mock database you set up is immutable. However, a common practice for firestore users is to manually write an id property to their documents, allowing them to query collectionGroup by id. InstallationĬonst mockFirebase ( database, options ) includeIdsInDataīy default, id's are not returned with the document's data.Īlthough you can declare an id when setting up your fake database, it will not be returned with data() as that is not the default behavior of firebase. This library provides an easy to use mocked version of firestore. I wrote a where clause, but all the records were returned!.Small, easy to grok pull requests are welcome, but please note that there is no official roadmap for making this library fully featured. This library is NOT feature complete with all available methods exposed by Firestore. This is not a pseudo-database - it is only for testing you are interfacing with firebase/firestore the way you expect. Jest Mock for testing Google Cloud FirestoreĪ simple way to mock calls to Cloud Firestore, allowing you to assert that you are requesting data correctly.
0 kommentar(er)
