make sure the place name always comes first in output

[nominatim.git] / test / bdd / api / search / queries.feature

diff --git a/test/bdd/api/search/queries.feature b/test/bdd/api/search/queries.feature
index d141122e1c32f145be2ef30b68b76cf574e3dca3..847f1dbf02823aff211fdfa073b65be4a042380a 100644 (file)
--- a/test/bdd/api/search/queries.feature
+++ b/test/bdd/api/search/queries.feature
@@ -2,6 +2,14 @@
 Feature: Search queries
     Generic search result correctness
 
 Feature: Search queries
     Generic search result correctness
 

+    Scenario: Search for natural object
+        When sending json search query "Samina"
+          | accept-language |
+          | en |
+        Then results contain
+          | ID | class    | type  | display_name    |
+          | 0  | waterway | river | Samina, Austria |
+

     Scenario: House number search for non-street address
         When sending json search query "6 Silum, Liechtenstein" with address
           | accept-language |
     Scenario: House number search for non-street address
         When sending json search query "6 Silum, Liechtenstein" with address
           | accept-language |


@@ -15,7 +23,7 @@ Feature: Search queries
           | postcode     | 9497 |
           | country      | Liechtenstein |
           | country_code | li |
           | postcode     | 9497 |
           | country      | Liechtenstein |
           | country_code | li |

-          | ISO3166-2-lvl10  | LI-10 |
+          | ISO3166-2-lvl8  | LI-10 |

 
     Scenario: House number interpolation
         When sending json search query "Grosssteg 1023, Triesenberg" with address
 
     Scenario: House number interpolation
         When sending json search query "Grosssteg 1023, Triesenberg" with address


@@ -42,7 +50,7 @@ Feature: Search queries
           | town          | Triesenberg |
           | country       | Liechtenstein |
           | country_code  | li |
           | town          | Triesenberg |
           | country       | Liechtenstein |
           | country_code  | li |

-          | ISO3166-2-lvl10  | LI-10 |
+          | ISO3166-2-lvl8  | LI-10 |

 
     Scenario Outline: Housenumber 0 can be found
         When sending <format> search query "Gnalpstrasse 0" with address
 
     Scenario Outline: Housenumber 0 can be found
         When sending <format> search query "Gnalpstrasse 0" with address


@@ -97,6 +105,7 @@ Feature: Search queries
           | class | type |
           | club  | scout |
 
           | class | type |
           | club  | scout |
 

+    @v1-api-php-only

     Scenario: With multiple amenity search only the first is used
         When sending json search query "[club=scout] [church] vaduz"
         Then results contain
     Scenario: With multiple amenity search only the first is used
         When sending json search query "[club=scout] [church] vaduz"
         Then results contain


@@ -119,6 +128,7 @@ Feature: Search queries
           | class   | type |
           | leisure | firepit |
 
           | class   | type |
           | leisure | firepit |
 

+    @v1-api-php-only

     Scenario: Arbitrary key/value search near given coordinate and named place
         When sending json search query "[leisure=firepit] ebenholz  47° 9′ 26″ N 9° 36′ 45″ E"
         Then results contain
     Scenario: Arbitrary key/value search near given coordinate and named place
         When sending json search query "[leisure=firepit] ebenholz  47° 9′ 26″ N 9° 36′ 45″ E"
         Then results contain


@@ -184,7 +194,6 @@ Feature: Search queries
         Then result addresses contain
           | ID | house_number |
           | 0  | 11 |
         Then result addresses contain
           | ID | house_number |
           | 0  | 11 |

-          | 1  | 11 a |

 
     Scenario Outline: Coordinate searches with white spaces
         When sending json search query "<data>"
 
     Scenario Outline: Coordinate searches with white spaces
         When sending json search query "<data>"