Tutorial: Authentication

Mocks are provided for most of Firebase’s authentication methods. Authentication methods will always succeed unless an error is specifically specified using failNext. You can still use methods like createUser. Instead of storing new users remotely, firebase-mock will maintain a local list of users and simulate normal Firebase behavior (e.g. prohibiting duplicate email addresses).

Creating Users

In this example, we’ll create a new user via our source code and test that the user is written to Firebase.

Source

var users = {
  create: function (credentials) {
    return firebase.auth().createUser(credentials);
  }
};

Test

users.create({
  email: 'ben@example.com',
  password: 'examplePass'
});
mocksdk.auth().flush();

mocksdk.auth().getUserByEmail('ben@example.com').then(function(user) {
  console.assert(user, 'ben was created');
});

Manually Changing Authentication State

MockFirebase provides a special changeAuthState method on references to aid in unit testing code that reacts to new user data. changeAuthState allows us to simulate a variety of authentication scenarios such as a new user logging in or a user logging out.

In this example, we want to redirect to an admin dashboard when a user is an administrator. To accomplish this, we’ll use custom authentication data.

Source

firebase.auth().onAuth(function (authData) {
  if (authData.auth.isAdmin) {
    document.location.href = '#/admin';
  }
});

Test

mocksdk.auth().changeAuthState({
  uid: 'testUid',
  provider: 'custom',
  token: 'authToken',
  expires: Math.floor(new Date() / 1000) + 24 * 60 * 60,
  auth: {
    isAdmin: true
  }
});
mocksdk.auth().flush();
console.assert(document.location.href === '#/admin', 'redirected to admin');