Testing the Swig bindings would be a good thing, the more thorough the better.
For the most part the Swig binding tests just make sure that they can load a
module, which isn't much of a test.
Regards,
John Ralls
> On Jul 19, 2019, at 8:44 AM, Christopher Lam
> wrote:
>
> Hi, not sure if .sc
Hi, not sure if .scm tests are welcome in engine/tests;
test-business-core.scm in maint is running well however in master it fails
to access the engine. ACCT-TYPE-LIABILITY is undefined, ditto
gnc-commodity-table-lookup etc. The following is not adequate to allow
test-business-core.scm to access co
Yes, I agree. On that count aging.scm wins.
What about Credit-Notes; should they automatically be applied to invoices
in the aging-table?
Sneak preview next gen aging report:
https://user-images.githubusercontent.com/1975870/61539513-36ba3780-aa2b-11e9-89d8-c1c35d945a04.png
On Fri, 19 Jul 2019 at
Christopher Lam writes:
> A corollary query is how to report on overpayments in the aging-table
>
> * the Customer Report counts overpayments as negative amounts
> * the Receivables Aging report shows $0 owed by customer
IMHO, this behavior is correct. If the Customer has overpaid then you
have
Wish to canvas opinion on what is considered best practice for the
following real-data simulations, for rebuilding owner-report and
aging-report. This illustrates current buggy behaviour.
* I have a $100 customer invoice, posted- and due-dates 6 weeks ago.
* I have a $50 credit-note to same custom
