A JS and CSS file to be included with your QUnit test runner. It modifies the look of the the test runner to make integration tests using ember-testing very pleasant.
Submodule the project or download the ember_testing_ui.js and ember_testing_ui.css files. Then include the js and css files in the test runner markup. The ember_testing_ui.js needs to be included before your test helper/tests js files.
In your test helper file, initialize EmberTestingUI.
// test_helper.js
// Registed test helpers
// Ember.Test.registerHelper(...);
EmberTestingUI.init(App); // App is your Ember application
The initialization process will build the needed markup and setup the Ember app for testing. It also sets the rootElement property on your app. If you need to use a specific root element, you can configure EmberTestingUI before initialization.
EmberTestingUI.configure({ rootElement: '#my-apps-root-element' }).init(App);
or
EmberTestingUI.configure(function() {
return { rootElement: '#my-apps-root-element' };
}).init(App);
In both cases, EmberTestingUI will create the dom element with the correct id for you, and assign that id as the rootElement for the app.
In the browser, you will see a 'QUnit' link in the top right corner. Clicking this will show the original qunit test runner with more details about the failures and links to run individual tests.
Currently only QUnit is supported, and I am looking into Mocha support.
To run the examples, clone the repository and open the examples/*.html files in the browser
Thank you to John Allison (@jrallison) and his blog post which inspired this work. Also thanks to Erik Bryn (@ebryn) and anyone else who has helped put ember-testing together.