accounting: fix validation of accounting transactions with too precise amounts
Round the amounts line by line when validating transactions balances and showing the totals on an accounting transaction. Even though float field configurations do not allow users to input transactions where amounts uses more digits that what makes sense for the selected currency, we had cases where some transactions generated by custom scripts were "too precise" and passed the validation because unlike in all reports where we display sum of rounded values, the check was only rounding the sum, which cause some transactions with 1.00 on one side and 0.333333 0.333333 and 0.333333 on the other side to be valid. The scripts used to display sums on an accounting transaction had the same problem, they were also showing the rounded sum and not the sum of rounded values.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#117699
external
|
ERP5.CodingStyleTest-Master |
01:21:13
|
||||||
failed |
#117694
external
|
ERP5.PerformanceTest-Master |
00:23:31
|
||||||
passed |
#117693
external
|
ERP5.UnitTest-Master |
01:53:10
|
||||||
failed |
#117707
external
|
ERP5.UnitTest-Master.Medusa |
02:26:36
|
||||||
passed |
#117713
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
00:20:47
|
||||||
passed |
#117700
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
00:20:57
|
||||||