]> git.openstreetmap.org Git - nominatim.git/blob - tests/features/api/regression.feature
fix top-bottom mixup in bounding box
[nominatim.git] / tests / features / api / regression.feature
1 Feature: API regression tests
2     Tests error cases reported in tickets.
3
4     Scenario: trac #2430
5         When sending json search query "89 River Avenue, Hoddesdon, Hertfordshire, EN11 0JT"
6         Then at least 1 result is returned
7
8     Scenario: trac #2440
9         When sending json search query "East Harvard Avenue, Denver"
10         Then more than 2 results are returned
11
12     Scenario: trac #2456
13         When sending xml search query "Borlänge Kommun"
14         Then results contain
15          | ID | place_rank
16          | 0  | 19
17
18     Scenario: trac #2530
19         When sending json search query "Lange Straße, Bamberg" with address
20         Then result addresses contain
21          | ID | town
22          | 0  | Bamberg
23
24     Scenario: trac #2541
25         When sending json search query "pad, germany"
26         Then results contain
27          | ID | class   | display_name
28          | 0  | aeroway | Paderborn/Lippstadt,.*
29
30     Scenario: trac #2579
31         When sending json search query "Johnsons Close, hackbridge" with address
32         Then result addresses contain
33          | ID | postcode
34          | 0  | SM5 2LU
35
36     @Fail
37     Scenario Outline: trac #2586
38         When sending json search query "<query>" with address
39         Then result addresses contain
40          | ID | country_code
41          | 0  | uk
42
43     Examples:
44         | query
45         | DL7 0SN
46         | DL70SN
47
48     Scenario: trac #2628 (1)
49         When sending json search query "Adam Kraft Str" with address
50         Then result addresses contain
51          | ID | road          
52          | 0  | Adam-Kraft-Straße
53
54     Scenario: trac #2628 (2)
55         When sending json search query "Maxfeldstr. 5, Nürnberg" with address
56         Then result addresses contain
57          | ID | house_number | road          | city
58          | 0  | 5            | Maxfeldstraße | Nürnberg
59
60     Scenario: trac #2638
61         When sending json search query "Nöthnitzer Str. 40, 01187 Dresden" with address
62         Then result addresses contain
63          | ID | house_number | road              | city
64          | 0  | 40           | Nöthnitzer Straße | Dresden
65
66     Scenario Outline: trac #2667
67         When sending json search query "<query>" with address
68         Then result addresses contain
69          | ID | house_number
70          | 0  | <number>
71
72     Examples:
73         | number | query
74         | 16     | 16 Woodpecker Way, Cambourne
75         | 14906  | 14906, 114 Street Northwest, Edmonton, Alberta, Canada
76         | 14904  | 14904, 114 Street Northwest, Edmonton, Alberta, Canada
77         | 15022  | 15022, 114 Street Northwest, Edmonton, Alberta, Canada
78         | 15024  | 15024, 114 Street Northwest, Edmonton, Alberta, Canada
79
80     Scenario: trac #2681
81         When sending json search query "kirchstraße troisdorf Germany"
82         Then results contain
83          | ID | display_name
84          | 0  | .*, Troisdorf, .*
85
86     Scenario: trac #2758
87         When sending json search query "6а, полуботка, чернигов" with address
88         Then result addresses contain
89          | ID | house_number
90          | 0  | 6а
91
92     Scenario: trac #2790
93         When looking up coordinates 49.0942079697809,8.27565898861822
94         Then result addresses contain
95          | ID | road          | village  | country
96          | 0  | Daimlerstraße | Jockgrim | Deutschland
97
98     Scenario: trac #2794
99         When sending json search query "4008"
100         Then results contain
101          | ID | class | type
102          | 0  | place | postcode
103
104     Scenario: trac #2797
105         When sending json search query "Philippstr.4, 52349 Düren" with address
106         Then result addresses contain
107          | ID | road          | town
108          | 0  | Philippstraße | Düren
109
110     Scenario: trac #2830
111         When sending json search query "528, Merkley Drive, K4A 1N5,CA" with address
112         Then result addresses contain
113          | ID | house_number | road          | postcode | country
114          | 0  | 528          | Merkley Drive | K4A 1N5  | Canada
115
116     Scenario: trac #2830
117         When sending json search query "K4A 1N5,CA"
118         Then results contain
119          | ID | class | type     | display_name
120          | 0  | place | postcode | .*, Canada
121
122     Scenario: trac #2845
123         When sending json search query "Leliestraat 31, Zwolle" with address
124         Then result addresses contain
125          | ID | city
126          | 0  | Zwolle
127
128     Scenario: trac #2852
129         When sending json search query "berlinerstrasse, leipzig" with address
130         Then result addresses contain
131          | ID | road
132          | 0  | Berliner Straße
133
134     Scenario: trac #2871
135         When looking up coordinates -33.906895553,150.99609375
136         Then result addresses contain
137          | ID | city       | postcode | country
138          | 0  | [^0-9]*    | 2197     | Australia
139
140     Scenario: trac #2974
141         When sending json search query "Azadi Square, Faruj" with address
142         Then result addresses contain
143          | ID | road        | city
144          | 0  | ميدان آزادي | فاروج
145         And results contain
146          | ID | latlon
147          | 0  | 37.2323,58.2193 +-1km
148
149      Scenario: trac #2981
150         When sending json search query "Ohmstraße 7, Berlin" with address
151         Then at least 2 results are returned
152         And result addresses contain
153          | house_number | road      | state
154          | 7            | Ohmstraße | Berlin
155
156      Scenario: trac #3049
157         When sending json search query "Soccer City"
158         Then results contain
159          | ID | class   | type    | latlon
160          | 0  | leisure | stadium | -26.2347261,27.982645 +-50m
161
162      Scenario: trac #3130
163         When sending json search query "Old Way, Frinton"
164         Then results contain
165          | ID | class   | latlon
166          | 0  | highway | 51.8324206,1.2447352 +-100m
167
168      Scenario Outline: trac #5025
169         When sending json search query "Kriegsstr <house_nr>, Karlsruhe" with address
170         Then result addresses contain
171           | house_number | road
172           | <house_nr>   | Kriegsstraße
173
174      Examples:
175         | house_nr
176         | 5c
177         | 25
178         | 78
179         | 80
180         | 99
181         | 130
182         | 153
183         | 196
184         | 256
185         | 294
186
187      Scenario: trac #5238
188         Given the request parameters
189          | bounded | viewbox
190          | 1       | 0,0,1,-1
191         When sending json search query "sy"
192         Then exactly 0 results are returned
193
194     Scenario: trac #5274
195         When sending json search query "Goedestraat 41-BS, Utrecht" with address
196         Then result addresses contain
197           | house_number | road        | city
198           | 41-BS        | Goedestraat | Utrecht
199
200     @poldi-only
201     Scenario Outline: github #36
202         When sending json search query "<query>" with address
203         Then result addresses contain
204          | ID | road     | city
205          | 0  | Seegasse | Wieselburg-Land
206
207     Examples:
208          | query
209          | Seegasse, Gemeinde Wieselburg-Land
210          | Seegasse, Wieselburg-Land
211          | Seegasse, Wieselburg
212
213     Scenario: github #190
214         When looking up place N257363453
215         Then the results contain
216          | osm_type   | osm_id     | latlon
217          | node       | 257363453  | 35.8404121,128.5586643 +-100m
218