1A loader test requires, at a minimum, a dbf file:
2
3<name>.dbf
4
5Most tests will use a shapefile, so these files as well:
6
7<name>.shp
8<name>.shx
9
10The loader will be run against the dbf/shapefile with no command-line flags,
11then the output will be run via psql to insert the table into PostGIS.
12
13If there is no <name>.opts file, the loader is then run with the -D flag,
14and the output again run via psql.
15
16See ../README for a description of optional setup/teardown script files.
17
18The following are optional files for each loader test:
19
20<name>.opts - If this exists, the first line that does not begin with a #
21 is read and passed as command line arguments to the loader. This
22 allows testing any arbitrary command line arguments (-s, -G, etc).
23 NOTE: When this file exists, this test is NOT run a second time
24 with -D, because -D can conflict with some arguments.
25
26<name>.sql.expected - If this exists, the output of the loader is compared
27 with this file before running it via psql.
28
29<name>.select.sql and
30<name>.select.expected - If these are present, after the loader output is
31 loaded into the database, the query in <name>.select.sql is run and
32 the psql output is compared with <name>.select.expected.
33
34<name>.select.sql and
35<name>-w.select.expected - If these are present, the loader is also run with
36 the -w flag to produce WKT output rather than WKB output. The query
37 in <name>.select.sql is run again and compared against
38 <name>-w.select.expected.
39
40<name>.shp.expected - If this is present, the dumper is run (after running
41 the WKB version, not the WKT version, as WKT can lose precision)
42 and the .shp file produced by the dumper is compared with
43 <name>.shp.expected.
44