+@SQLITE
@APIDB
Feature: Object details
Check details page for correctness
- Scenario: Details by place ID
- When sending details query for 107077
- Then the result is valid json
- And results contain
- | place_id |
- | 107077 |
-
-
Scenario Outline: Details via OSM id
When sending details query for <type><id>
Then the result is valid json
| N300209696:highway |
- @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
| place | houses | W | 1 | 15 |
- @v1-api-php-only
- Scenario: Details for Tiger way just return the dependent street
- When sending details query for 112871
- Then the result is valid json
- And results contain
- | category |
- | highway |
-
-
- @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 not attributes osm_type,osm_id
- @v1-api-php-only
- Scenario: Details for postcodes just return the dependent place
- When sending details query for 112820
- Then the result is valid json
- And results contain
- | category |
- | boundary |
-
-
- @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
| category | type | admin_level |
| place | postcode | 15 |
And result has not attributes osm_type,osm_id
+
+
+ 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 |