Rebase CreateAccreditedSystemDevice

NHSDigital · Nov 28, 2024 · 1c21964 · 1c21964
1 parent 66ccc20
commit 1c21964
Show file tree

Hide file tree

Showing 2 changed files with 18 additions and 18 deletions.
diff --git a/src/api/tests/feature_tests/features/createDeviceAccreditedSystem.success.feature b/src/api/tests/feature_tests/features/createDeviceAccreditedSystem.success.feature
@@ -89,7 +89,7 @@ Feature: Create AS Device - success scenarios
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 983              |
+      | Content-Length | 979              |
     And I note the response field "$.id" as "device_id"
     When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/Device/${ note(device_id) }"
     Then I receive a status code "200" with body
@@ -111,4 +111,4 @@ Feature: Create AS Device - success scenarios
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 1720             |
+      | Content-Length | 1632             |
diff --git a/src/api/tests/feature_tests/features/readDevice.success.feature b/src/api/tests/feature_tests/features/readDevice.success.feature
@@ -221,25 +221,25 @@ Feature: Read Device - success scenarios
     And I note the response field "$.id" as "device_id"
     When I make a "GET" request with "default" headers to "ProductTeam/<product_team_id>/Product/<product_id>/Device/${ note(device_id) }"
     Then I receive a status code "200" with body
-      | path                    | value                          |
-      | id                      | ${ note(device_id) }           |
-      | name                    | Product-AS                     |
-      | status                  | active                         |
-      | product_id              | ${ note(product_id) }          |
-      | product_team_id         | ${ note(product_team_id) }     |
-      | ods_code                | F5H1R                          |
-      | created_on              | << ignore >>                   |
-      | updated_on              | << ignore >>                   |
-      | deleted_on              | << ignore >>                   |
-      | keys                    | []                             |
-      | tags.0.0.0              | ${ note(party_key_tag) }       |
-      | tags.0.0.1              | ${ note(party_key_tag_value) } |
-      | questionnaire_responses | << ignore >>                   |
-      | device_reference_data   | << ignore >>                   |
+      | path                    | value                             |
+      | id                      | ${ note(device_id) }              |
+      | name                    | F5H1R-850000/ - Accredited System |
+      | status                  | active                            |
+      | product_id              | ${ note(product_id) }             |
+      | product_team_id         | ${ note(product_team_id) }        |
+      | ods_code                | F5H1R                             |
+      | created_on              | << ignore >>                      |
+      | updated_on              | << ignore >>                      |
+      | deleted_on              | << ignore >>                      |
+      | keys                    | []                                |
+      | tags.0.0.0              | ${ note(party_key_tag) }          |
+      | tags.0.0.1              | ${ note(party_key_tag_value) }    |
+      | questionnaire_responses | << ignore >>                      |
+      | device_reference_data   | << ignore >>                      |
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 1609             |
+      | Content-Length | 1632             |
 
     Examples:
       | product_team_id            | product_id            |