1 |
This directory contains unittests for Thuban. |
This directory contains the Thuban test suite. |
2 |
|
|
3 |
To run all tests run runtests.py: |
To run all tests run runtests.py: |
4 |
|
|
12 |
The tests use the unittest module of the python standard library. |
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 |
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. |
../Data and so may fail if you are working from a source archive |
16 |
|
unless you also add the data. |
17 |
|
|
18 |
|
Test for optional features should be automatically skipped when run on |
19 |
|
an installation where the feature is not available or the test can't be |
20 |
|
run for some other reason as may be the case with the postgis interface |
21 |
|
tests (see below). Skipped tests are marked with an S in the default |
22 |
|
brief output and are listed after all test have been run. |
23 |
|
|
24 |
|
The PostGIS tests require a PostGIS installation on the machine where |
25 |
|
the tests are run even though Thuban can use PostGIS database as long as |
26 |
|
psycopg is installed. The test will create their own database cluster in |
27 |
|
temp/postgis and start their own postmaster process, so the only |
28 |
|
requirement is that the software is installed and the various postgresql |
29 |
|
command line programs are on the PATH because they're executed as |
30 |
|
subprocesses to build the database cluster, start the postmaster, etc. |
31 |
|
|
32 |
|
E.g. Debian 4.0 (Etch) can have several PostGIS installations |
33 |
|
in parallel. So you can give the PATH to the one you want to test |
34 |
|
on the command line: |
35 |
|
|
36 |
|
$ PATH=$PATH:/usr/lib/postgresql/8.1/bin/ python runtests.py |
37 |
|
|
38 |
|
|
39 |
|
$Revision$ |
40 |
|
$Source$ |
41 |
|
$Id$ |