Skip to content

Commit f71d69b

Browse files
committed
[release/2024-10-29] fix-forward: update feature tests
1 parent 49705d3 commit f71d69b

File tree

3 files changed

+10
-9
lines changed

3 files changed

+10
-9
lines changed

src/api/createDeviceReferenceDataMessageSet/src/v1/steps.py

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,8 @@ def require_no_existing_message_sets_device_reference_data(
5959
)
6060
if len(results) > 0:
6161
raise AlreadyExistsError(
62-
"Message Sets Device Reference Data already exists for this Product"
62+
"This product already has a 'Message Set' DeviceReferenceData. "
63+
"Please update, or delete and recreate if you wish to make changes."
6364
)
6465

6566

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
Feature: Create Device Reference Data - success scenarios
2-
These scenarios demonstrate successful Device Reference Data creation
1+
Feature: Create "Message Set" Device Reference Data - failure scenarios
2+
These scenarios demonstrate failure to create "Message Set" Device Reference Data
33

44
Background:
55
Given "default" request headers:
@@ -115,13 +115,13 @@ Feature: Create Device Reference Data - success scenarios
115115
And I have already made a "POST" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/MhsMessageSet"
116116
When I make a "POST" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/MhsMessageSet"
117117
Then I receive a status code "400" with body
118-
| path | value |
119-
| errors.0.code | VALIDATION_ERROR |
120-
| errors.0.message | Message Sets Device Reference Data already exists for this Product |
118+
| path | value |
119+
| errors.0.code | VALIDATION_ERROR |
120+
| errors.0.message | This product already has a 'Message Set' DeviceReferenceData. Please update, or delete and recreate if you wish to make changes. |
121121
And the response headers contain:
122122
| name | value |
123123
| Content-Type | application/json |
124-
| Content-Length | 123 |
124+
| Content-Length | 185 |
125125

126126
Scenario: Fail to create an "MHS Message Set" Device Reference Data in non-EPR product
127127
Given I have already made a "POST" request with "default" headers to "ProductTeam" with body:

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
Feature: Create Device Reference Data - success scenarios
2-
These scenarios demonstrate successful Device Reference Data creation
1+
Feature: Create "Message Set" Device Reference Data - success scenarios
2+
These scenarios demonstrate successful "Message Set" Device Reference Data creation
33

44
Background:
55
Given "default" request headers:

0 commit comments

Comments
 (0)