add mention of required Tiger files for test database

[nominatim.git] / tests / features / api / reverse.feature

diff --git a/tests/features/api/reverse.feature b/tests/features/api/reverse.feature
index fa636acf548b773f9b5df287f9f7ef6ab812512e..7bd129138f9f983c0f1312934007355c1f046bfd 100644 (file)
--- a/tests/features/api/reverse.feature
+++ b/tests/features/api/reverse.feature
@@ -11,18 +11,31 @@ Feature: Reverse geocoding
          | ID | country
          | 0  | Deutschland
 
+
+    Scenario: Boundingbox is returned
+        Given the request parameters
+          | format | zoom
+          | xml    | 4
+        When looking up coordinates 53.9788769,13.0830313
+        And results contain valid boundingboxes
+
+    Scenario: Reverse geocoding for odd interpolated housenumber
+
+    Scenario: Reverse geocoding for even interpolated housenumber
+
     @Tiger
     Scenario: TIGER house number
         Given the request parameters
           | addressdetails
           | 1
-        When looking up coordinates 40.6863624710666,-112.060005720023
+        When looking up jsonv2 coordinates 40.6863624710666,-112.060005720023
         And exactly 1 result is returned
         And result addresses contain
           | ID | house_number | road               | postcode | country_code
-          | 0  | 7094         | Kings Estate Drive | 84128    | us
-        And result 0 has not attributes osm_id,osm_type
-
+          | 0  | 709.         | Kings Estate Drive | 84128    | us
+        And results contain
+          | osm_type | category | type
+          | way      | place    | house
 
     @Tiger
     Scenario: No TIGER house number for zoom < 18
@@ -61,3 +74,75 @@ Feature: Reverse geocoding
         | xml
         | json
         | jsonv2
+
+
+   Scenario Outline: Reverse Geocoding contains TEXT geometry
+        Given the request parameters
+          | polygon_text
+          | 1
+        When looking up <format> coordinates 48.86093,2.2978
+        Then result 0 has attributes <response_attribute>
+
+   Examples:
+        | format   | response_attribute
+        | xml      | geotext
+        | json     | geotext
+        | jsonv2   | geotext
+
+   Scenario Outline: Reverse Geocoding contains polygon-as-points geometry
+        Given the request parameters
+          | polygon
+          | 1
+        When looking up <format> coordinates 48.86093,2.2978
+        Then result 0 has not attributes <response_attribute>
+
+   Examples:
+        | format   | response_attribute
+        | xml      | polygonpoints
+        | json     | polygonpoints
+        | jsonv2   | polygonpoints
+
+
+
+   Scenario Outline: Reverse Geocoding contains SVG geometry
+        Given the request parameters
+          | polygon_svg
+          | 1
+        When looking up <format> coordinates 48.86093,2.2978
+        Then result 0 has attributes <response_attribute>
+
+   Examples:
+        | format   | response_attribute
+        | xml      | geosvg
+        | json     | svg
+        | jsonv2   | svg
+
+
+   Scenario Outline: Reverse Geocoding contains KML geometry
+        Given the request parameters
+          | polygon_kml
+          | 1
+        When looking up <format> coordinates 48.86093,2.2978
+        Then result 0 has attributes <response_attribute>
+
+   Examples:
+        | format   | response_attribute
+        | xml      | geokml
+        | json     | geokml
+        | jsonv2   | geokml
+
+
+   Scenario Outline: Reverse Geocoding contains GEOJSON geometry
+        Given the request parameters
+          | polygon_geojson
+          | 1
+        When looking up <format> coordinates 48.86093,2.2978
+        Then result 0 has attributes <response_attribute>
+
+   Examples:
+        | format   | response_attribute
+        | xml      | geojson
+        | json     | geojson
+        | jsonv2   | geojson
+
+