Update domain name to kpe.io

[clsql.git] / tests / README

diff --git a/tests/README b/tests/README
index d7418a3c2e0597f96d83de4e62c4ca6d9212eaef..aa6a9a691119a30cbab7362d54ff214d5a54f1af 100644 (file)
--- a/tests/README
+++ b/tests/README
@@ -1,28 +1,21 @@
 * RUNNING THE REGRESSION SUITE
 
-Just load clsql.asd or put it somewhere where ASDF can find it
-and call:
-
-(asdf:oos 'asdf:load-op 'clsql)
-
-You'll then need to load a CLSQL backend before you can do anything. 
+This test suite looks for a configuration file named
+".clsql-test.config" located in the users home directory. This file
+contains a single assoc-list that specifies the connection specs for
+each database type to be tested. There is an example file in
+contained in CLSQL's examples directory.
 
-To run the regression tests load clsql-tests.asd or put it
-somewhere where ASDF can find it, edit the file tests/test-init.lisp
-and set the following variables to appropriate values:
+These tests require the downloading of the rt package from
+http://files.kpe.io/.
 
-    *test-database-server*
-    *test-database-name*
-    *test-database-user*
-    *test-database-password* 
-
-And then call:
+Load clsql.asd or put it somewhere where ASDF can find it
+and call:
 
-(asdf:oos 'asdf:load-op 'clsql-tests)
-(clsql-tests:test-usql BACKEND)
+(asdf:oos 'asdf:test-op 'clsql)
 
-where BACKEND is the CLSQL database interface to use (currently one of
-:postgresql, :postgresql-socket, :sqlite or :mysql).
+The test suite will then automatically run on all of the backends that
+you have defined in .clsql-test.config
 
 * REGRESSION TEST SUITE GOALS
 
@@ -34,7 +27,7 @@ the system to support the following:
 Refactoring and redesign efforts are normally restricted to a single
 subsystem, or perhaps to interdependent subsystems.  In such cases, a
 set of regression tests which excercise the existing interface of the
-rest of USQL to the changing subsystems should be in place and passing
+rest of CLSQL to the changing subsystems should be in place and passing
 before the coding starts.
 
 ** Ensuring portability and Supporting new ports.
@@ -48,9 +41,9 @@ informal coordination between the mintainers of the various ports.
 
 ** Adding new RDBMS backends
 
-The entire USQL DBMS interface needs to be excercised by the test
+The entire CLSQL DBMS interface needs to be excercised by the test
 suite, such that a new RDBMS backend that passes all the tests can be
-reasonably assured of working with the USQL layers above that.  These
+reasonably assured of working with the CLSQL layers above that.  These
 tests should also serve as impromptu documentation for the details of
 that interface and what it expects frothe RDBMS driver layers.
 
@@ -68,7 +61,7 @@ spend finding the bug prior to fixing it.
 
 ** Multiple RDBMS Issues
 
-USQL supports several RDBMS backends, and it should be possible to run
+CLSQL supports several RDBMS backends, and it should be possible to run
 every test against all of them.  However, there are some features
 which we want tests for but which are not implemented on several of
 the backends.  
@@ -106,9 +99,9 @@ will be run.
    *** Error if existing DB
 
 ** Data Definition
-  *** Create Tables/Sequences/Indexes -- Should cover creation of
+  *** Create Tables/Views/Sequences/Indexes -- Should cover creation of
       tables with all supported types of fields.
-  *** Delete Tables/Sequences/Indexes
+  *** Delete Tables/Views/Sequences/Indexes
   *** Inspection of Tables and attributes, including types
 
 ** Data Manipulation
@@ -129,8 +122,3 @@ will be run.
   *** Object creation/manipulation/deletion
   *** Inter-object Relations
 
-** Editing Contexts
-  *** Object Create/Modification/Deletion in a context -- partly covered already
-  *** Interaction of multiple contexts
-  *** Schema manipulation within a context
-  *** Rollback and error handling within a context