Generated tests for mixin use the wrong path when the recipe is used in addons

[MiguelMadero]

Steps to reproduce

1. Create a new addon (ember addon ember-addon)
2. cd ember-addon
3. Generate a mixin ember g mixin sample
4. Run the tests ember test

Expected:

• The default test should succeed (or be incomplete)

Actual:

• The test fails with the message "Error: Could not find module dummy/mixins/sample imported from `dummy/tests/unit/mixins/sample-test".

The import statement used is import SampleMixin from '../../../mixins/sample'; When replaced with import SampleMixin from 'ember-addon/mixins/sample'; it works.

I could fix it by simply using modulePrefix on the import path, but I want to make sure I'm considering everything.

[kellyselden]

Just came across this, it's because the mixin isn't re-exported in the app folder like other blueprints are.

[MiguelMadero]

Well, I don't think the addon needs to re-export the mixin. That makes sense for other types of objects, but IMO, it's better it the consumer import's it via ES6 from the add-ons namespace. For other types of objects, re-exporting is important so they can be found by the resolver.

[rwjblue]

Confirm, it should be imported from addon-name/mixins/whatever-lol

[MiguelMadero]

Thanks. PR coming

[kellyselden]

Well, I don't think the addon needs to re-export the mixin.

Agreed. I didn't mean to imply we should, just that that was probably a copy paste issue of this test blueprint.

[MiguelMadero]

Makes sense. Thanks for clarifying.