3 Feature: Object details
4 Check details page for correctness
6 Scenario Outline: Details via OSM id
7 When sending details query for <type><id>
8 Then the result is valid json
20 Scenario Outline: Details for different class types for the same OSM id
21 When sending details query for N300209696:<class>
22 Then the result is valid json
24 | osm_type | osm_id | category |
25 | N | 300209696 | <class> |
34 Scenario Outline: Details via unknown OSM id
35 When sending details query for <object>
36 Then a HTTP 404 is returned
42 | N300209696:highway |
46 Scenario: Details for interpolation way just return the dependent street
47 When sending details query for W1
48 Then the result is valid json
55 Scenario: Details for interpolation way return the interpolation
56 When sending details query for W1
57 Then the result is valid json
59 | category | type | osm_type | osm_id | admin_level |
60 | place | houses | W | 1 | 15 |
65 Scenario: Details for Tiger way just return the dependent street
66 When sending details query for 112871
67 Then the result is valid json
75 Scenario: Details for interpolation way return the interpolation
76 When sending details query for 112871
77 Then the result is valid json
79 | category | type | admin_level |
80 | place | houses | 15 |
81 And result has not attributes osm_type,osm_id
86 Scenario: Details for postcodes just return the dependent place
87 When sending details query for 112820
88 Then the result is valid json
96 Scenario: Details for interpolation way return the interpolation
97 When sending details query for 112820
98 Then the result is valid json
100 | category | type | admin_level |
101 | place | postcode | 15 |
102 And result has not attributes osm_type,osm_id
106 Scenario Outline: Details debug output returns no errors
107 When sending debug details query for <feature>
108 Then the result is valid html