add new format 'raw' for CLI commands

[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 6bab1bc790ba649f7e72e50d0f04b28a0500001e..5e0bacc5a945b2909691072885b194e1fd032136 100644 (file)
--- a/test/bdd/api/details/simple.feature
+++ b/test/bdd/api/details/simple.feature
@@ -1,43 +1,82 @@
+@SQLITE

 @APIDB
 Feature: Object details
     Check details page for correctness
 
     Scenario Outline: Details via OSM id
 @APIDB
 Feature: Object details
     Check details page for correctness
 
     Scenario Outline: Details via OSM id

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

 
     Examples:
 
     Examples:

-     | format | object |
-     | html | 492887 |
-     | json | 492887 |
-     | html | N4267356889 |
-     | json | N4267356889 |
-     | html | W230804120 |
-     | json | W230804120 |
-     | html | R123924 |
-     | json | R123924 |
+     | type | id |
+     | N    | 5484325405 |
+     | W    | 43327921 |
+     | R    | 123924 |
+
+
+    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
 
     Scenario Outline: Details via unknown OSM id

-        When sending <format> details query for <object>
-        Then a HTTP 400 is returned
+        When sending details query for <object>
+        Then a HTTP 404 is returned

 
     Examples:
 
     Examples:

-      | format | object |
-      | html | 1 |
-      | json | 1 |
-      | html | R1 |
-      | json | R1 |
-
-    Scenario: Details with keywords
-        When sending details query for W78099902
-            | keywords |
-            | 1 |
-        Then the result is valid html
+      | object |
+      | 1 |
+      | R1 |
+      | N300209696:highway |
+
+
+     Scenario: Details for interpolation way return the interpolation
+        When sending details query for W1
+        Then the result is valid json
+        And results contain
+            | category | type   | osm_type | osm_id | admin_level |
+            | place    | houses | W        | 1      | 15          |
+
+
+     @Fail
+     Scenario: Details for interpolation way return the interpolation
+        When sending details query for 112871
+        Then the result is valid json
+        And results contain
+            | category | type   | admin_level |
+            | place    | houses | 15          |
+        And result has not attributes osm_type,osm_id
+
+
+     @Fail
+     Scenario: Details for interpolation way return the interpolation
+        When sending details query for 112820
+        Then the result is valid json
+        And results contain
+            | category | type     | admin_level |
+            | place    | postcode | 15          |
+        And result has not attributes osm_type,osm_id
+

 
 

-    # ticket #1343
-    Scenario: Details of a country with keywords
-        When sending details query for R287072
-            | keywords |
-            | 1 |
+    Scenario Outline: Details debug output returns no errors
+        When sending debug details query for <feature>

         Then the result is valid html
 
         Then the result is valid html
 

+        Examples:
+          | feature     |
+          | N5484325405 |
+          | W1          |
+          | 112820      |
+          | 112871      |