openmaptiles/tests/update/300_update-landcover.osc

<?xml version='1.0' encoding='UTF-8'?>
<osmChange version="0.6" generator="Manual" timestamp="2020-01-02T00:00:00Z">
  <!--
      Test 300: Landcover
        Change type of land cover from wood to scrub
  -->
  <modify>
    <way id="3000" timestamp="2020-01-02T00:00:00Z" version="2">
      <nd ref="300001" />
      <nd ref="300002" />
      <nd ref="300003" />
      <nd ref="300004" />
      <nd ref="300001" />
      <tag k="natural" v="scrub"/>
    </way>
  </modify>
</osmChange>
Framework for SQL-based unit tests for import and updates (#1249) This PR adds the ability to create SQL tests that ensure that OSM data is properly imported and updated in the OpenMapTiles data schema. The tests work by injecting test OSM data and updates into the database and checking to ensure that the data is properly loaded into the database using standard SQL statements. With this framework in place, developers can now write small tests to inject known data into the database and ensure that imports and updates are working correctly. In addition to the framework, basic tests are provided for four layers. These initial tests are in no way comprehensive, but they provide a structure and framework for developers to add their own tests or expand the existing ones to cover more cases. Usage: `make clean && make sql-test` ## How it works The SQL tests consist of the following parts: 1. Test import data, located in `tests/import`. This test data is in the [OSM XML](https://wiki.openstreetmap.org/wiki/OSM_XML) format and contains the data that should be initially injected into the database. The files are numbered in order to ensure that each test data file contains OSM id numbers that are distinct from the other files. For example, the file starting with `100` will use node ids from 100000-199999, way ids from 1000-1999, and relation ids from 100-199. 1. Test update data, located in `tests/update`. This test data is in the [osmChange XML](https://wiki.openstreetmap.org/wiki/OsmChange) format, and contains the data that will be used to update the test import data (in order to verify that the update process is working correctly. These files are also numbered using the same scheme as the test import data. 1. Import SQL test script, located at `tests/test-post-import.sql`. This script is executed after the test import data has been injected, and runs SQL-based checks to ensure that the import data was properly imported. If there are failures in the tests, an entry will be added to the table `omt_test_failures`, with one record per error that occurs during the import process. A test failure will also fail the build. To inspect the test failure messages, run `make psql` and issue the comment `SELECT * FROM omt_test_failures`. 1. Update SQL test script, located at `tests/test-post-update.sql`. This script performs the same function as the import test script, except that it occurs after the test update data has been applied to the database. Note that script will only run if the import script passes all tests. 2021-10-28 11:38:46 +00:00			`<?xml version='1.0' encoding='UTF-8'?>`
			`<osmChange version="0.6" generator="Manual" timestamp="2020-01-02T00:00:00Z">`
			`<!--`
			`Test 300: Landcover`
			`Change type of land cover from wood to scrub`
			`-->`
			`<modify>`
			`<way id="3000" timestamp="2020-01-02T00:00:00Z" version="2">`
			`<nd ref="300001" />`
			`<nd ref="300002" />`
			`<nd ref="300003" />`
			`<nd ref="300004" />`
			`<nd ref="300001" />`
			`<tag k="natural" v="scrub"/>`
			`</way>`
			`</modify>`
			`</osmChange>`