Perhaps rather than adding tests like this to the primary upgrade scripts, there should be a separate tool that does some consistency checks and reports that can be run from within the normal LedgerSMB UI, and a commandline.
The tests could be run as simple go/nogo with an option to show details of any problems for each test.
The upgrade scripts could then require that the tests have been run at least once since the last DB change and a state file (the go/nogo results) checked for issues that would be release blocking.
If the tests have not been run recently, then force them to run anyway.
This provides the advantage of being able to test the DB at any time with ease.
Regards
David G
On 10/02/14 21:49, Chris Travers wrote:
Also note, we could add it to LedgerSMB::Upgrade_Tests for 1.4 too as a pre-upgrade test (could be done for 1.3 and 1.2 together).
The only thing is that if we do that it would refuse to upgrade until the books are balanced so we'd want to think about that relatively carefully.
--
Best Wishes,Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________ Ledger-smb-devel mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Ledger-smb-devel mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel