You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a known issue about this w/ qunit v2 in ember apps (i.e. ember-cli-qunit 3.x), but for some reason, the suggested workarounds are not working in the one app I've seen this issue in. See ember-cli/ember-cli-qunit#162 (comment) Don't know if that's a sign of a fundamental issue w/ this addon, or that app, the way I tried to do the workaround, or a symptom of a broader problem.
Until that issue is resolved, we should try other workarounds (downgrade ember-cli-qunit version in that app), try the addon in other apps, and document the issue and any successful workarounds in the README.
The text was updated successfully, but these errors were encountered:
tomwayson
changed the title
Using this addon in an acceptance test exposes an issue w/ ember-cli-qunit
Using this addon in an acceptance test exposes an issue w/ using qunit >= v2 in an Ember app
Mar 27, 2017
tomwayson
changed the title
Using this addon in an acceptance test exposes an issue w/ using qunit >= v2 in an Ember app
Using this addon in an acceptance test causes "Assertion after the final assert.async was resolved" errors
Mar 27, 2017
Closing this b/c I'm no longer getting "Assertion after the final assert.async was resolved" errors, but I am having other errors w/ Acceptance tests, see #27 and #28.
There is a known issue about this w/ qunit v2 in ember apps (i.e. ember-cli-qunit 3.x), but for some reason, the suggested workarounds are not working in the one app I've seen this issue in. See ember-cli/ember-cli-qunit#162 (comment) Don't know if that's a sign of a fundamental issue w/ this addon, or that app, the way I tried to do the workaround, or a symptom of a broader problem.
Until that issue is resolved, we should try other workarounds (downgrade ember-cli-qunit version in that app), try the addon in other apps, and document the issue and any successful workarounds in the README.
The text was updated successfully, but these errors were encountered: