Skip to content

Commit a68d12e

Browse files
committed
Update feature tests after rebase
1 parent 62db27d commit a68d12e

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

src/api/tests/feature_tests/features/createDeviceAccreditedSystem.success.feature

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Feature: Create AS Device - success scenarios
1818
| name | My Great Product |
1919
And I note the response field "$.id" as "product_id"
2020
And I note the response field "$.keys.0.key_type" as "party_key_tag"
21-
And I note the response field "$.keys.0.key_value" as "party_key_value"
21+
And I note the response field "$.keys.0.key_value" as "party_key_tag_value"
2222
And I have already made a "POST" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/MhsMessageSet" with body:
2323
| path | value |
2424
| questionnaire_responses.spine_mhs_message_sets.0.Interaction ID | urn:nhs:names:services:ers:READ_PRACTITIONER_ROLE_R4_V001 |
@@ -30,6 +30,7 @@ Feature: Create AS Device - success scenarios
3030
| questionnaire_responses.spine_mhs.0.Address | http://example.com |
3131
| questionnaire_responses.spine_mhs.0.Unique Identifier | 123456 |
3232
| questionnaire_responses.spine_mhs.0.Managing Organization | Example Org |
33+
| questionnaire_responses.spine_mhs.0.MHS Manufacturer Organisation | AAA |
3334
| questionnaire_responses.spine_mhs.0.MHS Party key | party-key-001 |
3435
| questionnaire_responses.spine_mhs.0.MHS CPA ID | cpa-id-001 |
3536
| questionnaire_responses.spine_mhs.0.Approver URP | approver-123 |
@@ -79,22 +80,22 @@ Feature: Create AS Device - success scenarios
7980
And I note the response field "$.id" as "device_id"
8081
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/Device/${ note(device_id) }"
8182
Then I receive a status code "200" with body
82-
| path | value |
83-
| id | ${ note(device_id) } |
84-
| name | Product-AS |
85-
| status | active |
86-
| product_id | ${ note(product_id) } |
87-
| product_team_id | ${ note(product_team_id) } |
88-
| ods_code | F5H1R |
89-
| created_on | << ignore >> |
90-
| updated_on | << ignore >> |
91-
| deleted_on | << ignore >> |
92-
| keys | [] |
93-
| tags.0.0.0 | ${ note(party_key_tag) } |
94-
| tags.0.0.1 | ${ note(party_key_value) } |
95-
| questionnaire_responses | << ignore >> |
96-
| device_reference_data | << ignore >> |
83+
| path | value |
84+
| id | ${ note(device_id) } |
85+
| name | Product-AS |
86+
| status | active |
87+
| product_id | ${ note(product_id) } |
88+
| product_team_id | ${ note(product_team_id) } |
89+
| ods_code | F5H1R |
90+
| created_on | << ignore >> |
91+
| updated_on | << ignore >> |
92+
| deleted_on | << ignore >> |
93+
| keys | [] |
94+
| tags.0.0.0 | ${ note(party_key_tag) } |
95+
| tags.0.0.1 | ${ note(party_key_tag_value) } |
96+
| questionnaire_responses | << ignore >> |
97+
| device_reference_data | << ignore >> |
9798
And the response headers contain:
9899
| name | value |
99100
| Content-Type | application/json |
100-
| Content-Length | 1005 |
101+
| Content-Length | 1697 |

0 commit comments

Comments
 (0)