+* RUNNING THE REGRESSION SUITE
+
+Create a .clsql-tests.config file in your home directory.
+See test-init.lisp for the structure of the data.
+
+Load clsql.asd or put it somewhere where ASDF can find it
+and call:
+
+(asdf:oos 'asdf:test-op 'clsql)
+
+The test suite will then automatically run on all of the backends that
+you have defined in .clsql-tests.config
+
* REGRESSION TEST SUITE GOALS
The intent of this test suite is to provide sufficient coverage for
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.
** 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.
** 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.
*** 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
\ No newline at end of file
+ *** Rollback and error handling within a context