feat: added support in env setup glue for fetching device details dynamically

cypress/support/constants/constants.js

@@ -88,6 +88,7 @@ module.exports = {
   DEVICE_FIRMWARE: 'Device Firmware',
   DEVICE_HDCP: 'device.hdcp',
   DEVICE_HDR: 'device.hdr',
+  DEVICE_ID: 'device.id',
   DEVICE_IP: 'deviceIp',
   DEVICE_MAC: 'deviceMac',
   DEVICE_MAC_UNAVAILABLE: 'Device MAC unavailable',
@@ -99,6 +100,7 @@ module.exports = {
   DEVICE_PLATFORM: 'device.platform',
   DEVICE_VIDEORESOLUTION: 'device.videoResolution',
   DISCOVERY_LAUNCH: 'discovery.launch',
+  DYNAMIC_DEVICE_DETAILS_MODULES: ['Device'],
   EMAIL: 'email',
   ENV_PLATFORM_SDK_VERSION: 'platformSdkVersion',
   ENV_PLATFORM: 'platform',

cypress/support/step_definitions/testSetup.js

@@ -55,6 +55,23 @@ Given('the environment has been set up for {string} tests', (test) => {
     if (Cypress.env(CONSTANTS.TEST_TYPE).includes('rpc-Only')) {
       Cypress.env(CONSTANTS.IS_RPC_ONLY, true);
     }
+    // fetch device details dynamically
+    if (Cypress.env(CONSTANTS.FETCH_DEVICE_DETAILS_DYNAMICALLY_FLAG)) {
+      if (CONSTANTS.DYNAMIC_DEVICE_DETAILS_MODULES.includes(Cypress.env(CONSTANTS.TEST_TYPE))) {
+        cy.getDeviceData(CONSTANTS.DEVICE_ID, {}, CONSTANTS.ACTION_CORE.toLowerCase()).then(
+          (response) => {
+            if (response) {
+              const method = CONSTANTS.REQUEST_OVERRIDE_CALLS.FETCHDEVICEDETAILS;
+              const requestMap = {
+                method: method,
+                params: response,
+              };
+              cy.sendMessagetoPlatforms(requestMap);
+            }
+          }
+        );
+      }
+    }
   }
 });
 

cypress/support/step_definitions/validations.js

@@ -64,6 +64,17 @@ Given(
           const expectingError = item.expectingError;
           const isNullCase = item.isNullCase || false;
 
+          for (let i = 0; i < contentObject.data.length; i++) {
+            if (contentObject.data[i].validations[0].mode == CONSTANTS.DEVICE_CONTENT_VALIDATION) {
+              const type = contentObject.data[i].validations[0].type;
+              if (Cypress.env(CONSTANTS.DEVICE_DATA).hasOwnProperty(type)) {
+                contentObject.data[i].validations[0].type = Cypress.env(CONSTANTS.DEVICE_DATA)[
+                  type
+                ];
+              }
+            }
+          }
+
           // If the app ID is not passed from the feature, the default app ID will be retrieved.
           appId = !appId
             ? UTILS.getEnvVariable(CONSTANTS.THIRD_PARTY_APP_ID)

cypress/support/step_definitions/validations.md

@@ -412,3 +412,7 @@ While validating, if a key is present in both fcs-validation jsons (eg: cypress/
             }
         ]
 }
+
+# Device Content Validation
+
+For deviceContentValidation, the source of truth is fetched from an external API, which is dependent on the configuration module or platform on which we are testing. For the validation part, an override module called "fetchDeviceDetails" is expected to be in configModule to fetch the device details with the corresponding APIs mentioned for each config. DeviceId is passed from fcs to this override module as the only parameter, which is later used for fetching device details in the "configHelper" module.