[release/2024-10-16] fix-forward: update read device ref data tests

Author: jaklinger

src/api/tests/feature_tests/features/readDeviceReferenceData.failure.feature

@@ -55,3 +55,27 @@ Feature: Read Device Reference Data - failure scenarios
       | name           | value            |
       | Content-Type   | application/json |
       | Content-Length | 140              |
+
+  Scenario: Read an unknown DeviceReferenceData
+    Given I have already made a "POST" request with "default" headers to "ProductTeam" with body:
+      | path     | value                 |
+      | name     | My Great Product Team |
+      | ods_code | F5H1R                 |
+    And I note the response field "$.id" as "product_team_id"
+    And I have already made a "POST" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product" with body:
+      | path         | value            |
+      | product_name | My Great Product |
+    And I note the response field "$.id" as "product_id"
+    And I have already made a "POST" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData" with body:
+      | path | value                    |
+      | name | My Device Reference Data |
+    And I note the response field "$.id" as "device_reference_data_id"
+    When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/not-a-device-reference-data"
+    Then I receive a status code "404" with body
+      | path             | value                                                                                                                             |
+      | errors.0.code    | RESOURCE_NOT_FOUND                                                                                                                |
+      | errors.0.message | Could not find DeviceReferenceData for key ('${ note(product_team_id) }', '${ note(product_id) }', 'not-a-device-reference-data') |
+    And the response headers contain:
+      | name           | value            |
+      | Content-Type   | application/json |
+      | Content-Length | 192              |