RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
SI NO | Automation ID | Steps | Summary | Release | Contributor | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | TC-RDKB-RFC-1001 | 2 | Verify configurable RFC check-in trigger using tr181 parameter | Release 2 | RDKM | ||||||
2 | TC-RDKB-PARODUS-1005 | 9 | Verify parodus and webpa uptimes in bootup sequence | Release 2 | RDKM | ||||||
3 | TC-RDKB-WH-SNMP-1000 | 12 | Verify get SNMP for warehouse OIDs | Release 3 | RDKM | ||||||
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 | ||||||
5 | TC-RDKB-PARODUS-1006 | 19 | Verify themis curl to acquire JWT for parodus | Release 3 | RDKM | ||||||
6 | TC-RDKB-PARODUS-1008 | 12 | Verify Integrate parodus2ccsp with Yocto | Release 3 | RDKM | ||||||
7 | TC-RDKB-PARODUS-1007 | 18 | Verify Integrate parodus2ccsp with Yocto | Release 3 | RDKM | ||||||
8 | TC-RDKB-PARODUS-1009 | 10 | Test to verify configurable parodus reboot reason | Release 3 | RDKM | ||||||
9 | TC-RDKB-PARODUS-ENBL-1004 | 8 | Verify Webpa commands when Parodus is Enabled | Release 3 | RDKM | ||||||
10 | TC-RDKB-PARODUS-NOPOLL-1001 | 8 | Test to verify parodus nopoll | Release 3 | RDKM | ||||||
11 | TC-RDKB-SYSTEM-1021 | 5 | Test to verify removal of telnet daemon | Release 3 | RDKM | ||||||
12 | TC-RDKB-SYSTEM-5002 | 7 | Verify logging for Harvester and LMLite reports | Release 3 | RDKM | ||||||
13 | TC-RDKB-SYSTEM-5007 | 3 | Verify Xconf default value,Hardware version,Linux kernel upgrade version from logs | Release 3 | RDKM | ||||||
14 | TC-RDKB-REBOOT-5001 | 6 | Test case to verify the docsdevresetnow mib functionality | Release 3 | RDKM | ||||||
15 | TC-RDKB-FS-LAYOUT-1001 | 2 | nvram file system layout validation | Release 3 | RDKM | ||||||
16 | TC-RDKB-FS-LAYOUT-1002 | 2 | nvram2 file system layout validation | Release 3 | RDKM | ||||||
17 | TC-RDKB-FS-LAYOUT-1003 | 3 | tmp file system layout validation | Release 3 | RDKM | ||||||
18 | TC-RDKB-FS-LAYOUT-1004 | 3 | minidumps file system layout validation | Release 3 | RDKM | ||||||
19 | TC-RDKB-FS-LAYOUT-1005 | 2 | rdklogs file system layout validation | Release 3 | RDKM | ||||||
20 | TC-RDKB-FS-LAYOUT-1006 | 3 | cron and etc file system layout validation | Release 3 | RDKM | ||||||
21 | TC-RDKB-FS-LAYOUT-1007 | 2 | dhcp_static_hosts file system layout validation | Release 3 | RDKM | ||||||
22 | TC-RDKB-FS-LAYOUT-1008 | 2 | xupnp file system layout validation | Release 3 | RDKM | ||||||
23 | TC-RDKB-FS-LAYOUT-1009 | 2 | Dibbler file system layout validation | Release 3 | RDKM | ||||||
24 | TC-RDKB-PARODUS-1001 | 3 | Removal of parodus start shell script changes from yocto | Release 3 | RDKM | ||||||
25 | TC-RDKB-SYSTEM-1031 | 10 | Verify no zombie dnsmasq process detected by self heal | Release 3 | RDKM | ||||||
26 | TC-RDKB-SYSTEM-5502 | 2 | Verify the data only partition /nvram is mounted as non-executable | Release 3 | RDKM | ||||||
27 | TC-RDKB-SYSTEM-5503 | 2 | Verify the data only partition /nvram2 is mounted as non-executable | Release 3 | RDKM | ||||||
28 | TC-RDKB-SYSTEM-1101 | 1 | Verify DBus - Overly permissive system setting | Release 3 | RDKM | ||||||
29 | TC-RDKB-CPU_AND_MEMORY-1001 | 1 | Capture CPU and Memory usage individually per process based on request | Release 4 | RDKM | ||||||
30 | TC-RDKB-SYSTEM-7020 | 4 | Verify disk usage, up-time, top, date and disk space response from Arm Console | Release 4 | RDKM | ||||||
31 | TC-RDKB-LIGHTTPD-1002 | 2 | Verify lighttpd version | Release 4 | RDKM | ||||||
32 | TC-RDKB-WH-SNMP-1003 | 4 | Verify snmp set for warehouse DOCSIS OID | Release 4 | RDKM | ||||||
33 | TC-RDKB-PARODUS-RECON-1001 | 3 | Verify parodus restarted by self heal when killed | Release 4 | RDKM | ||||||
34 | TC-RDKB-SYSTEM-1001 | 5 | dnsmasq version check in RDKB devices | Release 4 | RDKM | ||||||
35 | TC-RDKB-WH-SNMP-1007 | 27 | Warehouse test coverage for Wireless OIDs - Sequence strict | Release 4 | RDKM | ||||||
36 | TC-RDKB-SYSTEM-5001 | 2 | Verify stanTC-RDKB-PARODUS-ENBL-1003dard timestamp format is used in RDKB logging | Release 4 | RDKM | ||||||
37 | TC-RDKB-PARODUS-1010 | 6 | Verify parodus reconnect with jitter algorithm | Release 4 | RDKM | ||||||
38 | TC-RDKB-PARODUS-1011 | 23 | Drop process privileges (RDK-B Platforms) | Release 4 | RDKM | ||||||
39 | TC-RDKB-PARODUS-ENBL-1003 | 17 | Verify Enable Parodus in log messages | Release 4 | RDKM | ||||||
40 | TC-RDKB-SYSTEM-5515 | 8 | Verify the logging of WebPA telemetry data in the Parodus Logs | Release 4 | RDKM | ||||||
41 | TC-RDKB-SYSTEM-3043 | 4 | Verify the stress testing for Encrypted file copying from /nvram/ to /opt/secure/ | Release 4 | RDKM | ||||||
42 | TC-RDKB-SYSTEM-3048 | 12 | Test case to verify whether DNS queries follow strict ordering or not | Release 4 | RDKM | ||||||
43 | TC-RDKB-AGGRESSIVE_SELF_HEAL-1001 | 13 | Verify Aggressive selfheal | Release 4 | RDKM | ||||||
44 | TC-RDKB-REBOOT-1015 | 6 | Test to verify abort reboot after reboot initiates | Release 4 | RDKM | ||||||
45 | TC-RDKB-SYSCFG-1000 | 12 | Read syscfg parameters encrypted DB | Release 4 | RDKM | ||||||
46 | TC-RDKB-PRO-INFO-5001 | 17 | Verify the sensitive keywords are removed from iptables | Release 4 | RDKM | ||||||
47 | TC-RDKB-FACTORYRBT-1002 | 25 | Factory reboot scenario using WebPA | Release 4 | RDKM | ||||||
48 | TC-RDKB-FACTORYRBT-1003 | 25 | Factory reboot scenario using SNMP | Release 4 | RDKM | ||||||
49 | TC-RDKB-SYSTEM-1026 | 12 | Verifiy the minidump generated during process crash is uploaded to S3/crash portal | Release 4 | RDKM | ||||||
50 | TC-RDKB-REBOOT-1011 | 7 | Perform reboot with device component, delay and reboot reason | Release 4 | RDKM | ||||||
51 | TC-RDKB-SYSTEM-5050 | 3 | Verify whether multiple udhcpc.script error messages getting printed in Consolelog.txt | Release 4 | RDKM | ||||||
52 | TC-RDKB-WAREHOUSE-1001 | 10 | Verify warehouse staging using xconf method | Release 4 | RDKM | ||||||
53 | TC-RDKB-WAREHOUSE-1002 | 10 | Verify warehouse staging using webpa method | Release 4 | RDKM | ||||||
54 | TC-RDKB-REBOOT-1014 | 8 | Verify Abort Reboot after successful CDL | Release 4 | RDKM | ||||||
55 | TC-RDKB-PRO-INFO-5002 | 17 | Verify the sensitive keywords are removed from ip6tables | Release 4 | RDKM | ||||||
56 | TC-RDKB-SYSTEM-PING-IPRUT-5001 | 4 | Verify Add IP from ATOM side private network using Ping and ip route | Release 4 | RDKM | ||||||
57 | TC-RDKB-CPUPROC-1000 | 14 | Test to verify CPU Performance Analysis - Process Analyzer | Release 4 | RDKM | ||||||
58 | TC-RDKB-REBOOT-5003 | 8 | Verify interface reboot due to brlan0 and verify logs in SelfHeal.txt.0 file | Release 4 | RDKM | ||||||
59 | TC-RDKB-FACTORYRESET_REBOOT-1001 | 49 | Test to verify default values after factory reset and value persistance after reboot | Release 4 | RDKM | ||||||
60 | TC-RDKB-CCSP-1000 | 6 | Verify service configuration feature is disabled | Release 4 | RDKM | ||||||
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 | ||||||
62 | TC-RDKB-SYSTEM-9010 | 17 | Verify ccsp-webpa-adapter | Release 4 | RDKM | ||||||
63 | TC-RDKB-SYSTEM-3042 | 21 | Verify that /opt/secure folder is encrypted | Release 4 | RDKM | ||||||
64 | TC-RDKB-CPU_AND_MEMORY-1002 | 6 | Capture CPU and Memory usage individually per process based on request | Release 4 | RDKM | ||||||
65 | TC-RDKB-SYSTEM-1028 | 5 | Test to verify CPU usage | Release 4 | RDKM | ||||||
66 | TC-RDKB-SYSTEM-5003 | 7 | Verify Webpa Notifications on Firmware Upgrade | Release 5 | RDKM | ||||||
67 | TC-RDKB-SYSTEM-DIBBLER-1001 | 2 | To check the dibbler version | Release 5 | RDKM | ||||||
68 | TC-RDKB-FS-LAYOUT-1010 | 3 | Test to verify resolv.conf file system layout validation and DNS value | Release 5 | RDKM | ||||||
69 | TC-RDKB-FACTORYRBT-1006 | 9 | Test to verify Default SSID and Password after Factory Resetting Router through WebPA | Release 5 | RDKM | ||||||
70 | TC-RDKB-FACTORYRBT-1007 | 6 | Verify Default SSID and Password after Factory Resetting WiFi through WebPA object | Release 5 | RDKM | ||||||
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 | ||||||
72 | TC-RDKB-SYSTEM-IPSET-1008 | 17 | Verify upgrade ipset to v.6.34 | Release 5 | RDKM | ||||||
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 | ||||||
74 | TC-RDKB-AUTOREBOOT-1000 | 12 | Test to verify the default parameter values of Auto reboot | Release 5 | RDKM | ||||||
75 | TC-RDKB-REBOOT-5005 | 8 | Test to Verify RDKB devices patches kernel - after reboot | Release 5 | RDKM | ||||||
76 | TC-RDKB-THERMAL_FAN-1000 | 11 | Device shall have the ability to retrieve the fan diagnostics via WebPA | Release 5 | RDKM | ||||||
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 | ||||||
78 | TC-RDKB-BUSYBOX-UTILITY-1001 | 7 | Validate Busybox utility tar | Release 5 | RDKM | ||||||
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 | ||||||
80 | TC-RDKB-BUSYBOX_UTILITY-1003 | 6 | Verify the installed busy box utilities on CM side | Release 5 | RDKM | ||||||
81 | TC-RDKB-RM-MODULE-1002 | 19 | Verify removal of SoundKernel, mtp-tools, libsven | Release 6 | RDKM | ||||||
82 | TC-RDKB-RM-MODULE-1001 | 10 | Verify removal of SoundKernel, mtp-tools, libsven | Release 6 | RDKM | ||||||
83 | TC-RDKB-SYSTEM-1023 | 5 | Test to verify ssh banners from sshbanner.txt file and command execution | Release 6 | RDKM | ||||||
84 | TC-RDKB-REVSSH-1001 | 9 | Verify Reverse SSH connection | Release 6 | RDKM | ||||||
85 | TC-RDKB-GBPAD-1001 | 5 | Test to Verify mini dump creation and upload to crash portal for the process PandM | Release 7 | RDKM | ||||||
86 | TC-RDKB-GBPAD-1005 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspPsm | Release 7 | RDKM | ||||||
87 | TC-RDKB-GBPAD-1007 | 5 | Test to Verify mini dump creation and upload to crash portal for the process webpa | Release 7 | RDKM | ||||||
88 | TC-RDKB-GBPAD-1008 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspWifiAgent | Release 7 | RDKM | ||||||
89 | TC-RDKB-GBPAD-1011 | 5 | Test to Verify mini dump creation and upload to crash portal for the process meshAgent | Release 7 | RDKM | ||||||
90 | TC-RDKB-GBPAD-1012 | 5 | Test to Verify mini dump creation and upload to crash portal for the process parodus | Release 7 | RDKM | ||||||
91 | TC-RDKB-GBPAD-1006 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspCr | Release 8 | RDKM | ||||||
92 | TC-RDKB-REBOOT-5002 | 1 | Verify BootTime using TR-181 Parameter(Device.DeviceInfo.X_RDKCENTRAL-COM_BootTime) | Release 8 | RDKM | ||||||
93 | TC-RDKB-GBPAD-1014 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspHotspot | Release 8 | RDKM | ||||||
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 | ||||||
95 | TC-RDKB-GBPAD-1004 | 5 | Test to Verify mini dump creation and upload to crash portal for the process CcspTr069 | Release 8 | RDKM | ||||||
96 | TC-RDKB-SYSTEM-9008 | 2 | Validate if RDKB SSH client is not accessible via WAN | Release 8 | RDKM | ||||||
97 | TC-RDKB-SYSTEM-1102 | 7 | Test case is created as to Enable Disable Feature Via DCM | Release 8 | RDKM | ||||||
98 | TC-RDKB-WIFI-FIRM-DWNL-5001 | 25 | Verify the Time frame validation for DUT online | Release 9 | RDKM | ||||||
99 | TC-RDKB-SYSTEM-5400 | 4 | Verify Mount options for tmp directory | Release 9 | RDKM | ||||||
100 | TC-RDKB-SYSTEM-1029 | 2 | Verify accessibilty for ARM to Atom SSH | Release 9 | RDKM | ||||||
101 | TC-RDKB-RBUS-1001 | 8 | Validate device status when rbus is enabled | Release 9 | RDKM | ||||||
102 | TC-RDKB-WH-FR-RS-5001 | 19 | Improved testing sequences for RDK-B WIFI warehouse | Release 9 | RDKM | ||||||
103 | TC-RDKB-SUBMSK-CHANGE-5001 | 2 | Verify subnet mask range in router mode | Release 9 | RDKM | ||||||
104 | TC-RDKB-SYSCFG-1001 | 12 | Verify syscfg parameters after removing unencrypted /nvram/syscfg.db | Release 9 | RDKM | ||||||
105 | TC-RDKB-PARODUS-1012 | 11 | Verify themis token fetch by passing Partner-ID as a request header | Release 10 | RDKM | ||||||
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 | ||||||
107 | TC-RDKB-BINARIES-1004 | 7 | Test to verify Removed or Encrypted Private Keys | Release 10 | RDKM | ||||||
108 | TC-RDKB-SWAP-5001 | 10 | Verify the swap memory can be enabled and disabled using ZRAM | Release 11 | RDKM | ||||||
109 | TC-RDKB-BOOTSTRAP-1031 | 48 | Test to verify bootstrap configuration with version and update source | Release 11 | RDKM | ||||||
110 | TC-RDKB-RFC-1202 | 12 | Test to Verify that RFC requests contain accountId Unknown on Every powercycle | Release 11 | RDKM | ||||||
111 | TC-RDKB-BOOTSTRAP-1030 | 48 | Test to verify bootstrap configuration and version | Release 11 | RDKM | ||||||
112 | TC-RDKB-SYSTEM-1033 | 10 | Test to verify reporting of RFC feature enable | Release 12 | RDKM | ||||||
113 | TC-RDKB-WIFI-REBOOT-1001 | 5 | Verification of any kind of crash in device if Multiple WiFi reset triggerred | Release 12 | RDKM | ||||||
114 | TC-RDKB-RFC-1006 | 10 | Verify Reboot required RFC change causes scheduled reboot in maintenance window | Release 12 | RDKM | ||||||
115 | TC-RDKB-RFC-1005 | 11 | To verify RFC versioning support | Release 12 | RDKM | ||||||
116 | TC-RDKB-RFC-SNMP-1001 | 7 | Verify RFC control of SNMPv2 | Release 12 | RDKM | ||||||
117 | TC-RDKB-DEVICE-RESET-1005 | 35 | Perform Factory reset from Admin GUI page and verify default values after factory reset | Release 12 | RDKM | ||||||
118 | TC-RDKB-RFC-DATABASE-1001 | 15 | Validate RFC default and enabled values in defaults/database file | Release 12 | RDKM | ||||||
119 | TC-RDKB-RFC-1003 | 12 | Verify RFC processing log messages present in dcmrfc.log for posted parameter value | Release 12 | RDKM | ||||||
120 | TC-RDKB-RFC-1201 | 9 | Test to Verify that xconf requests contain accountId | Release 12 | RDKM | ||||||
121 | TC-RDKB-RFC-1200 | 25 | Test to Verify that xconf requests contain accountId | Release 12 | RDKM | ||||||
122 | TC-RDKB-DEFAULT-VALUES-1001 | 97 | Verify the default values in the device after factory resetting by WebPA | Release 12 | RDKM | ||||||
123 | TC-RDKB-RFC_FEATUREINSTANCE-1001 | 9 | Verify RFC reports feature instance | Release 13 | RDKM | ||||||
124 | TC-RDKB-BOOTSTRAP-1029 | 193 | Verify bootstrap configuration | Release 13 | RDKM | ||||||
125 | 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 | ||||||
126 | TC-RDKB-IPV4-DEFAULT_ENCRY-2053 | 9 | To Verify 2.4GHz: Default SSID, Protection mode and encryption mode. | Release 17 | Vodafone | 127 | TC-RDKB-IPV4-PORTFW-2021 | 10 | To verify that port forwarding rule will be retained after reboot. | Release 17 | Vodafone |
128127 | TC-RDKB-IPV4-PORTFW-2022 | 33 | To verify the port forwarding scenarios using TCP and UDP protocols. | Release 17 | Vodafone | ||||||
129128 | TC-RDKB-IPV4-PORTFW-2023 | 8 | Verify port forwarding functionality by setting the source ipv4 address to 0.0.0.0. | Release 17 | Vodafone | ||||||
130129 | TC-RDKB-IPV4-PORTFW-2024 | 13 | Verify Port Range Forwarding - Disable specific entry in port forwarding. | Release 17 | Vodafone | ||||||
131130 | 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 | ||||||
132131 | TC-RDKB-IPV4-PORTFW-2029 | 9 | Test case to verify the product MUST support user configurable port forwarding. | Release 17 | Vodafone | ||||||
133132 | TC-RDKB-IPV4-PORTFW-2030 | 8 | Test case to verify the product MUST support deletion of port forwarding. | Release 17 | Vodafone | ||||||
134133 | TC-RDKB-IPV4-PORTFW-2047 | 10 | To verify the Port forwarding and DMZ rules after performing reset. | Release 17 | Vodafone | ||||||
135134 | TC-RDKB-RFC-MTLS-1001 | 16 | Test case to verify mutual TLS feature for log upload. | Release 19 | RDKM | ||||||
136135 | TC-RDKB-NTP-1004 | 17 | Verify Single build should include all the NTP FQDNs for the device. | Release 19 | RDKM | ||||||
137136 | TC-RDKB-SYNDICATION-WAN-SSH-1001 | 11 | To verify WAN-side SSH support in single build | Release 19 | RDKM | ||||||
138137 | TC-RDKB-DHCP-IPV6-1001 | 8 | Verify DHCPv6 address in Ethernet connected client on changing Min Address and Max Address | Release 19 | RDKM | ||||||
139138 | TC-RDKB-EROUTER-3000 | 4 | To validate if the erouter can operate on Ipv6 mode | Release 19 | Vodafone | ||||||
140139 | TC-RDKB-EROUTER-3001 | 4 | To validate if the erouter can operate on Dual Stack mode | Release 19 | Vodafone | ||||||
141140 | 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 | ||||||
142141 | TC-RDKB-IPV4-2057 | 8 | WiFi MAC Filter - Deny. | Release 19 | Vodafone | ||||||
143142 | TC-RDKB-IPV4-2059 | 4 | Verify DHCP start range ,end range and lease period are user configurable. | Release 19 | Vodafone | ||||||
144143 | 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 | ||||||
145144 | 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 | ||||||
146145 | 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 | ||||||
147146 | TC-RDKB-IPV4-2064 | 9 | Verify the DHCPv4 enable/disable functionality | Release 19 | Vodafone | ||||||
148147 | TC-RDKB-IPV4-2065 | 5 | Verify Device should provide DHCPv4 addresses after changing the LAN subnet range. | Release 19 | Vodafone | ||||||
149148 | TC-RDKB-IPV4-2066 | 4 | Add rule in DHCP with invalid MAC address and IP address. | Release 19 | Vodafone | ||||||
150149 | TC-RDKB-IPV4-2068 | 9 | To Verify 5GHz: Default SSID, Protection mode and encryption mode. | Release 19 | Vodafone | ||||||
151150 | TC-RDKB-IPV4-2070 | 2 | Add rule in DHCP with valid MAC address and IP address. | Release 19 | Vodafone | ||||||
152151 | TC-RDKB-IPV4-2071 | 5 | Add rule in DHCP with valid MAC address and IP address. | Release 19 | Vodafone | ||||||
153152 | TC-RDKB-IPV4-2074 | 2 | Dmcli report to make sure all WiFi Device loaded | Release 19 | Vodafone | ||||||
154153 | TC-RDKB-IPV4-2075 | 5 | To verify client get IP from CM provisioning while in bridge mode. | Release 19 | Vodafone | ||||||
155154 | TC-RDKB-WIFITEST-2000 | 6 | Verify that the user can enable/disable all SSIDs of 5G radio Ticket | Release 19 | Vodafone | ||||||
156155 | TC-RDKB-WIFITEST-2001 | 5 | Wi-Fi Auto and Manual channel selection for 5Ghz | Release 19 | Vodafone | ||||||
157156 | TC-RDKB-WIFITEST-2002 | 5 | Wi-Fi Auto and Manual channel selection for 2.4Ghz | Release 19 | Vodafone |