RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Total Test Cases: 91
| SI NO | Automation ID | Steps | Sub Feature | Summary |
| 1 | TC-RDKB-RFC-1001 | 2 | RFC Settings | Test to verify configurable RFC check-in trigger using tr181 parameter |
| 2 | TC-RDKB-PARODUS-1005 | 9 | Parodus | Test to verify parodus and webpa uptimes in bootup sequence |
| 3 | TC-RDKB-FS-LAYOUT-1001 | 2 | File system layout validation | Test to validate nvram file system layout |
| 4 | TC-RDKB-FS-LAYOUT-1003 | 3 | File system layout validation | Test to validate tmp file system layout |
| 5 | TC-RDKB-FS-LAYOUT-1004 | 3 | File system layout validation | Test to validate minidumps file system layout |
| 6 | TC-RDKB-FS-LAYOUT-1005 | 2 | File system layout validation | Test to validate rdklogs file system layout |
| 7 | TC-RDKB-FS-LAYOUT-1008 | 2 | File system layout validation | Test to validate xupnp file system layout |
| 8 | TC-RDKB-FS-LAYOUT-1009 | 2 | File system layout validation | Test to validate Dibbler file system layout |
| 9 | TC-RDKB-SYSTEM-1031 | 10 | System validation | Test to verify no zombie dnsmasq process detected by self heal |
| 10 | TC-RDKB-SYSTEM-1101 | 1 | System validation | Test to verify DBus - Overly permissive system setting |
| 11 | TC-RDKB-SYSTEM-7020 | 4 | CPU and Memory usage testing | Test to verify disk usage, up-time, top, date and disk space response from Arm Console |
| 12 | TC-RDKB-PARODUS-RECON-1001 | 3 | Parodus | Test to verify parodus restarted by self heal when killed |
| 13 | TC-RDKB-REBOOT-1011 | 7 | Reboot testing | Test to perform reboot with device component, delay and reboot reason |
| 14 | TC-RDKB-CCSP-1000 | 6 | System validation | Test to verify service configuration feature is disabled |
| 15 | TC-RDKB-SYSTEM-DIBBLER-1001 | 2 | Version test (dibbler version) | Test to check the dibbler version |
| 16 | TC-RDKB-FACTORYRBT-1007 | 6 | Factory Reset | Test to verify Default SSID and Password after Factory Resetting WiFi through WebPA object |
| 17 | TC-RDKB-EXEC-FILE-CHK-1001 | 10 | System validation | Test to verify whether user is able to run user or manual script even after giving 777 permission |
| 18 | TC-RDKB-AUTOREBOOT-1000 | 12 | Reboot testing | Test to verify the default parameter values of Auto reboot |
| 19 | TC-RDKB-REBOOT-5005 | 8 | Reboot testing | Test to verify RDKB devices patches kernel - after reboot |
| 20 | TC-RDKB-RM-MODULE-1001 | 10 | System validation | Test to verify removal of SoundKernel, mtp-tools, libsven |
| 21 | TC-RDKB-REBOOT-5002 | 1 | Reboot testing | Test to verify BootTime using TR-181 Parameter(Device.DeviceInfo.X_RDKCENTRAL-COM_BootTime) |
| 22 | TC-RDKB-RFC-1003 | 12 | RFC | Test to verify RFC processing log messages present in dcmrfc.log for posted parameter value |
| 23 | TC-RDKB-RFC_FEATUREINSTANCE-1001 | 9 | RFC | Test to verify RFC reports feature instance |
| 24 | TC-RDKB-FS-LAYOUT-1002 | 2 | File system layout validation | Test to validation nvram2 file system layout |
| 25 | TC-RDKB-NW-CONNECTIVITY-1010 | 17 | Ping test | Test to 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 |
| 26 | TC-RDKB-SYSTEM-PING-IPRUT-5001 | 4 | Ping test | Test to verify Add IP from ATOM side private network using Ping and ip route |
| 27 | TC-RDKB-PARODUS-1008 | 12 | Parodus | Test to verify Integrate parodus2ccsp with Yocto |
| 28 | TC-RDKB-PARODUS-ENBL-1004 | 8 | Parodus | Test to verify Webpa commands when Parodus is Enabled |
| 29 | TC-RDKB-SYSTEM-5502 | 2 | File system layout validation | Test to verify the data only partition /nvram is mounted as non-executable |
| 30 | TC-RDKB-SYSTEM-5503 | 2 | File system layout validation | Test to verify the data only partition /nvram2 is mounted as non-executable |
| 31 | TC-RDKB-SYSTEM-1028 | 5 | CPU and Memory usage testing | Test to verify CPU usage |
| 32 | TC-RDKB-SYSTEM-3043 | 4 | File system layout validation | Test to verify the stress testing for Encrypted file copying from /nvram/ to /opt/secure/ |
| 33 | TC-RDKB-LIGHTTPD-1002 | 2 | Version test | Test to verify lighttpd version |
| 34 | TC-RDKB-PRO-INFO-5001 | 17 | System validation | Test to verify the sensitive keywords are removed from iptables |
| 35 | TC-RDKB-PRO-INFO-5002 | 17 | System validation | Test to verify the sensitive keywords are removed from ip6tables |
| 36 | TC-RDKB-FACTORYRBT-1002 | 25 | Factory Reset | Test to verify Factory reboot scenario using WebPA |
| 37 | TC-RDKB-FACTORYRBT-1003 | 25 | Factory Reset | Test to verify Factory reboot scenario using SNMP |
| 38 | TC-RDKB-CPU_AND_MEMORY-1002 | 6 | CPU and Memory usage testing | Test to capture CPU and Memory usage individually per process based on request |
| 39 | TC-RDKB-BUSYBOX-UTILITY-1001 | 7 | Busybox | Test to validate Busybox utility tar |
| 40 | TC-RDKB-RM-MODULE-1002 | 19 | System validation | Test to verify removal of SoundKernel, mtp-tools, libsven |
| 41 | TC-RDKB-RBUS-1001 | 8 | System validation | Test to validate device status when rbus is enabled |
| 42 | TC-RDKB-SUBMSK-CHANGE-5001 | 2 | System validation | Test to verify subnet mask range in router mode |
| 43 | TC-RDKB-SYSTEM-1026 | 12 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verifiy the minidump generated during process crash is uploaded to S3/crash portal |
| 44 | TC-RDKB-PRO-INFO-5001 | 17 | System validation | Test to verify the sensitive keywords are removed from iptables |
| 45 | TC-RDKB-GBPAD-1015 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process SNMP_SUBAGENT |
| 46 | TC-RDKB-GBPAD-1014 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process CcspHotspot |
| 47 | TC-RDKB-GBPAD-1007 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process webpa |
| 48 | TC-RDKB-GBPAD-1008 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process CcspWifiAgent |
| 49 | TC-RDKB-GBPAD-1006 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process CcspCr |
| 50 | TC-RDKB-GBPAD-1004 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process CcspTr069 |
| 51 | TC-RDKB-GBPAD-1001 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process PandM |
| 52 | TC-RDKB-AGGRESSIVE_SELF_HEAL-1001 | 13 | System validation | Test to verify Aggressive selfheal |
| 53 | TC-RDKB-PARODUS-NOPOLL-1001 | 8 | Parodus | Test to verify parodus nopoll |
| 54 | TC-RDKB-GBPAD-1005 | 5 | Minidump and crash the process (CcspTr069,CcspHotspot,ProcessCcspCr) | Test to verify mini dump creation and upload to crash portal for the process CcspPsm |
| 55 | TC-RDKB-SYSTEM-1001 | 5 | System validation | Test to verify dnsmasq version in RDKB devices |
| 56 | TC-RDKB-REBOOT-5003 | 8 | Reboot testing | Test to verify interface reboot due to brlan0 and verify logs in SelfHeal.txt.0 file |
| 57 | TC-RDKB-SWAP-5001 | 10 | System validation | Test to verify the swap memory can be enabled and disabled using ZRAM |
| 58 | TC-RDKB-IPV4-PORTFW-2020 | 17 | Port Forwarding | Test to verify the port forwarding scenarios and ensure that UDP traffic is not successful when the protocol is set to TCP. |
| 59 | TC-RDKB-IPV4-PORTFW-2021 | 10 | Port Forwarding | Test to verify that port forwarding rule will be retained after reboot. |
| 60 | TC-RDKB-IPV4-PORTFW-2022 | 33 | Port Forwarding | Test to verify the port forwarding scenarios using TCP and UDP protocols. |
| 61 | TC-RDKB-IPV4-PORTFW-2023 | 8 | Port Forwarding | Test to verify port forwarding functionality by setting the source ipv4 address to 0.0.0.0. |
| 62 | TC-RDKB-IPV4-PORTFW-2024 | 13 | Port Forwarding | Test to verify Port Range Forwarding - Disable specific entry in port forwarding. |
| 63 | TC-RDKB-IPV4-PORTFW-2025 | 10 | Port Forwarding | Test to verify that port forwarding rule will be retained after 10 times reboot and the iperf3 traffic is successful after each reboot. |
| 64 | TC-RDKB-IPV4-PORTFW-2029 | 9 | Port Forwarding | Test to verify the product MUST support user configurable port forwarding. |
| 65 | TC-RDKB-IPV4-PORTFW-2030 | 8 | Port Forwarding | Test to verify the product MUST support deletion of port forwarding. |
| 66 | TC-RDKB-IPV4-PORTFW-2047 | 10 | Port Forwarding | Test to verify the Port forwarding and DMZ rules after performing reset. |
| 67 | TC-RDKB-NTP-1004 | 17 | NTP | Test to verify Single build should include all the NTP FQDNs for the device. |
| 68 | TC-RDKB-SYNDICATION-WAN-SSH-1001 | 11 | System validation | Test to verify WAN-side SSH support in single build |
| 69 | TC-RDKB-DHCP-IPV6-1001 | 8 | DHCP | Test to verify DHCPv6 address in Ethernet connected client on changing Min Address and Max Address |
| 70 | TC-RDKB-EROUTER-3000 | 4 | System validation | Test to validate if the erouter can operate on Ipv6 mode |
| 71 | TC-RDKB-EROUTER-3001 | 4 | System validation | Test to validate if the erouter can operate on Dual Stack mode |
| 72 | TC-RDKB-EROUTER-3002 | 5 | System validation | Test to verify IPv6 firewall can be enable/disable via dmcli commands and verify the status is reflecting the same in snmp |
| 73 | TC-RDKB-IPV4-2057 | 8 | Mac Filter | Test to validate WiFi MAC Filter - Deny. |
| 74 | TC-RDKB-IPV4-2059 | 4 | DHCP | Test to verify DHCP start range ,end range and lease period are user configurable. |
| 75 | TC-RDKB-IPV4-2060 | 8 | DHCP | Test to change the LAN DHCP pool on the fly and check if the connected clients get the IP address from DHCP Pool and check persistency |
| 76 | TC-RDKB-IPV4-2061 | 5 | DHCP | Test to verify the IPv4 address for the LAN client is not possible to reserve same as the DUT's LAN gateway inteface |
| 77 | TC-RDKB-IPV4-2062 | 5 | DHCP | Test to verify IPv4 address for the LAN client is not possible to reserve if it is 0.0.0.0. |
| 78 | TC-RDKB-IPV4-2064 | 9 | DHCP | Test to verify the DHCPv4 enable/disable functionality |
| 79 | TC-RDKB-IPV4-2065 | 5 | DHCP | Test to verify Device should provide DHCPv4 addresses after changing the LAN subnet range. |
| 80 | TC-RDKB-IPV4-2066 | 4 | DHCP | Test to add rule in DHCP with invalid MAC address and IP address. |
| 81 | TC-RDKB-IPV4-2068 | 9 | 2.4, 5 - Common configurations (Channel, Security modes, Autochannel selection) | Test to verify 5GHz: Default SSID, Protection mode and encryption mode. |
| 82 | TC-RDKB-IPV4-2070 | 2 | DHCP | Test to add rule in DHCP with valid MAC address and IP address. |
| 83 | TC-RDKB-IPV4-2071 | 5 | DHCP | Test to add rule in DHCP with valid MAC address and IP address. |
| 84 | TC-RDKB-IPV4-2074 | 2 | 2.4, 5 - Common configurations (Channel, Security modes, Autochannel selection) | Test to verify dmcli report to make sure all WiFi Device loaded |
| 85 | TC-RDKB-WIFITEST-2000 | 6 | 2.4, 5 - Common configurations (Channel, Security modes, Autochannel selection) | Test to verify that the user can enable/disable all SSIDs of 5G radio Ticket |
| 86 | TC-RDKB-WIFITEST-2001 | 5 | 2.4, 5 - Common configurations (Channel, Security modes, Autochannel selection) | Test to verify the Wi-Fi Auto and Manual channel selection for 5Ghz |
| 87 | TC-RDKB-WIFITEST-2002 | 5 | 2.4, 5 - Common configurations (Channel, Security modes, Autochannel selection) | Test to verify the Wi-Fi Auto and Manual channel selection for 2.4Ghz |
| 88 | TC-RDKB-EROUTER-DNS-3005 | 5 | DNS | Test to 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 |
| 89 | TC-RDKB-CC-TEAMS-TEST-1000 | 7 | Connection performance test - 2.4,5 | Test to verify the network connectivity and performance of microsoft teams from a client device |
| 90 | TC-RDKB-BUSYBOX-UTILITY-1002 | 4 | Busybox | Test to validate Busybox utility tftp |
| 91 | TC-RDKB-SELF-HEAL-TELEMETRY-1001 | 23 | CPU and Memory usage testing | Test to Verify that the device monitors its resource usage (CPU Usage ) averaged over a configurable time window |
Overview
Community Forums
Content Tools
Tasks