Just as another note on test safety. The following are listed in decreasing orders of safety:
1) Doesn't touch the database make test 2) Touches the database, but is never intended to commit. Direct sql scripts partition data using negative id's to the extent possible in case of accidental commit PGUSER=postgres PGPASSWORD='foo' PGDATABASE='lsmb13test6' LSMB_TEST_DB=1 make test 3) Has a number of safety features built in but errors in the code COULD potentially drop a database that currently exists if they exist (some recently corrected). Not recommended in production environments. Runs the same tests as above, but against a new database freshly loaded from Pg-database and sql/modules before cleaning itself up. PGPASSWORD='foo' LSMB_NEW_DB='foo' PGUSER=postgres LSMB_TEST_DB=1 PG_CONTRIB_DIR=/usr/share/pgsql/contrib/ LSMB_COUNTRY_CODE='us' LSMB_LOAD_COA='UCOA-Form990' LSMB_ADMIN_USERNAME=test123 LSMB_ADMIN_PASSWORD=testing LSMB_ADMIN_FNAME='Test' LSMB_ADMIN_LNAME='Test' LSMB_LOAD_GIFI=UCOA-Form990 make test 4) May write to the db. DO NOT RUN AGAINST PRODUCTION LSMB_USER='foo' LSMB_PASS='bar' PGDATABASE='baz' LSMB_BASE_URL='http://localhost/ledgersmb_13/' LSMB_TEST_LWP=1 make test Best Wishes, Chris Travers ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
