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
ok 5 Chrome 65.0 - helper:my-helper: it renders
not ok 6 Chrome 65.0 - Global error: Uncaught Error: Assertion Failed: this is a failure at http://localhost:7357/assets/vendor.js, line 24725
---
Log: |
{ type: 'error',
text: 'Uncaught Error: Assertion Failed: this is a failure at http://localhost:7357/assets/vendor.js, line 24725\n' }
...
not ok 7 Chrome 65.0 - Integration | Helper | my-helper: it renders
---
actual: >
null
stack: >
http://localhost:7357/assets/vendor.js:24725
message: >
Uncaught Error: Assertion Failed: this is a failure
Log: |
...
not ok 8 Chrome 65.0 - Global error: Uncaught Error: Assertion Failed: this is a failure at http://localhost:7357/assets/vendor.js, line 24725
---
Log: |
{ type: 'error',
text: 'Uncaught Error: Assertion Failed: this is a failure at http://localhost:7357/assets/vendor.js, line 24725\n' }
...
not ok 9 Chrome 65.0 - Integration | Helper | my-helper: it renders
---
actual: >
null
stack: >
http://localhost:7357/assets/vendor.js:24725
message: >
Uncaught Error: Assertion Failed: this is a failure
Log: |
...
The new way throws a red error to the console, but otherwise resolves the promise normally instead of rejecting.
The text was updated successfully, but these errors were encountered:
Not sure the right place to file this.
https://github.com/kellyselden/assert-render-bug
With code in a helper like:
A test the old way properly detects a failure:
But the new way will not throw:
Here are the logs:
The new way throws a red error to the console, but otherwise resolves the promise normally instead of rejecting.
The text was updated successfully, but these errors were encountered: