feat: Modify all setter/getter test cases to JSV2 format (#157)

rdkcentral · Aug 29, 2024 · bd6fa9b · bd6fa9b
1 parent ed212a7
commit bd6fa9b
Show file tree

Hide file tree

Showing 31 changed files with 798 additions and 360 deletions.
diff --git a/cypress/TestCases/FireboltCertification/Accessibility.feature b/cypress/TestCases/FireboltCertification/Accessibility.feature
@@ -8,12 +8,12 @@ Feature: Accessibility
     @sdk @transport
     Scenario Outline: Accessibility.closedCaptionsSettings - Positive Scenario: <Scenario>
         Given we test the 'ACCESSIBILITY_CLOSEDCAPTIONS_SETTINGS' getters and setters '<Method>' to '<Value>'
-        When '3rd party app' registers for the 'Firebolt' event
+        And '3rd party app' registers for the 'Firebolt' event
+        And '3rd party app' invokes the 'Firebolt' get API
+        When 1st party app invokes the 'Firebolt' API to set value
+        Then 'Firebolt' platform responds to '1st party app' set API
         When '3rd party app' invokes the 'Firebolt' get API
-        Given 1st party app invokes the 'Firebolt' API to set value
-        And 'Firebolt' platform responds to '1st party app' set API
-        When '3rd party app' invokes the 'Firebolt' get API
-        And 'Firebolt' platform responds to '3rd party app' get API
+        Then 'Firebolt' platform responds to '3rd party app' get API
         And 'Firebolt' platform triggers '3rd party app' event
 
         Examples:
@@ -53,9 +53,9 @@ Feature: Accessibility
 
    @sdk @transport
    Scenario Outline: Accessibility.closedCaptionsSettings - Positive Scenario: <Scenario> with 'null' params
-      When '3rd party app' registers for the 'accessibility onClosedCaptionsSettingsChanged' event using the 'Firebolt' API
+      Given '3rd party app' registers for the 'accessibility onClosedCaptionsSettingsChanged' event using the 'Firebolt' API
       And '3rd party app' invokes the 'Firebolt' API to 'get closedCaptions settings'
-      And 1st party app invokes the 'Firebolt' API to '<Key>'
+      When 1st party app invokes the 'Firebolt' API to '<Key>'
       Then 'Firebolt' platform responds to '1st party app' for '<Key>'
       When '3rd party app' invokes the 'Firebolt' API to 'get closedCaptions settings'
       Then 'Firebolt' platform responds with '<Method_Content>'
@@ -79,12 +79,12 @@ Feature: Accessibility
     @sdk @transport
     Scenario Outline: Accessibility.voiceGuidanceSettings - Positive Scenario: <Scenario>
         Given we test the 'ACCESSIBILITY_VOICEGUIDANCE_SETTINGS' getters and setters '<Method>' to '<Value>'
-        When '3rd party app' registers for the 'Firebolt' event
-        When '3rd party app' invokes the 'Firebolt' get API
-        Given 1st party app invokes the 'Firebolt' API to set value
-        And 'Firebolt' platform responds to '1st party app' set API
+        And '3rd party app' registers for the 'Firebolt' event
+        And '3rd party app' invokes the 'Firebolt' get API
+        When 1st party app invokes the 'Firebolt' API to set value
+        Then 'Firebolt' platform responds to '1st party app' set API
         When '3rd party app' invokes the 'Firebolt' get API
-        And 'Firebolt' platform responds to '3rd party app' get API
+        Then 'Firebolt' platform responds to '3rd party app' get API
         And 'Firebolt' platform triggers '3rd party app' event
 
         Examples:
@@ -98,12 +98,12 @@ Feature: Accessibility
     @sdk @transport
     Scenario Outline: Accessibility.audioDescriptionSettings - Positive Scenario: <Scenario>
         Given we test the 'AUDIODESCRIPTIONS_SETTINGS' getters and setters '<Method>' to '<Value>'
-        When '3rd party app' registers for the 'Firebolt' event
+        And '3rd party app' registers for the 'Firebolt' event
+        And '3rd party app' invokes the 'Firebolt' get API
+        When 1st party app invokes the 'Firebolt' API to set value
+        Then 'Firebolt' platform responds to '1st party app' set API
         When '3rd party app' invokes the 'Firebolt' get API
-        Given 1st party app invokes the 'Firebolt' API to set value
-        And 'Firebolt' platform responds to '1st party app' set API
-        When '3rd party app' invokes the 'Firebolt' get API
-        And 'Firebolt' platform responds to '3rd party app' get API
+        Then 'Firebolt' platform responds to '3rd party app' get API
         And 'Firebolt' platform triggers '3rd party app' event
 
         Examples:
@@ -114,11 +114,11 @@ Feature: Accessibility
     @sdk @transport
     Scenario Outline: Accessibility.closedCaptions - Positive Scenario: <Scenario>
         Given we test the 'ACCESSIBILITY_CLOSEDCAPTIONS' getters and setters '<Method>' to '<Value>'
-        When '3rd party app' registers for the 'Firebolt' event
-        Given 1st party app invokes the 'Firebolt' API to set value
-        And 'Firebolt' platform responds to '1st party app' set API
+        And '3rd party app' registers for the 'Firebolt' event
+        When 1st party app invokes the 'Firebolt' API to set value
+        Then 'Firebolt' platform responds to '1st party app' set API
         When '3rd party app' invokes the 'Firebolt' get API
-        And 'Firebolt' platform responds to '3rd party app' get API
+        Then 'Firebolt' platform responds to '3rd party app' get API
         And 'Firebolt' platform triggers '3rd party app' event
 
         Examples:
@@ -140,21 +140,21 @@ Feature: Accessibility
 
    @sdk @transport @requiresPlatformImplementation
    Scenario: Accessibility.onClosedCaptionsSettingsChanged event - Positive Scenario: Clear listeners
-      When '3rd party app' registers for the 'accessibility onClosedCaptionsSettingsChanged' event using the 'Firebolt' API
-      And 1st party stops listening to the event 'accessibility onClosedCaptionsSettingsChanged event'
-      And 1st party app invokes the 'Firebolt' API to 'disable closedCaptions'
+      Given '3rd party app' registers for the 'accessibility onClosedCaptionsSettingsChanged' event using the 'Firebolt' API
+      And 3rd party stops listening to the event 'accessibility onClosedCaptionsSettingsChanged event'
+      When 1st party app invokes the 'Firebolt' API to 'disable closedCaptions'
       Then 'Firebolt' platform responds to '1st party app' for 'disable closedCaptions'
       And 'Firebolt' platform does not trigger event for 'onclosedCaptionsSettingsChanged'
 
     @sdk @transport
     Scenario Outline: Accessibility.voiceGuidance - Positive Scenario: <Scenario>
         Given we test the 'ACCESSIBILITY_VOICEGUIDANCE' getters and setters '<Method>' to '<Value>'
-        When '3rd party app' registers for the 'Firebolt' event
-        When '3rd party app' invokes the 'Firebolt' get API
-        Given 1st party app invokes the 'Firebolt' API to set value
-        And 'Firebolt' platform responds to '1st party app' set API
+        And '3rd party app' registers for the 'Firebolt' event
+        And '3rd party app' invokes the 'Firebolt' get API
+        When 1st party app invokes the 'Firebolt' API to set value
+        Then 'Firebolt' platform responds to '1st party app' set API
         When '3rd party app' invokes the 'Firebolt' get API
-        And 'Firebolt' platform responds to '3rd party app' get API
+        Then 'Firebolt' platform responds to '3rd party app' get API
         And 'Firebolt' platform triggers '3rd party app' event
 
         Examples:

diff --git a/cypress/TestCases/FireboltCertification/Advertising.feature b/cypress/TestCases/FireboltCertification/Advertising.feature
@@ -7,9 +7,9 @@ Feature: Advertising
 
    @sdk @transport
    Scenario Outline: Advertising.policy - Positive Scenario: <Scenario>
-      When '3rd party app' registers for the 'advertising onPolicyChanged' event using the 'Firebolt' API
+      Given '3rd party app' registers for the 'advertising onPolicyChanged' event using the 'Firebolt' API
       And '3rd party app' invokes the 'Firebolt' API to 'get advertising policy'
-      And 1st party app invokes the 'Firebolt' API to '<API_Key>'
+      When 1st party app invokes the 'Firebolt' API to '<API_Key>'
       Then 'Firebolt' platform responds to '1st party app' for '<API_Key>'
       When '3rd party app' invokes the 'Firebolt' API to 'get advertising policy'
       Then 'Firebolt' platform responds with '<Method_Validation_key>'
@@ -22,25 +22,27 @@ Feature: Advertising
 
    @sdk @transport
    Scenario Outline: Advertising.policy - Positive Scenario: <Scenario>
-      When '3rd party app' registers for the 'advertising onPolicyChanged' event using the 'Firebolt' API
-      And '3rd party app' invokes the 'Firebolt' API to 'get advertising policy'
-      And 1st party app invokes the 'Firebolt' API to '<API_Key>'
-      Then 'Firebolt' platform responds to '1st party app' for '<API_Key>'
-      When '3rd party app' invokes the 'Firebolt' API to 'get advertising policy'
-      Then 'Firebolt' platform responds with '<Method_Validation_key>'
-      And 'Firebolt' platform triggers event '<Event_Validation_key>'
+      Given we test the 'ADVERTISING_SKIPRESTRICTION' getters and setters '<Method>' to '<Value>'
+      And '3rd party app' registers for the 'Firebolt' event
+      And '3rd party app' invokes the 'Firebolt' get API
+      When 1st party app invokes the 'Firebolt' API to set value
+      Then 'Firebolt' platform responds to '1st party app' set API
+      When '3rd party app' invokes the 'Firebolt' get API
+      Then 'Firebolt' platform responds to '3rd party app' get API
+      And 'Firebolt' platform triggers '3rd party app' event
 
       Examples:
-         | Scenario                     | API_Key                             | Method_Validation_key                              | Event_Validation_key                                              |
-         | SkipRestriction adsAll       | set skipRestriction as adsAll       | Advertising policy skipRestriction as adsAll       | onPolicyChanged for advertising skipRestriction with adsAll       |
-         | SkipRestriction none         | set skipRestriction as none         | Advertising policy skipRestriction as none         | onPolicyChanged for advertising skipRestriction with none         |
-         | SkipRestriction adsUnwatched | set skipRestriction as adsUnwatched | Advertising policy skipRestriction as adsUnwatched | onPolicyChanged for advertising skipRestriction with adsUnwatched |
-         | SkipRestriction all          | set skipRestriction as all          | Advertising policy skipRestriction as all          | onPolicyChanged for advertising skipRestriction with all          |
+         | Scenario                     | Method          | Value        |
+         | SkipRestriction adsAll       | skipRestriction | adsAll       |
+         | SkipRestriction none         | skipRestriction | none         |
+         | SkipRestriction adsUnwatched | skipRestriction | adsUnwatched |
+         | SkipRestriction all          | skipRestriction | all          |
 
    @sdk @transport
    Scenario: Advertising.deviceAttributes - Positive Scenario: Get deviceAttributes
-      When '3rd party app' invokes the 'Firebolt' API to 'get deviceAttributes'
-      Then 'Firebolt' platform responds with 'advertising device attributes'
+      Given we test the 'ADVERTISING_DEVICEATTRIBUTES' getters and setters
+      When '3rd party app' invokes the 'Firebolt' get API
+      Then 'Firebolt' platform responds to '3rd party app' get API
 
    @sdk @transport
    Scenario: Advertising.appBundleId - Positive Scenario: Get appBundleId
@@ -51,7 +53,7 @@ Feature: Advertising
    Scenario Outline: Advertising.advertisingId - Positive Scenario: Special Validation <Scenario>
       When '3rd party app' invokes the 'Firebolt' API to 'get advertisingId'
       And '3rd party app' invokes the 'Firebolt' API to 'get initialization parameters'
-      When 1st party app invokes the 'Firebolt' API to '<API_Key>'
+      And 1st party app invokes the 'Firebolt' API to '<API_Key>'
       Then 'Firebolt' platform responds to '1st party app' with '<API_Key>'
       When '3rd party app' invokes the 'Firebolt' API to 'get advertisingId'
       And '3rd party app' invokes the 'Firebolt' API to 'get initialization parameters'
@@ -143,8 +145,8 @@ Feature: Advertising
 
       @sdk @transport @requiresPlatformImplementation
       Scenario: Advertising.onPolicyChanged - Positive Scenario: Clearing event listeners
-            When '3rd party app' registers for the 'advertising onPolicyChanged' event using the 'Firebolt' API
-            And 1st party stops listening to the event 'advertising onPolicyChanged event'
-            And 1st party app invokes the 'Firebolt' API to 'set true for allowAppContentAdTargeting'
+            Given '3rd party app' registers for the 'advertising onPolicyChanged' event using the 'Firebolt' API
+            And 3rd party stops listening to the event 'advertising onPolicyChanged event'
+            When 1st party app invokes the 'Firebolt' API to 'set true for allowAppContentAdTargeting'
             Then 'Firebolt' platform responds to '1st party app' with 'set true for allowAppContentAdTargeting'
             And 'Firebolt' platform does not trigger event for 'onAdvertisingPolicyChanged'
diff --git a/cypress/TestCases/FireboltCertification/Capabilities.feature b/cypress/TestCases/FireboltCertification/Capabilities.feature
@@ -222,7 +222,7 @@ Feature: Capabilities
 
   @sdk @transport @requiresPlatformImplementation
   Scenario: Validate Capabilities.OnAvailable
-    When 1st party app registers for the 'capabilities onAvailable' event using the 'Firebolt' API
+    Given 1st party app registers for the 'capabilities onAvailable' event using the 'Firebolt' API
     And User set response for 'set keyboard response in platform'
     And Framework registers 'keyboard' test provider
     When 1st party app invokes the 'Firebolt' API to 'check availability of keyboard capability'
@@ -231,19 +231,19 @@ Feature: Capabilities
 
   @sdk @transport @requiresPlatformImplementation @notSupported
   Scenario: Validate Capabilities.OnUnavailable
-    When 1st party app registers for the 'capabilities onUnavailable' event using the 'Firebolt' API
+    Given 1st party app registers for the 'capabilities onUnavailable' event using the 'Firebolt' API
     And User set response for 'set keyboard response in platform'
-    When Framework registers 'keyboard' test provider
-    And 1st party app invokes the 'Firebolt' API to 'check availability of keyboard capability'
+    And Framework registers 'keyboard' test provider
+    When 1st party app invokes the 'Firebolt' API to 'check availability of keyboard capability'
     Then 'Firebolt' platform responds to '1st party app' with 'false for keyboard capability availability'
     And 'Firebolt' platform triggers to '1st party app' event 'expected value for capabilities onUnAvailable'
 
   @sdk @transport @requiresPlatformImplementation
   Scenario: Validate Capabilities.OnGranted
-    When '3rd party app' registers for the 'capabilities onGranted' event using the 'Firebolt' API
+    Given '3rd party app' registers for the 'capabilities onGranted' event using the 'Firebolt' API
     And User set response for 'set pinchallenge correct pin'
     And Framework registers 'pinChallenge' test provider
-    When User set response for 'set acknowledge granted'
+    And User set response for 'set acknowledge granted'
     And Framework registers 'ackchallenge' test provider
     When '3rd party app' invokes the 'Firebolt' API to 'fetch device id'
     Then 'Firebolt' platform responds with 'expected device id'
@@ -253,10 +253,10 @@ Feature: Capabilities
 
   @sdk @transport @requiresPlatformImplementation
   Scenario: Validate Capabilities.OnRevoked
-    When '3rd party app' registers for the 'capabilities onRevoked' event using the 'Firebolt' API
+    Given '3rd party app' registers for the 'capabilities onRevoked' event using the 'Firebolt' API
     And User set response for 'set pinchallenge wrong pin'
     And Framework registers 'pinChallenge' test provider
-    When User set response for 'set acknowledge granted'
+    And User set response for 'set acknowledge granted'
     And Framework registers 'ackchallenge' test provider
     When '3rd party app' invokes the 'Firebolt' API to 'expect error for device id'
     Then 'Firebolt' platform responds with 'invalid request for device id'

diff --git a/cypress/TestCases/FireboltCertification/Device.feature b/cypress/TestCases/FireboltCertification/Device.feature
@@ -22,13 +22,13 @@ Feature: Device
 
     @sdk @transport
     Scenario: Device.name - Positive Scenario: Validate device name change
-        When '3rd party app' registers for the 'device onNameChanged' event using the 'Firebolt' API
-        And '3rd party app' invokes the 'Firebolt' API to 'get device name'
-        And 1st party app invokes the 'Firebolt' API to 'set device name to living hall'
-        Then 'Firebolt' platform responds to '1st party app' for 'set device name to living hall'
-        When '3rd party app' invokes the 'Firebolt' API to 'get device name'
-        Then 'Firebolt' platform responds with 'living hall for device name'
-        And 'Firebolt' platform triggers event 'onDeviceNameChanged with living hall'
+        Given we test the 'DEVICE_NAME_CORE' getters and setters 'setName' to 'Living hall'
+        And '1st party app' registers for the 'Firebolt' event
+        When 1st party app invokes the 'Firebolt' API to set value
+        Then 'Firebolt' platform responds to '1st party app' set API
+        When '1st party app' invokes the 'Firebolt' get API
+        Then 'Firebolt' platform responds to '1st party app' get API
+        And 'Firebolt' platform triggers '1st party app' event
 
     @mfos  @regression @sdk
     Scenario Outline: Device.<Method> - Positive Scenario: <Scenario>
@@ -46,18 +46,18 @@ Feature: Device
 
     @regression @sdk @requiresPlatformImplementation
     Scenario: Device.onNameChanged - Positive Scenario: Clearing event listeners
-        When '3rd party app' registers for the 'device onNameChanged' event using the 'Firebolt' API
-        And 1st party stops listening to the event 'device onNameChanged event'
-        And 1st party app invokes the 'Firebolt' API to 'set device name to kitchen'
+        Given '3rd party app' registers for the 'device onNameChanged' event using the 'Firebolt' API
+        And 3rd party stops listening to the event 'device onNameChanged event'
+        When 1st party app invokes the 'Firebolt' API to 'set device name to kitchen'
         Then 'Firebolt' platform responds to '1st party app' for 'set device name to kitchen'
         And 'Firebolt' platform does not trigger event for 'onDeviceNameChanged'
 
     @sdk @transport @requiresPlatformImplementation @notSupported
     Scenario Outline: Device.network - Positive Scenario: <Scenario>
-        When '3rd party app' registers for the 'device onNetworkChanged' event using the 'Firebolt' API
-        And '3rd party app' invokes the 'Firebolt' API to 'fetch device network'
+        Given '3rd party app' registers for the 'device onNetworkChanged' event using the 'Firebolt' API
+        When '3rd party app' invokes the 'Firebolt' API to 'fetch device network'
         Then 'Firebolt' platform responds with '<Method_Validation_Key>'
-        When User triggers event with value as '<Event_Params>'
+        And User triggers event with value as '<Event_Params>'
         Then 'Firebolt' platform triggers event '<Event_Validation_Key>'
 
         Examples: