tell people to first test the dummy app, before going down this path

[stefanpenner]

cc @kellyselden / @rwjblue can you provide some use-cases where this add-on is required, and testing the existing dummy app does not work?

[simonihmig]

@stefanpenner did you notice the issue I created for documenting/collecting use cases? See #104

[trentmwillis]

IMO, the only really useful area this addon serves is testing build code which is not appropriately tested through normal unit tests. I view the use of this addon as an "acceptance" testing of sorts for add-ons that need to verify that when dropped into a real application the build output is correct.

This is what we use it for in ember-engines. Thus, if you need to test build behavior for your addon when used as a nested addon or used multiple times in an application or so on, then this helps facilitate that.

[stefanpenner]

IMO, the only really useful area this addon serves is testing build code which is not appropriately tested through normal unit tests.

It sounds like we should provide helpers (by default) that test the dummy app instead?

[kellyselden]

@stefanpenner I just discovered another use case.

• Your addon is failing in the wild because you accidentally installed a required dependency to dev deps instead of deps. There is no way (that I know of) to prevent this via normal testing because both the addon and dummy app share the same package.json.