3 Feature: Object details
4 Check details page for correctness
6 Scenario: Details by place ID
7 When sending details query for 107077
8 Then the result is valid json
14 Scenario Outline: Details via OSM id
15 When sending details query for <type><id>
16 Then the result is valid json
28 Scenario Outline: Details for different class types for the same OSM id
29 When sending details query for N300209696:<class>
30 Then the result is valid json
32 | osm_type | osm_id | category |
33 | N | 300209696 | <class> |
42 Scenario Outline: Details via unknown OSM id
43 When sending details query for <object>
44 Then a HTTP 404 is returned
50 | N300209696:highway |
54 Scenario: Details for interpolation way just return the dependent street
55 When sending details query for W1
56 Then the result is valid json
63 Scenario: Details for interpolation way return the interpolation
64 When sending details query for W1
65 Then the result is valid json
67 | category | type | osm_type | osm_id | admin_level |
68 | place | houses | W | 1 | 15 |
73 Scenario: Details for Tiger way just return the dependent street
74 When sending details query for 112871
75 Then the result is valid json
83 Scenario: Details for interpolation way return the interpolation
84 When sending details query for 112871
85 Then the result is valid json
87 | category | type | admin_level |
88 | place | houses | 15 |
89 And result has not attributes osm_type,osm_id
94 Scenario: Details for postcodes just return the dependent place
95 When sending details query for 112820
96 Then the result is valid json
104 Scenario: Details for interpolation way return the interpolation
105 When sending details query for 112820
106 Then the result is valid json
108 | category | type | admin_level |
109 | place | postcode | 15 |
110 And result has not attributes osm_type,osm_id
114 Scenario Outline: Details debug output returns no errors
115 When sending debug details query for <feature>
116 Then the result is valid html