Move integration container logic to TestModule

[nikz]

This moves the integration logic up into TestModule, so that you can specify:

  integration: true

And you'll be able to resolve other units in your application without adding them to needs.

(thanks @rwjblue!)

[rwjblue]

LGTM

[rwjblue]

@ef4 / @dgeb - Can you 👍 / 👎 ? This looks great, and should satisfy my comments in #21.

[ef4]

👍

[dgeb]

Nice work - thanks @nikz 👍

[cibernox]

Is this the end of needs: ['every', 'single', 'model', 'in', 'my', 'app', 'in', 'unit', 'tests'] ??

[rwjblue]

@cibernox - Yes, and it is released in ember-qunit@0.2.11.

[cibernox]

@rwjblue Updated ember-qunit in bower.json but I still need to specify needs on my model tests.

[ef4]

@cibernox You need to opt in to the new behavior by passing integration:true to your moduleFor call(s).

[cibernox]

It woks now: moduleForModel('post', { integration: true });

[IanVS]

Is this going to be added to the guides and documentation? (unless it's there already and I just can't find it)

• Ember-cli user guide - Using ember-qunit for integration tests
• Ember.js guide - Unit Test Helpers.
• Ember-qunit readme

I'm pretty new to Ember, and I'm glad I stumbled across this PR. It's going to be so nice not to have to include all the needs in tests.