diff --git a/src/api/tests/feature_tests/features/readDeviceReferenceData.success.feature b/src/api/tests/feature_tests/features/readDeviceReferenceData.success.feature
index 96a5f0d5..80fc173c 100644
--- a/src/api/tests/feature_tests/features/readDeviceReferenceData.success.feature
+++ b/src/api/tests/feature_tests/features/readDeviceReferenceData.success.feature
@@ -28,6 +28,7 @@ Feature: Read Device Reference Data - success scenarios
       | path                    | value                               |
       | id                      | ${ note(device_reference_data_id) } |
       | name                    | My Device Reference Data            |
+      | status                  | active                              |
       | product_id              | ${ note(product_id) }               |
       | product_team_id         | ${ note(product_team_id) }          |
       | ods_code                | F5H1R                               |
@@ -38,7 +39,7 @@ Feature: Read Device Reference Data - success scenarios
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 316              |
+      | Content-Length | 336              |
 
     Examples:
       | product_team_id            |
@@ -67,6 +68,7 @@ Feature: Read Device Reference Data - success scenarios
       | path                    | value                               |
       | id                      | ${ note(device_reference_data_id) } |
       | name                    | My Device Reference Data            |
+      | status                  | active                              |
       | product_id              | ${ note(product_id) }               |
       | product_team_id         | ${ note(product_team_id) }          |
       | ods_code                | F5H1R                               |
@@ -77,7 +79,7 @@ Feature: Read Device Reference Data - success scenarios
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 316              |
+      | Content-Length | 336              |
 
     Examples:
       | product_team_id            | product_id            |
diff --git a/src/api/tests/feature_tests/features/searchDeviceReferenceData.success.feature b/src/api/tests/feature_tests/features/searchDeviceReferenceData.success.feature
index 5a78092e..a978474a 100644
--- a/src/api/tests/feature_tests/features/searchDeviceReferenceData.success.feature
+++ b/src/api/tests/feature_tests/features/searchDeviceReferenceData.success.feature
@@ -49,6 +49,7 @@ Feature: Search Device Reference Data - success scenarios
       | results.0.product_id              | ${ note(product_id) }               |
       | results.0.product_team_id         | ${ note(product_team_id) }          |
       | results.0.name                    | My Device Reference Data            |
+      | results.0.status                  | active                              |
       | results.0.ods_code                | F5H1R                               |
       | results.0.created_on              | << ignore >>                        |
       | results.0.updated_on              | << ignore >>                        |
@@ -57,7 +58,7 @@ Feature: Search Device Reference Data - success scenarios
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 331              |
+      | Content-Length | 351              |
 
   Scenario: Successfully search more than one Device Reference Data
     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
       | path                              | value                                 |
       | results.0.id                      | ${ note(device_reference_data_id_1) } |
       | results.0.name                    | My Device Reference Data 1            |
+      | results.0.status                  | active                                |
       | results.0.product_id              | ${ note(product_id) }                 |
       | results.0.product_team_id         | ${ note(product_team_id) }            |
       | results.0.ods_code                | F5H1R                                 |
@@ -97,6 +99,7 @@ Feature: Search Device Reference Data - success scenarios
       | results.0.questionnaire_responses | {}                                    |
       | results.1.id                      | ${ note(device_reference_data_id_2) } |
       | results.1.name                    | My Device Reference Data 2            |
+      | results.1.status                  | active                                |
       | results.1.product_id              | ${ note(product_id) }                 |
       | results.1.product_team_id         | ${ note(product_team_id) }            |
       | results.1.ods_code                | F5H1R                                 |
@@ -106,6 +109,7 @@ Feature: Search Device Reference Data - success scenarios
       | results.1.questionnaire_responses | {}                                    |
       | results.2.id                      | ${ note(device_reference_data_id_3) } |
       | results.2.name                    | My Device Reference Data 3            |
+      | results.2.status                  | active                                |
       | results.2.product_id              | ${ note(product_id) }                 |
       | results.2.product_team_id         | ${ note(product_team_id) }            |
       | results.2.ods_code                | F5H1R                                 |
@@ -116,4 +120,4 @@ Feature: Search Device Reference Data - success scenarios
     And the response headers contain:
       | name           | value            |
       | Content-Type   | application/json |
-      | Content-Length | 973              |
+      | Content-Length | 1033             |