2 Feature: Object details
3 Check details page for correctness
5 Scenario: Details by place ID
6 When sending details query for 107077
7 Then the result is valid json
13 Scenario Outline: Details via OSM id
14 When sending details query for <type><id>
15 Then the result is valid json
27 Scenario Outline: Details for different class types for the same OSM id
28 When sending details query for N300209696:<class>
29 Then the result is valid json
31 | osm_type | osm_id | category |
32 | N | 300209696 | <class> |
41 Scenario Outline: Details via unknown OSM id
42 When sending details query for <object>
43 Then a HTTP 404 is returned
49 | N300209696:highway |
53 Scenario: Details for interpolation way just return the dependent street
54 When sending details query for W1
55 Then the result is valid json
62 Scenario: Details for interpolation way return the interpolation
63 When sending details query for W1
64 Then the result is valid json
66 | category | type | osm_type | osm_id | admin_level |
67 | place | houses | W | 1 | 15 |
72 Scenario: Details for Tiger way just return the dependent street
73 When sending details query for 112871
74 Then the result is valid json
82 Scenario: Details for interpolation way return the interpolation
83 When sending details query for 112871
84 Then the result is valid json
86 | category | type | admin_level |
87 | place | houses | 15 |
88 And result has not attributes osm_type,osm_id
93 Scenario: Details for postcodes just return the dependent place
94 When sending details query for 112820
95 Then the result is valid json
103 Scenario: Details for interpolation way return the interpolation
104 When sending details query for 112820
105 Then the result is valid json
107 | category | type | admin_level |
108 | place | postcode | 15 |
109 And result has not attributes osm_type,osm_id
113 Scenario Outline: Details debug output returns no errors
114 When sending debug details query for <feature>
115 Then the result is valid html