diff options
| author | Joren Van Onder <jov@odoo.com> | 2016-04-21 09:44:45 +0200 |
|---|---|---|
| committer | Joren Van Onder <jov@odoo.com> | 2016-04-28 10:26:09 +0200 |
| commit | 5c545e32448ddcd46716ab1fc0d20610504ddd21 (patch) | |
| tree | 43dc36574b92b013f14e300e4c683de06bcb5bb7 /addons/website/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | 5dc6828631e5c7226c41ba254b2b5f3e4835fd4c (diff) | |
[IMP] point_of_sale: rewrite frontend tests
There used to be some acceptance tests but they have not actually been
run since 8.0.
These acceptance tests are very useful for the POS because the POS is a
somewhat unusual module and it happens occasionally that a change in
another module unintentionally breaks the POS.
Another reason these tests are nice to have is because the POS
duplicates a lot of calculations in JS because it's meant to be able to
work offline (eg. calculation of taxes, orderline totals etc.). Subtle
differences (eg. rounding) between the frontend JS calculations and the
backend calculations make up the most common category of bugs in the
POS. These frontend tests will make it easy to write tests for these
scenario's. When phantom_js finishes we look through all the received
pos.order records and see that all of them are paid. If there would be a
difference between frontend and backend calculations the order would not
have the paid status because the payment on the order would be different
from the total. An example test for a previous bug has been included.
This will also come in handy for testing the upcoming pricelist
functionality that will be implemented in the POS.
Diffstat (limited to 'addons/website/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
