Re: running tests locally, local integration test failures, db disk usage

[Adam Monsen <me...@apache.org>]

I got a request for updated instructions how to run integration tests 
locally on the command line against mariadb.

Please see integration-test.sh, attached. Instructions are in the 
script. Feedback welcome. When I use this one I first start up mariadb 
then run time bash integration-test.sh.

I also attached my latest test result collector tool, aggregator.patch. 
Feedback not welcome. Just kidding, feedback welcome with that too. Use 
git apply to patch your Fineract clone, then ./gradlew --quiet 
testAggregateTestReport -x test to aggregate test results. They'll 
appear in test-results/build/reports/tests/test/aggregated-results/. I'm 
still unclear if this is generally useful so for now I'm just keeping it 
in my stash.

Maybe do a ./gradlew clean before running integration-test.sh or the 
aggregator may pick up stale test results.

This script and patch are subject to change, simplification, and 
hopefully complete deprecation and obliteration depending on results of 
ongoing work to improve the build and tests.