Using an initializer in an unit test? - unit-testing

Question

I have a stdlib initializer. In that initializer, i reopen some of built-in Ember classes and add some custom methods. For example, i added reverseEach to Ember.Enumerable and Array.
They work fine in the app, but in tests i receive "reverseEach: undefined is not a function".
How do i indicate that the test should use the initializer?
I tried needs: [..., 'initializer:stdlib']. It does not stumble upon that, but i still receive the "undefined" error.
Here's an example test:
`import { test, moduleForModel } from 'ember-qunit'`
moduleForModel 'foo', 'foo',
needs: [
'model:bar'
'initializer:stdlib'
]
test 'deleteLastNItems', ->
model = #subject()
model.set '', ['foo', 'bar', 'baz', 'quux']
model.deleteLastNItems 2 # This should not die with "reverseEach: undefined is not a function"
deepEquals model.get('someProperty'), ['foo', 'bar']

Answer 1

You can use ember g initializer stdlib, it will generate sample code for you, including test.
import Ember from 'ember';
import { initialize } from '../../../initializers/stdlib';
import { module, test } from 'qunit';
var registry, application;
module('Unit | Initializer | stdlib', {
beforeEach: function() {
Ember.run(function() {
application = Ember.Application.create();
registry = application.registry;
application.deferReadiness();
});
}
});
// Replace this with your real tests.
test('it works', function(assert) {
initialize(registry, application);
// you would normally confirm the results of the initializer here
assert.ok(true);
});
Refer: Ember blueprints