]> git.openstreetmap.org Git - nominatim.git/blob - tests/features/api/search_order.feature
Merge pull request #487 from lonvia/unify-reverse
[nominatim.git] / tests / features / api / search_order.feature
1 Feature: Result order for Geocoding
2     Testing that importance ordering returns sensible results
3
4     Scenario Outline: city order in street search
5         Given the request parameters
6           | limit
7           | 100
8         When sending json search query "<street>, <city>" with address
9         Then address of result 0 contains
10          | type   | value
11          | <type> | <city>
12
13     Examples:
14         | type   | city            | street
15         | city   | Zürich          | Rigistr
16         | city   | Karlsruhe       | Sophienstr
17         | city   | München         | Karlstr
18         | city   | Praha           | Dlouhá
19
20     Scenario Outline: use more important city in street search
21         When sending json search query "<street>, <city>" with address
22         Then result addresses contain
23           | ID | country_code
24           | 0  | <country>
25
26     Examples:
27         | country | city       | street
28         | gb      | London     | Main St
29         | gb      | Manchester | Central Street
30
31     # https://trac.openstreetmap.org/ticket/5094
32     Scenario: housenumbers are ordered by complete match first
33         When sending json search query "4 Докукина Москва" with address
34         Then result addresses contain
35           | ID | house_number
36           | 0  | 4