Skip to content

Commit

Permalink
feature/PI-581-create_mhs_device_with_drd Fix tests
Browse files Browse the repository at this point in the history
  • Loading branch information
@megan-bower4
megan-bower4 committed Nov 18, 2024
1 parent 93341ee commit 21f4e8b
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 9 deletions.
8 changes: 4 additions & 4 deletions ...ts/feature_tests/features/createDeviceReferenceDataAdditionalInteractions.failure.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -88,13 +88,13 @@ Feature: Create "Additional Interactions" Device Reference Data - failure scenar
| path | value |
| questionnaire_responses.bad_questionnaire_name.0.some_value | 123 |
Then I receive a status code "400" with body
| path | value |
| errors.0.code | VALIDATION_ERROR |
| errors.0.message | CreateDeviceReferenceAdditionalInteractionsDataParams.questionnaire_responses.__key__: unexpected value; permitted: 'spine_as_additional_interactions' |
| path | value |
| errors.0.code | VALIDATION_ERROR |
| errors.0.message | CreateDeviceReferenceAdditionalInteractionsDataParams.questionnaire_responses.__key__: unexpected value; permitted: <QuestionnaireInstance.SPINE_AS_ADDITIONAL_INTERACTIONS: 'spine_as_additional_interactions'> |
And the response headers contain:
| name | value |
| Content-Type | application/json |
| Content-Length | 207 |
| Content-Length | 265 |

Scenario: Fail to create a second "AS Additional Interactions" Device Reference Data in the same EPR Product
Given I have already made a "POST" request with "default" headers to "ProductTeam" with body:
Expand Down
10 changes: 5 additions & 5 deletions src/api/tests/feature_tests/features/createDeviceReferenceDataMessageSet.failure.feature
View file
Original file line number Diff line number Diff line change
Expand Up @@ -93,13 +93,13 @@ Feature: Create "Message Set" Device Reference Data - failure scenarios
| path | value |
| questionnaire_responses.bad_questionnaire_name.0.some_value | 123 |
Then I receive a status code "400" with body
| path | value |
| errors.0.code | VALIDATION_ERROR |
| errors.0.message | CreateDeviceReferenceMessageSetsDataParams.questionnaire_responses.__key__: unexpected value; permitted: 'spine_mhs_message_sets' |
| path | value |
| errors.0.code | VALIDATION_ERROR |
| errors.0.message | CreateDeviceReferenceMessageSetsDataParams.questionnaire_responses.__key__: unexpected value; permitted: <QuestionnaireInstance.SPINE_MHS_MESSAGE_SETS: 'spine_mhs_message_sets'> |
And the response headers contain:
| name | value |
| Content-Type | application/json |
| Content-Length | 186 |
| Content-Length | 234 |

Scenario: Fail to create a second "MHS Message Set" Device Reference Data in the same EPR Product
Given I have already made a "POST" request with "default" headers to "ProductTeam" with body:
Expand Down Expand Up @@ -137,7 +137,7 @@ Feature: Create "Message Set" Device Reference Data - failure scenarios
Then I receive a status code "400" with body
| path | value |
| errors.0.code | VALIDATION_ERROR |
| errors.0.message | Not an EPR Product: Cannot create MHS device for product without exactly one Party Key |
| errors.0.message | Not an EPR Product: Cannot create MHS Device for product without exactly one Party Key |
And the response headers contain:
| name | value |
| Content-Type | application/json |
Expand Down

0 comments on commit 21f4e8b

Please sign in to comment.