cartant
firebase-nightlight
What is it?
firebase-nightlight is an in-memory, JavaScript mock for the Firebase Web API.
Why might you need it?
Unit testing services or components that use the Firebase Web API can be tedious:
- stubbing multiple API methods for each test involves a writing a lot of code, and
- the alternative of running tests against an actual Firebase project is slow.
You might find using an in-memory mock that can be created and destroyed on a per-test or per-suite basis to be less frustrating.
How does it work?
Each Mock instance implements mocked versions of the properties and methods that are in the firebase namespace. The options passed when creating a Mock instance allow for the specification of the initial database content and authentication identities.
What is mocked?
- Most of the
databaseAPI is mocked:- References can be used to read, write and query data.
- Events are mocked and will be emitted between references.
- Security rules are not mocked.
- Priorities are not mocked.
onDisconnectis not mocked.- The sometimes-synchronous nature of
child_addedevents is not mimicked; mocked events are always asynchronous.
- Some of the
authAPI is mocked:createUserWithEmailAndPassword,onAuthStateChanged,signInAnonymously,signInWithCredential,signInWithCustomToken,signInWithEmailAndPassword, andsignOutare mocked.- Other methods are not mocked.
- The
firestore,messagingandstorageAPIs are not mocked.
Example
import * as firebase from "firebase/app";
import { expect } from "chai";
import { Mock } from "firebase-nightlight";
describe("something", () => {
let mockDatabase: any;
let mockApp: firebase.app.App;
beforeEach(() => {
mockDatabase = {
content: {
lorem: "ipsum"
}
};
const mock = new Mock({
database: mockDatabase,
identities: [{
email: "alice@firebase.com",
password: "wonderland"
}]
});
mockApp = mock.initializeApp({});
});
it("should do something with the mock", () => {
return mockApp
.auth()
.signInWithEmailAndPassword("alice@firebase.com", "wonderland")
.then((user) => {
expect(user).to.exist;
expect(user).to.have.property("email", "alice@firebase.com");
expect(user).to.have.property("uid");
return mockApp
.database()
.ref()
.once("value");
})
.then((snapshot) => {
expect(snapshot.val()).to.deep.equal({ lorem: "ipsum" });
return mockApp
.database()
.ref()
.update({ lorem: "something else" });
})
.then(() => {
expect(mockDatabase.content).to.deep.equal({ lorem: "something else" });
return mockApp
.auth()
.signOut();
});
});
});Install
Install the package using NPM:
npm install firebase-nightlight --save-devAnd import the Mock class for use with TypeScript or ES2015:
import { Mock } from "firebase-nightlight";
const mock = new Mock();
console.log(mock);Or require the module for use with Node or a CommonJS bundler:
const firebaseNightlight = require("firebase-nightlight");
const mock = new firebaseNightlight.Mock();
console.log(mock);Or include the UMD bundle for use as a script:
<script src="https://unpkg.com/firebase-nightlight"></script>
<script>
var mock = new firebaseNightlight.Mock();
console.log(mock);
</script>API
Instances of the Mock class implement the properties and methods that are in the Firebase Web API's firebase namespace.
The Mock constructor accepts an options object with the following optional properties:
| Property | Description |
|---|---|
database |
An object containing the initial database content. |
identities |
An array of identities to use use when authenticating users. |
apps |
An object containing database and identities configurations by app name. |
If identities are specified, they can have the following optional properties:
| Property | Description |
|---|---|
credential |
The firebase.auth.AuthCredential to match if signInWithCredential is called. |
email |
The user's email. |
password |
The password to match if signInWithEmailAndPassword is called. |
token |
The token to match if signInWithCustomToken is called. |
uid |
The user's UID. If not specified, a random UID is generated. |
Additions to the Firebase Web API
The mock's implementation of firebase.database.Reference includes a stats_ function that will return the current listener counts for each event type. For example:
mockRef.on("child_added", () => {});
mockRef.on("child_removed", () => {});
const stats = mockRef.stats_();
expect(stats.listeners).to.deep.equal({
child_added: 1,
child_changed: 0,
child_moved: 0,
child_removed: 1,
total: 2,
value: 0
});Forcing database errors
It's possible to force database errors by delcaring errors in the database content. For example, with this content:
const mockDatabase = {
content: {
a: {
b: {
".error": {
code: "database/boom",
message: "Boom!"
},
c: {
value: 3
}
}
}
}
};
const mock = new Mock({
database: mockDatabase
});All reads and writes on the a/b path will fail with the specified error. Any reads or writes on deeper paths - a/b/c, for example - will also fail with the specified error.