1 This directory contains functional and unit tests for the Nominatim API.
6 * Python 3 (https://www.python.org/)
7 * behave test framework >= 1.2.5 (https://github.com/behave/behave)
8 * nose (https://nose.readthedocs.org)
9 * pytidylib (http://countergram.com/open-source/pytidylib)
10 * psycopg2 (http://initd.org/psycopg/)
12 To get the prerequisites on a a fresh Ubuntu LTS 16.04 run:
14 [sudo] apt-get install python3-dev python3-pip python3-psycopg2 python3-tidylib phpunit php-cgi
15 pip3 install --user behave nose
21 There are two kind of tests in this test suite. There are functional tests
22 which test the API interface using a BDD test framework and there are unit
23 tests for specific PHP functions.
25 This test directory is sturctured as follows:
28 -+- bdd Functional API tests
30 | +- steps Step implementations for test descriptions
31 | +- osm2pgsql Tests for data import via osm2pgsql
32 | +- db Tests for internal data processing on import and update
33 | +- api Tests for API endpoints (search, reverse, etc.)
36 +- scenes Geometry test data
37 +- testdb Base data for generating API test database
43 Unit tests can be found in the php/ directory and tests selected php functions.
46 To execute the test suite run
51 It will read phpunit.xml which points to the library, test path, bootstrap
52 strip and set other parameters.
58 Functional tests are written as BDD instructions. For more information on
59 the philosophy of BDD testing, see http://pythonhosted.org/behave/philosophy.html
64 To run the functional tests, do
69 The tests can be configured with a set of environment variables:
71 * `BUILD_DIR` - build directory of Nominatim installation to test
72 * `TEMPLATE_DB` - name of template database used as a skeleton for
73 the test databases (db tests)
74 * `TEST_DB` - name of test database (db tests)
75 * `ABI_TEST_DB` - name of the database containing the API test data (api tests)
76 * `TEST_SETTINGS_TEMPLATE` - file to write temporary Nominatim settings to
77 * `REMOVE_TEMPLATE` - if true, the template database will not be reused during
78 the next run. Reusing the base templates speeds up tests
79 considerably but might lead to outdated errors for some
80 changes in the database layout.
81 * `KEEP_TEST_DB` - if true, the test database will not be dropped after a test
82 is finished. Should only be used if one single scenario is
83 run, otherwise the result is undefined.
85 Logging can be defined through command line parameters of behave itself. Check
86 out `behave --help` for details. Also keep an eye out for the 'work-in-progress'
87 feature of behave which comes in handy when writing new tests.
92 The following explanation assume that the reader is familiar with the BDD
93 notations of features, scenarios and steps.
95 All possible steps can be found in the `steps` directory and should ideally
98 ### API Tests (`test/bdd/api`)
100 These tests are meant to test the different API endpoints and their parameters.
101 They require a preimported test database, which consists of the import of a
102 planet extract. A precompiled PBF with the necessary data can be downloaded from
103 https://www.nominatim.org/data/test/nominatim-api-testdata.pbf
105 The polygons defining the extract can be found in the test/testdb
106 directory. There is also a reduced set of wikipedia data for this extract,
107 which you need to import as well. For Tiger tests the data of South Dakota
108 is required. Get the Tiger files `46*`.
110 The official test dataset is derived from the 160725 planet. Newer
111 planets are likely to work as well but you may see isolated test
112 failures where the data has changed. To recreate the input data
113 for the test database run:
115 wget https://free.nchc.org.tw/osm.planet/pbf/planet-160725.osm.pbf
116 osmconvert planet-160725.osm.pbf -B=test/testdb/testdb.polys -o=testdb.pbf
118 Before importing make sure to add the following to your local settings:
120 @define('CONST_Database_DSN', 'pgsql://@/test_api_nominatim');
121 @define('CONST_Wikipedia_Data_Path', CONST_BasePath.'/test/testdb');
125 The API tests also support code coverage tests. You need to install
126 [PHP_CodeCoverage](https://github.com/sebastianbergmann/php-code-coverage).
127 On Debian/Ubuntu run:
129 apt-get install php-codecoverage php-xdebug
131 The run the API tests as follows:
133 behave api -DPHPCOV=<coverage output dir>
135 The output directory must be an absolute path. To generate reports, you can use
136 the [phpcov](https://github.com/sebastianbergmann/phpcov) tool:
138 phpcov merge --html=<report output dir> <coverage output dir>
140 ### Indexing Tests (`test/bdd/db`)
142 These tests check the import and update of the Nominatim database. They do not
143 test the correctness of osm2pgsql. Each test will write some data into the `place`
144 table (and optionally `the planet_osm_*` tables if required) and then run
145 Nominatim's processing functions on that.
147 These tests need to create their own test databases. By default they will be
148 called `test_template_nominatim` and `test_nominatim`. Names can be changed with
149 the environment variables `TEMPLATE_DB` and `TEST_DB`. The user running the tests
150 needs superuser rights for postgres.
152 ### Import Tests (`test/bdd/osm2pgsql`)
154 These tests check that data is imported correctly into the place table. They
155 use the same template database as the Indexing tests, so the same remarks apply.