| 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 |
| 223 | 3DOTO-TC-RDKB-SAFEBROWSING-1002 | 10 | Test case to Verify the safebrowsing configuration using tr181 commands | Release 30 | RDKM | 3DOTO |
| 224 | TC-RDKB-HARV-5006 | 13 | Verify the Wifi Interface Devices Harvester Report generation with log messages. | Release 30 | RDKM | 1 DOT0 |
| 225 | TC-RDKB-HARV-6007 | 13 | Check after TTL whether InterfaceDevicesWifi Polling-Reporting Period changes back to defaults when set less than Default TTL Interval | Release 30 | RDKM | 1 DOT0 |
| 226 | TC-RDKB-XDNS_DNSSEC-1001 | 8 | Verify DNSSec flag when XDNS is enabled | Release 30 | RDKM | 1 DOT0 |
| 227 | 3DOTO-TC-RDKB-CUSTOM_MAPPER-1001 | 12 | Verification of implementation of Custom_Mapper(AliasMGR) functionality | Release 31 | RDKM | 3DOTO |
| 228 | 3DOTO-TC-RDKB-BHT-SYNDICATION-1000 | 10 | Validation of syndication feature | Release 31 | RDKM | 3DOTO |
| 229 | 3DOTO-TC-RDKB-PARODUS-1005 | 7 | Verify parodus and webpa uptimes in bootup sequence | Release 31 | RDKM | 3DOTO |
| 230 | TC-RDKB-PROCESS_COMPONENT_MESHAGENT-1000 | 2 | Verify whether MESHAGENT process is initialized properly | Release 31 | RDKM | 1 DOT0 |
| 231 | TC-RDKB-PARODUS-1002 | 2 | Verify the device manufacturer name in parodus log and through WebPA, both the values should be same | Release 31 | RDKM | 1DOTO |
| 232 | TC-RDKB-WH-WEBPA-1001 | 16 | Validate WebPA response time for warehouse | Release 31 | RDKM | 1 DOT0 |
| 233 | 3DOTO-TC-RDKB-IMAGE_HEALTH_OPMODE-1001 | 4 | Check different operating modes of image health checker RFC feature | Release 32 | RDKM | 3DOT0 |
