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
In Ember 2.11, rendering in a test no longer throws an error, if one occurred during the rendering, so QUnit's assert.throws doesn't catch the error and the test that asserts rendering with no unknownCardHandler throws fails.
The code is still behaving as expected, but the tests need to be updated to correctly exercise this behavior for Ember versions >= 2.11.0
The text was updated successfully, but these errors were encountered:
This was due to a change to make it so that the RSVP error handling and Backburner (runloop) error handling use a similar error dispatching mechanism. There's some discussion of how to fix that here: emberjs/ember.js#14898
Uses a customized test adapter for some tests that will rethrow errors
that occur during the render cycle. This fixes a few tests that were
false-negativing. Notes on the change to Ember are in emberjs/ember.js#14898Fixes#128
Uses a customized test adapter for some tests that will rethrow errors
that occur during the render cycle. This fixes a few tests that were
false-negativing. Notes on the change to Ember are in emberjs/ember.js#14898Fixes#128
In Ember 2.11, rendering in a test no longer throws an error, if one occurred during the rendering, so QUnit's
assert.throws
doesn't catch the error and the test that asserts rendering with no unknownCardHandler throws fails.The code is still behaving as expected, but the tests need to be updated to correctly exercise this behavior for Ember versions >= 2.11.0
The text was updated successfully, but these errors were encountered: