Special phrases documentation updated

[nominatim.git] / test / bdd / api / details / simple.feature

diff --git a/test/bdd/api/details/simple.feature b/test/bdd/api/details/simple.feature
index 19ef1bfcea8472a88eb6dbe91f8dd830f6856538..c38018bcea4506874da8852ded6ae4566a2283f1 100644 (file)
--- a/test/bdd/api/details/simple.feature
+++ b/test/bdd/api/details/simple.feature
@@ -2,52 +2,54 @@
 Feature: Object details
     Check details page for correctness
 
 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
     Scenario Outline: Details via OSM id

-        When sending details query for <object>
-        Then the result is valid html
+        When sending details query for <type><id>
+        Then the result is valid json
+        And results contain
+            | osm_type | osm_id |
+            | <type>   | <id> |

 
     Examples:
 
     Examples:

-     | object |
-     | 492887 |
-     | N4267356889 |
-     | W230804120 |
-     | R123924 |
-
-    Scenario: Details with keywords
-        When sending details query for W78099902
-            | keywords |
-            | 1 |
-        Then the result is valid html
-
-    Scenario: JSON Details
-        When sending json details query for W78099902
-        Then the result is valid json
-        And result has not attributes place_search_name_keywords,place_search_address_keywords,address_lines,linked_lines,parentof_lines
+     | type | id |
+     | N    | 5484325405 |
+     | W    | 43327921 |
+     | R    | 123924 |

 
 

-    Scenario: JSON Details with keywords
-        When sending json details query for W78099902
-            | keywords |
-            | 1 |
+     Scenario: Details for interpolation way just return the dependent street
+        When sending details query for W1

         Then the result is valid json
         Then the result is valid json

-        And result has attributes place_search_name_keywords,place_search_address_keywords
+        And results contain
+            | category |
+            | highway |

 
 

-    Scenario: JSON Details with addressdetails
-        When sending json details query for W78099902
-            | addressdetails |
-            | 1 |
+    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
         Then the result is valid json

-        And result has attributes address_lines
+        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 a HTTP 404 is returned
+
+    Examples:
+      | object |
+      | 1 |
+      | R1 |
+      | N300209696:highway |

 
 

-    Scenario: JSON Details with linkedplaces
-        When sending json details query for R123924
-            | linkedplaces |
-            | 1 |
-        Then the result is valid json
-        And result has attributes linked_lines

 
 

-    Scenario: JSON Details with childplaces
-        When sending json details query for W78099902
-            | childplaces |
-            | 1 |
-        Then the result is valid json
-        And result has attributes parentof_lines