RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Papers & Presentations Archive
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 6 Next »
Test Source | No. of test cases Released |
---|---|
1DOTO | 745 |
3DOTO | 106 |
Total | 851 |
CDL
Wi-Fi
SI NO | Features | No of Test Cases |
---|---|---|
1 | BLUETOOTH | 4 |
2 | CDL | 20 |
3 | CONNECTIVITY | 81 |
4 | GUI | 151 |
5 | MTA | 1 |
6 | OVS | 2 |
7 | PROTOCOL AGENT | 106 |
8 | RDM | 1 |
9 | SANITY | 14 |
10 | SECURITY | 37 |
11 | SELFHEAL | 12 |
12 | SYSTEM | 222 |
13 | TELEMETRY | 62 |
14 | WIFI | 122 |
15 | WEBCONFIG | 16 |
TOTAL | 851 |
Released Automatics Bluetooth Related Test Cases - 4
Test Case Type | Total Count |
---|---|
1 DOT0 | 1 |
3 DOT0 | 3 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-LIMIT_BLUETOOTH-1000 | 19 | Verify Limit Bluetooth LE beacon detection | Release 7 | RDKM | 1 DOT0 |
2 | 3DOT0-TC-RDKB-BLUETOOTH-1000 | 6 | Verify if all RDKB Linux kernels support bluetooth. | Release 14 | RDKM | 3 DOT0 |
3 | 3DOT0-TC-RDKB-BLEADV-1001 | 20 | Add Support to get all supported device status during continuous BLE advertisement mode | Release 16 | RDKM | 3 DOT0 |
4 | 3DOT0-TC-RDKB-BLUEZ-1001 | 12 | Bluetooth Stack Unification | Release 20 | RDKM | 3 DOT0 |
Released Automatics CDL Related Test Cases - 20
Test Case Type | Total Count |
---|---|
1 DOT0 | 20 |
3 DOT0 | 0 |
Features Covered
CDL - Device Firmware Upgrade & Downgrade(XCONF)
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-XCONF-1001 | 14 | Trigger XCONF/DIFD HTTP CDL during router mode [ Deferred Reboot] | Release 2 | RDKM | 1 DOT0 |
2 | TC-RDKB-CDL-EXCLUDE-1006 | 3 | To verify firmware update with AutoExcluded. Enable is true, AutoExcluded.XconfUrl is empty | Release 3 | RDKM | 1 DOT0 |
3 | TC-RDKB-CDL-EXCLUDE-1001 | 4 | To verify firmware update with AutoExclude.Enable is false, XconfUrl is empty | Release 3 | RDKM | 1 DOT0 |
4 | TC-RDKB-CDL-EXCLUDE-1003 | 3 | To verify firmware update with AutoExcluded.Enable is false, AutoExcluded.XconfUrl is CI XCONF URL | Release 3 | RDKM | 1 DOT0 |
5 | TC-RDKB-XCONF-CDL-1002 | 10 | Access SSR and Xconf CDL Via Direct Communication | Release 3 | RDKM | 1 DOT0 |
6 | TC-RDKB-CDL-5003 | 9 | Enhance TC-RDKB-CDL-502 to include code download using HTTPS | Release 3 | RDKM | 1 DOT0 |
7 | TC-RDKB-CDL-EXCLUDE-1008 | 4 | To verify firmware update with AutoExcluded.Enable is true, AutoExcluded.XconfUrl is MOCK XCONF URL | Release 3 | RDKM | 1 DOT0 |
8 | TC-RDKB-CDL-EXCLUDE-1007 | 3 | To verify firmware update with AutoExcluded.Enable is true, AutoExcluded.XconfUrl is CI XCONF URL | Release 3 | RDKM | 1 DOT0 |
9 | TC-RDKB-CDL-EXCLUDE-1005 | 4 | To verify firmware update with AutoExcluded.Enable is true, AutoExcluded.XconfUrl is empty | Release 3 | RDKM | 1 DOT0 |
10 | TC-RDKB-CDL-EXCLUDE-1002 | 3 | To verify firmware update with AutoExcluded.Enable is false, AutoExcluded.XconfUrl is empty | Release 3 | RDKM | 1 DOT0 |
11 | TC-RDKB-XCONF-1003 | 2 | Trigger XCONF/DIFD HTTP CDL with same image version | Release 4 | RDKM | 1 DOT0 |
12 | TC-RDKB-XCONF-1004 | 2 | Trigger XCONF/DIFD TFTP CDL with different image version | Release 4 | RDKM | 1 DOT0 |
13 | TC-RDKB-XCONF-DELAY-1001 | 12 | Verify the Xconf flag support the delay download at installation with invalid images | Release 4 | RDKM | 1 DOT0 |
14 | TC-RDKB-XCONF-PERIFWUP-1005 | 10 | Schedule Periodic Firmware Upgrade Check | Release 4 | RDKM | 1 DOT0 |
15 | TC-RDKB-XCONF-UP-DWN-5001 | 10 | Validate firmware Upgrade Time Check via xconf | Release 4 | RDKM | 1 DOT0 |
16 | TC-RDKB-CDL-EXCLUDE-1004 | 3 | To verify firmware update with AutoExcluded.Enable is false, AutoExcluded.XconfUrl is MOCK XCONF URL | Release 4 | RDKM | 1 DOT0 |
17 | TC-RDKB-NEGATIVE-CDL-1000 | 10 | Verify CDL fails for corrupt build generated from same device class | Release 5 | RDKM | 1 DOT0 |
18 | TC-RDKB-NEGATIVE-CDL-1001 | 10 | Verify CDL fails for corrupt build generated from different device class | Release 5 | RDKM | 1 DOT0 |
19 | TC-RDKB-NEGATIVE-CDL-1002 | 10 | Verify CDL fails for corrupt build which is partially downloaded or having CRC error | Release 5 | RDKM | 1 DOT0 |
20 | TC-RDKB-CDL-5502 | 9 | Verify the TR-181 Code Download using HTTP Protocol for VBN/ DEV Builds is successful. | Release 9 | RDKM | 1 DOT0 |
Released Automatics Connectivity Related Test Cases - 81
Test Case Type | Total Count |
---|---|
1 DOT0 | 81 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release |
---|---|---|---|---|
1 | TC-RDKB-NW-CONNECTIVITY-1003 | 9 | Verify whether valid IP address are set for the ping servers by Webpa and the ping success logs are captured in selfHeallog.txt.0 | Release 1 |
2 | TC-RDKB-NW-CONNECTIVITY-1001 | 12 | Verify the ping related default values in the device after factory resetting by Webpa | Release 1 |
3 | TC-RDKB-FIREWALL-1005 | 12 | Verify Echo Reply or Response with different firewall settings | Release 2 |
4 | TC-RDKB-IP-MCAST-1000 | 3 | Verify Broadband gateway providing CMTS Mac Address to IP Multicast Back Office | Release 2 |
5 | TC-RDKB-NW-CONNECTIVITY-1004 | 14 | Verify whether the invalid IP address of the ping server is set by webpa and failure messages are logged when the ping fails in selfHeal log and Ping failures are captured in telemetry dashboard | Release 2 |
6 | TC-RDKB-NW-CONNECTIVITY-1008 | 3 | verify the Configuration of ping packet size via WebPA and also in device logs | Release 2 |
7 | TC-RDKB-NW-CONNECTIVITY-1009 | 11 | Verify whether the invalid ping servers and valid ping servers are set by webpa and failure messages are logged when the ping fails in selfHeal log | Release 2 |
8 | TC-RDKB-NW-CONNECTIVITY-1002 | 12 | Verify the ping related default values in the device after factory resetting by SNMP | Release 3 |
9 | TC-RDKB-NW-CONNECTIVITY-1005 | 15 | Verify whether valid IP address are set for the ping servers by SNMP and the ping success logs are captured in selfHeallog.txt.0 | Release 3 |
10 | TC-RDKB-NW-CONNECTIVITY-1006 | 20 | Verify whether the Invalid IP address of the ping server is set by SNMP and failure messages are logged when the ping fails in selfHeal log and Ping failures are captured in telemetry dashboard | Release 3 |
11 | TC-RDKB-TRACE-ROUTE-1002 | 4 | Test to verify trace route of the device using ipv6 addres | Release 3 |
12 | TC-RDKB-FIREWALL-1000 | 9 | Verify WAN - LAN traffic is blocked when Firewall is configured to Custom Security | Release 4 |
13 | TC-RDKB-ETHWAN-1001 | 8 | Verify CM shutting down in ETHWAN Mode | Release 4 |
14 | TC-RDKB-NW-CHECK-1001 | 3 | Ping to IPV6 from Client connected device | Release 4 |
15 | TC-RDKB-BRIDGE-MODE-1003 | 10 | Test case to verify router functionalities persistency on mode transisitions | Release 4 |
16 | TC-RDKB-DOWNUPSTREAM-1001 | 3 | Validate the timestamp for upstream/downstream ranging | Release 4 |
17 | TC-RDKB-BRIDGE-MODE-1001 | 10 | Verification of enabling and disabling Bridge mode via SNMP | Release 4 |
18 | TC-RDKB-NetCat-1003 | 6 | This test is to verify that secure "nc" utility is implemented on Atom based devices, to run only in client mode | Release 4 |
19 | TC-RDKB-NTP-0003 | 8 | Synchronize System Time with NTP Server | Release 5 |
20 | TC-RDKB-DROPBEAR-1102 | 14 | Test class to Verify whether security keys related to SCP present in the device or not | Release 5 |
21 | TC-RDKB-DROPBEAR-1103 | 14 | Test class to Verify whether security keys related to SCP present in the device or not in ATOM side | Release 5 |
22 | TC-RDKB-FIREWALL-1001 | 11 | Verify LAN - WAN traffic is successful when Firewall is configured to 'Custom Security' | Release 5 |
23 | TC-RDKB-DHCP-SWITCH-1001 | 12 | Verify common DHCPv4 code functionality | Release 5 |
24 | TC-RDKB-IPV4-CHECK-5001 | 7 | Verify DNS Address persist to the Wi-Fi & Ethernet client after reboot and ethernet client gets IP within acceptable time of 5 mins | Release 5 |
25 | TC-RDKB-BRIDGE-MODE-1004 | 25 | Verify the functionality of LAN client after CM reboot in bridge mode | Release 5 |
26 | TC-RDKB-2GHZ-DNS-NSLOOKUP-5001 | 5 | Verifying the alternate DNS nslookup functionality for 2.4GHz | Release 5 |
27 | TC-RDKB-5GHZ-DNS-NSLOOKUP-5001 | 5 | Verifying the alternate DNS nslookup functionality for 5GHz | Release 5 |
28 | TC-RDKB-ALTN-DNS-1001 | 16 | Verify Alternate DNS in WiFi and Lan Connected clients | Release 5 |
29 | TC-RDKB-BRIDGEMODE-REVERSE-1001 | 12 | Verify Reverse SSH Connection on bridge mode | Release 6 |
30 | TC-RDKB-XDNS-1000 | 10 | To enable XDNS feature and Verify status after Reboot and Factory Reset the device | Release 6 |
31 | TC-RDKB-DHCP-CLIENTS-1001 | 12 | Test to verify DCHP range assigning of cable modem with connected clients | Release 6 |
32 | TC-RDKB-STATIC-IP-1000 | 14 | Configure Static IPv4 through CLI for business device | Release 6 |
33 | TC-RDKB-BRIDGE-MODE-1002 | 30 | Test script to validate basic Wi-Fi parameters on router mode transition | Release 6 |
34 | TC-RDKB-CERTS-1001 | 14 | To verify CA Bundle | Release 6 |
35 | TC-RDKB-INTRANET-ACC-1001 | 12 | Verify the Ping operation is successful between 2.4 GHz and Ethernet clients | Release 6 |
36 | TC-RDKB-INTRANET-ACC-1002 | 12 | Verify the Ping operation is successful between 5 GHz and Ethernet clients | Release 6 |
37 | TC-RDKB-FIREWALL-1002 | 16 | Test to verify the port forwarding and DMZ feature is working when firewall is configured to Maximum Security | Release 6 |
38 | TC-RDKB-XDNS-1001 | 5 | To apply and verify XDNS override at gateway level | Release 6 |
39 | TC-RDKB-XDNS-1002 | 15 | To apply and Verify XDNS override of Primary Level 1 ,2 and 3 IPv4 and IPv6 DNS server IPs for connected client | Release 6 |
40 | TC-RDKB-XDNS-1004 | 25 | Apply and Verify XDNS ,override with different cases of Invalid values of MAC and DNS IPs | Release 6 |
41 | TC-RDKB-INTRANET-ACC-1000 | 13 | Verify the Ping operation is successful between 2.4 GHz and 5 GHz Private Wi-Fi clients | Release 7 |
42 | TC-RDKB-INTRANET-ACC-1003 | 13 | Verify the Iperf operation is successful between 2.4 GHz and 5 GHz Private Wi-Fi clients | Release 7 |
43 | TC-RDKB-INTRANET-ACC-1004 | 12 | Verify the Iperf operation is successful between 2.4 GHz Private Wi-Fi and Ethernet clients | Release 7 |
44 | TC-RDKB-INTRANET-ACC-1005 | 12 | Verify the Iperf operation is successful between 5 GHz Private Wi-Fi and Ethernet clients | Release 7 |
45 | TC-RDKB-XDNS-PRI-ALL-LVL-5001 | 24 | Verify if Skipping either one of the DNS server IP configuration -LEVEL 1 ,2 and 3 Primary Servers | Release 7 |
46 | TC-RDKB-CCSP-XDNS-5001 | 6 | Verify XDNS in Process Monitor after reboot | Release 7 |
47 | TC-RDKB-LNF-NTWK-1001 | 23 | Verify network connectivity in clients when lnf enabled | Release 7 |
48 | TC-RDKB-XDNS-1006 | 23 | Test to verify Add support for secondary XDNS server | Release 7 |
49 | TC-RDKB-LOGUPLOAD-1001 | 3 | Verify when setting UploadLogsNow parameter to False, no upload happens | Release 8 |
50 | TC-RDKB-HARV-5001 | 8 | Verify the integration of RDK-B Logger with Harvester | Release 8 |
51 | TC-RDKB-VALIDATE-HARV-3001 | 3 | Validate Wi-Fi Harvester InterfaceDevicesWifi Report after Reboot of DUT | Release 8 |
52 | TC-RDKB-HARV-6009 | 14 | Validate Enable-Disable status configuration of Interface Devices Wifi Report, Radio Interface Statistics Report values after reboot | Release 8 |
53 | TC-RDKB-HARV-6010 | 14 | Verify PollingPeriod & ReportingPeriod values for InterfaceDevicesWifi Report and RadioInterfaceStatistics Report | Release 8 |
54 | TC-RDKB-UPGRADE-LOGUPLOAD-6001 | 8 | Verify successful log upload post upgrade and reboot | Release 8 |
55 | TC-RDKB-RDKLOG-HARV-INTG-5003 | 4 | Verify the integration of RDK-B Logger with Harvester | Release 8 |
56 | TC-RDKB-LOGUPLOAD-1004 | 3 | Verify when setting UploadlogsNow snmp OID (1.3.6.1.4.1.17270.43.1.2.1.0) to False using snmp, no upload happens | Release 8 |
57 | TC-RDKB-LOGUPLOAD-1003 | 10 | Verify whether log upload fails after adding dns names in hosts entry and on removing the dns names log upload should be successful | Release 8 |
58 | TC-RDKB-HARVESTER-REPORT-1003 | 9 | Test to verify single client harvester report for 5GHz client | Release 8 |
59 | TC-RDKB-LOGUPLOAD-1002 | 7 | Verify when setting UploadlogsNow parameter to true, logs gets uploaded | Release 8 |
60 | TC-RDKB-HARVESTER-REPORT-1001 | 17 | Test to verify single client harvester report configurations | Release 8 |
61 | TC-RDKB-LOGUPLOAD-1005 | 6 | Verify when setting UploadlogsNow snmp OID (1.3.6.1.4.1.17270.43.1.2.1.0) to True, logs get uploaded | Release 8 |
62 | TC-RDKB-LOGUPLOAD-1006 | 10 | Verify whether log upload fails after adding dns names in hosts entry and on removing the dns names log upload should be successful | Release 8 |
63 | TC-RDKB-HARVESTER-REPORT-1002 | 15 | Test to verify single client harvester report for 2.4GHz client | Release 8 |
64 | TC-RDKB-BRID-MODE-5001 | 47 | Verify device and connected client status while device is in bridge mode | Release 8 |
65 | TC-RDKB-DHCP-LANCLIENT-1001 | 4 | This test case is to Verify the DHCP Lan client | Release 9 |
66 | TC-RDKB-MIN-FIREWALL-1002 | 12 | Verify minimum firewall in WiFi2.4Ghz associated connected client | Release 10 |
67 | TC-RDKB-FIREWALL-1004 | 9 | Test to verify ICMP Ping Request to Ethernet client for Minimum Firewall | Release 10 |
68 | TC-RDKB-LAN-DNS-NSLOOKUP-5001 | 5 | Verifying the alternate DNS nslookup functionality for Ethernet | Release 11 |
69 | TC-RDKB-DHCP-NEG-5001 | 10 | Validate the error message when DHCP Starting and Ending address is invalid | Release 11 |
70 | TC-RDKB-RESERVEDIP-5011 | 18 | Verify Internet access for clients after setting the client IPV4 as reserved IP | Release 11 |
71 | TC-RDKB-FIREWALL-1006 | 22 | Verify ICMP Ping request ,Error message on changing firewall settings in WiFi Client | Release 12 |
72 | TC-RDKB-FIREWALL-1007 | 22 | Verify ICMP Ping request ,Error message on changing firewall settings in Ethernet Client | Release 12 |
73 | TC-RDKB-NetCat-1001 | 7 | Verify secure \"nc\" utility is implemented on Dev images for specific Devices | Release 13 |
74 | TC-RDKB-NTP-0002 | 2 | Validate if NTP Server is disabled on device through RFC | Release 13 |
75 | TC-RDKB-NTP-0001 | 2 | Validate if NTP Server is enabled on device through RFC | Release 13 |
76 | TC-RDKB-INTERFACE-1101 | 15 | Verify there are no reconnection of iot & config clients after successful connection | Release 13 |
77 | TC-RDKB-HARV-6001 | 9 | Validation of NetworkDevicesTraffic Report generation | Release 20 |
78 | TC-RDKB-HARV-6000 | 10 | Validation of NetworkDevicesStatus Report generation | Release 20 |
79 | TC-RDKB-HARV-5002 | 3 | Verify the polling period & reporting period attributes of Radio Interface Statistics Harvester Report is increased to 900 seconds. | Release 20 |
80 | TC-RDKB-HARV-6008 | 13 | Check after TTL whether RadioInterfaceStatistics Polling-Reporting Period changes back to defaults when set less than Default TTL Interval. | Release 20 |
81 | TC-RDKB-HARV-6005 | 13 | Check after TTL whether NetworkDevicesStatus Polling-Reporting Period changes back to defaults when set less than Default TTL Interval | Release 21 |
Released Automatics GUI Related Test Cases - 151
Test Case Type | Total Count |
---|---|
1 DOT0 | 151 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Sub Feature | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|---|
1 | TC-RDKB-CAPTIVE-PORTAL-5004 | 18 | Validate timestamp when SSID and Password changed in captive portal | Captive Portal | Release 8 | RDKM | 1 DOT0 |
2 | TC-RDKB-WEBUI-CONFIG-5003 | 3 | Test To verify local UI no longer supports the ability to save/restore the config file from Admin page | UI page navigation. | Release 9 | RDKM | 1 DOT0 |
3 | TC-RDKB-WIFI-SCRTY-CHECK-1001 | 12 | Validate Selecting open risky mode and cancelling it immediately should not gray out password field Ethernet | Security check | Release 9 | RDKM | 1 DOT0 |
4 | TC-RDKB-WIFI-SCRTY-CHECK-1002 | 12 | Validate Selecting open risky mode and cancelling it immediately should not gray out password field Wifi 2.4Ghz client | Security check | Release 9 | RDKM | 1 DOT0 |
5 | TC-RDKB-WIFI-SCRTY-CHECK-1003 | 12 | Validate Selecting open risky mode and cancelling it immediately should not gray out password field Wifi 5Ghz client | Security check | Release 9 | RDKM | 1 DOT0 |
6 | TC-RDKB-LAN-GUI-7001 | 7 | Verify that Wifi client gets a valid IPv6 prefix, when the gateway is configured with SLAAC | Local IP page | Release 9 | RDKM | 1 DOT0 |
7 | TC-RDKB-LAN-GUI-7002 | 7 | Verify that LAN client gets a valid IPv6 prefix, when the gateway is configured with SLAAC | Local IP page | Release 9 | RDKM | 1 DOT0 |
8 | TC-RDKB-DHCP-IPV6-1002 | 16 | Verify DHCPv6 address in 2.4Ghz WiFi connected client on changing Min Address and Max Address | DHCP (IPV6 ,2.4) | Release 9 | RDKM | 1 DOT0 |
9 | TC-RDKB-DHCP-IPV6-1003 | 10 | Verify DHCPv6 address in 2.4Ghz WiFi connected client on changing Min Address and Max Address | DHCP (IPV6 ,2.4) | Release 9 | RDKM | 1 DOT0 |
10 | TC-RDKB-WIFI-DFLT-ADM-LOGIN-5001 | 13 | Verify Login into admin page using default password and Verify default values in Firewall IPV4, IPV6 and Managed Devices Pages | Password - Security, updation | Release 9 | RDKM | 1 DOT0 |
11 | TC-RDKB-PWD-MGMT-1001 | 15 | Verify the password management for WEBUI user for Admin page | Password - Security, updation | Release 9 | RDKM | 1 DOT0 |
12 | TC-RDKB-CON-DEV-5001 | 14 | Verify the details of connected clients can be retrieved from User admin page | Functionality test | Release 9 | RDKM | 1 DOT0 |
13 | TC-RDKB-WEBUI-8028 | 12 | Verify setting LAN Client ip as static ip and verify internet connectivity | Static IP Configuration | Release 9 | RDKM | 1 DOT0 |
14 | TC-RDKB-CHANNEL-BANDWIDTH-1001 | 17 | Login to Lan side GUI page of device | UI page navigation | Release 9 | RDKM | 1 DOT0 |
15 | TC-RDKB-WEBUI-7040 | 10 | Verify IP ping and tracerout diagnostics for IPv4 & IPv6 Address from Gateway Diagnostics page | Ping Test and Traceroute | Release 10 | RDKM | 1 DOT0 |
16 | TC-RDKB-WIFI-2GHZ-PUBLIC-PAGE-5001 | 15 | Verify channel type, Upstream and Downstream information availability in admin login Public network page for 2.4 Ghz | Functionality test (2.4 Ghz) | Release 10 | RDKM | 1 DOT0 |
17 | TC-RDKB-WIFI-5GHZ-PUBLIC-PAGE-5001 | 15 | Verify channel type, Upstream and Downstream information availability in admin login Public network page for 5 Ghz | Functionality test (5 Ghz) | Release 10 | RDKM | 1 DOT0 |
18 | TC-RDKB-WEB-GUI-5013 | 9 | Verify ICMPv6 ping request, when Firewall is set to Custom, default and ICMPv6 is blocked and unblocked | Ping Connectivity | Release 10 | RDKM | 1 DOT0 |
19 | TC-RDKB-PUBLIC-WIFI-CONFIG-5002 | 8 | Verify public WiFi Configuration Using LAN Admin Login | Connection performance (2.4 Ghz) | Release 10 | RDKM | 1 DOT0 |
20 | TC-RDKB-PUBLIC-WIFI-CONFIG-5003 | 8 | Verify public WiFi Configuration Using LAN Admin Login 5 GHz | Connection performance (5 Ghz) | Release 10 | RDKM | 1 DOT0 |
21 | TC-RDKB-LOCAL-IP-UI-1001 | 15 | Verify Options in Local IP network page are configurable on ethernet client | Local IP Configuration | Release 10 | RDKM | 1 DOT0 |
22 | TC-RDKB-LOCAL-IP-UI-1002 | 15 | Verify Options in Local IP network page are configurable on 2.4GHz connected client | Local IP Configuration | Release 10 | RDKM | 1 DOT0 |
23 | TC-RDKB-LOCAL-IP-UI-1003 | 15 | Verify Options in Local IP network page are configurable on 5GHz connected client | Local IP Configuration | Release 10 | RDKM | 1 DOT0 |
24 | TC-RDKB-ADMIN-PAGE-5001 | 28 | Verify the user admin page can be logged in using cusadmin credentials in the wired and wireless connected clients and Validate negative Scenario in Admin GUI Login | UI page navigation and Security Check | Release 10 | RDKM | 1 DOT0 |
25 | TC-RDKB-WEB-GUI-ADMIN-6001 | 29 | Verify Admin GUI login and verify all pages are accessible in Firefox Browser for 2.4 GHz WiFi | UI page navigation ( Firefox Browser) | Release 10 | RDKM | 1 DOT0 |
26 | TC-RDKB-WEB-GUI-ADMIN-6002 | 29 | Verify Admin GUI login and verify all pages are accessible in Firefox Browser for 5 GHz WiFi | UI page navigation ( Firefox Browser) | Release 10 | RDKM | 1 DOT0 |
27 | TC-RDKB-WEBUI-7034 | 23 | Verify assigning DHCP Server Address while old one in use and with expire lease time | DHCP | Release 10 | RDKM | 1 DOT0 |
28 | TC-RDKB-WEBUI-7006 | 9 | Verify whether the CM can act as a DHCPv4 server 2.4GHz Wi-Fi client. | DHCP (IPV4 ,2.4 Ghz) | Release 11 | RDKM | 1 DOT0 |
29 | TC-RDKB-WEBUI-7008 | 9 | Verify whether the CM can act as a DHCPv4 server 5GHz Wi-Fi client . | DHCP (IPV6 ,5 Ghz) | Release 11 | RDKM | 1 DOT0 |
30 | TC-RDKB-WEBUI-8029 | 12 | Verify the internet access in connected WiFi client with static IP | Static IP | Release 11 | RDKM | 1 DOT0 |
31 | TC-RDKB-WEBUI-7002 | 9 | Verify whether the CM can act as a DHCPv4 server | DHCP (IPV4 ) | Release 11 | RDKM | 1 DOT0 |
32 | TC-RDKB-WEB-GUI-FF-5004 | 15 | Verify access to DUT via UserAdmin page - WAN (or) eRouter IP using Windows OS and Firefox browser (HTTPS Enabled and Disabled) | Remote Management (2.4 Ghz) | Release 11 | RDKM | 1 DOT0 |
33 | TC-RDKB-WEB-GUI-FF-5005 | 15 | Verify access to DUT via UserAdmin page - WAN (or) eRouter IP using Windows OS and Firefox browser (HTTPS Enabled and Disabled) | Remote Management (5 Ghz) | Release 11 | RDKM | 1 DOT0 |
34 | TC-RDKB-WEB-GUI-IE-5001 | 15 | Validate Pseudo Bridge mode configuration page is removed from MSO page,LAN GUI Admin page | Bridge mode | Release 11 | RDKM | 1 DOT0 |
35 | TC-RDKB-DEVICE-RESET-1005 | 35 | Perform Factory reset from Admin GUI page and verify default values after factory reset | Factory reset | Release 12 | RDKM | 1 DOT0 |
36 | TC-RDKB-CHANNEL-BANDWIDTH-1002 | 24 | Test to verify channel bandwidth of 5Ghz wifi ssid from Lan GUI | Wifi Features (Channel bandwidth) | Release12 | RDKM | 1 DOT0 |
37 | TC-RDKB-WEBUI-8026 | 11 | Test to verify Providing option in local UI to add/remove Reserved IP binding for offline devices from LAN page | Reserved IP Configuration | Release 12 | RDKM | 1 DOT0 |
38 | TC-RDKB-ADMIN-GUI-5002 | 20 | Verify that the AdminUI Network page displays the IPv6 values | Connection performance test | Release 12 | RDKM | 1 DOT0 |
39 | TC-RDKB-WEBUI-5004 | 10 | Verify that gateway does not accept LAN Gateway address as same as WAN IP address and CM IP Address | Gateway Configuration | Release 18 | RDKM | 1 DOT0 |
40 | TC-RDKB-WEBUI-5005 | 8 | Verify the IP address of online device cannot be configured as reserved IP | Reserved IP Configuration | Release 18 | RDKM | 1 DOT0 |
41 | TC-RDKB-WEBUI-7035 | 15 | Verify Port Forwarding- Pre-defined Service Names | Port Forwarding | Release 18 | RDKM | 1 DOT0 |
42 | TC-RDKB-WEBUI-7036 | 17 | Verify Port Forwarding testing via LAN GUI Page in WiFi 2.4GHz Client | Port Forwarding | Release 18 | RDKM | 1 DOT0 |
43 | TC-RDKB-WEBUI-7037 | 17 | Verify Port Forwarding testing via LAN GUI Page in WiFi 5GHz Client | Port Forwarding | Release 18 | RDKM | 1 DOT0 |
44 | TC-RDKB-ADVANCED-NEG-5001 | 30 | Verify the rule cannot be added, edited and deleted when Port Forwarding and Triggering is disabled | Port Forwarding | Release 19 | RDKM | 1 DOT0 |
45 | TC-RDKB-WEBUI-8021 | 27 | Verify editing customized blocked Devices and Services | Parental control | Release 19 | RDKM | 1 DOT0 |
46 | TC-RDKB-WEBUI-7032 | 45 | Verify Parental Control Negative Scenario for WiFi 5GHz Client | Parental control | Release 19 | RDKM | 1 DOT0 |
47 | TC-RDKB-WEBUI-7033 | 45 | Verify Parental Control Negative Scenario for Ethernet Client | Parental control | Release 19 | RDKM | 1 DOT0 |
48 | TC-RDKB-WEBUI-7015 | 16 | Verify values as such in Local IP Network Page and cross verify with WEBPA values and Verify on selection of different subnet mask the DHCP start and END address are auto populated for 2.4GHz Wi-Fi client Scenario | Local IP Configuration | Release 19 | RDKM | 1 DOT0 |
49 | TC-RDKB-UI-5006 | 19 | Verify the internet access in the client when deleted from Connected Devices and Managed Devices | Parental Control | Release 19 | RDKM | 1 DOT0 |
50 | TC-RDKB-WEBUI-8016 | 12 | Verify cancel button in troubleshooting-change password page and Default value of MAC based access control | UI page navigation | Release 19 | RDKM | 1 DOT0 |
51 | TC-RDKB-WIFI-GUI-1001 | 22 | Validate ajax handler for the wireless network configuration page for admin GUI | UI page navigation | Release 19 | RDKM | 1 DOT0 |
52 | TC-RDKB-LAN-WEBUI-LABEL-INFO-1001 | 18 | Verify Label information in WebUI | Functionality test | Release 19 | RDKM | 1 DOT0 |
53 | TC-RDKB-WIFI-LAN-WEBUI-IPSTATUS-5001 | 7 | Verify IP address supplied by router must persist after rebooting the Ethernet client | Connection performance | Release 19 | RDKM | 1 DOT0 |
54 | TC-RDKB-WEBUI-5050 | 14 | Verify all the details in the Hardware Page | Functionality test | Release 20 | RDKM | 1 DOT0 |
55 | TC-RDKB-WEBUI-5051 | 9 | Verify the Software Information available in the WEBGUI Page | Functionality test | Release 20 | RDKM | 1 DOT0 |
56 | TC-RDKB-WEBUI-7009 | 56 | Verify whether the Parental Control Report is generated in Parental Control Page in 2.4Ghz WIFI Connected Device | Parental Control | Release 20 | RDKM | 1 DOT0 |
57 | TC-RDKB-WEBUI-7010 | 56 | Verify whether the Parental Control Report is generated in Parental Control Page in 5Ghz WIFI Connected Device | Parental Control | Release 20 | RDKM | 1 DOT0 |
58 | TC-RDKB-WEBUI-7011 | 56 | Verify whether the Parental Control Report is generated in Parental Control Page in 5Ghz Ethernet Connected Device | Parental Control | Release 20 | RDKM | 1 DOT0 |
59 | TC-RDKB-WEBUI-4001 | 10 | Verify Advanced Device Discovery Scenarios for WiFi 5GHz Client | Discovery Scenarios | Release 20 | RDKM | 1 DOT0 |
60 | TC-RDKB-WEBUI-4002 | 10 | Verify Advanced Device Discovery Scenarios for Ethernet Client | Discovery Scenarios | Release 20 | RDKM | 1 DOT0 |
61 | TC-RDKB-WIFI_WEBUI-1103 | 8 | Verify Error message in LAN UI for setting invalid Private SSID name | Security check | Release 20 | RDKM | 1 DOT0 |
62 | TC-RDKB-MULTILINGUAL-1001 | 10 | Testcase to verify multilingual language welcome message in French language for partners | Multilingual | Release 20 | RDKM | 1 DOT0 |
63 | TC-RDKB-WEBUI-7053 | 11 | Verify Diagnostic Tool test for IPv4 address in 2.4ghz and 5ghz client | Diagnostic Tool test | Release 20 | RDKM | 1 DOT0 |
64 | TC-RDKB-WEBUI-7054 | 11 | Verify Diagnostic Tool test for IPv4 address in Ethernet client | Diagnostic Tool test | Release 20 | RDKM | 1 DOT0 |
65 | TC-RDKB-WEBUI-1102 | 20 | Verify ability to change all octet of the gateway IP from admin page | Gateway Configuration | Release 21 | RDKM | 1 DOT0 |
66 | TC-RDKB-WEBUI-2003 | 9 | Verify the 2.4GHz & 5GHz WiFi passwords visibility in LAN Admin GUI | password management | Release 21 | RDKM | 1 DOT0 |
67 | TC-RDKB-WEBUI-1010 | 1 | Verify Setting restricted IP address to Gateway IP From Admin Gui | Gateway Configuration | Release 21 | RDKM | 1 DOT0 |
68 | TC-RDKB-WEBUI-8024 | 19 | Test to verify WiFi Mode Support from admin page | Wi Fi | Release 21 | RDKM | 1 DOT0 |
69 | TC-RDKB-CAPTIVE-PORTAL-5001 | 17 | Verify the gateway admin page is accessible without redirecting to captive portal after a factory reset | Factory Reset | Release 21 | RDKM | 1 DOT0 |
70 | TC-RDKB-PC-MANAGE-DEVICE-1005 | 17 | Verification of pause-block screen on trying to access internet after blocking client connected to 2.4GHz | Parental Control | Release 21 | RDKM | 1 DOT0 |
71 | TC-RDKB-PC-MANAGE-DEVICE-1007 | 16 | Verification of pause-block screen on trying to access internet after blocking client connected to Ethernet Client | Parental Control | Release 21 | RDKM | 1 DOT0 |
72 | TC-RDKB-CAPTIVE-PORTAL-5002 | 21 | Verify that the user is redirected to captive portal page and able to customise SSID and password for the selected band's SSID after factory reset | Captive Portal and Factory Reset | Release 21 | RDKM | 1 DOT0 |
73 | TC-RDKB-CAPTIVE-PORTAL-5003 | 38 | Verify Capitive Portal GUI Elements and Alerts before and after configuring the private 2.4 GHz and 5 GHz private SSID | Captive Portal | Release 21 | RDKM | 1 DOT0 |
74 | TC-RDKB-WIFI-SSID-CHK-1001 | 24 | Verify wifi ssid name check with characters | Wi Fi (SSID check) | Release 21 | RDKM | 1 DOT0 |
75 | TC-RDKB-DEVICE-PAGE-1001 | 32 | Verify the user admin page can be logged in using cusadmin credentials in the wired and wireless connected clients | UI page navigation and Security Check | Release 21 | RDKM | 1 DOT0 |
76 | TC-RDKB-WIFI-WEBUI-LAN-STSPGE-3001 | 28 | Verify the status page has all the required fields for Ethernet Client | Status page | Release 21 | RDKM | 1 DOT0 |
77 | TC-RDKB-WIFI-WEBUI-2GHZ-STSPGE-3001 | 29 | Verify the status page has all the required fields for 2 GHZ client | Status page | Release 21 | RDKM | 1 DOT0 |
78 | TC-RDKB-WIFI-WEBUI-5GHZ-STSPGE-3001 | 28 | Verify the status page has all the required fields for 5 GHZ client | Status page | Release 21 | RDKM | 1 DOT0 |
79 | TC-RDKB-PARTNERUI_ADMIN-1001 | 14 | Testcase to verify Update UI Branding Product Name based branding change | Release 22 | RDKM | 1 DOT0 | |
80 | TC-RDKB-PC-MANAGE-DEVICE-1006 | 17 | Verification of pause-block screen on trying to access internet after blocking client connected to 2.4GHz | Release 22 | RDKM | 1 DOT0 | |
81 | TC-RDKB-WEBUI_LOGGING-1001 | 9 | Verify LAN WEBUI logging | Release 22 | RDKM | 1 DOT0 | |
82 | TC-RDKB-WEBUI-7016 | 16 | Verify values as such in Local IP Network Page and cross verify with WEBPA values and Verify on selection of different subnet mask the DHCP start and END address are auto populated for 5GHz Wi-Fi client Scenario | Release 22 | RDKM | 1 DOT0 | |
83 | TC-RDKB-WEBUI-7017 | 16 | Verify values as such in Local IP Network Page and cross verify with WEBPA values and Verify on selection of different subnet mask the DHCP start and END address are auto populated for ethernet client Scenario | Release 22 | RDKM | 1 DOT0 | |
84 | TC-RDKB-WIFI_WEBUI-1104 | 5 | Verify Error message in Captive portal for setting invalid Private SSID name | Release 22 | RDKM | 1 DOT0 | |
85 | TC-RDKB-2GHZ-SUBMSK-ADMGUI-5001 | 12 | Change and verify the subnet mask value for 2.4 GHz | Release 22 | RDKM | 1 DOT0 | |
86 | TC-RDKB-5GHZ-SUBMSK-ADMGUI-5001 | 12 | Change and verify the subnet mask value for 5 GHz | Release 22 | RDKM | 1 DOT0 | |
87 | TC-RDKB-LAN-SUBMSK-ADMGUI-5001 | 12 | Change and verify the subnet mask value for Ethernet Client | Release 22 | RDKM | 1 DOT0 | |
88 | TC-RDKB-SYNC-PART-1001 | 9 | Verify the header and footer of gateway admin GUI is designed specific to Syndicate partner | Release 22 | RDKM | 1 DOT0 | |
89 | TC-RDKB-WIFI-SEC-MODE-4003 | 16 | Verify that LAN side wireless CPE gets an IP address when dual radio bands 2.4GHZ and 5 GHZ are enabled in CM | Release 22 | RDKM | 1 DOT0 | |
90 | TC-RDKB-ADMINGUI-REMOTE-1000 | 19 | Verify Admin GUI remote management | Release 22 | RDKM | 1 DOT0 | |
91 | TC-RDKB-SYN-LAN-GUI-1001 | 37 | Verify all pages of Syndicate build are accessible,header and footer with Parnter labels in LAN Gui in Ethernet Client | Release 22 | RDKM | 1 DOT0 | |
92 | TC-RDKB-SYN-LAN-GUI-1002 | 37 | Verify all pages of Syndicate build are accessible,header and footer with Parnter labels in LAN Gui in Wifi 2.4Ghz client | Release 22 | RDKM | 1 DOT0 | |
93 | TC-RDKB-SYN-LAN-GUI-1003 | 37 | Verify all pages of Syndicate build are accessible,header and footer with Parnter labels in LAN Gui in Wifi 5 Ghz client | Release 22 | RDKM | 1 DOT0 | |
94 | TC-RDKB-WEBUI-6000 | 28 | Test to Verify Connection to SSID with Open security for 2.4 GHz and WPA2-PSK (AES) security modes - 2.4 GHz | Release 22 | RDKM | 1 DOT0 | |
95 | TC-RDKB-WEBUI-6001 | 28 | Test to Verify Connection to SSID with Open security for 5 GHz and WPA2-PSK (AES) security modes - 5 GHz | Release 22 | RDKM | 1 DOT0 | |
96 | TC-RDKB-WIFI-RESTORE-1004 | 25 | Verify WiFi settings can be restored to default settings after admin gui wifi reset | Release 22 | RDKM | 1 DOT0 | |
97 | TC-RDKB-WEBUI-7031 | 45 | Verify Parental Control Negative Scenario for WiFi 2.4GHz Client | Release 22 | RDKM | 1 DOT0 | |
98 | TC-RDKB-CON-DEV-5002 | 18 | Verify the details of connected clients can be retrieved from User admin page | Release 23 | RDKM | 1 DOT0 | |
99 | TC-RDKB-WEB-GUI-5011 | 8 | Verify access to DUT via LAN page - WAN (or) eRouter IP using Windows OS and Chrome browser (HTTP Enabled) | Release 23 | RDKM | 1 DOT0 | |
100 | TC-RDKB-WEBUI-7050 | 19 | Verify Port forwarding Negative Scenario validation and enable disable from CPE GUI(Ethernet) | Release 23 | RDKM | 1 DOT0 | |
101 | TC-RDKB-WEBUI-8022 | 14 | Test to verify webui changes from admin page | Release 23 | RDKM | 1 DOT0 | |
102 | TC-RDKB-WEBUI-7018 | 19 | Verify Port forwarding Negative Scenario validation and enable disable from CPE GUI(WiFi 2.4Ghz) | Release 23 | RDKM | 1 DOT0 | |
103 | TC-RDKB-WEBUI-7019 | 19 | Verify Port Forwarding Negative Scenario validation and enable disable from CPE GUI(WiFi 5Ghz) | Release 23 | RDKM | 1 DOT0 | |
104 | TC-RDKB-WEBUI-7038 | 17 | Verify Port Forwarding testing via LAN GUI Page in Ethernet Client | Release 23 | RDKM | 1 DOT0 | |
105 | TC-RDKB-WEBUI-8009 | 4 | Verify customer central and user guide footer links removed from local UI | Release 23 | RDKM | 1 DOT0 | |
106 | TC-RDKB-ADMIN-PAGE-5002 | 27 | Verify the remote management IP address in Remote Management page from the wired and wireless connected clients | Release 23 | RDKM | 1 DOT0 | |
107 | TC-RDKB-WIFI-5GHZ-ADMIN-GUI-5001 | 44 | Verify Admin GUI login with invalid & valid credentials and verify all pages are accessible for 5 GHz | Release 23 | RDKM | 1 DOT0 | |
108 | TC-RDKB-LAN-GUI-ADMIN-5001 | 44 | Verify Admin GUI login with invalid & valid credentials and verify all pages are accessible for Ethernet | Release 23 | RDKM | 1 DOT0 | |
109 | TC-RDKB-PRT-TGR-PG-VDTN-1002 | 30 | Verify Port Trigger page validation from Admin GUI in wifi 2.4Ghz client | Release 24 | RDKM | 1 DOT0 | |
110 | TC-RDKB-PRT-TGR-PG-VDTN-1003 | 30 | Verify Port Trigger page validation from Admin GUI in wifi 5Ghz client | Release 24 | RDKM | 1 DOT0 | |
111 | TC-RDKB-WIFI-TX-RATE-CONFIG-WEBUI-5001 | 24 | Verify the configuration of Transmission Control Rate for both 2.4GHz(g,n) and 5Ghz(n,ac,ax) Radio after reboot | Release 24 | RDKM | 1 DOT0 | |
112 | TC-RDKB-WIFI-RESTORE-1003 | 23 | Test to Verify WiFi settings can be restored to default settings after mso gui wifi reset | Release 24 | RDKM | 1 DOT0 | |
113 | TC-RDKB-DEVICE-RESET-1001 | 28 | Verification of factory default values of different Broad band Wi-Fi parameters/Settings | Release 24 | RDKM | 1 DOT0 | |
114 | TC-RDKB-WEBUI-7024 | 10 | Verify diagnostic Tool test for TEST CONNECTIVITY in troubleshooting page | Release 24 | RDKM | 1 DOT0 | |
115 | TC-RDKB-WEBUI-7030 | 107 | Verify Port Forwarding Negative Scenario,Enable,Disable,Delete,Edit validation from CPE GUI | Release 24 | RDKM | 1 DOT0 | |
116 | TC-RDKB-WEBUI-7007 | 14 | Verify whether the gateway can be changed to any private IP in Wired and Wireless client | Release 24 | RDKM | 1 DOT0 | |
117 | TC-RDKB-SYNC-PART-1000 | 6 | Verify the captive portal has requirements specific to syndicate partner | Release 24 | RDKM | 1 DOT0 | |
118 | TC-RDKB-UI-5007 | 16 | Verify the Remote Management feature configuring with customized port numbers for HTTP and HTTPS | Release 24 | RDKM | 1 DOT0 | |
119 | TC-RDKB-WIFI-REMOVEPREFERPRIVATE-1001 | 8 | Verification to check if Prefer Private functionality is removed in the Admin page and local GUI page | Release 24 | RDKM | 1 DOT0 | |
120 | TC-RDKB-WEBUI-8027 | 8 | Test to verify Providing option in local UI to add/remove Reserved IP binding for offline devices from admin page | Release 24 | RDKM | 1 DOT0 | |
121 | TC-RDKB-UI-5003 | 28 | Validate the Firewall Security settings configured in Admin GUI is reflected | Release 24 | RDKM | 1 DOT0 | |
122 | TC-RDKB-WEB-GUI-BRIDGE-5001 | 12 | Validate Pseudo Bridge mode configuration page is removed from LAN GUI Admin page | Release 24 | RDKM | 1 DOT0 | |
123 | TC-RDKB-DEVICE-RESET-1002 | 7 | Test case is to validate device reboot from GUI | Release 25 | RDKM | 1 DOT0 | |
124 | TC-RDKB-WEB-GUI-MOCA-5002 | 40 | Validate the MoCA page greyed out after enabling bridge mode in lan and Admin page | Release 25 | RDKM | 1 DOT0 | |
125 | TC-RDKB-DHCP-LANCLIENT-1002 | 16 | Verify DHCP IP configuration and subnetmask address details from Admin GUI page | Release 25 | RDKM | 1 DOT0 | |
126 | TC-RDKB-WEBUI-CON-DEV-5001 | 19 | Verify client connected to Wi-Fi radio has the same IP address in the Connected devices GUI as assigned to the client & also its shown in Connected devices as Wi-Fi | Release 25 | RDKM | 1 DOT0 | |
127 | TC-RDKB-GUI-ENBL-DSBL-RDO-CC-1001 | 40 | Verify client connectivity when 2.4 GHz and 5 GHz radio is enabled or disabled in LAN GUI | Release 25 | RDKM | 1 DOT0 | |
128 | TC-RDKB-RMT-MGNT-UI-CHK-1004 | 19 | Verify Admin UI of the gateway in Bridge mode using WAN IP under remote management in ethernet client | Release 25 | RDKM | 1 DOT0 | |
129 | TC-RDKB-WEB-GUI-5012 | 14 | Verify the details of connected retrieved from Admin page | Release 25 | RDKM | 1 DOT0 | |
130 | TC-RDKB-PFR_PRIVATE_CONN-1001 | 2 | Verify modifiying Prefer Private Connection through WebGui | Release 25 | RDKM | 1 DOT0 | |
131 | TC-RDKB-WEBUI_PHP_CODE-1005 | 17 | Verify unwanted php files were removed from ADMIN in Residential devices | Release 26 | RDKM | 1 DOT0 | |
132 | TC-RDKB-IP-CONN-1000 | 25 | Verify IPV4 and IPv6 connectivity from GUI, Gateway and Client | Release 26 | RDKM | 1 DOT0 | |
133 | TC-RDKB-PARE-CTRL-NEG-5002 | 17 | Verify the Manage Devices should not accept rule which has Start time greater than End Time | Release 26 | RDKM | 1 DOT0 | |
134 | TC-RDKB-WEBUI-7013 | 38 | Verify parental control services should not accept Start from time Greater than End to time when single day is selected | Release 26 | RDKM | 1 DOT0 | |
135 | TC-RDKB-WEBUI-1018 | 7 | Verify Static IPv4 using Admin Gui page on the LAN side interface | Release 26 | RDKM | 1 DOT0 | |
136 | TC-RDKB-WIFI-WIRELESS-MODE-1001 | 10 | Test to Verify mode of 2.4Ghz SSID | Release 26 | RDKM | 1 DOT0 | |
137 | TC-RDKB-WIFI-WIRELESS-MODE-1002 | 10 | Test to Verify mode of 5Ghz SSID | Release 26 | RDKM | 1 DOT0 | |
138 | TC-RDKB-PFER-PVT-WIFI-2GHZ-LAN-5001 | 29 | Verify RDKB resets Blacklist when Private wifi parameters are changed from LAN Admin page for 2.4 GHz | Release 26 | RDKM | 1 DOT0 | |
139 | TC-RDKB-PFER-PVT-WIFI-5GHZ-LAN-5001 | 29 | Verify RDKB resets Blacklist when Private wifi parameters are changed from LAN Admin page for 5GHz | Release 26 | RDKM | 1 DOT0 | |
140 | TC-RDKB-UI-5008 | 28 | Verify the gateway admin page can be accessed securely and status page is validated | Release 27 | RDKM | 1 DOT0 | |
141 | TC-RDKB-WEBGUI-1111 | 28 | Verify Connected device from admin page, lan gui admin page and TR181 Parameter | Release 27 | RDKM | 1 DOT0 | |
142 | TC-RDKB-SSID-DEFAULT-1001 | 14 | Test to verify device default security mode and device saves default SSID,Password after factory reset | Release 27 | RDKM | 1 DOT0 | |
143 | TC-RDKB-DEVICE-RESET-1004 | 5 | Test to Verify WiFi router restart ( Residential and Business Devices) status using WebGUI | Release 27 | RDKM | 1 DOT0 | |
144 | TC-RDKB-WIFI-CHNL-BW-5002 | 6 | Verify for 2.4Ghz & 5 GHz radio the channel bandwidth | Release 27 | RDKM | 1 DOT0 | |
145 | TC-RDKB-RMT-MGNT-UI-CHK-1001 | 12 | Verify Admin UI of the gateway using WAN IP under remote management in ethernet client | Release 27 | RDKM | 1 DOT0 | |
146 | TC-RDKB-WIFI-2GHZ-ADMIN-GUI-5001 | 43 | Verify Admin GUI login with invalid & valid credentials and verify all pages are accessible for 2 GHz | Release 27 | RDKM | 1 DOT0 | |
147 | TC-RDKB-WIFI-LAN-DHCP-IPV4-DSBLE-5001 | 5 | Verify the IP range in Ethernet connected client when DHCP Server Disabled. | Release 27 | RDKM | 1 DOT0 | |
148 | TC-RDKB-WEBUI-1009 | 3 | Verify setting restricted IP to gateway IP | Release 27 | RDKM | 1 DOT0 | |
149 | TC-RDKB-DEVICE-RESET-1003 | 5 | Test to Verify WiFi module restart ( Residential and Business Devices) status using WebGUI") | Release 27 | RDKM | 1 DOT0 | |
150 | TC-RDKB-WEBUI_PHP_CODE-1007 | 6 | Verify php pages which are not to be accessible by ADMIN in Residential devices | Release 29 | RDKM | 1 DOT0 | |
151 | TC-RDKB-UI-5009 | 24 | Verify the UPnP can be enabled and disabled in Lan Gui, cross-verified using SNMP and vice-versa | Release 29 | RDKM | 1 DOT0 |
Released Automatics MTA Related Test Cases - 1
Test Case Type | Total Count |
---|---|
1 DOT0 | 1 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-MTA-1001 | 3 | Test to reset MTA of the device | Release 5 | RDKM | 1 DOT0 |
Released Automatics OVS Related Test Cases -2
Test Case Type | Total Count |
---|---|
1 DOT0 | 2 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-OVS-1001 | 9 | Test to verify OVS functionality | Release 7 | RDKM | 1 DOT0 |
2 | TC-RDKB-OVS-1002 | 20 | Integrate OVS in RDKB - Productization | Release 11 | RDKM | 1 DOT0 |
Released Automatics Protocol Agent Related Test Cases -106
Test Case Type | Total Count |
---|---|
1 DOT0 | 103 |
3 DOT0 | 3 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-WIFI-WEBPA-1005 | 7 | Verifying the TR-181 Parameter Device.WiFi.AccessPoint.10101.Security.ModeEnabled using WebPA | Release 1 | RDKM | 1 DOT0 |
2 | TC-RDKB-WIFI-WEBPA-1006 | 7 | Verifying the TR-181 Parameter Device.WiFi.AccessPoint.10102.Security.ModeEnabled using WebPA | Release 1 | RDKM | 1 DOT0 |
3 | TC-RDKB-WIFI-WEBPA-1007 | 7 | Verification of Device.WiFi.AccessPoint.10103.Security.ModeEnabled using WebPA | Release 1 | RDKM | 1 DOT0 |
4 | TC-RDKB-WIFI-WEBPA-1008 | 7 | Verification of Device.WiFi.AccessPoint.10001.Security.ModeEnabled using WebPA | Release 1 | RDKM | 1 DOT0 |
5 | TC-RDKB-WIFI-WEBPA-1009 | 7 | Verifying the TR-181 Parameter Device.WiFi.AccessPoint.10002.Security.ModeEnabled | Release 1 | RDKM | 1 DOT0 |
6 | TC-RDKB-WIFI-WEBPA-1010 | 7 | Verification of Device.WiFi.AccessPoint.10003.Security.ModeEnabled using WebPA | Release 1 | RDKM | 1 DOT0 |
7 | TC-RDKB-WEBPA-1003 | 1 | Verify the retrieval of webpa version from tr181 parameter | Release 1 | RDKM | 1 DOT0 |
8 | TC-RDKB-SNMP-1002 | 1 | Test to Verify the Manufacturer serial number using DOCS-CABLE-DEVICE-MIB:: docsDevSerialNumber(1.3.6.1.2.1.69.1.1.4.0) SNMP MIB. | Release 1 | RDKM | 1 DOT0 |
9 | TC-RDKB-SNMP-1003 | 1 | Verify the WAN MAC Address using IF-MIB::ifPhysAddress.1 (.1.3.6.1.2.1.2.2.1.6) | Release 1 | RDKM | 1 DOT0 |
10 | TC-RDKB-SNMP-1004 | 1 | Test to Verify the Cable Modem MAC Address using IF-MIB::ifPhysAddress.2 (.1.3.6.1.2.1.2.2.1.6.2) SNMP MIB. | Release 1 | RDKM | 1 DOT0 |
11 | TC-RDKB-SNMP-1005 | 1 | Verify the Current software version using DOCS-CABLE-DEVICE-MIB::docsDevSwCurrentVers( 1.3.6.1.2.1.69.1.3.5.0) | Release 1 | RDKM | 1 DOT0 |
12 | TC-RDKB-SNMP-1001 | 10 | Verify system description, Modem Configuration Filename, EMTA Address, Cable Interface MAC Address, Serial Number via SNMP and cross validate with WEBPA | Release 2 | RDKM | 1 DOT0 |
13 | TC-RDKB-WEBPA-6013 | 1 | Validation of Wi-Fi bridge mode or LAN mode | Release 2 | RDKM | 1 DOT0 |
14 | TC-RDKB-WEBPA-6001 | 1 | Validating SSID of private 5 GHz network is advertised | Release 2 | RDKM | 1 DOT0 |
15 | TC-RDKB-WEBPA-6022 | 1 | Validating SSID of public 2.4 GHz SSID is advertised | Release 2 | RDKM | 1 DOT0 |
16 | TC-RDKB-WEBPA-6024 | 1 | Validating SSID of public 5 GHz SSID is advertised | Release 2 | RDKM | 1 DOT0 |
17 | TC-RDKB-WEBPA-PERF-1000 | 2 | Calculating End to End WebPA request Processing Time and Box Processing Time for WebPA Get Operation with Single Param | Release 2 | RDKM | 1 DOT0 |
18 | TC-RDKB-WEBPA-PERF-1001 | 2 | Calculate the Average Response Time for five Get parameters Requests in WEBPA | Release 2 | RDKM | 1 DOT0 |
19 | TC-RDKB-WEBPA-PERF-1002 | 2 | Calculate the Average Response Time for ten Get parameter Requests in WEBPA | Release 2 | RDKM | 1 DOT0 |
20 | TC-RDKB-WEBPA-PERF-1003 | 2 | Calculating average End to End WebPA request Processing Time and Box Processing Time for WebPA Set Operation with Single Param | Release 2 | RDKM | 1 DOT0 |
21 | TC-RDKB-WEBPA-PERF-1004 | 2 | Calculate the Average Response Time for five Set parameter Request in WEBPA | Release 2 | RDKM | 1 DOT0 |
22 | TC-RDKB-WEBPA-PERF-1005 | 2 | Calculate the Average Response Time for ten Set parameter Request in WEBPA | Release 2 | RDKM | 1 DOT0 |
23 | TC-RDKB-SNMP-5001 | 4 | Verify the Software file name, Server transport protocol, Server address type and Admin status can be retrieved from SNMP | Release 2 | RDKM | 1 DOT0 |
24 | TC-RDKB-SNMP-1006 | 1 | Verification of device Up Time | Release 2 | RDKM | 1 DOT0 |
25 | TC-RDKB-WIFI-WEBPA-1011 | 2 | Verification of TR-181 parameter - Device.WiFi.SSID.10101.SSID using WebPA | Release 2 | RDKM | 1 DOT0 |
26 | TC-RDKB-WIFI-WEBPA-1013 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10103.SSID using WebPA | Release 2 | RDKM | 1 DOT0 |
27 | TC-RDKB-WIFI-WEBPA-1014 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10001.SSID using WebPA | Release 2 | RDKM | 1 DOT0 |
28 | TC-RDKB-WIFI-WEBPA-1016 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10003.SSID using WebPA | Release 2 | RDKM | 1 DOT0 |
29 | TC-RDKB-WIFI-WEBPA-1017 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10101.MACAddress using WebPA | Release 2 | RDKM | 1 DOT0 |
30 | TC-RDKB-WIFI-WEBPA-1019 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10103.MACAddress using WebPA | Release 2 | RDKM | 1 DOT0 |
31 | TC-RDKB-WIFI-WEBPA-1020 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10001.MACAddress using WebPA | Release 2 | RDKM | 1 DOT0 |
32 | TC-RDKB-WIFI-WEBPA-1022 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10003.MACAddress using WebPA | Release 2 | RDKM | 1 DOT0 |
33 | TC-RDKB-WIFI-WEBPA-1023 | 2 | Verification of TR-181 parameter - Device.WiFi.SSID.10101.Enable using WebPA | Release 2 | RDKM | 1 DOT0 |
34 | TC-RDKB-WIFI-WEBPA-1025 | 2 | Verification of TR-181 parameter -Device.WiFi.SSID.10103.Enable using WebPA | Release 2 | RDKM | 1 DOT0 |
35 | TC-RDKB-WIFI-WEBPA-1030 | 4 | Verification of 2.4Ghz Private wifi been broadcasted by using this parameter 'Device.WiFi.AccessPoint.10001.SSIDAdvertisementEnabled' using WebPA and validating it by SNMP | Release 2 | RDKM | 1 DOT0 |
36 | TC-RDKB-WIFI-WEBPA-1031 | 4 | Verification of 5Ghz Private wifi been broadcasted by using this parameter 'Device.WiFi.AccessPoint.10101.SSIDAdvertisementEnabled' using WebPA and validating it by SNMP | Release 2 | RDKM | 1 DOT0 |
37 | TC-RDKB-WIFI-WEBPA-1034 | 4 | Verification of 2.4Ghz Public wifi been broadcasted by using this parameter 'Device.WiFi.AccessPoint.10003.SSIDAdvertisementEnabled' using WebPA and validating it by SNMP | Release 2 | RDKM | 1 DOT0 |
38 | TC-RDKB-WIFI-WEBPA-1035 | 4 | Verification of 5Ghz Public wifi been broadcasted by using this parameter 'Device.WiFi.AccessPoint.10103.SSIDAdvertisementEnabled' using WebPA and validating it by SNMP | Release 2 | RDKM | 1 DOT0 |
39 | TC-RDKB-SNMP-1026 | 6 | Verify Ethernet Related SNMP | Release 2 | RDKM | 1 DOT0 |
40 | TC-RDKB-SNMP-1009 | 2 | Verify DOCSIS Signal Quality Extended RxMER Samples Table MIB values and its READ-ONLY attribute | Release 2 | RDKM | 1 DOT0 |
41 | TC-RDKB-SNMP-1008 | 2 | Verify DOCSIS Signal Quality Extended RxMER Table MIB values and its READ-ONLY attribute | Release 2 | RDKM | 1 DOT0 |
42 | TC-RDKB-SNMP-1025 | 3 | Validate that the Delegated IPv6 prefix can be retrieved using rdkbRgDeviceConfigStaticIpv6 (.1.3.6.1.4.1.17270.50.2.1.4.7.0) | Release 2 | RDKM | 1 DOT0 |
43 | TC-RDKB-SNMP-SIGTONOISE-1021 | 2 | Verify the alues of DOCS-IF-MIB::docsIfSigQSignalNoise in the given MIB range | Release 2 | RDKM | 1 DOT0 |
44 | TC-RDKB-SNMP-1007 | 6 | Verification of DOCSIS Mib functionality | Release 3 | RDKM | 1 DOT0 |
45 | TC-RDKB-SNMP-5050 | 32 | Verify Access Points security mode via SNMP parameter | Release 3 | RDKM | 1 DOT0 |
46 | TC-RDKB-SNMP-1012 | 6 | Verify enabling/disabling bridge mode through SNMP v3 is successful | Release 3 | RDKM | 1 DOT0 |
47 | TC-RDKB-SNMP-1027 | 12 | Verify the cable modem SNMPv3 parameters from RDK using RFC/XConf (Broadcom RDKB platforms) | Release 3 | RDKM | 1 DOT0 |
48 | TC-RDKB-WEBPA-1013 | 10 | Verify Webpa requests (GET/SET/PUT/POST/DELETE) are working fine and Webpa notifications should be sent successfully to server | Release 3 | RDKM | 1 DOT0 |
49 | TC-RDKB-SNMP-1021 | 5 | Test to verify removal of telnet daemon | Release 3 | RDKM | 1 DOT0 |
50 | TC-RDKB-SNMP-1022 | 2 | Validate that the device does not give valid SNMP response for invalid MTA community String | Release 3 | RDKM | 1 DOT0 |
51 | TC-RDKB-SNMP-1010 | 8 | Verify Configuring the AAA server Primary/Secondary IP address for 2.4 and 5GHz | Release 3 | RDKM | 1 DOT0 |
52 | TC-RDKB-WEBPA-PARALLEL-1006 | 1 | Verify multiple WEBPA requests in parallel | Release 3 | RDKM | 1 DOT0 |
53 | TC-RDKB-WEBPA-1008 | 17 | Verify all reports for Harvester and LMLite are enabled and Verify CcspWebpaadapter responds to WEBPA GET, SET requests. | Release 3 | RDKM | 1 DOT0 |
54 | TC-RDKB-WEBPA-PERF-1006 | 6 | Calculate the Average Response Time for two, three and four Get parameter Requests in WEBPA | Release 3 | RDKM | 1 DOT0 |
55 | TC-RDKB-WH-SNMP-1001 | 8 | Verify SNMP get operation for warehouse DOCSIS OIDs and cross-verify the same with its corresponding TR-181 param using WebPA | Release 4 | RDKM | 1 DOT0 |
56 | TC-RDKB-WEBPA-1020 | 11 | Verify firmware download event notifications for invalid build with Manageable notification feature enabled | Release 4 | RDKM | 1 DOT0 |
57 | TC-RDKB-WH-SNMP-1002 | 9 | verify snmp set for warehouse OID | Release 4 | RDKM | 1 DOT0 |
58 | TC-RDKB-SNMP-1024 | 3 | Validate that the static IPv4 address can be retrieved using rdkbRgDeviceConfigStaticIp (.1.3.6.1.4.1.17270.50.2.1.4.6.0) | Release 4 | RDKM | 1 DOT0 |
59 | TC-RDKB-WEBPA-1007 | 5 | Verify XDNS Ccspxdns not crashing on overriding default values | Release 4 | RDKM | 1 DOT0 |
60 | TC-RDKB-SNMP-1014 | 6 | Verify resetting the device through SNMP v3 is successful | Release 4 | RDKM | 1 DOT0 |
61 | TC-RDKB-WEBPA-1012 | 18 | Verify reboot reason notifications sent for different types of reboot | Release 4 | RDKM | 1 DOT0 |
62 | TC-RDKB-TR69-1000 | 1 | Verification of Device Serial Number using TR69 parameter -Device.DeviceInfo.SerialNumber | Release 4 | RDKM | 1 DOT0 |
63 | TC-RDKB-TR69-1001 | 1 | Verification of Device Model Name using TR69 parameter -Device.DeviceInfo.ModelName | Release 4 | RDKM | 1 DOT0 |
64 | TC-RDKB-TR69-1002 | 1 | Verification of Device Software Version using TR69 parameter -Device.DeviceInfo.SoftwareVersion | Release 4 | RDKM | 1 DOT0 |
65 | TC-RDKB-WEBPA-1019 | 15 | Verify firmware download event notifications with Manageable notification feature disabled | Release 4 | RDKM | 1 DOT0 |
66 | TC-RDKB-WEBPA-1018 | 11 | Verify Implementation of new WifiClient data model for harvester under Device.WiFi | Release 4 | RDKM | 1 DOT0 |
67 | TC-RDKB-SNMP-1023 | 9 | Test to verify that the SNMP set/get can be performed successfully using valid MTA community string | Release 5 | RDKM | 1 DOT0 |
68 | TC-RDKB-WH-SNMP-1005 | 17 | Verify ECM Firmware Upgrade and Factory Reset OIDs - Sequence strict warehouse OIDs | Release 5 | RDKM | 1 DOT0 |
69 | TC-RDKB-SNMPV3-1001 | 19 | Test to verify snmpv3 migration | Release 5 | RDKM | 1 DOT0 |
70 | TC-RDKB-WH-SNMP-1006 | 16 | Verify ECM Docs DevSw Admin Status OIDs - Sequence strict warehouse OIDs | Release 5 | RDKM | 1 DOT0 |
71 | TC-RDKB-WIFI-WEBPA-3003 | 12 | Verify the ability to change mode from a/n/ac to ac only, a/n/ac to n only, a-n-ac to n-ac only radio on the 5 GHz radio | Release 5 | RDKM | 1 DOT0 |
72 | TC-RDKB-TR69-1007 | 24 | This method verifies whether WiFi objects can be enabled disabled via TR69 | Release 5 | RDKM | 1 DOT0 |
73 | TC-RDKB-TR69-1010 | 5 | This method verifies Advanced Management server parameters | Release 5 | RDKM | 1 DOT0 |
74 | TC-RDKB-TR69-2001 | 5 | Verify ACS related TR-69 functionality | Release 5 | RDKM | 1 DOT0 |
75 | TC-RDKB-TR69-1009 | 10 | Verifies whether WiFi objects can be enabled disabled via TR69 | Release 5 | RDKM | 1 DOT0 |
76 | TC-RDKB-WIFI-WEBPA-3002 | 6 | Test case is created to check the ability to change mode from g-n to n-only mode on the 2.4 GHz radio | Release 5 | RDKM | 1 DOT0 |
77 | TC-RDKB-WEBPA-1011 | 20 | Verify firmware download event notifications with Manageable notification feature enabled | Release 5 | RDKM | 1 DOT0 |
78 | TC-RDKB-TR69-1008 | 24 | Verifies whether Wi-Fi SSID objects can be enabled disabled via TR69 | Release 6 | RDKM | 1 DOT0 |
79 | TC-RDKB-TR69-1020 | 12 | Test to validate device IP objects against TR69 specifications | Release 6 | RDKM | 1 DOT0 |
80 | TC-RDKB-TR69-1021 | 66 | Test to validate Device interface objects as per TR69 specifications | Release 6 | RDKM | 1 DOT0 |
81 | TC-RDKB-TR69-1014 | 16 | Test to validate TR69 Wi-Fi radio stats objects as per TR69 specifications | Release 6 | RDKM | 1 DOT0 |
82 | TC-RDKB-TR69-1012 | 46 | Validate TR69 Radio objects(General) | Release 6 | RDKM | 1 DOT0 |
83 | TC-RDKB-TR69-1018 | 34 | Test to validate the TR69 Wi-Fi SSID objects against TR69 specifications | Release 6 | RDKM | 1 DOT0 |
84 | TC-RDKB-TR69-1013 | 60 | Validate TR69 Radio Child objects (Frequency Objects) | Release 6 | RDKM | 1 DOT0 |
85 | TC-RDKB-TR69-1019 | 32 | Validate TR69 WIFI Access Point objects | Release 6 | RDKM | 1 DOT0 |
86 | TC-RDKB-TR69-RBT-1002 | 7 | RDK B Reboot Validation tests using TR69/ACS | Release 6 | RDKM | 1 DOT0 |
87 | TC-RDKB-WEBPA-1016 | 34 | Send WebPA Sync Notification when selected data model parameters are changed | Release 6 | RDKM | 1 DOT0 |
88 | TC-RDKB-TR69-1023 | 34 | Validate TR69 Radio Child objects (Frequency Objects) | Release 6 | RDKM | 1 DOT0 |
89 | TC-RDKB-TR69-1005 | 18 | This method verifies the expected TR69 functionality with default values, changed values and after reboot values of Device Management Server Passwords | Release 6 | RDKM | 1 DOT0 |
90 | TC-RDKB-TR69-ETHNT-INTFC-1001 | 15 | Validate ethernet interface entries using Tr69 | Release 6 | RDKM | 1 DOT0 |
91 | TC-RDKB-TR69-1017 | 48 | Verify the write access of the WiFi AccessPoint objects | Release 7 | RDKM | 1 DOT0 |
92 | TC-RDKB-TR69-1015 | 12 | Verify the write access of the WiFi radio objects | Release 7 | RDKM | 1 DOT0 |
93 | TC-RDKB-TR69-1016 | 42 | Verify the write access of the WiFi SSID objects | Release 7 | RDKM | 1 DOT0 |
94 | TC-RDKB-SNMP-1018 | 6 | Test to verify 2.4 GHz & 5 GHz SSID of Private Wi-Fi, Public Wi-Fi and Passphrase of Private Wi-Fi can be retrieved successfully through SNMP v2 Queries | Release 8 | RDKM | 1 DOT0 |
95 | TC-RDKB-WiFi-SNMP-1031 | 30 | Verify SNMP configuration of Wifi | Release 8 | RDKM | 1 DOT0 |
96 | TC-RDKB-TR69-1011 | 10 | Validates Naming convention for TR69 parameters | Release 8 | RDKM | 1 DOT0 |
97 | TC-RDKB-WEBPA-1017 | 29 | Verify ManagementServer - Basic Parameters | Release 8 | RDKM | 1 DOT0 |
98 | TC-RDKB-WEBPA-1009 | 14 | Verify implementation of broadband functionalities for parodus client and Verify implemention of wrp-c library so that WebPA requests can be encoded and decoded | Release 13 | RDKM | 1 DOT0 |
99 | 3DOT0-TC-RDKB-TR069REMOVAL-1001 | 7 | To check tr069 support is removed for TXB8 | Release 14 | RDKM | 3 DOT0 |
100 | 3DOT0-TC-RDKB-WEBPA_SIZE_CCSP_BUS-1011 | 18 | Verify string size limit increased with CCSP bus enable | Release 16 | RDKM | 3 DOT0 |
101 | TC-RDKB-ST-AUT-5002 | 6 | Test to verify the speed test feature of Broadband device for ipv6 interface | Release 20 | RDKM | 1 DOT0 |
102 | TC-RDKB-WEBPA-1004 | 29 | Verify Syndication single Build Local UI and Wifi Personalisation | Release 22 | RDKM | 1 DOT0 |
103 | TC-RDKB-SYNDICATION-LOCAL-WIFI-UI-1006 | 13 | Verify Syndication single Build Local UI and Wifi Personalisation Phase One | Release 22 | RDKM | 1 DOT0 |
104 | 3DOT0-TC-RDKB-WEBPA-1015 | 5 | Verify weppa set/get | Release 27 | RDKM | 13DOT0 |
105 | TC-RDKB-WIFI_RADIO-1001 | 4 | verify the Ability to disable WiFi Radio through WebGUI | Release 29 | RDKM | 1 DOT0 |
106 | TC-RDKB-WEBPA-1006 | 60 | To Verify single Build for Syndication default bootstrap configurations with invalid partner id | Release 29 | RDKM | 1 DOT0 |
Released Automatics RDM Related Test Cases -1
Test Case Type | Total Count |
---|---|
1 DOT0 | 1 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-RDM-1006 | 3 | Test to verify rdm-manifest json in the device | Release 8 | RDKM | 1 DOT0 |
Released Automatics Sanity Related Test Cases -14
Test Case Type | Total Count |
---|---|
1 DOT0 | 13 |
3 DOT0 | 1 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-QUICK-1009 | 21 | Verification of RDKB firmware quality with basic sanity tests | Release 2 | RDKM | 1 DOT0 |
2 | TC-RDKB-ONBOARDING-1000 | 11 | Verify CPE on-boarding process logging in the already onboarded device | Release 6 | RDKM | 1 DOT0 |
3 | TC-RDKB-SESHAT-5001 | 7 | Test case is to verify the seshat service registration and component discovery distro - disabled scenario | Release 6 | RDKM | 1 DOT0 |
4 | TC-RDKB-XCONF-PTNRID-5001 | 3 | Verify the Partner Id parameter in any query to XCONF - CDL, DCM, and RFC | Release 8 | RDKM | 1 DOT0 |
5 | TC-RDKB-SYND-PTNRID-5002 | 2 | Verify Partner ID using WebPA and TR-069 | Release 8 | RDKM | 1 DOT0 |
6 | TC-RDKB-IDS-1006 | 6 | Test to verify Removal of IDS | Release 9 | RDKM | 1 DOT0 |
7 | TC-RDKB-CSRF-1101 | 4 | Verify CSRF protection is moved from Lighttpd | Release 12 | RDKM | 1 DOT0 |
8 | TC-RDKB-DSCP-MARK-CHK-1001 | 12 | DSCP Marking validation in Device | Release 13 | RDKM | 1 DOT0 |
9 | TC-RDKB-SYNDICATION-1002 | 7 | Verify Partner ID and erouter ips in Telemetry Log | Release 13 | RDKM | 1 DOT0 |
10 | TC-RDKB-QUICK-1017 | 5 | Verify Firmware Upgrade is successful in the DUT using XCONF server. | Release 17 | RDKM | 1 DOT0 |
11 | TC-RDKB-XCONF_SERVER-1001 | 120 | Test used for quick validation of RDKB build available in build server. Accept build name as parameter and pass it to test case as system property 'BUILD_NAME'. | Release 17 | RDKM | 1 DOT0 |
12 | TC-RDKB-IPV4-CM-2055 | 6 | Change the LAN DHCP pool on the fly and check if the connected clients get the changed IP address and check persistency (Sanity TC) | Release 17 | VODAFONE | 1 DOT0 |
13 | TC-RDKB-WIFI-SANITY-1001 | 17 | Verify the connectivity of 2.4ghz wifi on different configurations | Release 18 | RDKM | 1 DOT0 |
14 | TC-RDKB-QUICK-1017 | Enhancement of existing step | Test used for quick validation of RDKB build available in build server. Accept build name as parameter and pass it to test case as system property 'BUILD_NAME'. | Release 19 | RDKM | 1 DOT0 |
15 | TC-RDKB-WIFI-SANITY-1001 | Additional 31 steps | Verify the connectivity of 2.4ghz wifi on different configurations. Added 31 steps as enhancement - checks the device 2.4ghz wifi configurations and UI pages | Release 19 | RDKM | 1 DOT0 |
16 | 3DOT0-TC-RDKB-WIFI-CONN-STABILITY-1001 | 4 | 3.0 testcase to check the 2.4ghz wifi connection stability of device | Release 19 | RDKM | 3 DOT0 |
Released Automatics Security Related Test Cases - 37
Test Case Type | Total Count |
---|---|
1 DOT0 | 37 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-SECURITY-RM-LEGACY-1001 | 9 | Test to verify Rabid process should start up on boot | Release 1 | RDKM | 1 DOT0 |
2 | TC-RDKB-SECURITY_FIREWALL-1001 | 31 | Adding Security Firewall Parameters | Release 1 | RDKM | 1 DOT0 |
3 | TC-RDKB-SECURITY-5001 | 3 | Verify the telnet, rlogin, and NFS are removed from the build | Release 1 | RDKM | 1 DOT0 |
4 | TC-RDKB-TRACE-ROUTE-1001 | 4 | Test to verify trace route of the device using ipv4 address | Release 3 | RDKM | 1 DOT0 |
5 | TC-RDKB-SECURITY-1001 | 5 | Test to verify the latest OpenSSL version in RDKB devices | Release 3 | RDKM | 1 DOT0 |
6 | TC-RDKB-SECURITY-2203 | 16 | Verify third party tracker is blocked after firewall restart | Release 3 | RDKM | 1 DOT0 |
7 | TC-RDKB-SECURITY-2001 | 2 | Upgrade Dropbear to latest version | Release 3 | RDKM | 1 DOT0 |
8 | TC-RDKB-SECURITY-1106 | 1 | To verify whether PHP version is upgraded to 7.2.13 or above | Release 4 | RDKM | 1 DOT0 |
9 | TC-RDKB-SECURITY-1105 | 2 | To Verify lighttpd and php fingerprinting | Release 4 | RDKM | 1 DOT0 |
10 | TC-RDKB-SECURITY-2201 | 9 | Enable 3rd party tracker blocking on a gateway | Release 4 | RDKM | 1 DOT0 |
11 | TC-RDKB-SECURITY-2202 | 9 | Verify third party tracker is not blocked | Release 4 | RDKM | 1 DOT0 |
12 | TC-RDKB-SECURITY-1002 | 8 | Testcase for securing syscfg.db parameters via encryption. | Release 4 | RDKM | 1 DOT0 |
13 | TC-RDKB-ENCRYPT-1001 | 10 | Test to verify Encrypt WiFi passwords stored in NVRAM | Release 4 | RDKM | 1 DOT0 |
14 | TC-RDKB-WIFI-SEC-MODE-1001 | 7 | Verification of 2.4 GHz Private SSID connectivity using valid and invalid WPA2-PSK-AES key | Release 4 | RDKM | 1 DOT0 |
15 | TC-RDKB-WIFI-SEC-MODE-1002 | 7 | Verification of 5 GHz Private SSID connectivity using valid and invalid WPA2-PSK-AES key | Release 4 | RDKM | 1 DOT0 |
16 | TC-RDKB-PC-MNG-SITE-1001 | 19 | Test to Verify the internet access to the sites and keywords added to manages sites are blocked for a specific day and time period in Wi-Fi and LAN clients | Release6 | RDKM | 1 DOT0 |
17 | TC-RDKB-SECURITY-1104 | 2 | Test to verify Shell Shock Vulnerability | Release 6 | RDKM | 1 DOT0 |
18 | TC-RDKB-SEC-RM-SENS-INFO-5001 | 14 | Test to verify the sensitive informations are removed from logs | Release 7 | RDKM | 1 DOT0 |
19 | TC-RDKB-ST-AUT-5001 | 4 | Test to verify the speed test feature of Broadband device for ipv6 interface | Release 7 | RDKM | 1 DOT0 |
20 | TC-RDKB-FINGERPRINT-1005 | 8 | Verify telemetry logging for Advanced security Cloud association success or failure and Advsec Status Enable or Disable, Advsec Agent Running or not, with configurable LoggingPeriod parameter | Release 7 | RDKM | 1 DOT0 |
21 | TC-RDKB-WIFI-SECTY-WPA2-5002 | 70 | Verify the WIFI Connectivity on Dual Band Radio for Client for 2.4 and 5 GHz with security mode WPA2-PSK | Release 7 | RDKM | 1 DOT0 |
22 | TC-RDKB-PC-MANAGE-DEVICE-1001 | 16 | Test to verify the wireless client connected to 5 GHz Private Wi-Fi network is blocked for all days & for particular time period | Release 7 | RDKM | 1 DOT0 |
23 | TC-RDKB-XDNS_SECURITYEDGE-1001 | 13 | Validation of XDNS redirection when clients are excluded from security edge | Release 9 | RDKM | 1 DOT0 |
24 | TC-RDKB-PARE-CTRL-NEG-5001 | 18 | Verify the Manage Sites and Managed Services should not accept rule which has Start time greater than End Time | Release 9 | RDKM | 1 DOT0 |
25 | TC-RDKB-MIN-FIREWALL-1001 | 12 | Verify minimum firewall in Ethernet connected client | Release 10 | RDKM | 1 DOT0 |
26 | TC-RDKB-MIN-FIREWALL-1003 | 12 | Verify minimum firewall in WiFi5Ghz associated connected client | Release 10 | RDKM | 1 DOT0 |
27 | TC-RDKB-CertValidation-1001 | 3 | Test to verify whether any new certificates are added to RDK devices other than the trusted ones defined in the default CA bundle under /usr/share/ca-certificates/ca-certificates.crt | Release 11 | RDKM | 1 DOT0 |
28 | TC-RDKB-SECURITY-2003 | 5 | Enable forwardSSH via RFC and verify whether we can do forwardSSH | Release 12 | RDKM | 1 DOT0 |
29 | TC-RDKB-SECURITY-2004 | 4 | Set invalid string to forwardSSH | Release 12 | RDKM | 1 DOT0 |
30 | TC-RDKB-SECURITY-2002 | 6 | Disable forwardSSH via RFC and verify whether we can do forwardSSH | Release 13 | RDKM | 1 DOT0 |
31 | TC-RDKB-WIFI-SECTY-WPA-WPA2-5003 | 69 | Verify the WIFI Connectivity on Dual Band Radio for Client for 2.4 and 5 GHz with security mode WPA-WPA2-PSK | Release 13 | RDKM | 1 DOT0 |
32 | TC-RDKB-PC-MNG-SITE-1000 | 33 | Test to verify the internet access to the sites & keywords added to manages sites are blocked in Wi-Fi & LAN clients | Release 13 | RDKM | 1 DOT0 |
33 | TC-RDKB-XCONF_CERT_DWNLD-1001 | 10 | Verify CPE is able to download and install the cert bundle for myrouter.io | Release 13 | RDKM | 1 DOT0 |
34 | TC-RDKB-PC-MNG-SERVICES-1000 | 15 | Verify the FTP port can be blocked in Parental Control - Managed Services | Release 13 | RDKM | 1 DOT0 |
35 | TC-RDKB-LIGHTTPD-1001 | 12 | Verify lighttpd version upgrade | Release 19 | RDKM | 1 DOT0 |
36 | TC-RDKB-PC-MNG-SERVICES-1001 | 17 | Test to Verify the HTTP port can be blocked in Parental Control - Managed Services | Release 21 | RDKM | 1 DOT0 |
37 | TC-RDKB-PC-MNG-SERVICES-CUS-FW-1000 | 23 | Verify the FTP port can be blocked in Parental Control - Managed Services when firewall setting is configured to 'Custom Security' | Release 22 | RDKM | 1 DOT0 |
Released Automatics Self Heal Related Test Cases - 12
Test Case Type | Total Count |
---|---|
1 DOT0 | 12 |
3 DOT0 | 0 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-SELF-HEAL-PING-SERVER-3001 | 7 | List of servers (URIs) and minimum set of servers to ping MUST be configurable via bootfile or Comcast SNMP OIDs | Release 4 | RDKM | 1 DOT0 |
2 | TC-RDKB-SELF-HEAL-4000 | 22 | Test to verify Self healing feature must be enabled by default using snmp mibs | Release 4 | RDKM | 1 DOT0 |
3 | TC-RDKB-SELF-HEAL-4011 | 12 | Verify wan link heal check after firmware upgrade | Release 4 | RDKM | 1 DOT0 |
4 | TC-RDKB-SELF-HEAL-ACW-3001 | 5 | Average usage must be computed over 15 minute time window | Release 4 | RDKM | 1 DOT0 |
5 | TC-RDKB-SELF-HEAL-4003 | 6 | Test to validate if the cron scheduling on ATOM side whether it is having LogUploadFrequency value _TR181 | Release 4 | RDKM | 1 DOT0 |
6 | TC-RDKB-AGGRESSIVE_SELF_HEAL-1002 | 24 | Verify critical & non-critical processes are handling independently in SelfHealAggressive log file and SelfHeal file | Release 4 | RDKM | 1 DOT0 |
7 | TC-RDKB-SELF-HEAL-4002 | 6 | Test to Validate if corrective action is taken (eRouter reboot only) when DNS resolve test failure case | Release 4 | RDKM | 1 DOT0 |
8 | TC-RDKB-SELF-HEAL-4009 | 8 | Verify that the MSO is able to configure the resource usage time window via SNMP | Release 4 | RDKM | 1 DOT0 |
9 | TC-RDKB-SELF-HEAL-4010 | 5 | Verification of setting invalid values to avgCPUThreshold and avgMemoryThreshold using SNMP MIB | Release 4 | RDKM | 1 DOT0 |
10 | TC-RDKB-SELF-HEAL-4005 | 8 | Test to verify self heal diagnostic mode test scenarios using WebPA parameter | Release 5 | RDKM | 1 DOT0 |
11 | TC-RDKB-SELF-HEAL-4004 | 15 | Test to verify diagnostic mode test scenarios | Release 5 | RDKM | 1 DOT0 |
12 | TC-RDKB-SELF-HEAL-4001 | 32 | Test to Verify default Self Heal configuration and configuration persistence after reboot | Release 8 | RDKM | 1 DOT0 |
Released Automatics System Related Test Cases - 219
Test Case Type | Total Count |
---|---|
1 DOT0 | 176 |
3 DOT0 | 46 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-RFC-1001 | 2 | Verify configurable RFC check-in trigger using tr181 parameter | Release 2 | RDKM | 1 DOT0 |
2 | TC-RDKB-PARODUS-1005 | 9 | Verify parodus and webpa uptimes in bootup sequence | Release 2 | RDKM | 1 DOT0 |
3 | TC-RDKB-WH-SNMP-1000 | 12 | Verify get SNMP for warehouse OIDs | Release 3 | RDKM | 1 DOT0 |
4 | TC-RDKB-NW-CONNECTIVITY-1010 | 17 | Verify whether the invalid ping servers and valid ping servers are set by SNMP and failure messages are logged when the ping fails in selfHeal log | Release 3 | RDKM | 1 DOT0 |
5 | TC-RDKB-PARODUS-1006 | 19 | Verify themis curl to acquire JWT for parodus | Release 3 | RDKM | 1 DOT0 |
6 | TC-RDKB-PARODUS-1008 | 12 | Verify Integrate parodus2ccsp with Yocto | Release 3 | RDKM | 1 DOT0 |
7 | TC-RDKB-PARODUS-1007 | 18 | Verify Integrate parodus2ccsp with Yocto | Release 3 | RDKM | 1 DOT0 |
8 | TC-RDKB-PARODUS-1009 | 10 | Test to verify configurable parodus reboot reason | Release 3 | RDKM | 1 DOT0 |
9 | TC-RDKB-PARODUS-ENBL-1004 | 8 | Verify Webpa commands when Parodus is Enabled | Release 3 | RDKM | 1 DOT0 |
10 | TC-RDKB-PARODUS-NOPOLL-1001 | 8 | Test to verify parodus nopoll | Release 3 | RDKM | 1 DOT0 |
11 | TC-RDKB-SYSTEM-1021 | 5 | Test to verify removal of telnet daemon | Release 3 | RDKM | 1 DOT0 |
12 | TC-RDKB-SYSTEM-5002 | 7 | Verify logging for Harvester and LMLite reports | Release 3 | RDKM | 1 DOT0 |
13 | TC-RDKB-SYSTEM-5007 | 3 | Verify Xconf default value,Hardware version,Linux kernel upgrade version from logs | Release 3 | RDKM | 1 DOT0 |
14 | TC-RDKB-REBOOT-5001 | 6 | Test case to verify the docsdevresetnow mib functionality | Release 3 | RDKM | 1 DOT0 |
15 | TC-RDKB-FS-LAYOUT-1001 | 2 | nvram file system layout validation | Release 3 | RDKM | 1 DOT0 |
16 | TC-RDKB-FS-LAYOUT-1002 | 2 | nvram2 file system layout validation | Release 3 | RDKM | 1 DOT0 |
17 | TC-RDKB-FS-LAYOUT-1003 | 3 | tmp file system layout validation | Release 3 | RDKM | 1 DOT0 |
18 | TC-RDKB-FS-LAYOUT-1004 | 3 | minidumps file system layout validation | Release 3 | RDKM | 1 DOT0 |
19 | TC-RDKB-FS-LAYOUT-1005 | 2 | rdklogs file system layout validation | Release 3 | RDKM | 1 DOT0 |
20 | TC-RDKB-FS-LAYOUT-1006 | 3 | cron and etc file system layout validation | Release 3 | RDKM | 1 DOT0 |
21 | TC-RDKB-FS-LAYOUT-1007 | 2 | dhcp_static_hosts file system layout validation | Release 3 | RDKM | 1 DOT0 |
22 | TC-RDKB-FS-LAYOUT-1008 | 2 | xupnp file system layout validation | Release 3 | RDKM | 1 DOT0 |
23 | TC-RDKB-FS-LAYOUT-1009 | 2 | Dibbler file system layout validation | Release 3 | RDKM | 1 DOT0 |
24 | TC-RDKB-PARODUS-1001 | 3 | Removal of parodus start shell script changes from yocto | Release 3 | RDKM | 1 DOT0 |
25 | TC-RDKB-SYSTEM-1031 | 10 | Verify no zombie dnsmasq process detected by self heal | Release 3 | RDKM | 1 DOT0 |
26 | TC-RDKB-SYSTEM-5502 | 2 | Verify the data only partition /nvram is mounted as non-executable | Release 3 | RDKM | 1 DOT0 |
27 | TC-RDKB-SYSTEM-5503 | 2 | Verify the data only partition /nvram2 is mounted as non-executable | Release 3 | RDKM | 1 DOT0 |
28 | TC-RDKB-SYSTEM-1101 | 1 | Verify DBus - Overly permissive system setting | Release 3 | RDKM | 1 DOT0 |
29 | TC-RDKB-CPU_AND_MEMORY-1001 | 1 | Capture CPU and Memory usage individually per process based on request | Release 4 | RDKM | 1 DOT0 |
30 | TC-RDKB-SYSTEM-7020 | 4 | Verify disk usage, up-time, top, date and disk space response from Arm Console | Release 4 | RDKM | 1 DOT0 |
31 | TC-RDKB-LIGHTTPD-1002 | 2 | Verify lighttpd version | Release 4 | RDKM | 1 DOT0 |
32 | TC-RDKB-WH-SNMP-1003 | 4 | Verify snmp set for warehouse DOCSIS OID | Release 4 | RDKM | 1 DOT0 |
33 | TC-RDKB-PARODUS-RECON-1001 | 3 | Verify parodus restarted by self heal when killed | Release 4 | RDKM | 1 DOT0 |
34 | TC-RDKB-SYSTEM-1001 | 5 | dnsmasq version check in RDKB devices | Release 4 | RDKM | 1 DOT0 |
35 | TC-RDKB-WH-SNMP-1007 | 27 | Warehouse test coverage for Wireless OIDs - Sequence strict | Release 4 | RDKM | 1 DOT0 |
36 | TC-RDKB-SYSTEM-5001 | 2 | Verify stanTC-RDKB-PARODUS-ENBL-1003dard timestamp format is used in RDKB logging | Release 4 | RDKM | 1 DOT0 |
37 | TC-RDKB-PARODUS-1010 | 6 | Verify parodus reconnect with jitter algorithm | Release 4 | RDKM | 1 DOT0 |
38 | TC-RDKB-PARODUS-1011 | 23 | Drop process privileges (RDK-B Platforms) | Release 4 | RDKM | 1 DOT0 |
39 | TC-RDKB-PARODUS-ENBL-1003 | 17 | Verify Enable Parodus in log messages | Release 4 | RDKM | 1 DOT0 |
40 | TC-RDKB-SYSTEM-5515 | 8 | Verify the logging of WebPA telemetry data in the Parodus Logs | Release 4 | RDKM | 1 DOT0 |
41 | TC-RDKB-SYSTEM-3043 | 4 | Verify the stress testing for Encrypted file copying from /nvram/ to /opt/secure/ | Release 4 | RDKM | 1 DOT0 |
42 | TC-RDKB-SYSTEM-3048 | 12 | Test case to verify whether DNS queries follow strict ordering or not | Release 4 | RDKM | 1 DOT0 |
43 | TC-RDKB-AGGRESSIVE_SELF_HEAL-1001 | 13 | Verify Aggressive selfheal | Release 4 | RDKM | 1 DOT0 |
44 | TC-RDKB-REBOOT-1015 | 6 | Test to verify abort reboot after reboot initiates | Release 4 | RDKM | 1 DOT0 |
45 | TC-RDKB-SYSCFG-1000 | 12 | Read syscfg parameters encrypted DB | Release 4 | RDKM | 1 DOT0 |
46 | TC-RDKB-PRO-INFO-5001 | 17 | Verify the sensitive keywords are removed from iptables | Release 4 | RDKM | 1 DOT0 |
47 | TC-RDKB-FACTORYRBT-1002 | 25 | Factory reboot scenario using WebPA | Release 4 | RDKM | 1 DOT0 |
48 | TC-RDKB-FACTORYRBT-1003 | 25 | Factory reboot scenario using SNMP | Release 4 | RDKM | 1 DOT0 |
49 | TC-RDKB-SYSTEM-1026 | 12 | Verifiy the minidump generated during process crash is uploaded to S3/crash portal | Release 4 | RDKM | 1 DOT0 |
50 | TC-RDKB-REBOOT-1011 | 7 | Perform reboot with device component, delay and reboot reason | Release 4 | RDKM | 1 DOT0 |
51 | TC-RDKB-SYSTEM-5050 | 3 | Verify whether multiple udhcpc.script error messages getting printed in Consolelog.txt | Release 4 | RDKM | 1 DOT0 |
52 | TC-RDKB-WAREHOUSE-1001 | 10 | Verify warehouse staging using xconf method | Release 4 | RDKM | 1 DOT0 |
53 | TC-RDKB-WAREHOUSE-1002 | 10 | Verify warehouse staging using webpa method | Release 4 | RDKM | 1 DOT0 |
54 | TC-RDKB-REBOOT-1014 | 8 | Verify Abort Reboot after successful CDL | Release 4 | RDKM | 1 DOT0 |
55 | TC-RDKB-PRO-INFO-5002 | 17 | Verify the sensitive keywords are removed from ip6tables | Release 4 | RDKM | 1 DOT0 |
56 | TC-RDKB-SYSTEM-PING-IPRUT-5001 | 4 | Verify Add IP from ATOM side private network using Ping and ip route | Release 4 | RDKM | 1 DOT0 |
57 | TC-RDKB-CPUPROC-1000 | 14 | Test to verify CPU Performance Analysis - Process Analyzer | Release 4 | RDKM | 1 DOT0 |
58 | TC-RDKB-REBOOT-5003 | 8 | Verify interface reboot due to brlan0 and verify logs in SelfHeal.txt.0 file | Release 4 | RDKM | 1 DOT0 |
59 | TC-RDKB-FACTORYRESET_REBOOT-1001 | 49 | Test to verify default values after factory reset and value persistance after reboot | Release 4 | RDKM | 1 DOT0 |
60 | TC-RDKB-CCSP-1000 | 6 | Verify service configuration feature is disabled | Release 4 | RDKM | 1 DOT0 |
61 | TC-RDKB-REBOOT-1013 | 24 | Verify device gives response as invalid request when there is no reboot is pending and abort reboot command is sent | Release 4 | RDKM | 1 DOT0 |
62 | TC-RDKB-SYSTEM-9010 | 17 | Verify ccsp-webpa-adapter | Release 4 | RDKM | 1 DOT0 |
63 | TC-RDKB-SYSTEM-3042 | 21 | Verify that /opt/secure folder is encrypted | Release 4 | RDKM | 1 DOT0 |
64 | TC-RDKB-CPU_AND_MEMORY-1002 | 6 | Capture CPU and Memory usage individually per process based on request | Release 4 | RDKM | 1 DOT0 |
65 | TC-RDKB-SYSTEM-1028 | 5 | Test to verify CPU usage | Release 4 | RDKM | 1 DOT0 |
66 | TC-RDKB-SYSTEM-5003 | 7 | Verify Webpa Notifications on Firmware Upgrade | Release 5 | RDKM | 1 DOT0 |
67 | TC-RDKB-SYSTEM-DIBBLER-1001 | 2 | To check the dibbler version | Release 5 | RDKM | 1 DOT0 |
68 | TC-RDKB-FS-LAYOUT-1010 | 3 | Test to verify resolv.conf file system layout validation and DNS value | Release 5 | RDKM | 1 DOT0 |
69 | TC-RDKB-FACTORYRBT-1006 | 9 | Test to verify Default SSID and Password after Factory Resetting Router through WebPA | Release 5 | RDKM | 1 DOT0 |
70 | TC-RDKB-FACTORYRBT-1007 | 6 | Verify Default SSID and Password after Factory Resetting WiFi through WebPA object | Release 5 | RDKM | 1 DOT0 |
71 | TC-RDKB-REBOOT-1012 | 12 | Verify device provides notification via WebPA to indicate that reboot is about to occur after firmware upgrade and adds delay to the reboot | Release 5 | RDKM | 1 DOT0 |
72 | TC-RDKB-SYSTEM-IPSET-1008 | 17 | Verify upgrade ipset to v.6.34 | Release 5 | RDKM | 1 DOT0 |
73 | TC-RDKB-EXEC-FILE-CHK-1001 | 10 | Verify whether user is able to run user or manual script even after giving 777 permission | Release 5 | RDKM | 1 DOT0 |
74 | TC-RDKB-AUTOREBOOT-1000 | 12 | Test to verify the default parameter values of Auto reboot | Release 5 | RDKM | 1 DOT0 |
75 | TC-RDKB-REBOOT-5005 | 8 | Test to Verify RDKB devices patches kernel - after reboot | Release 5 | RDKM | 1 DOT0 |
76 | TC-RDKB-THERMAL_FAN-1000 | 11 | Device shall have the ability to retrieve the fan diagnostics via WebPA | Release 5 | RDKM | 1 DOT0 |
77 | TC-RDKB-WIFI-5021 | 8 | Test to verify number of allowed clients for Public Secure and open SSID can be writable using WebPA/TR69 and changes are logged in WebPA/TR69 log file | Release 5 | RDKM | 1 DOT0 |
78 | TC-RDKB-BUSYBOX-UTILITY-1001 | 7 | Validate Busybox utility tar | Release 5 | RDKM | 1 DOT0 |
79 | TC-RDKB-NMI_REBOOT-1001 | 16 | Verify NMI mtdoops& SRAM support for BCM ARM processors to capture system state during watchdog reset | Release 5 | RDKM | 1 DOT0 |
80 | TC-RDKB-BUSYBOX_UTILITY-1003 | 6 | Verify the installed busy box utilities on CM side | Release 5 | RDKM | 1 DOT0 |
81 | TC-RDKB-RM-MODULE-1002 | 19 | Verify removal of SoundKernel, mtp-tools, libsven | Release 6 | RDKM | 1 DOT0 |
82 | TC-RDKB-RM-MODULE-1001 | 10 | Verify removal of SoundKernel, mtp-tools, libsven | Release 6 | RDKM | 1 DOT0 |
83 | TC-RDKB-SYSTEM-1023 | 5 | Test to verify ssh banners from sshbanner.txt file and command execution | Release 6 | RDKM | 1 DOT0 |
84 | TC-RDKB-REVSSH-1001 | 9 | Verify Reverse SSH connection | Release 6 | RDKM | 1 DOT0 |
85 | TC-RDKB-GBPAD-1001 | 5 | Test to Verify mini dump creation and upload to crash portal for the process PandM | Release 7 | RDKM | 1 DOT0 |
86 | TC-RDKB-GBPAD-1005 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspPsm | Release 7 | RDKM | 1 DOT0 |
87 | TC-RDKB-GBPAD-1007 | 5 | Test to Verify mini dump creation and upload to crash portal for the process webpa | Release 7 | RDKM | 1 DOT0 |
88 | TC-RDKB-GBPAD-1008 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspWifiAgent | Release 7 | RDKM | 1 DOT0 |
89 | TC-RDKB-GBPAD-1011 | 5 | Test to Verify mini dump creation and upload to crash portal for the process meshAgent | Release 7 | RDKM | 1 DOT0 |
90 | TC-RDKB-GBPAD-1012 | 5 | Test to Verify mini dump creation and upload to crash portal for the process parodus | Release 7 | RDKM | 1 DOT0 |
91 | TC-RDKB-GBPAD-1006 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspCr | Release 8 | RDKM | 1 DOT0 |
92 | TC-RDKB-REBOOT-5002 | 1 | Verify BootTime using TR-181 Parameter(Device.DeviceInfo.X_RDKCENTRAL-COM_BootTime) | Release 8 | RDKM | 1 DOT0 |
93 | TC-RDKB-GBPAD-1014 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspHotspot | Release 8 | RDKM | 1 DOT0 |
94 | TC-RDKB-GBPAD-1015 | 5 | Test to Verify mini dump creation and upload to crash portal for the process SNMP_SUBAGENT | Release 8 | RDKM | 1 DOT0 |
95 | TC-RDKB-GBPAD-1004 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspTr069 | Release 8 | RDKM | 1 DOT0 |
96 | TC-RDKB-SYSTEM-9008 | 2 | Validate if RDKB SSH client is not accessible via WAN | Release 8 | RDKM | 1 DOT0 |
97 | TC-RDKB-SYSTEM-1102 | 7 | Test case is created as to Enable Disable Feature Via DCM | Release 8 | RDKM | 1 DOT0 |
98 | TC-RDKB-WIFI-FIRM-DWNL-5001 | 25 | Verify the Time frame validation for DUT online | Release 9 | RDKM | 1 DOT0 |
99 | TC-RDKB-SYSTEM-5400 | 4 | Verify Mount options for tmp directory | Release 9 | RDKM | 1 DOT0 |
100 | TC-RDKB-SYSTEM-1029 | 2 | Verify accessibilty for ARM to Atom SSH | Release 9 | RDKM | 1 DOT0 |
101 | TC-RDKB-RBUS-1001 | 8 | Validate device status when rbus is enabled | Release 9 | RDKM | 1 DOT0 |
102 | TC-RDKB-WH-FR-RS-5001 | 19 | Improved testing sequences for RDK-B WIFI warehouse | Release 9 | RDKM | 1 DOT0 |
103 | TC-RDKB-SUBMSK-CHANGE-5001 | 2 | Verify subnet mask range in router mode | Release 9 | RDKM | 1 DOT0 |
104 | TC-RDKB-SYSCFG-1001 | 12 | Verify syscfg parameters after removing unencrypted /nvram/syscfg.db | Release 9 | RDKM | 1 DOT0 |
105 | TC-RDKB-PARODUS-1012 | 11 | Verify themis token fetch by passing Partner-ID as a request header | Release 10 | RDKM | 1 DOT0 |
106 | TC-RDKB-ACS-PERSIST-MESH-1001 | 23 | Verify Private WiFi channel selection (ACS) should remain same post MESH enabled or disabled | Release 10 | RDKM | 1 DOT0 |
107 | TC-RDKB-BINARIES-1004 | 7 | Test to verify Removed or Encrypted Private Keys | Release 10 | RDKM | 1 DOT0 |
108 | TC-RDKB-SWAP-5001 | 10 | Verify the swap memory can be enabled and disabled using ZRAM | Release 11 | RDKM | 1 DOT0 |
109 | TC-RDKB-BOOTSTRAP-1031 | 48 | Test to verify bootstrap configuration with version and update source | Release 11 | RDKM | 1 DOT0 |
110 | TC-RDKB-RFC-1202 | 12 | Test to Verify that RFC requests contain accountId Unknown on Every powercycle | Release 11 | RDKM | 1 DOT0 |
111 | TC-RDKB-BOOTSTRAP-1030 | 48 | Test to verify bootstrap configuration and version | Release 11 | RDKM | 1 DOT0 |
112 | TC-RDKB-SYSTEM-1033 | 10 | Test to verify reporting of RFC feature enable | Release 12 | RDKM | 1 DOT0 |
113 | TC-RDKB-WIFI-REBOOT-1001 | 5 | Verification of any kind of crash in device if Multiple WiFi reset triggerred | Release 12 | RDKM | 1 DOT0 |
114 | TC-RDKB-RFC-1006 | 10 | Verify Reboot required RFC change causes scheduled reboot in maintenance window | Release 12 | RDKM | 1 DOT0 |
115 | TC-RDKB-RFC-1005 | 11 | To verify RFC versioning support | Release 12 | RDKM | 1 DOT0 |
116 | TC-RDKB-RFC-SNMP-1001 | 7 | Verify RFC control of SNMPv2 | Release 12 | RDKM | 1 DOT0 |
117 | TC-RDKB-RFC-DATABASE-1001 | 15 | Validate RFC default and enabled values in defaults/database file | Release 12 | RDKM | 1 DOT0 |
118 | TC-RDKB-RFC-1003 | 12 | Verify RFC processing log messages present in dcmrfc.log for posted parameter value | Release 12 | RDKM | 1 DOT0 |
119 | TC-RDKB-RFC-1201 | 9 | Test to Verify that xconf requests contain accountId | Release 12 | RDKM | 1 DOT0 |
120 | TC-RDKB-RFC-1200 | 25 | Test to Verify that xconf requests contain accountId | Release 12 | RDKM | 1 DOT0 |
121 | TC-RDKB-DEFAULT-VALUES-1001 | 97 | Verify the default values in the device after factory resetting by WebPA | Release 12 | RDKM | 1 DOT0 |
122 | TC-RDKB-RFC_FEATUREINSTANCE-1001 | 9 | Verify RFC reports feature instance | Release 13 | RDKM | 1 DOT0 |
123 | TC-RDKB-BOOTSTRAP-1029 | 193 | Verify bootstrap configuration | Release 13 | RDKM | 1 DOT0 |
124 | 3DOT0-TC-RDKB-DEFAULT-VALUES-1002 | 15 | Test case to validate default values after FR. | Release 14 | RDKM | 3 DOT0 |
125 | 3DOT0-TC-RDKB-DHCP_CONFIG-1001 | 13 | Testcase to verify WAN DHCPv6 deriving the LAN side ip configuration | Release 14 | RDKM | 3 DOT0 |
126 | 3DOT0-TC-RDKB-DISABLE_TR181-1001 | 13 | Verify tr181 parameters are not supported for features disabled during build time | Release 14 | RDKM | 3 DOT0 |
127 | 3DOT0-TC-RDKB-LOGUPLOAD-1007 | 12 | Test to Verify bootup logupload is happening via appropriate location | Release 14 | RDKM | 3 DOT0 |
128 | 3DOT0-TC-RDKB-NOTIFY-1001 | 13 | Test case to verify notify component to store notification list in a file for recovery after crash | Release 14 | RDKM | 3 DOT0 |
129 | 3DOT0-TC-RDKB-PARODUS_BREADKPAD_1000 | 5 | Verify Parodus breakpad integration in generic way in RDKB | Release 14 | RDKM | 3 DOT0 |
130 | 3DOT0-TC-RDKB-PARTNERIDCHECK-1001 | 16 | Testcase for testing partnerId for the devices | Release 14 | RDKM | 3 DOT0 |
131 | 3DOT0-TC-RDKB-RED-RECOVERY-CERT-1001 | 3 | Check the certificate presents and validity | Release 14 | RDKM | 3 DOT0 |
132 | 3DOT0-TC-RDKB-SAFEBROWSE-1002 | 10 | Test case to Verify the safebrowsing configuration using tr181 commands | Release 14 | RDKM | 3 DOT0 |
133 | 3DOT0-TC-RDKB-SPEEDTEST-1009 | 12 | CPE Speed test changes to disable RDKB stats collection prior to speedtest execution | Release 14 | RDKM | 3 DOT0 |
134 | 3DOT0-TC-RDKB-SYSTEM-1027 | 11 | Verifiy the minidump generated during process crash on atom console is uploaded to S3/crash portal and failover upload to new crashportal url | Release 14 | RDKM | 3 DOT0 |
135 | 3DOT0-TC-RDKB-SYSTEM-1032 | 4 | Test case to verify xsmartd deprecation | Release 14 | RDKM | 3 DOT0 |
136 | 3DOT0-TC-RDKB-SYSTEMD-1001 | 3 | Testcase to verify randomFileUpload service is running | Release 14 | RDKM | 3 DOT0 |
137 | 3DOT0-TC-RDKB-MESH-1101 | 6 | Verify API failures are not seen in Meshlogs | Release 14 | RDKM | 3 DOT0 |
138 | 3D0T0-TC-RDKB-OPENSSLOLDERTLSREMOVE-1001 | 8 | Testcase to verify whether the older tls versions are disabled properly | Release 14 | RDKM | 3 DOT0 |
139 | 3DOT0-TC-RDKB-UPNP_XPKI_CERTS-1001 | 14 | Testcase to verify UPnP device protection modifications. | Release 14 | RDKM | 3 DOT0 |
140 | 3DOT0-TC-RDKB-KVFEATURE-1001 | 18 | Test to verify if KV Feature- Radio Resource Management configuration reflect at driver layer | Release 16 | RDKM | 3 DOT0 |
141 | 3DOT0-TC-RDKB-PARTNER-WEBCONFIG-1001 | 14 | Verify partner specific Webconfig URL | Release 16 | RDKM | 3 DOT0 |
142 | 3DOT0-TC-RDKB-SECURITYNONROOTRDKSSA-1001 | 13 | Validation of RDKSSA cli hardening - Drop process privileges | Release 16 | RDKM | 3 DOT0 |
143 | 3DOT0-TC-RDKB-SECURITYNONROOTRDKSSA-1002 | 11 | Validation of RDKSSA cli hardening - Drop process privileges | Release 16 | RDKM | 3 DOT0 |
144 | 3DOT0-TC-RDKB-WEBPA-1010 | 13 | Testcase to unify TR-181 firmware name across platforms | Release 16 | RDKM | 3 DOT0 |
145 | 3DOT0-TC-RDKB-HTTPS_RDM_DOWNLOADS-1001 | 15 | Testcase to verify HTTPS support for RDM downloads | Release 16 | RDKM | 3 DOT0 |
146 | 3DOT0-TC-RDKB-LONG_TERM_CERTS-1001 | 19 | Issue Long Term TLS Certs for EOL Platforms | Release 16 | RDKM | 3 DOT0 |
147 | 3DOT0-TC-RDKB-OFFCHANNELSCAN-1001 | 21 | 5GHz WiFi Off-Channel Scan support | Release 16 | RDKM | 3 DOT0 |
148 | 3DOT0-TC-RDKB-SM-PAUSE-1001 | 24 | SM Stats disablement during speedtest | Release 16 | RDKM | 3 DOT0 |
149 | 3DOT0-TC-RDKB-WAN_FAILOVER-1000 | 20 | WAN Failover during Tech-trials to test during docsis lindown | Release 16 | RDKM | 3 DOT0 |
150 | 3DOT0-TC-RDKB-LAST-REBOOT-001 | 4 | Stability testcase to check multiple reboot scenario | Release 16 | RDKM | 3 DOT0 |
151 | TC-RDKB-IPV4-PORTFW-2020 | 17 | To verify the port forwarding scenarios and ensure that UDP traffic is not successful when the protocol is set to TCP. | Release 17 | Vodafone | 1 DOT0 |
152 | TC-RDKB-IPV4-PORTFW-2021 | 10 | To verify that port forwarding rule will be retained after reboot. | Release 17 | Vodafone | 1 DOT0 |
153 | TC-RDKB-IPV4-PORTFW-2022 | 33 | To verify the port forwarding scenarios using TCP and UDP protocols. | Release 17 | Vodafone | 1 DOT0 |
154 | TC-RDKB-IPV4-PORTFW-2023 | 8 | Verify port forwarding functionality by setting the source ipv4 address to 0.0.0.0. | Release 17 | Vodafone | 1 DOT0 |
155 | TC-RDKB-IPV4-PORTFW-2024 | 13 | Verify Port Range Forwarding - Disable specific entry in port forwarding. | Release 17 | Vodafone | 1 DOT0 |
156 | TC-RDKB-IPV4-PORTFW-2025 | 10 | To verify that port forwarding rule will be retained after 10 times reboot and the iperf3 traffic is successful after each reboot. | Release 17 | Vodafone | 1 DOT0 |
157 | TC-RDKB-IPV4-PORTFW-2029 | 9 | Test case to verify the product MUST support user configurable port forwarding. | Release 17 | Vodafone | 1 DOT0 |
158 | TC-RDKB-IPV4-PORTFW-2030 | 8 | Test case to verify the product MUST support deletion of port forwarding. | Release 17 | Vodafone | 1 DOT0 |
159 | TC-RDKB-IPV4-PORTFW-2047 | 10 | To verify the Port forwarding and DMZ rules after performing reset. | Release 17 | Vodafone | 1 DOT0 |
160 | 3DOT0-TC-RDKB-FR-DEFAULT-1000 | 13 | Testcase to check Factory reset Stability | Release 17 | RDKM | 3 DOT0 |
161 | 3DOT0-TC-RDKB-T2-SYS-INIT-1001 | 20 | Validate SYS Int broadband markers | Release 18 | RDKM | 3 DOT0 |
162 | 3DOT0-TC-RDKB-WAN-COUNT-1001 | 24 | Testcase to verify WAN speed count via lmlite in required format in DOCSIS mode | Release 18 | RDKM | 3 DOT0 |
163 | 3DOT0-TC-RDKB-MOCA-1007 | 28 | Ability to restart MoCA module/interface | Release 18 | RDKM | 3 DOT0 |
164 | 3DOT0-TC-RDKB-TR181-STABILITY-1000 | 2 | Testcase to check the stability of TR181 parameters in the DUT | Release 18 | RDKM | 3 DOT0 |
165 | 3DOT0-TC-RDKB-IDM-1001 | 35 | Testcase to validate whether InterDeviceManager built on dut devices | Release 19 | RDKM | 3 DOT0 |
166 | 3DOT0-TC-RDKB-SYSTEM-1002 | 10 | Testcase to verify CR has support to notify Component Ready Event | Release 19 | RDKM | 3 DOT0 |
167 | TC-RDKB-RFC-MTLS-1001 | 16 | Test case to verify mutual TLS feature for log upload. | Release 19 | RDKM | 1 DOT0 |
168 | TC-RDKB-NTP-1004 | 17 | Verify Single build should include all the NTP FQDNs for the device. | Release 19 | RDKM | 1 DOT0 |
169 | TC-RDKB-SYNDICATION-WAN-SSH-1001 | 11 | To verify WAN-side SSH support in single build | Release 19 | RDKM | 1 DOT0 |
170 | TC-RDKB-DHCP-IPV6-1001 | 8 | Verify DHCPv6 address in Ethernet connected client on changing Min Address and Max Address | Release 19 | RDKM | 1 DOT0 |
171 | TC-RDKB-EROUTER-3000 | 4 | To validate if the erouter can operate on Ipv6 mode | Release 19 | Vodafone | 1 DOT0 |
172 | TC-RDKB-EROUTER-3001 | 4 | To validate if the erouter can operate on Dual Stack mode | Release 19 | Vodafone | 1 DOT0 |
173 | TC-RDKB-EROUTER-3002 | 5 | To verify IPv6 firewall can be enable/disable via dmcli commands and verify the status is reflecting the same in snmp | Release 19 | Vodafone | 1 DOT0 |
174 | TC-RDKB-IPV4-2057 | 8 | WiFi MAC Filter - Deny. | Release 19 | Vodafone | 1 DOT0 |
175 | TC-RDKB-IPV4-2059 | 4 | Verify DHCP start range ,end range and lease period are user configurable. | Release 19 | Vodafone | 1 DOT0 |
176 | TC-RDKB-IPV4-2060 | 8 | Change the LAN DHCP pool on the fly and check if the connected clients get the IP address from DHCP Pool and check persistency | Release 19 | Vodafone | 1 DOT0 |
177 | TC-RDKB-IPV4-2061 | 5 | IPv4 address for the LAN client is not possible to reserve same as the DUT's LAN gateway inteface | Release 19 | Vodafone | 1 DOT0 |
178 | TC-RDKB-IPV4-2062 | 5 | Verify IPv4 address for the LAN client is not possible to reserve if it is 0.0.0.0. | Release 19 | Vodafone | 1 DOT0 |
179 | TC-RDKB-IPV4-2064 | 9 | Verify the DHCPv4 enable/disable functionality | Release 19 | Vodafone | 1 DOT0 |
180 | TC-RDKB-IPV4-2065 | 5 | Verify Device should provide DHCPv4 addresses after changing the LAN subnet range. | Release 19 | Vodafone | 1 DOT0 |
181 | TC-RDKB-IPV4-2066 | 4 | Add rule in DHCP with invalid MAC address and IP address. | Release 19 | Vodafone | 1 DOT0 |
182 | TC-RDKB-IPV4-2068 | 9 | To Verify 5GHz: Default SSID, Protection mode and encryption mode. | Release 19 | Vodafone | 1 DOT0 |
183 | TC-RDKB-IPV4-2070 | 2 | Add rule in DHCP with valid MAC address and IP address. | Release 19 | Vodafone | 1 DOT0 |
184 | TC-RDKB-IPV4-2071 | 5 | Add rule in DHCP with valid MAC address and IP address. | Release 19 | Vodafone | 1 DOT0 |
185 | TC-RDKB-IPV4-2074 | 2 | Dmcli report to make sure all WiFi Device loaded | Release 19 | Vodafone | 1 DOT0 |
186 | TC-RDKB-IPV4-2075 | 5 | To verify client get IP from CM provisioning while in bridge mode. | Release 19 | Vodafone | 1 DOT0 |
187 | TC-RDKB-WIFITEST-2000 | 6 | Verify that the user can enable/disable all SSIDs of 5G radio Ticket | Release 19 | Vodafone | 1 DOT0 |
188 | TC-RDKB-WIFITEST-2001 | 5 | Wi-Fi Auto and Manual channel selection for 5Ghz | Release 19 | Vodafone | 1 DOT0 |
189 | TC-RDKB-WIFITEST-2002 | 5 | Wi-Fi Auto and Manual channel selection for 2.4Ghz | Release 19 | Vodafone | 1 DOT0 |
190 | TC-RDKB-EROUTER-DNS-3005 | 5 | Verify IPv4 -DNS query from LAN ipv4 host The eRouter must be able to respond to an A DNS queries with its own IPv4 address | Release 19 | Vodafone | 1 DOT0 |
191 | TC-RDKB-CC-TEAMS-TEST-1000 | 7 | Verify the network connectivity and performance of microsoft teams from a client device | Release 20 | RDKM | 1 DOT0 |
192 | TC-RDKB-BUSYBOX-UTILITY-1002 | 4 | Validate Busybox utility tftp | Release 20 | RDKM | 1 DOT0 |
193 | 3DOT0-TC-RDKB-NTP-1007 | 53 | Verify devices convey the Unified Reliable Time Status | Release 20 | RDKM | 3 DOT0 |
194 | 3DOT0-TC-RDKB-RBUS-PUBLISH-1000 | 14 | Verify publishing RBUS event(Device.WiFi.Events.Frames.Mgmt) for management and association frames from onewifi | Release 20 | RDKM | 3 DOT0 |
195 | 3DOT0-TC-RDKB-RBUSCLI-1002 | 12 | Automation task for Backport Wildcard Support from RBUS to CCSP | Release 20 | RDKM | 3 DOT0 |
196 | TC-RDKB-SELF-HEAL-TELEMETRY-1001 | 23 | Test to Verify that the device monitors its resource usage (CPU Usage ) averaged over a configurable time window | Release 21 | RDKM | 1 DOT0 |
197 | TC-RDKB-RMT-MGNT-UI-CHK-1002 | 12 | Verify Admin UI of the gateway using WAN IP under remote management in wifi 2.4Ghz client | Release 22 | RDKM | 1 DOT0 |
198 | TC-RDKB-RMT-MGNT-UI-CHK-1003 | 12 | Verify Admin UI of the gateway using WAN IP under remote management in 5Ghz wifi client | Release 22 | RDKM | 1 DOT0 |
199 | TC-RDKB-WEBUI-SECURITY_CLIENT-1001 | 13 | To verify client connectivity in WPA2-Personal,WPA-WPA2-Personal and Open modes | Release 22 | RDKM | 1 DOT0 |
200 | TC-RDKB-WEBUI-SECURITY_CLIENT-1002 | 13 | To verify client connectivity in WPA2-Personal,WPA-WPA2-Personal and Open modes | Release 22 | RDKM | 1 DOT0 |
201 | TC-RDKB-GBPAD-1017 | 10 | Test to Verify mini dump creation and upload to crash portal for the process trigger | Release 22 | RDKM | 1 DOT0 |
202 | TC-RDKB-GBPAD-1019 | 10 | Test to Verify mini dump creation and upload to crash portal for the process IGD | Release 22 | RDKM | 1 DOT0 |
203 | TC-RDKB-CPUPROC-1001 | 14 | This test case is written as part of validating CPUProcAnalyzer feature | Release 22 | RDKM | 1 DOT0 |
204 | TC-RDKB-NTP-1006 | 7 | Verify New NTP Feature and Partner JSON File Entries | Release 22 | RDKM | 1 DOT0 |
205 | TC-RDKB-UI-5001 | 11 | Verify the gateway should not accept Gateway IP and DNAT IP as Reserved IP | Release 22 | RDKM | 1 DOT0 |
206 | TC-RDKB-PAU-BLK-PAGE-5001 | 6 | Verify the "Pause Block" Page in RDKB uses only HTML rather than PHP | Release 22 | RDKM | 1 DOT0 |
207 | TC-RDKB-HARV-5005 | 13 | Verify the Radio Interface Statistics Harvester Report generation with log messages | Release 23 | RDKM | 1 DOT0 |
208 | TC-RDKB-HARV-6006 | 13 | Check after TTL whether NetworkDevicesTraffic Polling-Reporting Period changes back to defaults when set less than Default TTL Interval | Release 24 | RDKM | 1 DOT0 |
209 | TC-RDKB-SYSTEM-MEM-STRESS-1027 | 7 | Test case to Verify MEM usage, verify when MEM usage reaches threshold value, MEM threshold details gets logged in SelfHeal.txt.0 | Release 24 | RDKM | 1 DOT0 |
210 | 3DOT0-TC-TMT-REBOOT-1000 | 6 | TMT-Reboot Validation | Release 25 | RDKM | 1 DOT0 |
211 | 3DOT0-TC-RDKB-SYSTEM_EVENT-1001 | 14 | To log the sysevent sets happening on the RDKB platforms to better understand the boot time issues and also to have more insight on when the value change happened. | Release 25 | RDKM | 1 DOT0 |
212 | 3DOT0-TC_RDKB_VERIFY_PROCESS_LIST-1000 | 7 | To verify that the major processes are running as expected and there are no duplicates or zombie processes | Release 26 | RDKM | 3DOT0 |
213 | 3DOT0-TC-RDKB-FACTORY_DEFAULT_VALUE-1000 | 12 | To verify the factory default value of WiFi SSID | Release 26 | RDKM | 3DOT0 |
214 | 3DOT0-TC-RDKB-RBUS-1005 | 18 | Implementation of RBUS Publish API to send Raw Data | Release 26 | RDKM | 3DOT0 |
215 | 3DOT0-TC-RDKB-REBOOT-WANREADY-1001 | 14 | Verify wan_ready event and depended processes | Release 26 | RDKM | 3DOT0 |
216 | 3DOT0-TC-RDKB-TMT-FACTORYRESET-1002 | 6 | TMT-Factory reset validation | Release 26 | RDKM | 3DOT0 |
217 | TC-RDKB-PROCESS_COMPONENT_MANAGERS-1000 | 6 | Verify whether CcspPandMSsp, PsmSsp, and CcspLMLite processes are initialized properly | Release 26 | RDKM | 1 DOT0 |
218 | 3DOT0-TC-RDKB-SECURITYMODES_1001 | 2 | Verify supported security modes | Release 27 | RDKM | 3DOT0 |
219 | 3DOT0-TC-RDKB-BOOTSTRAP-URLS-1001 | 10 | Validate Webpa/Xmidt URLs to bootstrap as read-only config | Release 27 | RDKM | 3DOT0 |
220 | TC-RDKB-TELEMETRY-1005 | 10 | Verify Telemetry statistics for captive portal occurence after factory reset | Release 29 | RDKM | 1 DOT0 |
221 | TC-RDKB-WIFI-BRATE-2001 | 13 | Verify Beacon rate of 5Ghz using webpa and dmcli in a,n,ac mode | Release 29 | RDKM | 1 DOT0 |
222 | TC-RDKB-BINARIES-1003 | 16 | To Verify Removed or Encrypted Private Keys in Binaries (CVSS 7.5) in WEB GUI page | Release 29 | RDKM | 1 DOT0 |
Released Automatics Telemetry Related Test Cases - 62
Test Case Type | Total Count |
---|---|
1 DOT0 | 24 |
3 DOT0 | 38 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-TELEMETRY-VER2-1001 | 6 | Verify default values for T2 component TR-181 parameters | Release 3 | RDKM | 1 DOT0 |
2 | TC-RDKB-TELEMETRY-VER2-1002 | 15 | Verify T2 component log files, process and other basic checks | Release 3 | RDKM | 1 DOT0 |
3 | TC-RDKB-TELEMETRY-VER2-1004 | 4 | Verify negative scenarios for Telemetry version 2 | Release 3 | RDKM | 1 DOT0 |
4 | TC-RDKB-TELEMETRY-VER2-1005 | 14 | Verify negative scenarios for Telemetry version 2 | Release 3 | RDKM | 1 DOT0 |
5 | TC-RDKB-TELEMETRY-VER2-1003 | 15 | Verify telemetry 2 configurations persist over a device upgrade | Release 4 | RDKM | 1 DOT0 |
6 | TC-RDKB-TELEMETRY-1004 | 12 | Verify TR-181 message-bus as new data source for telemetry | Release 6 | RDKM | 1 DOT0 |
7 | TC-RDKB-WIFI-TELEMETRY-1004 | 10 | Validate CPU & Memory usage for Maximum Tx&Rx rate | Release 6 | RDKM | 1 DOT0 |
8 | TC-RDKB-WIFI-TELEMETRY-1008 | 13 | Verify enhanced Wi-Fi logging in Telemetry for 2.4ghz public Wi-Fi parameters | Release 6 | RDKM | 1 DOT0 |
9 | TC-RDKB-WIFI-TELEMETRY-1009 | 13 | Verify enhanced Wi-Fi logging in Telemetry for 5ghz Public Wi-Fi parameters | Release 6 | RDKM | 1 DOT0 |
10 | TC-RDKB-TELEMETRYENDPOINT-2250 | 10 | Test to verify Use new telemetry endpoint | Release 6 | RDKM | 1 DOT0 |
11 | TC-RDKB-TELEMETRY-CC-1006 | 12 | Test to verify telemetry Logging for Wi-Fi Connected devices | Release 6 | RDKM | 1 DOT0 |
12 | TC-RDKB-TELEMETRY-CC-1005 | 12 | Test to verify telemetry Logging for Ethernet Connected devices | Release 6 | RDKM | 1 DOT0 |
13 | TC-RDKB-WIFI-TELEMETRY-1005 | 11 | Verify enhanced Wi-Fi logging in Telemetry for 5ghz private Wi-Fi parameters | Release 6 | RDKM | 1 DOT0 |
14 | TC-RDKB-WIFI-TELEMETRY-1001 | 12 | Validate telemetry markers for Maximum Tx&Rx rate for each wifi clients | Release 7 | RDKM | 1 DOT0 |
15 | TC-RDKB-TELEMETRY-1006 | 9 | Verify telemetry/logging for memory fragmentation details | Release 7 | RDKM | 1 DOT0 |
16 | TC-RDKB-GWCONFIG-TLMTRY-5002 | 12 | Verify the telemetry marker & log messages for Gateway Configuration with the different SSID Name set for both 2.4 GHz & 5 GHz Radios | Release 7 | RDKM | 1 DOT0 |
17 | TC-RDKB-GWCONFIG-TLMTRY-5001 | 12 | Verify the telemetry marker & log messages for Gateway Configuration with the same SSID Name set for both 2.4 GHz & 5 GHz Radios | Release 7 | RDKM | 1 DOT0 |
18 | TC-RDKB-WIFI-TELEMETRY-1000 | 10 | Verify enhanced Wifi logging in Telemetry for 2.4ghz private wifi parameters | Release 7 | RDKM | 1 DOT0 |
19 | TC-RDKB-TELEMETRY-1003 | 30 | Verify configurable telemetry tag functionality | Release 8 | RDKM | 1 DOT0 |
20 | TC-RDKB-TMTRY_UPLD_RCVRY-1015 | 30 | Telemetry upload failure recovery | Release 9 | RDKM | 1 DOT0 |
21 | TC-RDKB-NONROOT-T2-1000 | 13 | Verify Running Telemetry 2.0 process as non-root Previllages | Release 11 | RDKM | 1 DOT0 |
22 | TC-RDKB-WIFI-WIFI-RDKB-TELE-5001 | 28 | Verify the RDKB telemetry logs in Gateway connected with Private WiFi,XHS,Xfinity | Release 11 | RDKM | 1 DOT0 |
23 | TC-RDKB-TELEMETRY-1500 | 17 | To Collect network latency and metadata | Release 11 | RDKM | 1 DOT0 |
24 | TC-RDKB-ACTV-TMTRY-5001 | 11 | validate the Activation Journey including various events with log Messages | Release 13 | RDKM | 1 DOT0 |
25 | 3DOT0-TC-RDKB-TELEMETRY-RBUS-1002 | 29 | Test to verify T2 does not do retries when protocol is RBUS_METHOD and allow empty Parameter[] in profiles | Release 16 | RDKM | 3 DOT0 |
26 | 3DOT0-TC-RDKB-MTLS-1005 | 7 | Testcase to verify telemetry 2.0 multiple profile | Release 16 | RDKM | 3 DOT0 |
27 | 3DOT0-TC-RDKB-MTLS-1006 | 9 | Testcase to verify telemetry 2.0 multiple profile | Release 16 | RDKM | 3 DOT0 |
28 | 3DOT0-TC-RDKB-RBUS-1003 | 6 | Add Support to RBUS Subscribe API to get Initial Value | Release 16 | RDKM | 3 DOT0 |
29 | 3DOT0-TC-RDKB-TELEMETRY_WIFI-1001 | 12 | Test case to verify wifihealth markers telemetry 2.0 upload | Release 16 | RDKM | 3 DOT0 |
30 | 3DOT0-TC-RDKB-WEBPA_SIZE_RBUS-1012 | 17 | Verify string size limit increased with RBUS enable. | Release 16 | RDKM | 3 DOT0 |
31 | 3DOT0-TC-RDKB-MESHAGENT-1001 | 33 | Test to verify Telemetry 2.0 - Non CCSP Components |Mesh agent | Release 17 | RDKM | 3 DOT0 |
32 | 3DOT0-TC-RDKB-MTLS-1002 | 7 | Testcase to verify telemetry 2.0 multiple profile | Release 17 | RDKM | 3 DOT0 |
33 | 3DOT0-TC-RDKB-TELEMETRY-1026 | 42 | [Telemetry 2] Short-lived Report Profiles | Release 17 | RDKM | 3 DOT0 |
34 | 3DOT0-TC-RDKB-TELEMETRY-1028 | 29 | [Telemetry Framework] Flexible Reporting Adjustments - Part 1 | Release 17 | RDKM | 3 DOT0 |
35 | 3DOT0-TC-RDKB-TELEMETRY-RBUS-1009 | 29 | [Telemetry Framework] Profile processing changes for reports using RBUS_METHOD | Release 17 | RDKM | 3 DOT0 |
36 | 3DOT0-TC-RDKB-RBUSCLI-1001 | 18 | Executing the RBUSCLI command in Interactive mode | Release 17 | RDKM | 3 DOT0 |
37 | 3DOT0-TC-RDKB-TELEMETRY_ETH-1001 | 41 | Test to verify Telemetry for Ethernet Connected Clients | Release 18 | RDKM | 3 DOT0 |
38 | 3DOT0-TC-RDKB-TELEMETRY-1027 | 44 | Short-lived Report Profiles controls (Failure in S7 can be traced in the open ticket https://ccp.sys.comcast.net/browse/RTAUTO-41820) | Release 18 | RDKM | 3 DOT0 |
39 | 3DOT0-TC-RDKB-TELEMETRY-RBUS-1001 | 29 | Test to verify Support inclusion of rbus event data in T2 reports | Release 18 | RDKM | 3 DOT0 |
40 | 3DOT0-TC-RDKB-TELEMETRY2_RBUS-1001 | 25 | Test case to verify new protocols supported by telemetry 2 | Release 18 | RDKM | 3 DOT0 |
41 | 3DOT0-TC-RDKB-MTLS-1003 | 17 | Test to check that T2 shall use static xPKI certs available in firmware whenever dynamic xPKI certs are not available. | Release 19 | RDKM | 3 DOT0 |
42 | 3DOT0-TC-RDKB-RBUS-MP-RPLMT-1001 | 17 | Verify profile replacement check in RBUS mode | Release 20 | RDKM | 3 DOT0 |
43 | 3DOT0-TC-RDKB-TELEMETRY_WIFI-1002 | 22 | Test to verify the 2.4ghz and 5ghz channel values between telemetry and wifi health | Release 20 | RDKM | 3 DOT0 |
44 | 3DOT0-TC-RDKB-RBUS-T2-MP-1001 | 25 | Verify updating profiles with different configurations like ReportingInterval, ActivationTimeOut. | Release 20 | RDKM | 3 DOT0 |
45 | 3DOT0-TC-TELEMETRY-V2-002 | 7 | Testcase to verify telemetry 2.0 multiple profile | Release 21 | RDKM | 3 DOT0 |
46 | 3DOT0-TC-TELEMETRY-V2-004 | 9 | Same ReportingIntervals and ActivationTimeOut check | Release 21 | RDKM | 3 DOT0 |
47 | 3DOT0-TC-TELEMETRY-V2-023 | 8 | Verify Profile Name check | Release 21 | RDKM | 3 DOT0 |
48 | 3DOT0-TC-TELEMETRY-V2-015 | 6 | Telemetry data Model check | Release 21 | RDKM | 3 DOT0 |
49 | 3DOT0-TC-TELEMETRY-V2-003 | 7 | Different ReportingIntervals and ActivationTimeOut check | Release 21 | RDKM | 3 DOT0 |
50 | 3DOT0-TC-TELEMETRY-V2-005 | 8 | Profile Deletion Check | Release 21 | RDKM | 3 DOT0 |
51 | 3DOT0-TC-TELEMETRY-V2-018 | 8 | Profile persist after Reboot | Release 21 | RDKM | 3 DOT0 |
52 | 3DOT0-TC-TELEMETRY-V2-1024 | 19 | Test to verify telemetry2_0 process with non-root privilege | Release 22 | RDKM | 3 DOT0 |
53 | 3DOT0-TC-TELEMETRY-V2-024 | 7 | Telemetry t2 negative checks | Release 22 | RDKM | 3 DOT0 |
54 | 3DOT0-TC-TELEMETRY-V2-1031 | 11 | Test to verify T2 Ad hoc Checks | Release 22 | RDKM | 3 DOT0 |
55 | 3DOT0-TC-RDKB-RBUS-T2-SWP-1001 | 17 | Verify if T2 component supports more than 800 parameters per profile | Release 23 | RDKM | 3 DOT0 |
56 | 3DOT0-TC-TELEMETRY-V2-001 | 10 | Test case to verify telemetry 2.0 with multiple profile | Release 25 | RDKM | 3 DOT0 |
57 | 3DOT0-TC-TELEMETRY-V2-006 | 6 | GenerateNow parameter check | Release 25 | RDKM | 3 DOT0 |
58 | 3DOT0-TC-TELEMETRY-V2-1034 | 11 | Test to verify non-root privileges in RBUS mode | Release 25 | RDKM | 3 DOT0 |
59 | 3DOT0-TC-TELEMETRY-UTOPIA-1001 | 30 | Test to verify telemetry2_0 btime markers | Release 25 | RDKM | 3 DOT0 |
60 | 3DOT0-TC-RDKB-TELEMETRY-PROFILE-1001 | 40 | Verify device allow built-in T2 Report Profiles as part of RDK image | Release 25 | RDKM | 3 DOT0 |
61 | 3DOT0-TC-RDKB-TELEMETRY-ACCUM-1001 | 12 | [Telemetry 2] Support value accumulation markers | Release 28 | RDKM | 3 DOT0 |
62 | 3DOT0-TC-TELEMETRY-UTOPIA-1003 | 29 | Test to verify telemetry2_0 Sys info utopia markers | Release 28 | RDKM | 3 DOT0 |
Released Automatics Webconfig Related Test Cases - 16
Test Case Type | Total Count |
---|---|
1 DOT0 | 11 |
3 DOT0 | 5 |
Features Covered
1 | TC-RDKB-WEBCONFIG_SUBDOC_VERSION-1001 | 12 | Testcase to verify Webconfig Metadata for supported Docs and Versioning | Release 27 | RDKM | 1 DOT0 |
2 | TC-RDKB-WEBCONFIG-WIFI-1002 | 14 | Verify WiFi Component Changes for Webconfig for synchronization | Release 27 | RDKM | 1 DOT0 |
3 | TC-RDKB-WEB-CONFIG-5001 | 7 | Error handling framework for Webconfig BLOB | Release 27 | RDKM | 1 DOT0 |
4 | TC-RDKB_WEBCONFIG_PRIVATE_VAP-1002​ | 25 | Validate Private Vap feature using Webconfig | Release 27 | RDKM | 1 DOT0 |
5 | 3DOT0-TC-RDKB-WEBCONFIG_TELEMETRY_1001 | 39 | Validate WebConfig Client: Webconfig Metadata for Supplementary services(Telemetry) | Release 27 | RDKM | 3DOT0 |
6 | 3DOT0-TC-RDKB-LAN_BLOB_THROUGH_WEBCONFIG | 6 | Executing lan blob through webconfig | Release 27 | RDKM | 3DOT0 |
7 | 3DOT0-KILL-WEBCONFIG-PROCESS-1000 | 6 | To validate if all the processes are gracefully restarted after killing the process | Release 27 | RDKM | 3 DOT0 |
8 | 3DOT0-TC-RDKB-DMZ_WEBCONFIG-1000 | 6 | Post DMZ Configuration through webconfig and validate success logs | Release 28 | RDKM | 3DOT0 |
9 | 3DOT0-TC-RDKB-WEBCONFIG-PRISUPHDR-1000 | 7 | Support metadata information in both Webconfig Primary and supplementary sync | Release 28 | RDKM | 3 DOT0 |
10 | TC-RDKB-WEBCONFIG_FR_REBOOT-1001 | 43 | Validate Factory default and reboot values using Webconfig | Release 28 | RDKM | 1 DOT0 |
11 | TC-RDKB-WEBCONFIG-WIFI-1000 | 12 | Verify WiFi Component Changes for Webconfig for validation and timing | Release 28 | RDKM | 1 DOT0 |
12 | TC-RDKB-WEBCONFIG_PORT_FORWADING-1002 | 14 | Validate Portforwarding feature using Webconfig | Release 28 | RDKM | 1 DOT0 |
13 | TC-RDKB-WEBCONFIG_COMMON_FRAMEWORK-1001 | 40 | Validate Common framework for Webconfig | Release 28 | RDKM | 1 DOT0 |
14 | TC-RDKB-WEBCONFIG_PORT_FORWADING-1001 | 35 | Validate Portforwarding rules using Webconfig | Release 28 | RDKM | 1 DOT0 |
15 | TC-RDKB-WEBCONFIG_LAN-1002 | 14 | Validate LAN feature using Webconfig | Release 28 | RDKM | 1 DOT0 |
16 | TC-RDKB-WEBCONFIG_LAN-1001 | 109 | test to Validate Lan rules using webconfig | Release 28 | RDKM | 1 DOT0 |
Released Automatics WiFi Related Test Cases - 122
Test Case Type | Total Count |
---|---|
1 DOT0 | 118 |
3 DOT0 | 4 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-WIFI-1011 | 6 | Verify default SSID on devices using SNMP | Release 1 | RDKM | 1 DOT0 |
2 | TC-RDKB-WIFI-BAND-STEERING-1001 | 2 | Validate the default value of band steering Capacity using TR181 data object via WEBPA and verify this Parameter is read only | Release 1 | RDKM | 1 DOT0 |
3 | TC-RDKB-WIFI-ATM-1002 | 4 | Validate AirTimeManagement by Assigning Percentages to the Stations added via dmcli. (2.4Ghz) | Release 1 | RDKM | 1 DOT0 |
4 | TC-RDKB-WIFI-1010 | 6 | Verify default SSID using WebPA | Release 1 | RDKM | 1 DOT0 |
5 | TC-RDKB-WIFI-1016 | 11 | Verify telemetry for wifi channel bandwidth for 2.4G | Release 1 | RDKM | 1 DOT0 |
6 | TC-RDKB-WIFI-MESH-1000 | 7 | Verify Mesh Enable does not change the 5ghz channel to DFS range | Release 1 | RDKM | 1 DOT0 |
7 | TC-RDKB-DEF-SSID-5005 | 4 | Cross-verify the Default Private Wi-Fi SSID and password retrieved from WebPA with the configurations from SNMP | Release 2 | RDKM | 1 DOT0 |
8 | TC-RDKB-MESH-WIFI-1001 | 5 | Verify enabling Bridge Mode using WebPA when the MESH is enabled | Release 2 | RDKM | 1 DOT0 |
9 | TC-RDKB-MESH-WIFI-1002 | 5 | Verify enabling Bridge Mode using SNMP when the MESH is enabled | Release 2 | RDKM | 1 DOT0 |
10 | TC-RDKB-WIFI-RESTORE-1001 | 21 | Verify WiFi settings like SSID ,Network Security mode,Channel Selection Mode,Channel bandwidth,Network name enabled status,Guard interval ,Network active status,Supported Protocols,Radio Status and Radio Channel can be restored to default settings using webpa command for doing WIFI settings reset | Release 3 | RDKM | 1 DOT0 |
11 | TC-RDKB-MESH-WIFI-1004 | 2 | Verify enabling MESH when the Bridge Mode is enabled. | Release 3 | RDKM | 1 DOT0 |
12 | TC-RDKB-WIFI-2050 | 6 | Verify that Wi-Fi connectivity of 5 GHz frequency SSID is not affected when 2.4 GHz frequency SSID is disabled | Release 4 | RDKM | 1 DOT0 |
13 | TC-RDKB-WIFI-1001 | 18 | verify the status of wifi mesh service on enabling and disabling it | Release 4 | RDKM | 1 DOT0 |
14 | TC-RDKB-WIFI-5051 | 24 | Verify Management Frame Power Controls for 2.4 GHz and 5 GHz Radios using WebPA | Release 4 | RDKM | 1 DOT0 |
15 | TC-RDKB-WIFI-ATM-1001 | 3 | Validate AirTimeManagement by Assigning Values at APGroup Level | Release 4 | RDKM | 1 DOT0 |
16 | TC-RDKB-WIFI-TX-RATE-CONFIG-5064 | 17 | To verfiy high power support in 5GHZ band channel | Release 4 | RDKM | 1 DOT0 |
17 | TC-RDKB-WIFI-RESTORE-1002 | 19 | Verify WiFi settings like SSID ,Network Security mode,Channel Selection Mode,Channel bandwidth,Network name enabled status,Guard interval ,Network active status,Supported Protocols,Radio Status and Radio Channel can be restored to default settings using SNMP command for doing WIFI settings reset. | Release 4 | RDKM | 1 DOT0 |
18 | TC-RDKB-WIFI-TX-RATE-CONFIG-5061 | 48 | Verify the configuration of Transmission Control Rate for 2.4 GHz and 5GHz Radio using WebPA | Release 4 | RDKM | 1 DOT0 |
19 | TC-RDKB-WIFI-CON-PERF-1002 | 2 | Find out the average mean time for Wi-Fi connection establishment of 2.4GHz radio band with 20 times | Release 4 | RDKM | 1 DOT0 |
20 | TC-RDKB-WIFI-CON-PERF-1003 | 2 | Find out the average mean time for Wi-Fi connection establishment of 5GHz radio band with 20 times | Release 4 | RDKM | 1 DOT0 |
21 | TC-RDKB-WIFI-4001 | 10 | Ping via IPV4 and IPV6 on 2.4GHz when 5GHz is disabled. | Release 4 | RDKM | 1 DOT0 |
22 | TC-RDKB-WIFI-4002 | 10 | Ping via IPV4 and IPV6 on 5GHz when 2.4GHz is disabled. | Release 4 | RDKM | 1 DOT0 |
23 | TC-RDKB-WIFI-4003 | 12 | Test to verify that LAN side wireless CPE gets an IP address when dual radio bands(2.4GHZ and 5 GHZ) are enabled in CM | Release 4 | RDKM | 1 DOT0 |
24 | TC-RDKB-WIFI-4004 | 20 | Enable/Disable both 2.4GHz, and 5Ghz and confirm Client connects/disconnects successfully | Release 4 | RDKM | 1 DOT0 |
25 | TC-RDKB-WIFI-5001 | 15 | Verify 2.4 GHz WiFi beacon rate changing behavior | Release 4 | RDKM | 1 DOT0 |
26 | TC-RDKB-WIFI-2001 | 6 | Enable/Disable Broadcast SSID for 2.4 Ghz WiFi network and verify disabled status | Release 4 | RDKM | 1 DOT0 |
27 | TC-RDKB-WIFI-2002 | 6 | Enable/Disable Broadcast SSID for 5 Ghz WiFi network and verify disabled status | Release 4 | RDKM | 1 DOT0 |
28 | TC-RDKB-WIFI-BAND-STEERING-1005 | 3 | Verify Set or Get PhyRate threshold for 2.4GHz band to initiate Steering using TR69 data objects | Release 4 | RDKM | 1 DOT0 |
29 | TC-RDKB-WIFI-BAND-STEERING-1004 | 3 | Verify Set or Get PhyRate threshold for 5GHz band to initiate Steering using TR69 data objects | Release 4 | RDKM | 1 DOT0 |
30 | TC-RDKB-WIFI-BAND-STEERING-1011 | 15 | Set IdleInactiveTime and OverlaodInactiveTimne to values and verify cfg -s and lbd.conf is updated | Release 4 | RDKM | 1 DOT0 |
31 | TC-RDKB-WIFI-BAND-STEERING-1003 | 7 | verify the factory default value of Band steering paarmeters using webpa and dmcli | Release 4 | RDKM | 1 DOT0 |
32 | TC-RDKB-WIFI-CON-PERF-1000 | 5 | Find out the successful Wi-Fi connectivity rate of 2.4GHz radio band with 10 times in Wireless Gateway | Release 5 | RDKM | 1 DOT0 |
33 | TC-RDKB-WIFI-CON-PERF-1001 | 5 | Find out the successful Wi-Fi connectivity rate of 5GHz radio band with 10 times in Wireless Gateway | Release 5 | RDKM | 1 DOT0 |
34 | TC-RDKB-WIFI-5020 | 4 | Test to verify the default number of allowed clients for PublicWiFi Secure and open SSID using WebPA. | Release 5 | RDKM | 1 DOT0 |
35 | TC-RDKB-WIFI-CC-NEG-1001 | 22 | Validate that SSH, telnet to LAN geteway IP from connected clients is not successful | Release 5 | RDKM | 1 DOT0 |
36 | TC-RDKB-WIFI-5053 | 10 | Verify the reduction in power level of 2.4GHz WiFi Access Point does not impact the non-management frames | Release 5 | RDKM | 1 DOT0 |
37 | TC-RDKB-WIFI-5054 | 10 | Verify the reduction in power level of 5GHz WiFi Access Point does not impact the non-management frames. | Release 5 | RDKM | 1 DOT0 |
38 | TC-RDKB-WIFI-5014 | 15 | This test case is to Verify the controlled user access (Allow) for 5GHZ against different MAC addresses by way of MAC ACLs | Release 5 | RDKM | 1 DOT0 |
39 | TC-RDKB-WIFI_RADIO-1002 | 7 | Ability to disable WiFi Radio through WEBPA | Release 5 | RDKM | 1 DOT0 |
40 | TC-RDKB-WIFI-5011 | 14 | This test case is to verify the controlled user access (Allow All) to the Specific Device for 2.4 and 5 GHZ against different MAC addresses by way of MAC ACLs | Release 5 | RDKM | 1 DOT0 |
41 | TC-RDKB-WIFI-5012 | 15 | Verify the controlled user access (Allow) to the specific Devices for 2.4 GHZ against different MAC addresses by way of MACc ACLs | Release 5 | RDKM | 1 DOT0 |
42 | TC-RDKB-WIFI-CLIENT-1001 | 13 | Test to verify WiFi client connect disconnect events | Release 5 | RDKM | 1 DOT0 |
43 | TC-RDKB-WIFI-2GHZ-DHCP-IPV4-DSBLE-5001 | 5 | Verify the IP range in 2.4GHZ WiFi connected client when DHCP Server disabled. | Release 5 | RDKM | 1 DOT0 |
44 | TC-RDKB-WIFI-5GHZ-DHCP-IPV4-DSBLE-5001 | 5 | Verify the IP range in 5GHZ WiFi connected client when DHCP Server disabled. | Release 5 | RDKM | 1 DOT0 |
45 | TC-RDKB-WIFI-KEY-PHARSE-5001 | 14 | Verify 2.4 GHz SSID is enabled | Release 5 | RDKM | 1 DOT0 |
46 | TC-RDKB-WIFI-KEY-PHARSE-5002 | 14 | Verify that the passphrase key of WIFI access point can be updated for 5 Ghz | Release 5 | RDKM | 1 DOT0 |
47 | TC-RDKB-WIFI-4005 | 16 | Verify Security Mode for WiFi access bands (2.4 and 5 GHz) | Release 5 | RDKM | 1 DOT0 |
48 | TC-RDKB-WIFI-POSSIBLE-CHANNELS-1001 | 4 | Verify that WIFI radio does not support channel number other than the possible channels defined | Release 5 | RDKM | 1 DOT0 |
49 | TC-RDKB-WIFI-RESERVED-IP-1003 | 8 | Verify the Reserved IP for clients for Ethernet client | Release 5 | RDKM | 1 DOT0 |
50 | TC-RDKB-WIFI-RADIO-5001 | 25 | Verify that Wi-Fi connectivity of 2.4GHz frequency is not affected when 5GHz frequency Radio is disabled | Release 6 | RDKM | 1 DOT0 |
51 | TC-RDKB-WIFI-CC-IP-5001 | 30 | Verify that when WIFI Radio is disabled in CM, wireless CPE should not get an ip address | Release 6 | RDKM | 1 DOT0 |
52 | TC-RDKB-WIFI-CHNL-CONFIG-5073 | 18 | Verify Client Connectivity to 5GHz bands with Channel Selection Mode is Manual | Release 6 | RDKM | 1 DOT0 |
53 | TC-RDKB-WIFI-TRANS-1000 | 4 | Test to verify data transmission between 2 connected(LAN-WLAN;WLAN to LAN) clients | Release 6 | RDKM | 1 DOT0 |
54 | TC-RDKB-WIFI-CHNL-CONFIG-5072 | 20 | Verify Client Connectivity to 2.4GHz bands with Channel Selection Mode is Manual | Release 6 | RDKM | 1 DOT0 |
55 | TC-RDKB-WIFI-IE-1002 | 8 | Test to verify Wi-Fi Interworking Information Element | Release 6 | RDKM | 1 DOT0 |
56 | TC-RDKB-WIFI-TX-RATE-CONFIG-5062 | 29 | Test case is created as part of Configuration of Wi-Fi Tx Rate for 2.4GHz Radio and 5Ghz Radio | Release 6 | RDKM | 1 DOT0 |
57 | TC-RDKB-WIFISSID-2003 | 12 | Test case is to validate the failure authentication attempts | Release 6 | RDKM | 1 DOT0 |
58 | TC-RDKB-WIFI-CONFIG-CC-5001 | 22 | Verify the WIFI Connectivity on Dual Band Radio 802.11n client with security mode open | Release 6 | RDKM | 1 DOT0 |
59 | TC-RDKB-MFPCONFIG-1002 | 4 | Verify power cycle persist the MFPConfig values | Release 7 | RDKM | 1 DOT0 |
60 | TC-RDKB-MFPCONFIG-1003 | 4 | Verify MFPConfig is configurable by Wi-Fi HAL | Release 7 | RDKM | 1 DOT0 |
61 | TC-RDKB-WIFI_BLASTER-1001 | 13 | Test to verify Default values after factory reset and value persistent after reboot | Release 7 | RDKM | 1 DOT0 |
62 | TC-RDKB-WIFI_GAS-1001 | 25 | Verify WiFi GAS TR-181 parameters and their default values | Release 7 | RDKM | 1 DOT0 |
63 | TC-RDKB-FORCE_DISABLE_WIFI-1002 | 21 | Verify force disable wifi radio functionality in bridge mode | Release 7 | RDKM | 1 DOT0 |
64 | TC-RDKB-PUBLIC-WIFI-CONFIG-1001 | 8 | Validate the SSID name and BSSID of the Publicwifi | Release 7 | RDKM | 1 DOT0 |
65 | TC-RDKB-PUBLIC-WIFI-AUTO-CH-3001 | 21 | Private WiFi channel selection should remain same post PublicWiFi enabled | Release 7 | RDKM | 1 DOT0 |
66 | TC-RDKB-WIFI-RESERVED-IP-1001 | 9 | Verify the Reserved IP for clients for 2.4ghz | Release 7 | RDKM | 1 DOT0 |
67 | TC-RDKB-WIFI-RESERVED-IP-1002 | 9 | Verify the Reserved IP for clients for 5ghz | Release 7 | RDKM | 1 DOT0 |
68 | TC-RDKB-WIFI-SECTY-OPEN-5001 | 58 | Verify the WIFI Connectivity on Dual Band Radio for Client for 2.4 and 5 Ghz with security mode open | Release 7 | RDKM | 1 DOT0 |
69 | TC-RDKB-WIFI-CC-RADIO-5001 | 46 | Verify enable one radio & disable another radio and check the internet connectivity | Release 7 | RDKM | 1 DOT0 |
70 | TC-RDKB-WIFI-5015 | 15 | This test case is to Verify the controlled user access (Deny) for 5GHZ against different MAC addresses by way of MAC ACLs | Release 7 | RDKM | 1 DOT0 |
71 | TC-RDKB-WIFI-5013 | 15 | This test case is to Verify the controlled user access (Deny) for 2.4GHZ against different MAC addresses by way of MAC ACLs | Release 7 | RDKM | 1 DOT0 |
72 | TC-RDKB-WIFI-CONFIG-CC-5002 | 26 | Verify the WIFI Connectivity on Dual Band Radio 2.4 - 802.11n, 5-802.11ac with security mode WPA2-PSK ( AES ) | Release 7 | RDKM | 1 DOT0 |
73 | TC-RDKB-WIFI-CC-WIN-5004 | 12 | Method to verify Logging all occurrences of connections to LNF PSK SSIDs | Release 7 | RDKM | 1 DOT0 |
74 | TC-RDKB-WIFI-CHANNEL-5001 | 46 | Verify the default channel bandwidth and enable & disable the radio for 2.4GHz & 5GHz with connected clients | Release 7 | RDKM | 1 DOT0 |
75 | TC-RDKB-WIFI-CC-AUTH-1001 | 20 | Validate notification is not seen for unauthenticated clients | Release 8 | RDKM | 1 DOT0 |
76 | TC-RDKB-WIFI-5016 | 26 | Verify Connecting Multiple Clients to the Gateway device via Wi-Fi network and check the internet connectivity | Release 8 | RDKM | 1 DOT0 |
77 | TC-RDKB-WIFI-RESET-1001 | 17 | Verify WiFi status after disabling and enabling | Release 8 | RDKM | 1 DOT0 |
78 | TC-RDKB-WIFI-CC-OPEN-5001 | 16 | Verify WG supports Open Security mode for 2.4 &5 GHZ frequency band | Release 8 | RDKM | 1 DOT0 |
79 | TC-RDKB-WIFI-RESET-1002 | 17 | Verify WiFi status after disabling | Release 8 | RDKM | 1 DOT0 |
80 | TC-RDKB-WIFI-CC-WPA2-5001 | 22 | Verify WG supports WAP2(AES) Security mode for 2.4 &5 GHZ frequency band with valid & invalid key passpharse | Release 8 | RDKM | 1 DOT0 |
81 | TC-RDKB-BSSID-PERSIST-1001 | 10 | Test to validate the private 24/5ghz_Verify BSSID remains same after Factory Reset | Release 8 | RDKM | 1 DOT0 |
82 | TC-RDKB-WIFI-CC-WIN-5003 | 6 | Test to verify that 802.11a should not be able to connect to CM when operating standard is 'b,g,n', 'g,n' mode | Release 9 | RDKM | 1 DOT0 |
83 | TC-RDKB-2GHZ-HOME-NTW-PSWD-1001 | 6 | Verify the password validations when client connected to 2.4GHz | Release 9 | RDKM | 1 DOT0 |
84 | TC-RDKB-5GHZ-HOME-NTW-PSWD-1002 | 6 | Verify the password validations when client connected to 5GHz | Release 9 | RDKM | 1 DOT0 |
85 | TC-RDKB-LAN-HOME-NTW-PSWD-1003 | 6 | Verify the password validations when client connected to LAN | Release 9 | RDKM | 1 DOT0 |
86 | TC-RDKB-WIFI-RADIO-3001 | 14 | Verify the configuration of Transmission Control Rate for 5Ghz(a,n,ac) Radio after reboot | Release 10 | RDKM | 1 DOT0 |
87 | TC-RDKB-WIFI-DHCP-SNMP-5001 | 12 | Validate the DHCP configuration Using SNMP | Release 10 | RDKM | 1 DOT0 |
88 | TC-RDKB-WIFI-PREFERPRIVATE-1002 | 15 | Prefer Private functionality should be applicable for Public WiFi open and secure hotspot SSIDs | Release 10 | RDKM | 1 DOT0 |
89 | TC-RDKB-WIFI-RADIO-3002 | 14 | Verify the configuration of Transmission Control Rate for 5Ghz(n) Radio after reboot | Release 10 | RDKM | 1 DOT0 |
90 | TC-RDKB-WIFI-PREFERPRIVATE-1003 | 15 | Connect to the Connected client having 2.4GHZ WiFi Capability | Release 10 | RDKM | 1 DOT0 |
91 | TC-RDKB-WIFI-MIGRATION-1001 | 51 | Verify WiFi settings after Migration to QA Release | Release11 | RDKM | 1 DOT0 |
92 | TC-RDKB-HOTSPOT_INVALID-1001 | 20 | Test to verify XPC notification for public hotspot parameters with invalid values using webpa | Release12 | RDKM | 1 DOT0 |
93 | TC-RDKB-PC-MNG-SITE-1002 | 12 | Verify internet access to the part of keyword added to manages sites are accessible in Wi-Fi. | Release 17 | RDKM | 1 DOT0 |
94 | TC-RDKB-SYNDICATE-PARTNER-9003 | 8 | Verify Wi-Fi Driver supports an API used by RDKB to set the Wi-Fi Region | Release 17 | RDKM | 1 DOT0 |
95 | TC-RDKB-SYNDICATE-PARTNER-9002 | 6 | Verify Change in Wi-Fi region is reflected in regulatory region after device reboot. | Release 17 | RDKM | 1 DOT0 |
96 | TC-RDKB-IPV4-DEFAULT_ENCRY-2053 | 9 | To Verify 2.4GHz: Default SSID, Protection mode and encryption mode. | Release 17 | Vodafone | 1 DOT0 |
97 | TC-RDKB-IPV4-GATEWAYIP-2013 | 3 | To validate if an error message is displayed when gateway address is set to outside of the range. | Release 17 | Vodafone | 1 DOT0 |
98 | TC-RDKB-IPV4-HOSTNAME-2019 | 5 | To validate if 2 Wi-Fi LAN connected devices can communicate via host name. | Release 17 | Vodafone | 1 DOT0 |
99 | TC-RDKB-IPV4-NETACCESS-2033 | 5 | To verify the device must be able to connect 2.4GHz Wi-Fi and Internet should work. | Release 17 | Vodafone | 1 DOT0 |
100 | TC-RDKB-IPV4-BOOTTIME-2039 | 4 | To verify the Boot Time of the device is less than 5 MIN (300s) | Release 17 | Vodafone | 1 DOT0 |
101 | TC-RDKB-IPV4-CM-2043 | 12 | To verify SNMP walk/Get/Set on RDKB MIBs for CM IPv4 and IPv6 | Release 17 | Vodafone | 1 DOT0 |
102 | TC-RDKB-IPV4-CM-2045 | 3 | To verify if the Dut is accessible using CM IPv6 Address. | Release 17 | Vodafone | 1 DOT0 |
103 | TC-RDKB-IPV4-DHCP-2054 | 2 | The DHCP settings should not allow user to set same DHCP Pool MinAddress and MaxAddress- max CPE as One. | Release 17 | Vodafone | 1 DOT0 |
104 | TC-RDKB-IPV4-MAC_FILTER-2056 | 7 | Wi-Fi MAC Filter - Allow. | Release 17 | Vodafone | 1 DOT0 |
105 | TC-RDKB-IPV4-PORTFW-2052 | 15 | Verify Wired performance (TCP) test on WAN to LAN side (Smoke). | Release 17 | Vodafone | 1 DOT0 |
106 | 3DOT0-TC-RDKB-MESH-DFS-1001 | 21 | Wi-Fi DFS support in MESH solution | Release 18 | RDKM | 3 DOT0 |
107 | TC-RDKB-WIFI-PWR-1006 | 9 | Test to verify WiFi power tables | Release 19 | RDKM | 1 DOT0 |
108 | 3DOT0-TC-RDKB-HARVESTER-1001 | 11 | Compare the time stamp of the Single client uuid in wiFiLog.txt.0 and Received upstream event data in PARODUSLOg.txt.0 | Release 19 | RDKM | 3 DOT0 |
109 | TC-RDKB-PC-MANAGE-DEVICE-1000 | 16 | Test to verify the wireless client connected to 2.4 GHz Private Wi-Fi network is blocked for all days & for particular time period | Release 20 | RDKM | 1 DOT0 |
110 | TC-RDKB-OneWiFi-1000 | 8 | Validate client connectivity with 6GHz, 5GHz High, 5GHz Low bands in OneWifi | Release 20 | RDKM | 1 DOT0 |
111 | TC-RDKB-CC-MODE-CHANGE-5002 | 23 | Verify the internet connectivity and iperf traffic when client mode is set to 'g' for 2.4 GHz and 'a' for 5 GHz. | Release 20 | RDKM | 1 DOT0 |
112 | TC-RDKB-WIFI-SANITY-1002 | 16 | Verify the connectivity of 5ghz wifi on different configurations. | Release 20 | RDKM | 1 DOT0 |
113 | 3DOT0-TC-RDKB-WIFI-1100 | 18 | Monitor for WIFI_ERROR_WifiDmCliError marker after upgrade and Ccspwifi process is in zombie state. | Release 20 | RDKM | 3 DOT0 |
114 | TC-RDKB-WIFI-WHIX-6001 | 8 | Validate the 2.4G Utilization with Increased Population of Devices | Release 21 | RDKM | 1 DOT0 |
115 | TC-RDKB-WIFI-LATENCY-CLIENT-1001 | 6 | Coverage Improvement for Latency in Wifi clients | Release 21 | RDKM | 1 DOT0 |
116 | 3DOT0-TC-RDKB-WIFI_DB-1001 | 6 | Store RDKB Wi-FI DB in encrypted NVRAM | Release 21 | RDKM | 3 DOT0 |
117 | TC-RDKB-WIFI-WHIX-1005 | 12 | Validate data model and default configuration settings for client activity stats telemetry markers | Release 22 | RDKM | 1 DOT0 |
118 | TC-RDKB-WIFI-SPECTRUM-ANALYZER-5001 | 7 | Verify WiFi Spectrum Analyzer tab contains fields like Band, channel, MAC, SSID, Signal Level, Mode, Security. | Release 22 | RDKM | 1 DOT0 |
119 | TC-RDKB-SSID-PWD-1001 | 16 | Test to verify password failure for private SSID | Release 22 | RDKM | 1 DOT0 |
120 | TC-RDKB-WIFI-WEBPA-1026 | 9 | Verify Manual channel selection for WiFi frequency band using tr69/webpa | Release 23 | RDKM | 1 DOT0 |
121 | TC-RDKB-RFC-CTRL-WIFI-5001 | 15 | Verify the RFC support on set & get of Private WiFi password via SNMP and verify the gateway supports to set & get private WiFi password via WebPA regardless of RFC status. | Release 23 | RDKM | 1 DOT0 |
122 | TC-RDKB-WIFI-WHIX-6002 | 21 | Validate Telemetry Marker for WiFi Channel Utilization | Release 24 | RDKM | 1 DOT0 |
DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.
Powered by a free Atlassian Confluence Open Source Project License granted to RDKCentral. Evaluate Confluence today.