Chris Millsap, Chris Good There is some limited test and example data in the GnuCash sources .../gnucash-src/doc/examples. Not very extensive. These days a lot of testing effort is shifted towards unit tests rather than extensive overall functional tests although they still have a place. I would think there would be a serious problem in validation of a data set and then the maintenance issues you alluded to. Another difficulty would be defining a test data set which would cover the various feature sets adequately, e.g. business, trading, multicurrency etc. To define an adequate test data suite would also require an extensive knowledge of the code base in any case.
Possible but is it really worth the effort? In accounting if major features like compliance with the accounting equation, zero sum for transaction splits are broken, then it will be generally obvious very quickly and the unit tests on the engine seem likely pick that up. What is it that you would wan't a test data suite to do that is not covered by the existing unit tests? David Cousens ----- David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
