Tests fail to run with Mirage

Versions:

• Embroider: current master (418af5a7fe53e8947a9a0454fdc01649be6fb22b)
• ember-cli-mirage: 1.1.0
• ember-auto-import: 1.5.2

When an application has Mirage installed, test runs give an early failure, when checking if Mirage should be used:

TypeError: Cannot destructure property `getContext` of 'undefined' or 'null'.
    at getRfc232TestContext (webpack:///./node_modules/ember-cli-mirage/get-rfc232-test-context.js?:18:9)
    at _shouldUseMirage (webpack:///./initializers/ember-cli-mirage.js?:57:109)
    at Object.initialize (webpack:///./initializers/ember-cli-mirage.js?:38:9)
    at http://localhost:7357/assets/vendor.js:46464:21

https://github.com/samselikoff/ember-cli-mirage/blob/0e0740a6c7844cbeb159a340924590554d1232ee/addon/get-rfc232-test-context.js#L9-L17

I suspect it might be because those lines in Mirage use require to check if @ember/test-helpers is a project dependency.

I have a reproduction of this on the mirage branch of my Embroider sandbox, here: https://github.com/balinterdi/go-embroider-go/tree/mirage

(The test passes on the master branch, before adding Mirage)

[ef4]

Probably has something to do with:

https://github.com/samselikoff/ember-cli-mirage/blob/dcef77adced352d43d314ab484e47075018addb7/addon/utils/read-modules.js#L18-L25

or

https://github.com/samselikoff/ember-cli-mirage/blob/dcef77adced352d43d314ab484e47075018addb7/addon/utils/ember-data.js#L5

The most static options are enabled, the fewer things will reliably appear in requirejs.entries.

[ef4]

Yes, that would be the solution for how to fix this upstream in mirage. Though you should probably hold off until @embroider/macros is updated to match the current RFC.

The more temporary workaround is to use a compatAdapter to force @ember/test-selectors to be included as an implicit-test-module.