Old Guides - You are viewing the guides for Ember v1.13.0. VIEW v3.28.0
Edit Page

Testing Models

Unit testing methods and computed properties follows previous patterns shown in Unit Testing Basics because DS.Model extends Ember.Object.

Ember Data Models can be tested using the moduleForModel helper.

Let's assume we have a Player model that has level and levelName attributes. We want to call levelUp() to increment the level and assign a new levelName when the player reaches level 5.

export default DS.Model.extend({
  level:     DS.attr('number', { defaultValue: 0 }),
  levelName: DS.attr('string', { defaultValue: 'Noob' }),

  levelUp: function() {
    var newLevel = this.incrementProperty('level');
    if (newLevel === 5) {
      this.set('levelName', 'Professional');

Now let's create a test which will call levelUp on the player when they are level 4 to assert that the levelName changes. We will use moduleForModel:


test('levelUp', function(assert) {
  // this.subject aliases the createRecord method on the model
  var player = this.subject({ level: 4 });

  // wrap asynchronous call in run loop
  Ember.run(function() {

  assert.equal(player.get('level'), 5);
  assert.equal(player.get('levelName'), 'Professional');

Testing Relationships

For relationships you probably only want to test that the relationship declarations are setup properly.

Assume that a User can own a Profile.

export default DS.Model.extend({

export default DS.Model.extend({
  profile: DS.belongsTo('profile')

Then you could test that the relationship is wired up correctly with this test.

moduleForModel('user', {
  // Specify the other units that are required for this test.
  needs: ['model:profile']

test('profile relationship', function(assert) {
  var User = this.store().modelFor('user');
  var relationship = Ember.get(User, 'relationshipsByName').get('profile');

  assert.equal(relationship.key, 'profile');
  assert.equal(relationship.kind, 'belongsTo');

Ember Data contains extensive tests around the functionality of relationships, so you probably don't need to duplicate those tests. You could look at the Ember Data tests for examples of deeper relationship testing if you feel the need to do it.