Merge branch '13-test-storage-extension-functions' into 'main'

Update negative tests for test storage extension

See merge request !58

src/main/resources/REST/json/Policy.json

@@ -32,14 +32,16 @@
   "storageKey": {
     "key": "dataEntry1"
   },
-  "missingKey": {
-    "data": {
-      "record1": "value for record 1",
-      "record2": true,
-      "record3": 3
-    }
+  "emptyKey": {
+    "key": "",
+    "data": "data for empty key"
   },
-  "missingData": {
-    "key": "dataEntry1"
+  "numberAsKey": {
+    "key": 1,
+    "data": "data for numeric key"
+  },
+  "emptyData": {
+    "key": "dataEntry1",
+    "data": ""
   }
 }
\ No newline at end of file

src/test/resources/features/tsa/policy/policy/{respository}/{group}/{name}/{version}/evaluation/POST.feature

@@ -107,32 +107,23 @@ Feature: API -TSA - Policy - {repository}/{group}/{name}/{version}/evaluation PO
     And the response is valid according to the {Policy_EvaluateDID_negative_schema.json} REST schema
     And the field {data.didResolutionMetadata.error} has the value {notFound}
 
-  @negative @phase2 @IDM.TSA.E1.00014 @wip @https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/issues/54
-  Scenario:  TSA - Work with database storage - Set data with empty body - Negative
-    When I load the REST request {Policy.json} with profile {empty}
+  @negative @phase2 @IDM.TSA.E1.00014
+  Scenario:  TSA - Work with database storage - Set data with empty key - Negative
+    When I load the REST request {Policy.json} with profile {emptyKey}
     And I execute the Policy group {example} name {storageSet} version {1.0} via TSA Policy API
-    Then the status code should be {400}
+    Then the status code should be {500}
+    And the field {message} has the value {error evaluating rego query}
 
-  @negative @phase2 @IDM.TSA.E1.00014 @wip @wip @https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/issues/54
-  Scenario:  TSA - Work with database storage - Set data with missing key - Negative
-    When I load the REST request {Policy.json} with profile {missingKey}
+  @negative @phase2 @IDM.TSA.E1.00014
+  Scenario:  TSA - Work with database storage - Set data with incorrect key - Negative
+    When I load the REST request {Policy.json} with profile {numberAsKey}
     And I execute the Policy group {example} name {storageSet} version {1.0} via TSA Policy API
-    Then the status code should be {400}
+    Then the status code should be {500}
+    And the field {message} has the value {error evaluating rego query}
 
-  @negative @phase2 @IDM.TSA.E1.00014 @wip @wip @https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/issues/54
-  Scenario:  TSA - Work with database storage - Set data with missing data field - Negative
-    When I load the REST request {Policy.json} with profile {missingData}
+  @negative @phase2 @IDM.TSA.E1.00014
+  Scenario:  TSA - Work with database storage - Set data with empty data field - Negative
+    When I load the REST request {Policy.json} with profile {emptyData}
     And I execute the Policy group {example} name {storageSet} version {1.0} via TSA Policy API
-    Then the status code should be {400}
-
-  @negative @phase2 @IDM.TSA.E1.00014 @wip @wip @https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/issues/54
-  Scenario:  TSA - Work with database storage - Get data with empty body - Negative
-    When I load the REST request {Policy.json} with profile {empty}
-    And I execute the Policy group {example} name {storageGet} version {1.0} via TSA Policy API
-    Then the status code should be {400}
-
-  @negative @phase2 @IDM.TSA.E1.00014 @wip @wip @https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/issues/54
-  Scenario:  TSA - Work with database storage - Delete data with empty body - Negative
-    When I load the REST request {Policy.json} with profile {empty}
-    And I execute the Policy group {example} name {storageDelete} version {1.0} via TSA Policy API
-    Then the status code should be {400}
+    Then the status code should be {500}
+    And the field {message} has the value {error evaluating rego query}