1 Feature: Simple Reverse Tests
2 Simple tests for internal server errors and response format.
3 These tests should pass on any Nominatim installation.
5 Scenario Outline: Simple reverse-geocoding
6 When looking up xml coordinates <lat>,<lon>
7 Then the result is valid xml
8 When looking up json coordinates <lat>,<lon>
9 Then the result is valid json
10 When looking up jsonv2 coordinates <lat>,<lon>
11 Then the result is valid json
20 Scenario Outline: Wrapping of legal jsonp requests
21 Given the request parameters
24 When looking up <format> coordinates 67.3245,0.456
25 Then the result is valid json
32 Scenario: Reverse-geocoding without address
33 Given the request parameters
36 When looking up xml coordinates 36.791966,127.171726
37 Then the result is valid xml
38 When looking up json coordinates 36.791966,127.171726
39 Then the result is valid json
40 When looking up jsonv2 coordinates 36.791966,127.171726
41 Then the result is valid json
43 Scenario: Reverse-geocoding with zoom
44 Given the request parameters
47 When looking up xml coordinates 36.791966,127.171726
48 Then the result is valid xml
49 When looking up json coordinates 36.791966,127.171726
50 Then the result is valid json
51 When looking up jsonv2 coordinates 36.791966,127.171726
52 Then the result is valid json
54 Scenario: Missing lon parameter
55 Given the request parameters
58 When sending an API call reverse
59 Then exactly 0 results are returned
61 Scenario: Missing lat parameter
62 Given the request parameters
65 When sending an API call reverse
66 Then exactly 0 results are returned
68 Scenario: Missing osm_id parameter
69 Given the request parameters
72 When sending an API call reverse
73 Then exactly 0 results are returned
75 Scenario: Missing osm_type parameter
76 Given the request parameters
79 When sending an API call reverse
80 Then exactly 0 results are returned
82 Scenario Outline: Bad format for lat or lon
83 Given the request parameters
86 When sending an API call reverse
87 Then exactly 0 results are returned