Ember Qunit should warn when forcing an integration test into a unit test.

[matthewconstantine]

The readme explains that using needs will force a test into unit mode.

You do not require dependencies through needs:. Doing so will force the test into unit mode.

This is super hard to debug if you don't know about that behavior. Ember Qunit should throw an error or warn when it sees something like this:

moduleForComponent('x-foo', {
  integration: true,
  needs: ['component:x-bar']
});

The developer's intent is to use an integration test with integration: true. Without a warning the tests fail on this.set() or this.on(). And those failures are difficult to trace back to this behavior.

[rwjblue]

As demonstrated by http://rwjblue.jsbin.com/cukuku/edit?html,js,output, if you have integration: true and needs in the same module you do get an error:

cannot declare 'integration: true' and 'needs' in the same module

This error was implemented in emberjs/ember-test-helpers#78, and released in ember-qunit@0.4.10.