If ED is being used and integration:true then I should be able to access the store

[abuiles]

Currently if we set integration:true the store is not available, I asked @dgeb and he mentioned that we should be able to do this.

[ronco]

👍

[blimmer]

I definitely agree with this. It seems a bit backwards that the store is available in a unit test, but not in an integration: true test.

[pgasiorowski]

This seems to be possible as of 0.5

moduleForComponent('my-comp', {
  integration: true,
  beforeEach: function() {
    this.store = this.registry.lookup('service:store');
  }
}

[elwayman02]

The point is that this shouldn't be necessary, though. It should already be there, @WooDzu

[ef4]

We have service injection support now. The store is just a service, and I don't think it needs to be special-cased. The following already works in the current release:

moduleForComponent('my-comp', {
  integration: true,
  beforeEach: function() {
    this.inject.service('store');
    this.get('store').createRecord(...);
  }
}

[elwayman02]

@ef4 what if the service is already injected in the component itself rather than via initializer? That doesn't seem to be working...

[ef4]

I recommend against doing injection in an initializer. Declare in each component exactly which services should be injected, and tests will all work automatically.

If you really need something in an initializer, you'll need to call it yourself. Initializers don't run before integration tests.

[elwayman02]

Right, hence my question, relevant to #109 @ef4...

[ef4]

Sorry, I misread your earlier comment.

Please provide a reproduction in #109. I have lots of examples of components that do someService: Ember.inject.service() that are working fine in integration tests, so we need more to go on to figure out why yours don't.

[Turbo87]

closing due to inactivity