From ee39f29cf48e873e015c0da8b1257097c4fb966e Mon Sep 17 00:00:00 2001 From: einhverfr Date: Mon, 17 Nov 2008 17:30:44 +0000 Subject: More test cases and framework stuff. t/62-api.t is currently not working. git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@2403 4979c152-3d1c-0410-bac9-87ea11338e46 --- README.tests | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) (limited to 'README.tests') diff --git a/README.tests b/README.tests index ebbdac82..52bea2ae 100644 --- a/README.tests +++ b/README.tests @@ -8,3 +8,27 @@ Test file number allocation: 90 - 99: Packaging checks Environment variables can be used as flags to disable/enable tests >= 40 + +LSMB_TEST_DB must be set to a defined value if databases are going to be tested. + +if LSMB_NEW_DB is set, test 40 (when it is complete) will create a database with +the name from this environment variable, and subsequent database tests will run +against that database. If this is not set, and PGDATABASE is set, tests will +run on that database. If neither are set, the tests will bail out. + +Special notes on specific test cases: + +42-dbobject.t: Some tests will run even if LSMB_TEST_DB is not enabled. These +tests do not require a database connection. + +43-dbtest.t: This runs defined test cases from sql/modules/test/. If new +scripts are added, they must be listed in this script as well. + +62-api.t uses request hashes defined in t/data/62-request-data. This +script employs a database commit filter to prevent commits to the db. It is +safe to run on existing databases. + +63-lwp.t will re-use the request hashes defined in test/data/62-request-data. +It does NOT employ a commit filter, so is NOT safe to run against production +data. It will only run if the environment variable LSMB_TEST_LWN is set to true. + -- cgit v1.2.3