Skip to content

Commit a8f08e2

Browse files
megan-bower4megan-bower4
committed
Merge branch 'feature/PI-643-add_status_to_drd' into release/2024-11-25
2 parents 4689d33 + 74083af commit a8f08e2

File tree

6 files changed

+37
-16
lines changed

6 files changed

+37
-16
lines changed

‎src/api/tests/feature_tests/features/createDeviceReferenceData.success.feature‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ Feature: Create Device Reference Data - success scenarios
2626
| path | value |
2727
| id | << ignore >> |
2828
| name | My Device Reference Data |
29+
| status | active |
2930
| product_id | ${ note(product_id) } |
3031
| product_team_id | ${ note(product_team_id) } |
3132
| ods_code | F5H1R |
@@ -36,13 +37,14 @@ Feature: Create Device Reference Data - success scenarios
3637
And the response headers contain:
3738
| name | value |
3839
| Content-Type | application/json |
39-
| Content-Length | 316 |
40+
| Content-Length | 336 |
4041
And I note the response field "$.id" as "device_reference_data_id"
4142
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/${ note(device_reference_data_id) }"
4243
Then I receive a status code "200" with body
4344
| path | value |
4445
| id | ${ note(device_reference_data_id) } |
4546
| name | My Device Reference Data |
47+
| status | active |
4648
| product_id | ${ note(product_id) } |
4749
| product_team_id | ${ note(product_team_id) } |
4850
| ods_code | F5H1R |
@@ -53,7 +55,7 @@ Feature: Create Device Reference Data - success scenarios
5355
And the response headers contain:
5456
| name | value |
5557
| Content-Type | application/json |
56-
| Content-Length | 316 |
58+
| Content-Length | 336 |
5759

5860
Examples:
5961
| product_team_id |
@@ -80,6 +82,7 @@ Feature: Create Device Reference Data - success scenarios
8082
| path | value |
8183
| id | << ignore >> |
8284
| name | My Device Reference Data |
85+
| status | active |
8386
| product_id | ${ note(product_id) } |
8487
| product_team_id | ${ note(product_team_id) } |
8588
| ods_code | F5H1R |
@@ -90,13 +93,14 @@ Feature: Create Device Reference Data - success scenarios
9093
And the response headers contain:
9194
| name | value |
9295
| Content-Type | application/json |
93-
| Content-Length | 316 |
96+
| Content-Length | 336 |
9497
And I note the response field "$.id" as "device_reference_data_id"
9598
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/${ note(device_reference_data_id) }"
9699
Then I receive a status code "200" with body
97100
| path | value |
98101
| id | ${ note(device_reference_data_id) } |
99102
| name | My Device Reference Data |
103+
| status | active |
100104
| product_id | ${ note(product_id) } |
101105
| product_team_id | ${ note(product_team_id) } |
102106
| ods_code | F5H1R |
@@ -107,7 +111,7 @@ Feature: Create Device Reference Data - success scenarios
107111
And the response headers contain:
108112
| name | value |
109113
| Content-Type | application/json |
110-
| Content-Length | 316 |
114+
| Content-Length | 336 |
111115

112116
Examples:
113117
| product_team_id | product_id |

‎src/api/tests/feature_tests/features/createDeviceReferenceDataAdditionalInteractions.success.feature‎

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ Feature: Create "Additional Interactions" Device Reference Data - success scenar
2525
| path | value |
2626
| id | << ignore >> |
2727
| name | F5H1R-850000 - AS Additional Interactions |
28+
| status | active |
2829
| product_id | ${ note(product_id) } |
2930
| product_team_id | ${ note(product_team_id) } |
3031
| ods_code | F5H1R |
@@ -35,13 +36,14 @@ Feature: Create "Additional Interactions" Device Reference Data - success scenar
3536
And the response headers contain:
3637
| name | value |
3738
| Content-Type | application/json |
38-
| Content-Length | 333 |
39+
| Content-Length | 353 |
3940
And I note the response field "$.id" as "device_reference_data_id"
4041
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/${ note(device_reference_data_id) }"
4142
Then I receive a status code "200" with body
4243
| path | value |
4344
| id | ${ note(device_reference_data_id) } |
4445
| name | F5H1R-850000 - AS Additional Interactions |
46+
| status | active |
4547
| product_id | ${ note(product_id) } |
4648
| product_team_id | ${ note(product_team_id) } |
4749
| ods_code | F5H1R |
@@ -52,7 +54,7 @@ Feature: Create "Additional Interactions" Device Reference Data - success scenar
5254
And the response headers contain:
5355
| name | value |
5456
| Content-Type | application/json |
55-
| Content-Length | 333 |
57+
| Content-Length | 353 |
5658

5759
Examples:
5860
| product_team_id | product_id |
@@ -82,6 +84,7 @@ Feature: Create "Additional Interactions" Device Reference Data - success scenar
8284
| path | value |
8385
| id | << ignore >> |
8486
| name | F5H1R-850000 - AS Additional Interactions |
87+
| status | active |
8588
| product_id | ${ note(product_id) } |
8689
| product_team_id | ${ note(product_team_id) } |
8790
| ods_code | F5H1R |
@@ -101,13 +104,14 @@ Feature: Create "Additional Interactions" Device Reference Data - success scenar
101104
And the response headers contain:
102105
| name | value |
103106
| Content-Type | application/json |
104-
| Content-Length | 938 |
107+
| Content-Length | 958 |
105108
And I note the response field "$.id" as "device_reference_data_id"
106109
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/${ note(device_reference_data_id) }"
107110
Then I receive a status code "200" with body
108111
| path | value |
109112
| id | ${ note(device_reference_data_id) } |
110113
| name | F5H1R-850000 - AS Additional Interactions |
114+
| status | active |
111115
| product_id | ${ note(product_id) } |
112116
| product_team_id | ${ note(product_team_id) } |
113117
| ods_code | F5H1R |
@@ -127,7 +131,7 @@ Feature: Create "Additional Interactions" Device Reference Data - success scenar
127131
And the response headers contain:
128132
| name | value |
129133
| Content-Type | application/json |
130-
| Content-Length | 938 |
134+
| Content-Length | 958 |
131135

132136
Examples:
133137
| product_team_id | product_id |

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

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ Feature: Create "Message Set" Device Reference Data - success scenarios
2525
| path | value |
2626
| id | << ignore >> |
2727
| name | F5H1R-850000 - MHS Message Set |
28+
| status | active |
2829
| product_id | ${ note(product_id) } |
2930
| product_team_id | ${ note(product_team_id) } |
3031
| ods_code | F5H1R |
@@ -35,13 +36,14 @@ Feature: Create "Message Set" Device Reference Data - success scenarios
3536
And the response headers contain:
3637
| name | value |
3738
| Content-Type | application/json |
38-
| Content-Length | 322 |
39+
| Content-Length | 342 |
3940
And I note the response field "$.id" as "device_reference_data_id"
4041
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/${ note(device_reference_data_id) }"
4142
Then I receive a status code "200" with body
4243
| path | value |
4344
| id | ${ note(device_reference_data_id) } |
4445
| name | F5H1R-850000 - MHS Message Set |
46+
| status | active |
4547
| product_id | ${ note(product_id) } |
4648
| product_team_id | ${ note(product_team_id) } |
4749
| ods_code | F5H1R |
@@ -52,7 +54,7 @@ Feature: Create "Message Set" Device Reference Data - success scenarios
5254
And the response headers contain:
5355
| name | value |
5456
| Content-Type | application/json |
55-
| Content-Length | 322 |
57+
| Content-Length | 342 |
5658

5759
Examples:
5860
| product_team_id | product_id |
@@ -87,6 +89,7 @@ Feature: Create "Message Set" Device Reference Data - success scenarios
8789
| path | value |
8890
| id | << ignore >> |
8991
| name | F5H1R-850000 - MHS Message Set |
92+
| status | active |
9093
| product_id | ${ note(product_id) } |
9194
| product_team_id | ${ note(product_team_id) } |
9295
| ods_code | F5H1R |
@@ -113,13 +116,14 @@ Feature: Create "Message Set" Device Reference Data - success scenarios
113116
And the response headers contain:
114117
| name | value |
115118
| Content-Type | application/json |
116-
| Content-Length | 1199 |
119+
| Content-Length | 1219 |
117120
And I note the response field "$.id" as "device_reference_data_id"
118121
When I make a "GET" request with "default" headers to "ProductTeam/${ note(product_team_id) }/Product/${ note(product_id) }/DeviceReferenceData/${ note(device_reference_data_id) }"
119122
Then I receive a status code "200" with body
120123
| path | value |
121124
| id | ${ note(device_reference_data_id) } |
122125
| name | F5H1R-850000 - MHS Message Set |
126+
| status | active |
123127
| product_id | ${ note(product_id) } |
124128
| product_team_id | ${ note(product_team_id) } |
125129
| ods_code | F5H1R |
@@ -146,4 +150,4 @@ Feature: Create "Message Set" Device Reference Data - success scenarios
146150
And the response headers contain:
147151
| name | value |
148152
| Content-Type | application/json |
149-
| Content-Length | 1199 |
153+
| Content-Length | 1219 |

‎src/api/tests/feature_tests/features/readDeviceReferenceData.success.feature‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ Feature: Read Device Reference Data - success scenarios
2828
| path | value |
2929
| id | ${ note(device_reference_data_id) } |
3030
| name | My Device Reference Data |
31+
| status | active |
3132
| product_id | ${ note(product_id) } |
3233
| product_team_id | ${ note(product_team_id) } |
3334
| ods_code | F5H1R |
@@ -38,7 +39,7 @@ Feature: Read Device Reference Data - success scenarios
3839
And the response headers contain:
3940
| name | value |
4041
| Content-Type | application/json |
41-
| Content-Length | 316 |
42+
| Content-Length | 336 |
4243

4344
Examples:
4445
| product_team_id |
@@ -67,6 +68,7 @@ Feature: Read Device Reference Data - success scenarios
6768
| path | value |
6869
| id | ${ note(device_reference_data_id) } |
6970
| name | My Device Reference Data |
71+
| status | active |
7072
| product_id | ${ note(product_id) } |
7173
| product_team_id | ${ note(product_team_id) } |
7274
| ods_code | F5H1R |
@@ -77,7 +79,7 @@ Feature: Read Device Reference Data - success scenarios
7779
And the response headers contain:
7880
| name | value |
7981
| Content-Type | application/json |
80-
| Content-Length | 316 |
82+
| Content-Length | 336 |
8183

8284
Examples:
8385
| product_team_id | product_id |

‎src/api/tests/feature_tests/features/searchDeviceReferenceData.success.feature‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,7 @@ Feature: Search Device Reference Data - success scenarios
4949
| results.0.product_id | ${ note(product_id) } |
5050
| results.0.product_team_id | ${ note(product_team_id) } |
5151
| results.0.name | My Device Reference Data |
52+
| results.0.status | active |
5253
| results.0.ods_code | F5H1R |
5354
| results.0.created_on | << ignore >> |
5455
| results.0.updated_on | << ignore >> |
@@ -57,7 +58,7 @@ Feature: Search Device Reference Data - success scenarios
5758
And the response headers contain:
5859
| name | value |
5960
| Content-Type | application/json |
60-
| Content-Length | 331 |
61+
| Content-Length | 351 |
6162

6263
Scenario: Successfully search more than one Device Reference Data
6364
Given I have already made a "POST" request with "default" headers to "ProductTeam" with body:
@@ -88,6 +89,7 @@ Feature: Search Device Reference Data - success scenarios
8889
| path | value |
8990
| results.0.id | ${ note(device_reference_data_id_1) } |
9091
| results.0.name | My Device Reference Data 1 |
92+
| results.0.status | active |
9193
| results.0.product_id | ${ note(product_id) } |
9294
| results.0.product_team_id | ${ note(product_team_id) } |
9395
| results.0.ods_code | F5H1R |
@@ -97,6 +99,7 @@ Feature: Search Device Reference Data - success scenarios
9799
| results.0.questionnaire_responses | {} |
98100
| results.1.id | ${ note(device_reference_data_id_2) } |
99101
| results.1.name | My Device Reference Data 2 |
102+
| results.1.status | active |
100103
| results.1.product_id | ${ note(product_id) } |
101104
| results.1.product_team_id | ${ note(product_team_id) } |
102105
| results.1.ods_code | F5H1R |
@@ -106,6 +109,7 @@ Feature: Search Device Reference Data - success scenarios
106109
| results.1.questionnaire_responses | {} |
107110
| results.2.id | ${ note(device_reference_data_id_3) } |
108111
| results.2.name | My Device Reference Data 3 |
112+
| results.2.status | active |
109113
| results.2.product_id | ${ note(product_id) } |
110114
| results.2.product_team_id | ${ note(product_team_id) } |
111115
| results.2.ods_code | F5H1R |
@@ -116,4 +120,4 @@ Feature: Search Device Reference Data - success scenarios
116120
And the response headers contain:
117121
| name | value |
118122
| Content-Type | application/json |
119-
| Content-Length | 973 |
123+
| Content-Length | 1033 |

0 commit comments

Comments
 (0)