X-Git-Url: https://git.openstreetmap.org./nominatim.git/blobdiff_plain/e90087a063698139beb087f24c068ce04171e8bf..8b896f37f34cc53b151d71df3a7a6a7b7fc2b52f:/tests/features/api/search_params.feature?ds=sidebyside diff --git a/tests/features/api/search_params.feature b/tests/features/api/search_params.feature index 7099c72f..de6bd53d 100644 --- a/tests/features/api/search_params.feature +++ b/tests/features/api/search_params.feature @@ -8,6 +8,7 @@ Feature: Search queries And result 0 has attributes lat,lon,display_name And result 0 has attributes class,type,importance,icon And result 0 has not attributes address + And results contain valid boundingboxes Scenario: Simple JSON search When sending json search query "Vaduz" @@ -15,6 +16,7 @@ Feature: Search queries And result 0 has attributes osm_type,osm_id,boundingbox And result 0 has attributes lat,lon,display_name,importance And result 0 has not attributes address + And results contain valid boundingboxes Scenario: JSON search with addressdetails When sending json search query "Montevideo" with address @@ -29,11 +31,16 @@ Feature: Search queries When sending xml search query "Inuvik" with address Then address of result 0 contains | type | value - | city | Inuvik | state | Northwest Territories | country | Canada | country_code | ca + Scenario: coordinate search with addressdetails + When sending json search query "51.193058013916,15.5245780944824" with address + Then result addresses contain + | village | country | country_code + | Kraszowice | Polska | pl + Scenario: Address details with unknown class types When sending json search query "foobar, Essen" with address Then results contain @@ -185,7 +192,6 @@ Feature: Search queries | 0.0 | 0.5 | 999 - | nan Scenario Outline: Search with polygon threshold (xml) Given the request parameters @@ -201,7 +207,14 @@ Feature: Search queries | 0.0 | 0.5 | 999 - | nan + + Scenario Outline: Search with invalid polygon threshold (xml) + Given the request parameters + | polygon_geojson | polygon_threshold + | 1 | + When sending xml search query "switzerland" + Then a HTTP 400 is returned + Scenario Outline: Search with extratags Given the request parameters @@ -230,3 +243,73 @@ Feature: Search queries | xml | json | jsonv2 + + + Scenario Outline: Search result with contains TEXT geometry + Given the request parameters + | polygon_text + | 1 + When sending search query "switzerland" + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geotext + | json | geotext + | jsonv2 | geotext + + Scenario Outline: Search result contains polygon-as-points geometry + Given the request parameters + | polygon + | 1 + When sending search query "switzerland" + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | polygonpoints + | json | polygonpoints + | jsonv2 | polygonpoints + + + + Scenario Outline: Search result contains SVG geometry + Given the request parameters + | polygon_svg + | 1 + When sending search query "switzerland" + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geosvg + | json | svg + | jsonv2 | svg + + + Scenario Outline: Search result contains KML geometry + Given the request parameters + | polygon_kml + | 1 + When sending search query "switzerland" + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geokml + | json | geokml + | jsonv2 | geokml + + + Scenario Outline: Search result contains GEOJSON geometry + Given the request parameters + | polygon_geojson + | 1 + When sending search query "switzerland" + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geojson + | json | geojson + | jsonv2 | geojson