Project:
| View Revisions: Issue #29811 | [ Back to Issue ] | ||
| Summary | 0029811: Better handling of critical, application breaking errors | ||
| Revision | 2015-05-07 14:54 by Orekaria | ||
| Steps To Reproduce | provoke an unhandled error. e.g: add receipt.set('bp', null) to the 'requirementsAreMet' method of the 'toolbar-left.js' file: ... var receipt = model.get('order'); receipt.set('bp', null); requirements.isReceipt = !OB.UTIL.isNullOrUndefined(receipt); ... logging into the webpos will create a receipt with no business partner verify that when a new product is added, an unhandled exception is thrown verify that the message is shown in the messages' bubble verify that the same message is shown again and again |
||
| Revision | 2015-05-07 14:53 by Orekaria | ||
| Steps To Reproduce | provoke an unhandled error. e.g: add receipt.set('bp', null) to the 'requirementsAreMet' method of the 'toolbar-left.js' file: ... var receipt = model.get('order'); receipt.set('bp', null); requirements.isReceipt = !OB.UTIL.isNullOrUndefined(receipt); ... logging into the webpos will create a receipt with no business partner verify that when a new product is add, and unhandled exception is thrown verify that the message is shown in the messages' bubble verify that the same message is shown again and again |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |