RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Total Test Cases: 39
| SI NO | Automation ID | Steps | Sub Feature | Summary |
| 1 | TC-RDKB-NW-CONNECTIVITY-1001 | 12 | Ping Test,Factory Reset | Verify the ping related default values in the device after factory resetting by Webpa |
| 2 | TC-RDKB-NW-CONNECTIVITY-1002 | 12 | Ping Test,Factory Reset | Verify the ping related default values in the device after factory resetting by SNMP |
| 3 | TC-RDKB-NTP-0003 | 8 | NTP Server check | Synchronize System Time with NTP Server |
| 4 | TC-RDKB-LOGUPLOAD-1001 | 3 | Logupload Validation | Verify when setting UploadLogsNow parameter to False, no upload happens |
| 5 | TC-RDKB-VALIDATE-HARV-3001 | 3 | Harvester | Validate Wi-Fi Harvester InterfaceDevicesWifi Report after Reboot of DUT |
| 6 | TC-RDKB-LOGUPLOAD-1004 | 3 | Logupload Validation,SNMP | 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 |
| 7 | TC-RDKB-LOGUPLOAD-1003 | 10 | Logupload Validation,DNS | Verify whether log upload fails after adding dns names in hosts entry and on removing the dns names log upload should be successful |
| 8 | TC-RDKB-LOGUPLOAD-1006 | 10 | Logupload Validation,DNS | Verify whether log upload fails after adding dns names in hosts entry and on removing the dns names log upload should be successful |
| 9 | TC-RDKB-NTP-0002 | 2 | NTP Server check , RFC | Validate if NTP Server is disabled on device through RFC |
| 10 | TC-RDKB-NTP-0001 | 2 | NTP Server check , RFC | Validate if NTP Server is enabled on device through RFC |
| 11 | TC-RDKB-ALTN-DNS-1001 | 16 | DNS | Verify Alternate DNS in WiFi and Lan Connected clients |
| 12 | TC-RDKB-INTRANET-ACC-1000 | 13 | Ping Test | Verify the Ping operation is successful between 2.4 GHz and 5 GHz Private Wi-Fi clients |
| 13 | TC-RDKB-INTRANET-ACC-1003 | 13 | Iperf Test, | Verify the Iperf operation is successful between 2.4 GHz and 5 GHz Private Wi-Fi clients |
| 14 | TC-RDKB-FIREWALL-1001 | 11 | Iperf Test, | Verify LAN - WAN traffic is successful when Firewall is configured to 'Custom Security' |
| 15 | TC-RDKB-NW-CONNECTIVITY-1003 | 9 | Ping Test | Verify whether valid IP address are set for the ping servers by Webpa and the ping success logs are captured in selfHeallog.txt.0 |
| 16 | TC-RDKB-NW-CONNECTIVITY-1004 | 14 | Ping Test , Telemetry | 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 |
| 17 | TC-RDKB-NW-CONNECTIVITY-1005 | 15 | Ping Test,Factory Reset | Verify whether valid IP address are set for the ping servers by SNMP and the ping success logs are captured in selfHeallog.txt.0 |
| 18 | TC-RDKB-NW-CONNECTIVITY-1006 | 20 | Ping Test | 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 |
| 19 | TC-RDKB-NW-CONNECTIVITY-1008 | 3 | Ping Test | verify the Configuration of ping packet size via WebPA and also in device logs |
| 20 | TC-RDKB-IPV4-CHECK-5001 | 7 | DNS | Verify DNS Address persist to the Wi-Fi & Ethernet client after reboot and ethernet client gets IP within acceptable time of 5 mins |
| 21 | TC-RDKB-2GHZ-DNS-NSLOOKUP-5001 | 5 | DNS | Verifying the alternate DNS nslookup functionality for 2.4GHz |
| 22 | TC-RDKB-5GHZ-DNS-NSLOOKUP-5001 | 5 | DNS | Verifying the alternate DNS nslookup functionality for 5GHz |
| 23 | TC-RDKB-XDNS-1000 | 10 | DNS | To enable XDNS feature and Verify status after Reboot and Factory Reset the device |
| 24 | TC-RDKB-XDNS-1001 | 5 | DNS | To apply and verify XDNS override at gateway level |
| 25 | TC-RDKB-LOGUPLOAD-1005 | 6 | Logupload Validation | Verify when setting UploadlogsNow snmp OID (1.3.6.1.4.1.17270.43.1.2.1.0) to True, logs get uploaded |
| 26 | TC-RDKB-LOGUPLOAD-1002 | 7 | Logupload Validation | Verify when setting UploadlogsNow parameter to true, logs gets uploaded |
| 27 | TC-RDKB-LAN-DNS-NSLOOKUP-5001 | 5 | DNS | Verifying the alternate DNS nslookup functionality for Ethernet |
| 28 | TC-RDKB-FIREWALL-1000 | 9 | Iperf Test, | Verify WAN - LAN traffic is blocked when Firewall is configured to Custom Security |
| 29 | TC-RDKB-DHCP-LANCLIENT-1001 | 4 | DHCP | This test case is to Verify the DHCP Lan client |
| 30 | TC-RDKB-CCSP-XDNS-5001 | 6 | DNS | Verify XDNS in Process Monitor after reboot |
| 31 | TC-RDKB-BRID-MODE-5001 | 47 | Bridge Mode | Verify device and connected client status while device is in bridge mode |
| 32 | TC-RDKB-BRIDGE-MODE-1002 | 30 | Bridge Mode, WiFi | Test script to validate basic Wi-Fi parameters on router mode transition |
| 33 | TC-RDKB-NW-CONNECTIVITY-1009 | 11 | Ping Test | 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 |
| 34 | TC-RDKB-BRIDGE-MODE-1003 | 10 | Bridge Mode | Test case to verify router functionalities persistency on mode transisitions |
| 35 | TC-RDKB-HARV-6001 | 9 | Harvester | Validation of NetworkDevicesTraffic Report generation |
| 36 | TC-RDKB-HARV-6000 | 10 | Harvester | Validation of NetworkDevicesStatus Report generation |
| 37 | TC-RDKB-HARV-5002 | 3 | Harvester | Verify the polling period & reporting period attributes of Radio Interface Statistics Harvester Report is increased to 900 seconds. |
| 38 | TC-RDKB-HARV-6008 | 13 | Harvester | Check after TTL whether RadioInterfaceStatistics Polling-Reporting Period changes back to defaults when set less than Default TTL Interval. |
| 39 | TC-RDKB-HARV-6005 | 13 | Harvester | Check after TTL whether NetworkDevicesStatus Polling-Reporting Period changes back to defaults when set less than Default TTL Interval |
Overview
Community Forums
Content Tools
Tasks