1 Feature: Search API geocodejson output
2 Testing correctness of geocodejson output.
4 Scenario: Search geocodejson - City housenumber-level address with street
5 When sending v1/search with format geocodejson
7 | Im Winkel 8, Triesen | 1 |
8 Then a HTTP 200 is returned
9 And the result is valid geocodejson
10 And all results contain
11 | housenumber | street | postcode | city | country |
12 | 8 | Im Winkel | 9495 | Triesen | Liechtenstein |
14 Scenario: Search geocodejson - Town street-level address with street
15 When sending v1/search with format geocodejson
16 | q | addressdetails |
17 | Gnetsch, Balzers | 1 |
18 Then a HTTP 200 is returned
19 And the result is valid geocodejson
20 And all results contain
21 | name | city | postcode | country |
22 | Gnetsch | Balzers | 9496 | Liechtenstein |
24 Scenario: Search geocodejson - Town street-level address with footway
25 When sending v1/search with format geocodejson
26 | q | addressdetails |
27 | burg gutenberg 6000 jahre geschichte | 1 |
28 Then a HTTP 200 is returned
29 And the result is valid geocodejson
30 And all results contain
31 | street | city | postcode | country |
32 | Burgweg | Balzers | 9496 | Liechtenstein |
34 Scenario: Search geocodejson - City address with suburb
35 When sending v1/search with format geocodejson
36 | q | addressdetails |
37 | Lochgass 5, Ebenholz, Vaduz | 1 |
38 Then a HTTP 200 is returned
39 And the result is valid geocodejson
40 And all results contain
41 | housenumber | street | district | city | postcode | country |
42 | 5 | Lochgass | Ebenholz | Vaduz | 9490 | Liechtenstein |