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
+ And results contain
+ | osm_type | osm_id |
+ | <type> | <id> |
+
+ Examples:
+ | type | id |
+ | N | 5484325405 |
+ | W | 43327921 |
+ | R | 123924 |
+
+ 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 |
+
+ 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 |
+
+