mirror of
https://github.com/osm-search/Nominatim.git
synced 2024-12-18 18:41:51 +03:00
97 lines
2.9 KiB
Gherkin
97 lines
2.9 KiB
Gherkin
Feature: Simple Reverse Tests
|
|
Simple tests for internal server errors and response format.
|
|
These tests should pass on any Nominatim installation.
|
|
|
|
Scenario Outline: Simple reverse-geocoding
|
|
When looking up xml coordinates <lat>,<lon>
|
|
Then the result is valid xml
|
|
When looking up json coordinates <lat>,<lon>
|
|
Then the result is valid json
|
|
When looking up jsonv2 coordinates <lat>,<lon>
|
|
Then the result is valid json
|
|
|
|
Examples:
|
|
| lat | lon
|
|
| 0.0 | 0.0
|
|
| 45.3 | 3.5
|
|
| -79.34 | 23.5
|
|
| 0.23 | -178.555
|
|
|
|
Scenario Outline: Wrapping of legal jsonp requests
|
|
Given the request parameters
|
|
| json_callback
|
|
| foo
|
|
When looking up <format> coordinates 67.3245,0.456
|
|
Then the result is valid json
|
|
|
|
Examples:
|
|
| format
|
|
| json
|
|
| jsonv2
|
|
|
|
Scenario: Reverse-geocoding without address
|
|
Given the request parameters
|
|
| addressdetails
|
|
| 0
|
|
When looking up xml coordinates 36.791966,127.171726
|
|
Then the result is valid xml
|
|
When looking up json coordinates 36.791966,127.171726
|
|
Then the result is valid json
|
|
When looking up jsonv2 coordinates 36.791966,127.171726
|
|
Then the result is valid json
|
|
|
|
Scenario: Reverse-geocoding with zoom
|
|
Given the request parameters
|
|
| zoom
|
|
| 10
|
|
When looking up xml coordinates 36.791966,127.171726
|
|
Then the result is valid xml
|
|
When looking up json coordinates 36.791966,127.171726
|
|
Then the result is valid json
|
|
When looking up jsonv2 coordinates 36.791966,127.171726
|
|
Then the result is valid json
|
|
|
|
Scenario: Missing lon parameter
|
|
Given the request parameters
|
|
| lat
|
|
| 51.51
|
|
When sending an API call reverse
|
|
Then exactly 0 results are returned
|
|
|
|
Scenario: Missing lat parameter
|
|
Given the request parameters
|
|
| lon
|
|
| -79.39114
|
|
When sending an API call reverse
|
|
Then exactly 0 results are returned
|
|
|
|
Scenario: Missing osm_id parameter
|
|
Given the request parameters
|
|
| osm_type
|
|
| N
|
|
When sending an API call reverse
|
|
Then exactly 0 results are returned
|
|
|
|
Scenario: Missing osm_type parameter
|
|
Given the request parameters
|
|
| osm_id
|
|
| 3498564
|
|
When sending an API call reverse
|
|
Then exactly 0 results are returned
|
|
|
|
Scenario Outline: Bad format for lat or lon
|
|
Given the request parameters
|
|
| lat | lon |
|
|
| <lat> | <lon> |
|
|
When sending an API call reverse
|
|
Then exactly 0 results are returned
|
|
|
|
Examples:
|
|
| lat | lon
|
|
| 48.9660 | 8,4482
|
|
| 48,9660 | 8.4482
|
|
| 48,9660 | 8,4482
|
|
| 48.966.0 | 8.4482
|
|
| 48.966 | 8.448.2
|
|
| Nan | 8.448
|
|
| 48.966 | Nan |