ember-test-helpers

ember-test-helpers

A test-framework-agnostic set of helpers for testing Ember.js applications.

Usage

This library is best used by way of a test-framework-specific wrapper, such as ember-qunit or ember-mocha.

Test Helpers

TestModule

The TestModule class is used to configure modules for unit testing different aspects of your Ember application. This class can be extended to create modules focused on particular types of unit tests.

TestModule is intended to be used in conjunction with modules specific to a test framework. For instance, you could create QUnit-compatible modules with a method such as:

function moduleFor(name, description, callbacks) {
  let module = new TestModule(name, description, callbacks);

  QUnit.module(module.name, {
    beforeEach() {
      return module.setup();
    },
    afterEach() {
      return module.teardown();
    }
  });
}

---

TestModule(name [, description [, callbacks]])

• name - the full name of the test subject as it is registered in a container (e.g. 'controller:application', 'route:index', etc.).

• description (optional) - the description of the test module as it should be displayed in test output. If omitted, defaults to name.

• callbacks (optional) - an object that may include setup and teardown steps as well as the other units needed by tests.

• callbacks.resolver (optional) - a Resolver instance to be used for the test module. Takes precedence over the globally set Resolver.

TestModuleForComponent

TestModuleForComponent extends TestModule to allow unit testing of Ember Components.

---

TestModuleForComponent(name [, description [, callbacks]])

• name - the short name of the component that you'd use in a template (e.g. 'x-foo', 'color-picker', etc.).

TestModuleForModel

TestModuleForModel extends TestModule to allow unit testing of Ember Data Models.

---

TestModuleForModel(name [, description [, callbacks]])

• name - the short name of the model that you'd use in store operations (e.g. 'user', 'assignmentGroup', etc.).

Miscellaneous Helpers

• getContext / setContext - access the context to be used in each test.

• setResolver - sets a Resolver globally which will be used to look up objects from each test's container.

• isolatedContainer - creates a new isolated container for unit testing.

Collaborating

Installation

• git clone <repository-url> this repository
• cd ember-test-helpers
• npm install

Running

• ember serve
• Visit your app at http://localhost:4200.

Running Tests

• npm test (Runs ember try:each to test your addon against multiple Ember versions)
• ember test
• ember test --server

Building

• ember build

For more information on using ember-cli, visit https://ember-cli.com/.

Attribution

Much of ember-test-helpers was extracted from the original ember-qunit, which was written by Stefan Penner, Robert Jackson, and Ryan Florence.

Copyright and License

Copyright 2015 Switchfly and contributors.

Dual-licensed under the Apache License, Version 2.0 and the MIT License.

Changelog

v0.7.0-beta.5 (2017-10-16)

Full Changelog

Implemented enhancements:

• Expose element in component integration tests #184
• Deprecate this.container and this.registry when using Ember 2.3.0. #120
• Way to use extended EventDispatcher #20
• Expose test helpers for component unit tests #3
• Basic implementation for new testing API. #220 (rwjblue)

Fixed bugs:

• Tests fail after upgrading to 0.5.17 - unable to find custom store #130
• Document "integration: true" and "needs" #55

Closed issues:

• Simplify support matrix. #206
• contextualizeCallbacks prevents custom test instance helpers #204
• 0.6.3 is breaking existing tests #203
• initializers affect component integration tests if there is an acceptance test #146
• Service injection fails in integration tests #109
• Integration test with router injected into component #103
• Failing test suite under 0.5.9 #97
• Inject integration test helpers into component integration tests. #67
• add-ons unit tests fail to retrieve custom factories #54
• View-rendering with {{outlet}} in views template fails #36
• If ED is being used and integration:true then I should be able to access the store #31
• Working with new Container/Registry Implementation #7

Merged pull requests:

• Use yarn instead of npm #219 (Turbo87)
• Reorganize repo internals to prepare for RFC 232 implementation. #218 (rwjblue)