Gathering detailed insights and metrics for firebase-jest-testing-fs
Gathering detailed insights and metrics for firebase-jest-testing-fs
Gathering detailed insights and metrics for firebase-jest-testing-fs
Gathering detailed insights and metrics for firebase-jest-testing-fs
npm install firebase-jest-testing-fs
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (99.47%)
Shell (0.53%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
21 Stars
169 Commits
3 Forks
2 Watchers
11 Branches
1 Contributors
Updated on Sep 16, 2022
Latest Version
0.1.0
Package Id
firebase-jest-testing-fs@0.1.0
Unpacked Size
79.51 kB
Size
28.13 kB
File Count
27
NPM Version
8.1.0
Node Version
16.13.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
2
1
Tools for testing Firebase backend features, using Jest.
Offers:
🥫Emulator detection. The library automatically picks up the configuration when running the tests. Less boilerplate!
🪶Light. Uses Firestore REST API so no Firebase client JS SDK is required.
⚡️Fast. Optimized for multithreading and Node.js. You'll likely max out your cores.
‖‖‖ Security Rules are tested immutably - a passing write or delete operation does not change the data, and cannot disturb other tests. This is why we can parallelize the tests so much. No flaky tests.
﹛﹜Help functions for priming Firestore with JSON data.
+
Means for testing callables (without a client SDK).
Only to be used with Jest 27 and above.
Jest 27
The module is built with ES modules in mind.
In your application project:
$ npm install --save-dev firebase-jest-testing@beta
Add this to the jest.config.js
:
// Needed until Jest supports ESM's with multiple entry points (Jest 28?).
//
resolver: "hack-jest/jestResolver.cjs"
Create the custom Jest resolver.
/* * hack-jest/jestResolver.cjs * * Note: It's really CHEAP that we don't use the 'exports' in the package itself, but this works, and eventually * Jest will support 'exports' for real. Also, we've narrowed down to only those entries that we need. * * References: * - Configuring Jest > resolver (Jest docs) * -> https://jestjs.io/docs/en/configuration#resolver-string [1] */// Add mappings to any libraries you use which 'export' more than the default ('.') entry point (Jest 27 takes care of that). // const entries = Object.entries({ // firebase-jest-testing "firebase-jest-testing/firestoreAdmin": "./src/firestoreAdmin/index.js", "firebase-jest-testing/firestoreAdmin/setup": "./src/firestoreAdmin/setup/index.js", "firebase-jest-testing/firestoreRules": "./src/firestoreRules/index.js", "firebase-jest-testing/firebaseClientLike": "./src/firebaseClientLike/index.js",
// firebase-admin "firebase-admin/app": "./lib/esm/app/index.js", "firebase-admin/firestore": "./lib/esm/firestore/index.js"
}).map( ([k,v]) => { const arr = k.match(/(.+?)//); // pick the node_modules name const name = arr[1] || fail("No '/' in key"); return [ k, v.replace(/^.//,
${name}/
) ] });const lookup = new Map(entries);
const res = ( request, options ) => { // (string, { ..see above.. }) => ...
const hit = lookup.get(request); if (hit) { return options.defaultResolver( hit, options ); } else { return options.defaultResolver( request, options ); } };
module.exports = res;
With Docker Compose, your emulators are likely running under another host than the one running the Jest tests.
Set the EMUL_HOST
env.var. to indicate the host name.
services:
emul:
...
sample:
...
environment: ['EMUL_HOST=emul']
packages/backend
subpackage is customer #0.If you find the library useful, you may file a PR for adding a link to your project here. 😊
Writing tests walks you through the API.
If you wish to support the development of this software, be in touch with the author. We'll figure out something nice! ;)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
Found 0/22 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-14
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More