osm-search/Nominatim
1
1
Fork 0
mirror of https://github.com/osm-search/Nominatim.git synced 2024-11-29 16:42:23 +03:00
Code Issues Packages Projects Releases Wiki Activity
d1143b4580
Nominatim/test/bdd/api/search/queries.feature

150 lines
5.3 KiB
Gherkin
Raw Normal View History

more API search tests also move directory name back to api
2016-12-19 23:38:42 +03:00
@APIDB
Feature: Search queries
Generic search result correctness
Scenario: House number search for non-street address
When sending json search query "2 Steinwald, Austria" with address
| accept-language |
| en |
Then address of result 0 is
| type | value |
| house_number | 2 |
| hamlet | Steinwald |
| postcode | 6811 |
| country | Austria |
| country_code | at |
Scenario: House number interpolation even
When sending json search query "Schellingstr 86, Hamburg" with address
| accept-language |
| de |
Then address of result 0 is
| type | value |
| house_number | 86 |
| road | Schellingstraße |
| suburb | Eilbek |
| postcode | 22089 |
| city_district | Wandsbek |
| state | Hamburg |
| country | Deutschland |
| country_code | de |
Scenario: House number interpolation odd
When sending json search query "Schellingstr 73, Hamburg" with address
| accept-language |
| de |
Then address of result 0 is
| type | value |
| house_number | 73 |
| road | Schellingstraße |
| suburb | Eilbek |
| postcode | 22089 |
| city_district | Wandsbek |
| state | Hamburg |
| country | Deutschland |
| country_code | de |
tests: more coverage for all API endpoints
2017-10-04 01:05:34 +03:00
Scenario: With missing housenumber search falls back to road
When sending json search query "342 rocha, santa lucia" with address
Then address of result 0 is
| type | value |
| road | Rocha |
| city | Santa Lucía |
| state | Canelones |
| postcode | 90700 |
| country | Uruguay |
| country_code | uy |
more API search tests also move directory name back to api
2016-12-19 23:38:42 +03:00
@Tiger
Scenario: TIGER house number
When sending json search query "323 22nd Street Southwest, Huron"
Then results contain
| osm_type |
| way |
Scenario: Search with class-type feature
limit number of considered places in POI queries When searching for POIs in place_classtype_ tables limit the number of objects considered to 300. The distinct and order by clauses forced until now to retrive all matching objects and order them first which can cause long running queries when retriving them for large areas like the US. Fixes #735.
2017-06-05 22:33:50 +03:00
When sending jsonv2 search query "Hotel in California"
more API search tests also move directory name back to api
2016-12-19 23:38:42 +03:00
Then results contain
| place_rank |
| 30 |
finish search API tests
2016-12-21 22:28:27 +03:00
more API tests for code coverage Also fixes two minor issues related to structured queries.
2017-09-18 00:30:08 +03:00
Scenario: Search with specific amenity
When sending json search query "[restaurant] Vaduz" with address
Then result addresses contain
| country |
| Liechtenstein |
And results contain
| class | type |
| amenity | restaurant |
reinstate key-value amenity search Reenable search by the secret special term [key=value] matching against the given main tag. Note that for most cases that works only for tags that also have a special search table.
2017-09-18 23:07:08 +03:00
Scenario: Search with key-value amenity
When sending json search query "[shop=hifi] hamburg"
Then results contain
| class | type |
| shop | hifi |
Scenario: With multiple amenity search only the first is used
When sending json search query "[shop=hifi] [church] hamburg"
Then results contain
| class | type |
| shop | hifi |
Scenario: With multiple amenity search only the first is used
When sending json search query "[church] [restaurant] hamburg"
Then results contain
| class | type |
| amenity | place_of_worship |
fix handling of near queries with special search Make sure to use the classtype tables with near search and allow to search for arbitrary key/values (forbidding it for viewbox searches). Add tests for near queries.
2017-09-19 01:07:11 +03:00
Scenario: POI search near given coordinate
When sending json search query "restaurant near 47.16712,9.51100"
Then results contain
| class | type |
| amenity | restaurant |
Scenario: Arbitrary key/value search near given coordinate
tests: more coverage for all API endpoints
2017-10-04 01:05:34 +03:00
When sending json search query "[man_made=mast] 47.15739° N 9.61264° E"
Then results contain
| class | type |
| man_made | mast |
Scenario: Arbitrary key/value search near given coordinate and named place
When sending json search query "[man_made=mast] amerlugalpe 47° 9′ 26″ N 9° 36′ 45″ E"
fix handling of near queries with special search Make sure to use the classtype tables with near search and allow to search for arbitrary key/values (forbidding it for viewbox searches). Add tests for near queries.
2017-09-19 01:07:11 +03:00
Then results contain
| class | type |
| man_made | mast |
tests: more coverage for all API endpoints
2017-10-04 01:05:34 +03:00
Scenario: Name search near given coordinate
When sending json search query "amerlugalpe, N 47.15739° E 9.61264°"
Then exactly 1 result is returned
Scenario: Name search near given coordinate without result
When sending json search query "amerlugalpe, N 47 15 7 W 9 61 26"
Then exactly 0 results are returned
more coverage tests for Geocode.php
2017-10-03 00:09:45 +03:00
Scenario: Arbitrary key/value search near a road
When sending json search query "[leisure=table_soccer_table] immenbusch"
Then results contain
| class | type |
| leisure | table_soccer_table |
Scenario: Ignore other country codes in structured search with country
When sending json search query ""
| city | country |
| li | de |
Then exactly 0 results are returned
Scenario: Ignore country searches when query is restricted to countries
When sending json search query "de"
| countrycodes |
| li |
Then exactly 0 results are returned
finish search API tests
2016-12-21 22:28:27 +03:00
# https://trac.openstreetmap.org/ticket/5094
Scenario: housenumbers are ordered by complete match first
When sending json search query "6395 geminis, montevideo" with address
Then result addresses contain
| ID | house_number |
| 0 | 6395 |
| 1 | 6395 BIS |
Reference in New Issue Copy Permalink