From 78f41710be0391de49689cdc0defc5e3d670dd43 Mon Sep 17 00:00:00 2001 From: Jordan Roe Date: Mon, 28 Oct 2024 13:02:57 -0400 Subject: [PATCH 1/5] Feat: Updating Scenario names --- .../FireboltCertification/Device.feature | 92 +++++++++++-------- 1 file changed, 56 insertions(+), 36 deletions(-) diff --git a/cypress/TestCases/FireboltCertification/Device.feature b/cypress/TestCases/FireboltCertification/Device.feature index dfec0699..dbda2679 100644 --- a/cypress/TestCases/FireboltCertification/Device.feature +++ b/cypress/TestCases/FireboltCertification/Device.feature @@ -5,28 +5,32 @@ Feature: Device Given the environment has been set up for 'Device' tests And 3rd party 'certification' app is launched - @sdk @transport - Scenario Outline:Device. - Positive Scenario: + @sdk @transport @Sev0 + Scenario Outline:Device. - Validate API Method Response Content for When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' Examples: - | Scenario | Method | Validation_Key | API_Key | - | Validate Device id | id | expected device id | fetch device id | - | Validate Device distributor | distributor | expected device distributor | fetch device distributor | - | Validate Device uid | uid | expected device uid | fetch device uid | - | Validate Device type | type | expected device type | fetch device type | - | Validate Device model | model | expected device model | fetch device model | - | Validate Device sku | sku | expected device sku | fetch device sku | - | Validate Device make | make | expected device make | fetch device make | + | Method | Validation_Key | API_Key | + | id | expected device id | fetch device id | + | distributor | expected device distributor | fetch device distributor | + | type | expected device type | fetch device type | + | platform | expected device platform | fetch device platfor | - @sdk @transport - Scenario: Device.platform - Positive Scenario: Validate device platform - When '3rd party app' invokes the 'Firebolt' API to 'fetch device platform' - Then 'Firebolt' platform responds with 'expected device platform' + @sdk @transport @Sev1 + Scenario Outline:Device. - Validate API Method Response Content for + When '3rd party app' invokes the 'Firebolt' API to '' + Then 'Firebolt' platform responds with '' + + Examples: + | Method | Validation_Key | API_Key | + | uid | expected device uid | fetch device uid | + | model | expected device model | fetch device model | + | sku | expected device sku | fetch device sku | + | make | expected device make | fetch device make | - @sdk @transport - Scenario: Device.name - Positive Scenario: Validate device name change + @sdk @transport @Sev2 + Scenario: Device.name - Validating API and Event Responses for name change 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 @@ -35,30 +39,46 @@ Feature: Device Then 'Firebolt' platform responds to '1st party app' get API And 'Firebolt' platform triggers '1st party app' event - @regression @sdk @transport - Scenario Outline: Device. - Positive Scenario: + @regression @sdk @transport @Sev0 + Scenario Outline: Device. - Validate API Method Response Content for + When '3rd party app' invokes the 'Firebolt' API to '' + Then 'Firebolt' platform responds with '' + + Examples: + | Method | API_Key | validation_key | + | hdcp | fetch hdcp | expected hdcp | + | hdr | fetch hdr | expected hdr | + | screenResolution | fetch screenResolution | expected screenResolution | + | videoResolution | fetch videoResolution | expected videoResolution | + + @regression @sdk @transport @Sev1 + Scenario Outline: Device. - Validate API Method Response Content for + When '3rd party app' invokes the 'Firebolt' API to '' + Then 'Firebolt' platform responds with '' + + Examples: + | Method | API_Key | validation_key | + | audio | fetch audio | expected audio | + + @regression @sdk @transport @Sev2 + Scenario Outline: Device. - Validate API Method Response Content for When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' Examples: - | Scenario | Method | API_Key | validation_key | - | Validate device version | version | fetch device version | expected device version | - | Validate hdcp | hdcp | fetch hdcp | expected hdcp | - | Validate hdr | hdr | fetch hdr | expected hdr | - | Validate screenResolution | screenResolution | fetch screenResolution | expected screenResolution | - | Validate videoResolution | videoResolution | fetch videoResolution | expected videoResolution | - | Validate audio | audio | fetch audio | expected audio | + | Method | API_Key | validation_key | + | version | fetch device version | expected device version | - @regression @sdk @requiresPlatformImplementation - Scenario: Device.onNameChanged - Positive Scenario: Clearing event listeners + @regression @sdk @requiresPlatformImplementation @Sev2 + Scenario: Device.onNameChanged - Clearing event listeners 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: + @sdk @transport @requiresPlatformImplementation @notSupported @Sev2 + Scenario Outline: Device.network - Get and validate state of 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 '' @@ -66,10 +86,10 @@ Feature: Device Then 'Firebolt' platform triggers event '' Examples: - | Scenario | Method_Validation_Key | Event_Validation_Key | Event_Params | - | Validate network_wifi_connected | device network as wifi connected | onNetworkChanged with wifi connected | onNetworkChanged events with wifi connected | - | Validate network_wifi_disconnected | device network as wifi disconnected | onNetworkChanged with wifi disconnected | onNetworkChanged events with wifi disconnected | - | Validate network_Ethernet_connected | device network as ethernet connected | onNetworkChanged with ethernet connected | onNetworkChanged events with ethernet connected | - | Validate network_Ethernet_disconnected | device network as ethernet disconnected | onNetworkChanged with ethernet disconnected | onNetworkChanged events with ethernet disconnected | - | Validate network_Hybrid_connected | device network as hybrid connected | onNetworkChanged with hybrid connected | onNetworkChanged events with hybrid connected | - | Validate network_Hybrid_disconnected | device network as hybrid disconnected | onNetworkChanged with hybrid disconnected | onNetworkChanged events with hybrid disconnected | + | Scenario | Method_Validation_Key | Event_Validation_Key | Event_Params | + | Network_wifi_connected | device network as wifi connected | onNetworkChanged with wifi connected | onNetworkChanged events with wifi connected | + | Network_wifi_disconnected | device network as wifi disconnected | onNetworkChanged with wifi disconnected | onNetworkChanged events with wifi disconnected | + | Network_Ethernet_connected | device network as ethernet connected | onNetworkChanged with ethernet connected | onNetworkChanged events with ethernet connected | + | Network_Ethernet_disconnected | device network as ethernet disconnected | onNetworkChanged with ethernet disconnected | onNetworkChanged events with ethernet disconnected | + | Network_Hybrid_connected | device network as hybrid connected | onNetworkChanged with hybrid connected | onNetworkChanged events with hybrid connected | + | Network_Hybrid_disconnected | device network as hybrid disconnected | onNetworkChanged with hybrid disconnected | onNetworkChanged events with hybrid disconnected | \ No newline at end of file From caf257a1951ac4bf00d3dacc5571359104847029 Mon Sep 17 00:00:00 2001 From: Jordan Roe Date: Tue, 29 Oct 2024 11:15:04 -0400 Subject: [PATCH 2/5] typo --- cypress/TestCases/FireboltCertification/Device.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cypress/TestCases/FireboltCertification/Device.feature b/cypress/TestCases/FireboltCertification/Device.feature index dbda2679..4c1efe1c 100644 --- a/cypress/TestCases/FireboltCertification/Device.feature +++ b/cypress/TestCases/FireboltCertification/Device.feature @@ -15,7 +15,7 @@ Feature: Device | id | expected device id | fetch device id | | distributor | expected device distributor | fetch device distributor | | type | expected device type | fetch device type | - | platform | expected device platform | fetch device platfor | + | platform | expected device platform | fetch device platform | @sdk @transport @Sev1 Scenario Outline:Device. - Validate API Method Response Content for From d2c1df2ec3fe1a01d00ae2a7d0017401354ffc40 Mon Sep 17 00:00:00 2001 From: Jordan Roe Date: Tue, 29 Oct 2024 11:42:04 -0400 Subject: [PATCH 3/5] Change for report cleanup --- .../TestCases/FireboltCertification/Device.feature | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/cypress/TestCases/FireboltCertification/Device.feature b/cypress/TestCases/FireboltCertification/Device.feature index 4c1efe1c..eb23dd65 100644 --- a/cypress/TestCases/FireboltCertification/Device.feature +++ b/cypress/TestCases/FireboltCertification/Device.feature @@ -6,7 +6,7 @@ Feature: Device And 3rd party 'certification' app is launched @sdk @transport @Sev0 - Scenario Outline:Device. - Validate API Method Response Content for + Scenario Outline:Device. - Validate API Method Response Content When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' @@ -18,7 +18,7 @@ Feature: Device | platform | expected device platform | fetch device platform | @sdk @transport @Sev1 - Scenario Outline:Device. - Validate API Method Response Content for + Scenario Outline:Device. - Validate API Method Response Content When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' @@ -40,7 +40,7 @@ Feature: Device And 'Firebolt' platform triggers '1st party app' event @regression @sdk @transport @Sev0 - Scenario Outline: Device. - Validate API Method Response Content for + Scenario Outline: Device. - Validate API Method Response Content When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' @@ -52,7 +52,7 @@ Feature: Device | videoResolution | fetch videoResolution | expected videoResolution | @regression @sdk @transport @Sev1 - Scenario Outline: Device. - Validate API Method Response Content for + Scenario Outline: Device. - Validate API Method Response Content When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' @@ -61,7 +61,7 @@ Feature: Device | audio | fetch audio | expected audio | @regression @sdk @transport @Sev2 - Scenario Outline: Device. - Validate API Method Response Content for + Scenario Outline: Device. - Validate API Method Response Content When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' @@ -78,7 +78,7 @@ Feature: Device And 'Firebolt' platform does not trigger event for 'onDeviceNameChanged' @sdk @transport @requiresPlatformImplementation @notSupported @Sev2 - Scenario Outline: Device.network - Get and validate state of + Scenario Outline: Device.onNetworkChanged - Get and validate state of 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 '' From cb3d4eb8bc2f85a3cfaf1ae9891b5eefacf14d05 Mon Sep 17 00:00:00 2001 From: Jordan Roe Date: Tue, 29 Oct 2024 12:58:43 -0400 Subject: [PATCH 4/5] Account Scenario name Adjustment --- cypress/TestCases/FireboltCertification/Account.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cypress/TestCases/FireboltCertification/Account.feature b/cypress/TestCases/FireboltCertification/Account.feature index 6f2c6885..f1a7801f 100644 --- a/cypress/TestCases/FireboltCertification/Account.feature +++ b/cypress/TestCases/FireboltCertification/Account.feature @@ -6,7 +6,7 @@ Feature: Account And 3rd party 'certification' app is launched @sdk @transport @Sev0 - Scenario Outline: Account. - Get and validate method response content + Scenario Outline: Account. - Validate API Method Response Content When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' Examples: From eb1707aa724a092dfd280455304e100220b1f47f Mon Sep 17 00:00:00 2001 From: Jordan Roe Date: Mon, 4 Nov 2024 12:14:15 -0500 Subject: [PATCH 5/5] Changes/update for already merged Account --- .../TestCases/FireboltCertification/Account.feature | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/cypress/TestCases/FireboltCertification/Account.feature b/cypress/TestCases/FireboltCertification/Account.feature index f1a7801f..5b8e3aa6 100644 --- a/cypress/TestCases/FireboltCertification/Account.feature +++ b/cypress/TestCases/FireboltCertification/Account.feature @@ -15,13 +15,13 @@ Feature: Account | uid | account uid | fetch account UID | @sdk @transport @notSupported @requiresPlatformImplementation @Sev2 - Scenario Outline: Account. - + Scenario Outline: Account. - Validate API Method Response Content with When '3rd party app' invokes the 'Firebolt' API to '' Then 'Firebolt' platform responds with '' Examples: | Scenario | Method | API_Key | Validation_key | - | Device not provisioned | id | fetch account ID when device is not provisioned | invalid parameter error for account id | - | Device not provisioned | uid | fetch account UID when device is not provisioned | invalid parameter error for account uid | - | Account retrieval attempt | id | fetch account ID when account is not provisioned | invalid parameter error for account id | - | Account retrieval attempt | uid | fetch account UID when account is not provisioned | invalid parameter error for account uid | \ No newline at end of file + | device not provisioned | id | fetch account ID when device is not provisioned | invalid parameter error for account id | + | device not provisioned | uid | fetch account UID when device is not provisioned | invalid parameter error for account uid | + | account retrieval attempt | id | fetch account ID when account is not provisioned | invalid parameter error for account id | + | account retrieval attempt | uid | fetch account UID when account is not provisioned | invalid parameter error for account uid | \ No newline at end of file