mirror of
https://github.com/osm-search/Nominatim.git
synced 2026-02-16 05:18:00 +00:00
add api tests for language, details and lookup
This commit is contained in:
14
test/bdd/api/details/simple.feature
Normal file
14
test/bdd/api/details/simple.feature
Normal file
@@ -0,0 +1,14 @@
|
||||
@APIDB
|
||||
Feature: Object details
|
||||
Check details page for correctness
|
||||
|
||||
Scenario Outline: Details via OSM id
|
||||
When sending details query for <object>
|
||||
Then the result is valid html
|
||||
|
||||
Examples:
|
||||
| object |
|
||||
| 492887 |
|
||||
| N4267356889 |
|
||||
| W230804120 |
|
||||
| R123924 |
|
||||
17
test/bdd/api/lookup/simple.feature
Normal file
17
test/bdd/api/lookup/simple.feature
Normal file
@@ -0,0 +1,17 @@
|
||||
@APIDB
|
||||
Feature: Places by osm_type and osm_id Tests
|
||||
Simple tests for internal server errors and response format.
|
||||
|
||||
Scenario Outline: address lookup for existing node, way, relation
|
||||
When sending <format> lookup query for N3284625766,W6065798,,R123924,X99,N0
|
||||
Then the result is valid <format>
|
||||
And exactly 3 results are returned
|
||||
|
||||
Examples:
|
||||
| format |
|
||||
| xml |
|
||||
| json |
|
||||
|
||||
Scenario: address lookup for non-existing or invalid node, way, relation
|
||||
When sending xml lookup query for X99,,N0,nN158845944,ABC,,W9
|
||||
Then exactly 0 results are returned
|
||||
36
test/bdd/api/reverse/language.feature
Normal file
36
test/bdd/api/reverse/language.feature
Normal file
@@ -0,0 +1,36 @@
|
||||
@APIDB
|
||||
Feature: Localization of reverse search results
|
||||
|
||||
Scenario: default language
|
||||
When sending json reverse coordinates 18.1147,-15.95
|
||||
Then result addresses contain
|
||||
| ID | country |
|
||||
| 0 | Mauritanie موريتانيا |
|
||||
|
||||
Scenario: accept-language parameter
|
||||
When sending json reverse coordinates 18.1147,-15.95
|
||||
| accept-language |
|
||||
| en,fr |
|
||||
Then result addresses contain
|
||||
| ID | country |
|
||||
| 0 | Mauritania |
|
||||
|
||||
Scenario: HTTP accept language header
|
||||
Given the HTTP header
|
||||
| accept-language |
|
||||
| fr-ca,fr;q=0.8,en-ca;q=0.5,en;q=0.3 |
|
||||
When sending json reverse coordinates 18.1147,-15.95
|
||||
Then result addresses contain
|
||||
| ID | country |
|
||||
| 0 | Mauritanie |
|
||||
|
||||
Scenario: accept-language parameter and HTTP header
|
||||
Given the HTTP header
|
||||
| accept-language |
|
||||
| fr-ca,fr;q=0.8,en-ca;q=0.5,en;q=0.3 |
|
||||
When sending json reverse coordinates 18.1147,-15.95
|
||||
| accept-language |
|
||||
| en |
|
||||
Then result addresses contain
|
||||
| ID | country |
|
||||
| 0 | Mauritania |
|
||||
62
test/bdd/api/search/language.feature
Normal file
62
test/bdd/api/search/language.feature
Normal file
@@ -0,0 +1,62 @@
|
||||
@APIDB
|
||||
Feature: Localization of search results
|
||||
|
||||
Scenario: default language
|
||||
When sending json search query "Vietnam"
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Việt Nam |
|
||||
|
||||
Scenario: accept-language first
|
||||
When sending json search query "Mauretanien"
|
||||
| accept-language |
|
||||
| en,de |
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Mauritania |
|
||||
|
||||
Scenario: accept-language missing
|
||||
When sending json search query "Mauretanien"
|
||||
| accept-language |
|
||||
| xx,fr,en,de |
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Mauritanie |
|
||||
|
||||
Scenario: http accept language header first
|
||||
Given the HTTP header
|
||||
| accept-language |
|
||||
| fr-ca,fr;q=0.8,en-ca;q=0.5,en;q=0.3 |
|
||||
When sending json search query "Mauretanien"
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Mauritanie |
|
||||
|
||||
Scenario: http accept language header and accept-language
|
||||
Given the HTTP header
|
||||
| accept-language |
|
||||
| fr-ca,fr;q=0.8,en-ca;q=0.5,en;q=0.3 |
|
||||
When sending json search query "Mauretanien"
|
||||
| accept-language |
|
||||
| de,en |
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Mauretanien |
|
||||
|
||||
Scenario: http accept language header fallback
|
||||
Given the HTTP header
|
||||
| accept-language |
|
||||
| fr-ca,en-ca;q=0.5 |
|
||||
When sending json search query "Mauretanien"
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Mauritanie |
|
||||
|
||||
Scenario: http accept language header fallback (upper case)
|
||||
Given the HTTP header
|
||||
| accept-language |
|
||||
| fr-FR;q=0.8,en-ca;q=0.5 |
|
||||
When sending json search query "Mauretanie"
|
||||
Then results contain
|
||||
| ID | display_name |
|
||||
| 0 | Mauritanie |
|
||||
@@ -30,6 +30,8 @@ Feature: Search queries
|
||||
|
||||
Scenario: XML search with addressdetails
|
||||
When sending xml search query "Aleg" with address
|
||||
| accept-language |
|
||||
| en |
|
||||
Then address of result 0 is
|
||||
| type | value |
|
||||
| city | Aleg |
|
||||
@@ -39,6 +41,8 @@ Feature: Search queries
|
||||
|
||||
Scenario: coordinate search with addressdetails
|
||||
When sending json search query "14.271104294939,107.69828796387"
|
||||
| accept-language |
|
||||
| en |
|
||||
Then results contain
|
||||
| display_name |
|
||||
| Plei Ya Rê, Kon Tum province, Vietnam |
|
||||
|
||||
Reference in New Issue
Block a user