+@SQLITE
@APIDB
Feature: Object details
Check details page for correctness
Scenario Outline: Details via OSM id
+ When sending details query for <type><id>
+ Then the result is valid json
+ And results contain
+ | osm_type | osm_id |
+ | <type> | <id> |
+
+ Examples:
+ | type | id |
+ | N | 5484325405 |
+ | W | 43327921 |
+ | R | 123924 |
+
+
+ Scenario Outline: Details for different class types for the same OSM id
+ When sending details query for N300209696:<class>
+ Then the result is valid json
+ And results contain
+ | osm_type | osm_id | category |
+ | N | 300209696 | <class> |
+
+ Examples:
+ | class |
+ | tourism |
+ | natural |
+ | mountain_pass |
+
+
+ Scenario Outline: Details via unknown OSM id
When sending details query for <object>
- Then the result is valid html
+ Then a HTTP 404 is returned
Examples:
- | object |
- | 492887 |
- | N4267356889 |
- | W230804120 |
- | R123924 |
-
- Scenario: Details with keywords
- When sending details query for W78099902
- | keywords |
- | 1 |
- Then the result is valid html
+ | object |
+ | 1 |
+ | R1 |
+ | N300209696:highway |
- Scenario: JSON Details
- When sending json details query for W78099902
+
+ @v1-api-php-only
+ Scenario: Details for interpolation way just return the dependent street
+ When sending details query for W1
+ Then the result is valid json
+ And results contain
+ | category |
+ | highway |
+
+
+ @v1-api-python-only
+ Scenario: Details for interpolation way return the interpolation
+ When sending details query for W1
Then the result is valid json
- And result has not attributes place_search_name_keywords,place_search_address_keywords,address_lines,linked_lines,parentof_lines
+ And results contain
+ | category | type | osm_type | osm_id | admin_level |
+ | place | houses | W | 1 | 15 |
+
- Scenario: JSON Details with keywords
- When sending json details query for W78099902
- | keywords |
- | 1 |
+ @v1-api-php-only
+ @Fail
+ Scenario: Details for Tiger way just return the dependent street
+ When sending details query for 112871
Then the result is valid json
- And result has attributes place_search_name_keywords,place_search_address_keywords
+ And results contain
+ | category |
+ | highway |
+
- Scenario: JSON Details with addressdetails
- When sending json details query for W78099902
- | addressdetails |
- | 1 |
+ @v1-api-python-only
+ @Fail
+ Scenario: Details for interpolation way return the interpolation
+ When sending details query for 112871
Then the result is valid json
- And result has attributes address_lines
+ And results contain
+ | category | type | admin_level |
+ | place | houses | 15 |
+ And result has not attributes osm_type,osm_id
- Scenario: JSON Details with linkedplaces
- When sending json details query for R123924
- | linkedplaces |
- | 1 |
+
+ @v1-api-php-only
+ @Fail
+ Scenario: Details for postcodes just return the dependent place
+ When sending details query for 112820
Then the result is valid json
- And result has attributes linked_lines
+ And results contain
+ | category |
+ | boundary |
+
- Scenario: JSON Details with childplaces
- When sending json details query for W78099902
- | childplaces |
- | 1 |
+ @v1-api-python-only
+ @Fail
+ Scenario: Details for interpolation way return the interpolation
+ When sending details query for 112820
Then the result is valid json
- And result has attributes parentof_lines
+ And results contain
+ | category | type | admin_level |
+ | place | postcode | 15 |
+ And result has not attributes osm_type,osm_id
+
+
+ @v1-api-python-only
+ Scenario Outline: Details debug output returns no errors
+ When sending debug details query for <feature>
+ Then the result is valid html
+
+ Examples:
+ | feature |
+ | N5484325405 |
+ | W1 |
+ | 112820 |
+ | 112871 |