Merge remote-tracking branch 'upstream/master'

[nominatim.git] / test / bdd / api / reverse / params.feature

diff --git a/test/bdd/api/reverse/params.feature b/test/bdd/api/reverse/params.feature
index 0d35cdc7f3dbee839824e9c9599a4a4cbd080f7a..374272d0594f37526f85ca17a1e9dabff0ba5186 100644 (file)
--- a/test/bdd/api/reverse/params.feature
+++ b/test/bdd/api/reverse/params.feature
@@ -1,9 +1,9 @@
 @APIDB
 Feature: Parameters for Reverse API
-    Testing diferent parameter options for reverse API.
+    Testing different parameter options for reverse API.
 
     Scenario Outline: Reverse-geocoding without address
-        When sending <format> reverse coordinates 53.603,10.041
+        When sending <format> reverse coordinates 47.13,9.56
           | addressdetails |
           | 0 |
         Then exactly 1 result is returned
@@ -13,10 +13,20 @@ Feature: Parameters for Reverse API
       | format |
       | json |
       | jsonv2 |
+      | geojson |
       | xml |
 
+    Scenario Outline: Coordinates must be floating-point numbers
+        When sending reverse coordinates <coords>
+        Then a HTTP 400 is returned
+
+    Examples:
+      | coords    |
+      | -45.3,;   |
+      | gkjd,50   |
+
     Scenario Outline: Reverse Geocoding with extratags
-        When sending <format> reverse coordinates 10.776234290950017,106.70425325632095
+        When sending <format> reverse coordinates 47.1395013150811,9.522098077031046
           | extratags |
           | 1 |
         Then result 0 has attributes extratags
@@ -26,9 +36,10 @@ Feature: Parameters for Reverse API
         | xml |
         | json |
         | jsonv2 |
+        | geojson |
 
     Scenario Outline: Reverse Geocoding with namedetails
-        When sending <format> reverse coordinates 10.776455623137625,106.70175343751907
+        When sending <format> reverse coordinates 47.1395013150811,9.522098077031046
           | namedetails |
           | 1 |
         Then result 0 has attributes namedetails
@@ -38,6 +49,7 @@ Feature: Parameters for Reverse API
         | xml |
         | json |
         | jsonv2 |
+        | geojson |
 
     Scenario Outline: Reverse Geocoding contains TEXT geometry
         When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
@@ -51,18 +63,6 @@ Feature: Parameters for Reverse API
         | json     | geotext |
         | jsonv2   | geotext |
 
-    Scenario Outline: Reverse Geocoding contains polygon-as-points geometry
-        When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
-          | polygon |
-          | 1 |
-        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
         When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
           | polygon_svg |
@@ -98,5 +98,17 @@ Feature: Parameters for Reverse API
         | xml      | geojson |
         | json     | geojson |
         | jsonv2   | geojson |
+        | geojson  | geojson |
 
+    Scenario Outline: Reverse Geocoding in geojson format contains no non-geojson geometry
+        When sending geojson reverse coordinates 47.165989816710066,9.515774846076965
+          | polygon_text | polygon_svg | polygon_geokml |
+          | 1            | 1           | 1              |
+        Then result 0 has not attributes <response_attribute>
 
+    Examples:
+        | response_attribute |
+        | geotext            |
+        | polygonpoints      |
+        | svg                |
+        | geokml             |