RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
...
| No | Test case ID | Steps | Description |
|---|---|---|---|
| 1 | 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 |
| 2 | TC-RDKB-WEBPA-1020 | 11 | Verify firmware download event notifications for invalid build with Manageable notification feature enabled |
| 3 | TC-RDKB-XCONF-1003 | 2 | Trigger XCONF/DIFD HTTP CDL with same image version |
| 4 | TC-RDKB-XCONF-1004 | 2 | Trigger XCONF/DIFD TFTP CDL with different image version |
| 5 | TC-RDKB-XCONF-DELAY-1001 | 12 | Verify the Xconf flag support the delay download at installation with invalid images |
| 6 | TC-RDKB-CPU_AND_MEMORY-1001 | 1 | Capture CPU and Memory usage individually per process based on request |
| 7 | TC-RDKB-SYSTEM-7020 | 4 | Verify disk usage, up-time, top, date and disk space response from Arm Console |
| 8 | TC-RDKB-LIGHTTPD-1002 | 2 | Verify lighttpd version |
| 9 | TC-RDKB-WH-SNMP-1002 | 9 | verify snmp set for warehouse OID |
| 10 | 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 |
| 11 | TC-RDKB-SECURITY-1106 | 1 | To verify whether PHP version is upgraded to 7.2.13 or above |
| 12 | TC-RDKB-SECURITY-1105 | 2 | To Verify lighttpd and php fingerprinting |
| 13 | 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) |
| 14 | TC-RDKB-WEBPA-1007 | 5 | Verify XDNS Ccspxdns not crashing on overriding default values |
| 15 | TC-RDKB-SECURITY-2201 | 9 | Enable 3rd party tracker blocking on a gateway |
| 16 | TC-RDKB-SECURITY-2202 | 9 | Verify third party tracker is not blocked |
| 17 | TC-RDKB-WH-SNMP-1003 | 4 | Verify snmp set for warehouse DOCSIS OID |
| 18 | TC-RDKB-PARODUS-RECON-1001 | 3 | Verify parodus restarted by self heal when killed |
| 19 | TC-RDKB-SYSTEM-1001 | 5 | dnsmasq version check in RDKB devices |
| 20 | TC-RDKB-WH-SNMP-1007 | 27 | Warehouse test coverage for Wireless OIDs - Sequence strict |
| 21 | TC-RDKB-SYSTEM-5001 | 2 | Verify stanTC-RDKB-PARODUS-ENBL-1003dard timestamp format is used in RDKB logging |
| 22 | TC-RDKB-SECURITY-1002 | 8 | Testcase for securing syscfg.db parameters via encryption. |
| 23 | TC-RDKB-PARODUS-1010 | 6 | Verify parodus reconnect with jitter algorithm |
| 24 | TC-RDKB-PARODUS-1011 | 23 | Drop process privileges (RDK-B Platforms) |
| 25 | TC-RDKB-WIFI-1001 | 18 | verify the status of wifi mesh service on enabling and disabling it |
| 26 | TC-RDKB-PARODUS-ENBL-1003 | 17 | Verify Enable Parodus in log messages |
| 27 | TC-RDKB-FIREWALL-1000 | 9 | Verify WAN - LAN traffic is blocked when Firewall is configured to Custom Security |
| 28 | TC-RDKB-WIFI-5051 | 24 | Verify Management Frame Power Controls for 2.4 GHz and 5 GHz Radios using WebPA |
| 29 | 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 |
| 30 | TC-RDKB-SYSTEM-5515 | 8 | Verify the logging of WebPA telemetry data in the Parodus Logs |
| 31 | TC-RDKB-SYSTEM-3043 | 4 | Verify the stress testing for Encrypted file copying from /nvram/ to /opt/secure/ |
| 32 | TC-RDKB-SYSTEMWIFI-ATM-10001001 | 3 | Test to Verify verify configparamgen utility testValidate AirTimeManagement by Assigning Values at APGroup Level |
| 33 | TC-RDKB-SNMP-1014 | 6 | Verify resetting the device through SNMP v3 is successful |
| 34 | TC-RDKB-WIFI-TX-RATE-CONFIG-5064 | 17 | To verfiy high power support in 5GHZ band channel |
| 35 | TC-RDKB-SELF-HEAL-4000 | 22 | Test to verify Self healing feature must be enabled by default using snmp mibs |
| 36 | TC-RDKB-SYSTEM-3048 | 12 | Test case to verify whether DNS queries follow strict ordering or not |
| 37 | TC-RDKB-AGGRESSIVE_SELF_HEAL-1001 | 13 | Verify Aggressive selfheal |
| 38 | TC-RDKB-ETHWAN-1001 | 8 | Verify CM shutting down in ETHWAN Mode |
| 39 | TC-RDKB-NW-CHECK-1001 | 3 | Ping to IPV6 from Client connected device |
| 40 | TC-RDKB-WEBPA-1012 | 18 | Verify reboot reason notifications sent for different types of reboot |
| 41 | TC-RDKB-REBOOT-1015 | 6 | Test to verify abort reboot after reboot initiates |
| 42 | TC-RDKB-SELF-HEAL-4011 | 12 | Verify wan link heal check after firmware upgrade |
| 43 | TC-RDKB-TELEMETRY-VER2-1003 | 15 | Verify telemetry 2 configurations persist over a device upgrade |
| 44 | TC-RDKB-SYSCFG-1000 | 12 | Read syscfg parameters encrypted DB |
| 45 | TC-RDKB-PRO-INFO-5001 | 17 | Verify the sensitive keywords are removed from iptables |
| 46 | TC-RDKB-XCONF-PERIFWUP-1005 | 10 | Schedule Periodic Firmware Upgrade Check |
| 47 | TC-RDKB-BRIDGE-MODE-1003 | 10 | Test case to verify router functionalities persistency on mode transisitions |
| 48 | TC-RDKB-FACTORYRBT-1002 | 25 | Factory reboot scenario using WebPA |
| 49 | TC-RDKB-FACTORYRBT-1003 | 25 | Factory reboot scenario using SNMP |
| 50 | TC-RDKB-SYSTEM-1026 | 12 | Verifiy the minidump generated during process crash is uploaded to S3/crash portal |
| 51 | TC-RDKB-REBOOT-1011 | 7 | Perform reboot with device component, delay and reboot reason |
| 52 | TC-RDKB-SYSTEM-5050 | 3 | Verify whether multiple udhcpc.script error messages getting printed in Consolelog.txt |
| 53 | TC-RDKB-WAREHOUSE-1001 | 10 | Verify warehouse staging using xconf method |
| 54 | TC-RDKB-WAREHOUSE-1002 | 10 | Verify warehouse staging using webpa method |
| 55 | TC-RDKB-DOWNUPSTREAM-1001 | 3 | Validate the timestamp for upstream/downstream ranging |
| 56 | TC-RDKB-SELF-HEAL-ACW-3001 | 5 | Average usage must be computed over 15 minute time window |
| 57 | TC-RDKB-REBOOT-1014 | 8 | Verify Abort Reboot after successful CDL |
| 58 | TC-RDKB-PRO-INFO-5002 | 17 | Verify the sensitive keywords are removed from ip6tables |
| 59 | TC-RDKB-SELF-HEAL-4003 | 6 | Test to validate if the cron scheduling on ATOM side whether it is having LogUploadFrequency value _TR181 |
| 60 | TC-RDKB-TR69-1000 | 1 | Verification of Device Serial Number using TR69 parameter -Device.DeviceInfo.SerialNumber |
| 61 | TC-RDKB-TR69-1001 | 1 | Verification of Device Model Name using TR69 parameter -Device.DeviceInfo.ModelName |
| 62 | TC-RDKB-TR69-1002 | 1 | Verification of Device Software Version using TR69 parameter -Device.DeviceInfo.SoftwareVersion |
| 63 | 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 |
| 64 | TC-RDKB-SYSTEM-PING-IPRUT-5001 | 4 | Verify Add IP from ATOM side private network using Ping and ip route |
| 65 | TC-RDKB-XCONF-UP-DWN-5001 | 10 | Validate firmware Upgrade Time Check via xconf |
| 66 | TC-RDKB-WEBPA-1019 | 15 | Verify firmware download event notifications with Manageable notification feature disabled |
| 67 | TC-RDKB-CPUPROC-1000 | 14 | Test to verify CPU Performance Analysis - Process Analyzer |
| 68 | TC-RDKB-REBOOT-5003 | 8 | Verify interface reboot due to brlan0 and verify logs in SelfHeal.txt.0 file |
| 69 | TC-RDKB-FACTORYRESET_REBOOT-1001 | 49 | Test to verify default values after factory reset and value persistance after reboot |
| 70 | TC-RDKB-CCSP-1000 | 6 | Verify service configuration feature is disabled |
| 71 | TC-RDKB-AGGRESSIVE_SELF_HEAL-1002 | 24 | Verify critical & non-critical processes are handling independently in SelfHealAggressive log file and SelfHeal file |
| 72 | 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 |
| 73 | TC-RDKB-WIFI-TX-RATE-CONFIG-5061 | 48 | Verify the configuration of Transmission Control Rate for 2.4 GHz and 5GHz Radio using WebPA |
| 74 | TC-RDKB-BRIDGE-MODE-1001 | 10 | Verification of enabling and disabling Bridge mode via SNMP |
| 75 | 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 |
| 76 | 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 |
| 77 | TC-RDKB-WIFI-4001 | 10 | Ping via IPV4 and IPV6 on 2.4GHz when 5GHz is disabled. |
| 78 | TC-RDKB-WIFI-4002 | 10 | Ping via IPV4 and IPV6 on 5GHz when 2.4GHz is disabled. |
| 79 | 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 |
| 80 | TC-RDKB-ENCRYPT-1001 | 10 | Test to verify Encrypt WiFi passwords stored in NVRAM |
| 81 | TC-RDKB-WIFI-SEC-MODE-1001 | 7 | Verification of 2.4 GHz Private SSID connectivity using valid and invalid WPA2-PSK-AES key |
| 82 | TC-RDKB-WIFI-SEC-MODE-1002 | 7 | Verification of 5 GHz Private SSID connectivity using valid and invalid WPA2-PSK-AES key |
| 83 | TC-RDKB-SYSTEM-9010 | 17 | Verify ccsp-webpa-adapter |
| 84 | TC-RDKB-WIFI-4004 | 20 | Enable/Disable both 2.4GHz, and 5Ghz and confirm Client connects/disconnects successfully |
| 85 | TC-RDKB-SYSTEM-3042 | 21 | Verify that /opt/secure folder is encrypted |
| 86 | 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 |
| 87 | TC-RDKB-CDL-EXCLUDE-1004 | 3 | To verify firmware update with AutoExcluded.Enable is false, AutoExcluded.XconfUrl is MOCK XCONF URL |
| 88 | TC-RDKB-WIFI-5001 | 15 | Verify 2.4 GHz WiFi beacon rate changing behavior |
| 89 | TC-RDKB-CPU_AND_MEMORY-1002 | 6 | Capture CPU and Memory usage individually per process based on request |
| 90 | TC-RDKB-WIFI-2001 | 6 | Enable/Disable Broadcast SSID for 2.4 Ghz WiFi network and verify disabled status |
| 91 | TC-RDKB-WIFI-2002 | 6 | Enable/Disable Broadcast SSID for 5 Ghz WiFi network and verify disabled status |
| 92 | TC-RDKB-SYSTEM-1028 | 5 | Test to verify CPU usage |
| 93 | TC-RDKB-WIFI-BAND-STEERING-1005 | 3 | Verify Set or Get PhyRate threshold for 2.4GHz band to initiate Steering using TR69 data objects |
| 94 | TC-RDKB-WIFI-BAND-STEERING-1004 | 3 | Verify Set or Get PhyRate threshold for 5GHz band to initiate Steering using TR69 data objects |
| 95 | TC-RDKB-WEBPA-1018 | 11 | Verify Implementation of new WifiClient data model for harvester under Device.WiFi. |
| 96 | TC-RDKB-WIFI-BAND-STEERING-1011 | 15 | Set IdleInactiveTime and OverlaodInactiveTimne to values and verify cfg -s and lbd.conf is updated |
| 97 | TC-RDKB-SELF-HEAL-4002 | 6 | Test to Validate if corrective action is taken (eRouter reboot only) when DNS resolve test failure case |
| 98 | TC-RDKB-SELF-HEAL-4009 | 8 | Verify that the MSO is able to configure the resource usage time window via SNMP |
| 99 | TC-RDKB-WIFI-BAND-STEERING-1003 | 7 | verify the factory default value of Band steering paarmeters using webpa and dmcli |
| 100 | TC-RDKB-SELF-HEAL-4010 | 5 | Verification of setting invalid values to avgCPUThreshold and avgMemoryThreshold using SNMP MIB |
...
Overview
Community Forums
Content Tools
Tasks