Integration tests failing with "Failed to create an instance of 'breakpoints:main'. "

[bmfay]

Trying to understand why my integration tests are failing with the following error:

Failed to create an instance of 'breakpoints:main'. Most likely an improperly defined class or an invalid module export.

I have my own custom app/breakpoints.js but it's standard format and is working just fine (and these errors show up even if I delete it). I get this failure for any integration test of a component that is using the media helper.

Version: "ember-responsive": "^3.0.0-beta.3"

Thanks for your time.

[k-fish]

Hey @bmfay, I took a look and tried to reproduce this issue on a new app and it seems to be fine (you can pull the branch for yourself to compare: k-fish/ember-responsive-example@33f84bd). I think it might be something around qunit and the new test helpers vs. the old ones. Are your qunit tests migrated to the latest format?

[laurmurclar]

I have a bit of time this week and would like to contribute by looking into this! We noticed it failing in our app too. Did you look into it any more @k-fish? No worries if not

[bmfay]

@k-fish sorry, I forgot to respond to this. My qunit tests are still in the old format and I haven't had time to update them so I cannot say whether or not that's the issue. If I get a moment to do that, I'll let you know; meanwhile I'll stay tuned to hear what @laurmurclar digs up.

[k-fish]

I took a peek after I last posted, and I'm reasonably certain that it's related to the old vs. new style of qunit tests. For now, unless I hear otherwise, I'm probably going to declare the 3.0 version only compatible with new qunit so that others aren't confused, but this probably could be made backwards compatible (I haven't had time to look, sorry).

@laurmurclar if you'd like to see if it's backwards compatible (if that is in fact the problem) or better yet put up a PR with the changes to make it backwards compatible, the help would be welcome 👍. https://dockyard.com/blog/2018/01/18/test-helpers-the-next-generation has a section on backwards compatibility and would probably be a good place to start.

[laurmurclar]

Sorry, forgot to post an update. We looked into it and you're right, it was because we had a strange mixture of old/new style tests. We're now focusing on updating our tests so that this isn't a problem for us anymore, but if I have time later in the week I could try make it backwards-compatible.

Thanks for the starting point, looks useful!

[laurmurclar]

@bmfay we had to move over to using the setApplication approach in test-helpers.js (see here for an example). It worked for us then, though we had some other failures (unrelated to ember-responsive) caused by that change.

[k-fish]

@laurmurclar glad to hear it's working, let me know if you make progress on making the tests backwards compatible.