After migrating to AngularJS 1.6 there are some "Possibly unhandled rejection: {}" bugs running around. It is caused by some of the promises lacking rejection handling. Find those places and fix them. If the problem is caused by the angular-ui-router upgrade it to the version compatible with our current version of AngularJS.
Environment
None
QAlity Plus - Test Management
Checklists
Activity
Show:
Mateusz Kwiatkowski
December 22, 2016 at 3:04 PM
@Nick Reid From my understanding not handling those rejections will only cause this information in browser console. My only question is if we want to display those kinda errors in other way rather than not displaying at all. Maybe good solution will be to catch them and display nested error(if those unhandled errors have one???)?
I found the qProvider settings that someone added to app.js and realized that it wasn't being run in the tests — which was why we were seeing these errors in karma but not in the browser
I don't think it makes sense to revert the changes done in this ticket — but we should be able to not handle the rejection of promises any more
Question: Does anyone know if not handling the rejection of premisses is bad news?
Paulina Borowa
December 19, 2016 at 2:49 PM
I did not notice this error.
Mateusz Kwiatkowski
December 19, 2016 at 10:29 AM
I think the only way to test this is actually to enter all pages possible and check if in browser console there is no "Possibly unhandled rejection" errors. It will be also great if we could make through submit/authorize/approve process for few requisitions.
Sebastian Brudziński
December 19, 2016 at 9:39 AM
@Nick Reid@Mateusz Kwiatkowski I moved this to QA.
@Mateusz Kwiatkowski Can you leave a short note for testers how to verify this ticket?
Done
Pinned fields
Click on the next to a field label to start pinning.
After migrating to AngularJS 1.6 there are some "Possibly unhandled rejection: {}" bugs running around. It is caused by some of the promises lacking rejection handling. Find those places and fix them. If the problem is caused by the angular-ui-router upgrade it to the version compatible with our current version of AngularJS.