Factories

Factories are used in your tests. Their purpose is to make it easy to populate your Mirage server’s database with data. Whenever you generate an object via a factory, it will automatically get added to the database, and thus get an autoassigned id.

You define factories by creating files under /mirage/factories/some-factory.js. The name of the factory, which you reference in your tests, is determined by the filename.

Factories have attributes, and you create objects from factory definitions using create and createList.

Defining factories

Attributes can be static (strings, numbers or booleans) or dynamic (a function). Here’s a factory with some static attributes:

// mirage/factories/user.js
import Mirage from 'ember-cli-mirage';

export default Mirage.Factory.extend({
  name: 'Link',
  age: 563,
  evil: false,
});

Functions receive the sequence number i as an argument, which is useful to create dynamic attributes:

// mirage/factories/user.js
import Mirage from 'ember-cli-mirage';

export default Mirage.Factory.extend({
  name: function(i) {
    return 'User' + i
  }
});

The first user generated (per test) would have a name of User 0, the second a name of User 1, and so on.

Finally, you can also reference static attributes (numbers, strings or booleans) within your dynamic attributes via this:

// mirage/factories/contact.js
import Mirage from 'ember-cli-mirage';

export default Mirage.Factory.extend({
  age: 18,
  is_admin: function(i) {
    return this.age > 30;
  }
});

You should define the attributes of your factory as the “base case” for your objects, and override them within your tests. We’ll discuss how do to this in the Creating Objects section.

Extending factories

You can extend factories:

// mirage/factories/human.js
import Mirage from 'ember-cli-mirage';

export default Mirage.Factory.extend({
  species: 'homo sapiens'
});

// mirage/factories/man.js
import Human from './human';

export default Human.extend({
  gender: 'male'
});

Creating objects

Once you’ve defined a factory for a model, you can generate data for that model using server.create and server.createList from within your acceptance tests.

# server.create(type [, attrs])

Generates a single model of type type, inserts it into the database (giving it an id), and returns the data that was added.

test("I can view a contact's details", function() {
  var contact = server.create('contact');

  visit('/contacts/' + contact.id);

  andThen(function() {
    equal( find('h1').text(), 'The contact is Link');
  });
});

You can override the attributes from the factory definition with a hash passed in as the second parameter. For example, if we had this factory

export default Mirage.Factory.extend({
  name: 'Link'
});

we could override the name like this:

test("I can view the contacts", function() {
  server.create('contact', { name: 'Zelda' });

  visit('/');

  andThen(function() {
    equal( find('p').text(), 'Zelda' );
  });
});

# server.createList(type, amount [, attrs])

Creates amount models of type type, optionally overriding the attributes from the factory with attrs.

Returns the array of records that were added to the database.

test("I can view the contacts", function() {
  server.createList('contact', 5);
  var youngContacts = server.createList('contact', 5, { age: 15 });

  visit('/');

  andThen(function() {
    equal(currentRouteName(), 'index');
    equal( find('p').length, 10 );
  });
});