| 1 |
This directory contains the Thuban test suite. |
| 2 |
|
| 3 |
To run all tests run runtests.py: |
| 4 |
|
| 5 |
$ python runtests.py |
| 6 |
|
| 7 |
To run individual tests, run one of the test_*.py scripts, e.g.: |
| 8 |
|
| 9 |
$ python test_table.py -v |
| 10 |
|
| 11 |
|
| 12 |
The tests use the unittest module of the python standard library. |
| 13 |
|
| 14 |
Some of the tests expect the iceland sample data to be present in |
| 15 |
../Data and so may fail if you're working from a source archive. |
| 16 |
|
| 17 |
Test for optional features should be automatically skipped when run on |
| 18 |
an installation where the feature is not available or the test can't be |
| 19 |
run for some other reason as may be the case with the postgis interface |
| 20 |
tests (see below). Skipped tests are marked with an S in the default |
| 21 |
brief output and are listed after all test have been run. |
| 22 |
|
| 23 |
The PostGIS tests require a PostGIS installation on the machine where |
| 24 |
the tests are run even though Thuban can use PostGIS database as long as |
| 25 |
psycopg is installed. The test will create their own database cluster in |
| 26 |
temp/postgis and start their own postmaster process, so the only |
| 27 |
requirement is that the software is installed and the various postgresql |
| 28 |
command line programs are on the PATH because they're executed as |
| 29 |
subprocesses to build the database cluster, start the postmaster, etc. |
| 30 |
|
| 31 |
|
| 32 |
$Revision$ |
| 33 |
$Source$ |
| 34 |
$Id$ |
Parent Directory
| 
Revision Log