RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Released Automatics Connectivity Related Test Cases - 81
| Test Case Type | Total Count |
|---|---|
| 1 DOT0 | 81 |
| 3 DOT0 | 0 |
Features Covered
- CONNECTIVITY-NETWORK (IPv4 & IPv6 Integrity)
- CONNECTIVITY-FACTORY RESETTING THROUGH SNMP/WEBPA
- CONNECTIVITY-FIREWALL SETTING
- CONNECTIVITY- DNS NS LOOKUP FUNCTIONALITY
- CONNECTIVITY - PING TEST
- CONNECTIVITY- SPEEDTEST ((Iperf)
- CONNECTIVITY - RFC
- CONNECTIVITY-BRIDGE MODE MONITRORING
- CONNECTIVITY-DHCP CONFIGURATION
- CONNECTIVITY-HARVESTER
- CONNECTIVITY -NETWORK DEVICE STATUS REPORT GENERATION
- CONNECTIVITY- CHECK THE TTL , AFTER CHANGE RADIOINTERFACESTATICS POLLING INTERVAL AND VERIFY THE VALUE LESS THAN TTL DEFAULT
- CONNECTIVITY- CHECK THE TTL , AFTER CHANGE NETWORK DEVICE STATICS POLLING INTERVAL AND VERIFY THE VALUE LESS THAN TTL DEFAULT
| SI NO | Automation ID | Steps | Summary | Release |
|---|---|---|---|---|
| 1 | TC-RDKB-NW-CONNECTIVITY-1003 | 9 | Verify whether valid IP address are set for the ping servers by Webpa and the ping success logs are captured in selfHeallog.txt.0 | Release 1 |
| 2 | TC-RDKB-NW-CONNECTIVITY-1001 | 12 | Verify the ping related default values in the device after factory resetting by Webpa | Release 1 |
| 3 | TC-RDKB-FIREWALL-1005 | 12 | Verify Echo Reply or Response with different firewall settings | Release 2 |
| 4 | TC-RDKB-IP-MCAST-1000 | 3 | Verify Broadband gateway providing CMTS Mac Address to IP Multicast Back Office | Release 2 |
| 5 | TC-RDKB-NW-CONNECTIVITY-1004 | 14 | 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 | Release 2 |
| 6 | TC-RDKB-NW-CONNECTIVITY-1008 | 3 | verify the Configuration of ping packet size via WebPA and also in device logs | Release 2 |
| 7 | TC-RDKB-NW-CONNECTIVITY-1009 | 11 | 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 | Release 2 |
| 8 | TC-RDKB-NW-CONNECTIVITY-1002 | 12 | Verify the ping related default values in the device after factory resetting by SNMP | Release 3 |
| 9 | TC-RDKB-NW-CONNECTIVITY-1005 | 15 | Verify whether valid IP address are set for the ping servers by SNMP and the ping success logs are captured in selfHeallog.txt.0 | Release 3 |
| 10 | TC-RDKB-NW-CONNECTIVITY-1006 | 20 | 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 | Release 3 |
| 11 | TC-RDKB-TRACE-ROUTE-1002 | 4 | Test to verify trace route of the device using ipv6 addres | Release 3 |
| 12 | TC-RDKB-FIREWALL-1000 | 9 | Verify WAN - LAN traffic is blocked when Firewall is configured to Custom Security | Release 4 |
| 13 | TC-RDKB-ETHWAN-1001 | 8 | Verify CM shutting down in ETHWAN Mode | Release 4 |
| 14 | TC-RDKB-NW-CHECK-1001 | 3 | Ping to IPV6 from Client connected device | Release 4 |
| 15 | TC-RDKB-BRIDGE-MODE-1003 | 10 | Test case to verify router functionalities persistency on mode transisitions | Release 4 |
| 16 | TC-RDKB-DOWNUPSTREAM-1001 | 3 | Validate the timestamp for upstream/downstream ranging | Release 4 |
| 17 | TC-RDKB-BRIDGE-MODE-1001 | 10 | Verification of enabling and disabling Bridge mode via SNMP | Release 4 |
| 18 | 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 | Release 4 |
| 19 | TC-RDKB-NTP-0003 | 8 | Synchronize System Time with NTP Server | Release 5 |
| 20 | TC-RDKB-DROPBEAR-1102 | 14 | Test class to Verify whether security keys related to SCP present in the device or not | Release 5 |
| 21 | TC-RDKB-DROPBEAR-1103 | 14 | Test class to Verify whether security keys related to SCP present in the device or not in ATOM side | Release 5 |
| 22 | TC-RDKB-FIREWALL-1001 | 11 | Verify LAN - WAN traffic is successful when Firewall is configured to 'Custom Security' | Release 5 |
| 23 | TC-RDKB-DHCP-SWITCH-1001 | 12 | Verify common DHCPv4 code functionality | Release 5 |
| 24 | TC-RDKB-IPV4-CHECK-5001 | 7 | Verify DNS Address persist to the Wi-Fi & Ethernet client after reboot and ethernet client gets IP within acceptable time of 5 mins | Release 5 |
| 25 | TC-RDKB-BRIDGE-MODE-1004 | 25 | Verify the functionality of LAN client after CM reboot in bridge mode | Release 5 |
| 26 | TC-RDKB-2GHZ-DNS-NSLOOKUP-5001 | 5 | Verifying the alternate DNS nslookup functionality for 2.4GHz | Release 5 |
| 27 | TC-RDKB-5GHZ-DNS-NSLOOKUP-5001 | 5 | Verifying the alternate DNS nslookup functionality for 5GHz | Release 5 |
| 28 | TC-RDKB-ALTN-DNS-1001 | 16 | Verify Alternate DNS in WiFi and Lan Connected clients | Release 5 |
| 29 | TC-RDKB-BRIDGEMODE-REVERSE-1001 | 12 | Verify Reverse SSH Connection on bridge mode | Release 6 |
| 30 | TC-RDKB-XDNS-1000 | 10 | To enable XDNS feature and Verify status after Reboot and Factory Reset the device | Release 6 |
| 31 | TC-RDKB-DHCP-CLIENTS-1001 | 12 | Test to verify DCHP range assigning of cable modem with connected clients | Release 6 |
| 32 | TC-RDKB-STATIC-IP-1000 | 14 | Configure Static IPv4 through CLI for business device | Release 6 |
| 33 | TC-RDKB-BRIDGE-MODE-1002 | 30 | Test script to validate basic Wi-Fi parameters on router mode transition | Release 6 |
| 34 | TC-RDKB-CERTS-1001 | 14 | To verify CA Bundle | Release 6 |
| 35 | TC-RDKB-INTRANET-ACC-1001 | 12 | Verify the Ping operation is successful between 2.4 GHz and Ethernet clients | Release 6 |
| 36 | TC-RDKB-INTRANET-ACC-1002 | 12 | Verify the Ping operation is successful between 5 GHz and Ethernet clients | Release 6 |
| 37 | TC-RDKB-FIREWALL-1002 | 16 | Test to verify the port forwarding and DMZ feature is working when firewall is configured to Maximum Security | Release 6 |
| 38 | TC-RDKB-XDNS-1001 | 5 | To apply and verify XDNS override at gateway level | Release 6 |
| 39 | TC-RDKB-XDNS-1002 | 15 | To apply and Verify XDNS override of Primary Level 1 ,2 and 3 IPv4 and IPv6 DNS server IPs for connected client | Release 6 |
| 40 | TC-RDKB-XDNS-1004 | 25 | Apply and Verify XDNS ,override with different cases of Invalid values of MAC and DNS IPs | Release 6 |
| 41 | TC-RDKB-INTRANET-ACC-1000 | 13 | Verify the Ping operation is successful between 2.4 GHz and 5 GHz Private Wi-Fi clients | Release 7 |
| 42 | TC-RDKB-INTRANET-ACC-1003 | 13 | Verify the Iperf operation is successful between 2.4 GHz and 5 GHz Private Wi-Fi clients | Release 7 |
| 43 | TC-RDKB-INTRANET-ACC-1004 | 12 | Verify the Iperf operation is successful between 2.4 GHz Private Wi-Fi and Ethernet clients | Release 7 |
| 44 | TC-RDKB-INTRANET-ACC-1005 | 12 | Verify the Iperf operation is successful between 5 GHz Private Wi-Fi and Ethernet clients | Release 7 |
| 45 | TC-RDKB-XDNS-PRI-ALL-LVL-5001 | 24 | Verify if Skipping either one of the DNS server IP configuration -LEVEL 1 ,2 and 3 Primary Servers | Release 7 |
| 46 | TC-RDKB-CCSP-XDNS-5001 | 6 | Verify XDNS in Process Monitor after reboot | Release 7 |
| 47 | TC-RDKB-LNF-NTWK-1001 | 23 | Verify network connectivity in clients when lnf enabled | Release 7 |
| 48 | TC-RDKB-XDNS-1006 | 23 | Test to verify Add support for secondary XDNS server | Release 7 |
| 49 | TC-RDKB-LOGUPLOAD-1001 | 3 | Verify when setting UploadLogsNow parameter to False, no upload happens | Release 8 |
| 50 | TC-RDKB-HARV-5001 | 8 | Verify the integration of RDK-B Logger with Harvester | Release 8 |
| 51 | TC-RDKB-VALIDATE-HARV-3001 | 3 | Validate Wi-Fi Harvester InterfaceDevicesWifi Report after Reboot of DUT | Release 8 |
| 52 | TC-RDKB-HARV-6009 | 14 | Validate Enable-Disable status configuration of Interface Devices Wifi Report, Radio Interface Statistics Report values after reboot | Release 8 |
| 53 | TC-RDKB-HARV-6010 | 14 | Verify PollingPeriod & ReportingPeriod values for InterfaceDevicesWifi Report and RadioInterfaceStatistics Report | Release 8 |
| 54 | TC-RDKB-UPGRADE-LOGUPLOAD-6001 | 8 | Verify successful log upload post upgrade and reboot | Release 8 |
| 55 | TC-RDKB-RDKLOG-HARV-INTG-5003 | 4 | Verify the integration of RDK-B Logger with Harvester | Release 8 |
| 56 | TC-RDKB-LOGUPLOAD-1004 | 3 | 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 | Release 8 |
| 57 | TC-RDKB-LOGUPLOAD-1003 | 10 | Verify whether log upload fails after adding dns names in hosts entry and on removing the dns names log upload should be successful | Release 8 |
| 58 | TC-RDKB-HARVESTER-REPORT-1003 | 9 | Test to verify single client harvester report for 5GHz client | Release 8 |
| 59 | TC-RDKB-LOGUPLOAD-1002 | 7 | Verify when setting UploadlogsNow parameter to true, logs gets uploaded | Release 8 |
| 60 | TC-RDKB-HARVESTER-REPORT-1001 | 17 | Test to verify single client harvester report configurations | Release 8 |
| 61 | TC-RDKB-LOGUPLOAD-1005 | 6 | Verify when setting UploadlogsNow snmp OID (1.3.6.1.4.1.17270.43.1.2.1.0) to True, logs get uploaded | Release 8 |
| 62 | TC-RDKB-LOGUPLOAD-1006 | 10 | Verify whether log upload fails after adding dns names in hosts entry and on removing the dns names log upload should be successful | Release 8 |
| 63 | TC-RDKB-HARVESTER-REPORT-1002 | 15 | Test to verify single client harvester report for 2.4GHz client | Release 8 |
| 64 | TC-RDKB-BRID-MODE-5001 | 47 | Verify device and connected client status while device is in bridge mode | Release 8 |
| 65 | TC-RDKB-DHCP-LANCLIENT-1001 | 4 | This test case is to Verify the DHCP Lan client | Release 9 |
| 66 | TC-RDKB-MIN-FIREWALL-1002 | 12 | Verify minimum firewall in WiFi2.4Ghz associated connected client | Release 10 |
| 67 | TC-RDKB-FIREWALL-1004 | 9 | Test to verify ICMP Ping Request to Ethernet client for Minimum Firewall | Release 10 |
| 68 | TC-RDKB-LAN-DNS-NSLOOKUP-5001 | 5 | Verifying the alternate DNS nslookup functionality for Ethernet | Release 11 |
| 69 | TC-RDKB-DHCP-NEG-5001 | 10 | Validate the error message when DHCP Starting and Ending address is invalid | Release 11 |
| 70 | TC-RDKB-RESERVEDIP-5011 | 18 | Verify Internet access for clients after setting the client IPV4 as reserved IP | Release 11 |
| 71 | TC-RDKB-FIREWALL-1006 | 22 | Verify ICMP Ping request ,Error message on changing firewall settings in WiFi Client | Release 12 |
| 72 | TC-RDKB-FIREWALL-1007 | 22 | Verify ICMP Ping request ,Error message on changing firewall settings in Ethernet Client | Release 12 |
| 73 | TC-RDKB-NetCat-1001 | 7 | Verify secure \"nc\" utility is implemented on Dev images for specific Devices | Release 13 |
| 74 | TC-RDKB-NTP-0002 | 2 | Validate if NTP Server is disabled on device through RFC | Release 13 |
| 75 | TC-RDKB-NTP-0001 | 2 | Validate if NTP Server is enabled on device through RFC | Release 13 |
| 76 | TC-RDKB-INTERFACE-1101 | 15 | Verify there are no reconnection of iot & config clients after successful connection | Release 13 |
| 77 | TC-RDKB-HARV-6001 | 9 | Validation of NetworkDevicesTraffic Report generation | Release 20 |
| 78 | TC-RDKB-HARV-6000 | 10 | Validation of NetworkDevicesStatus Report generation | Release 20 |
| 79 | TC-RDKB-HARV-5002 | 3 | Verify the polling period & reporting period attributes of Radio Interface Statistics Harvester Report is increased to 900 seconds. | Release 20 |
| 80 | TC-RDKB-HARV-6008 | 13 | Check after TTL whether RadioInterfaceStatistics Polling-Reporting Period changes back to defaults when set less than Default TTL Interval. | Release 20 |
| 81 | TC-RDKB-HARV-6005 | 13 | Check after TTL whether NetworkDevicesStatus Polling-Reporting Period changes back to defaults when set less than Default TTL Interval | Release 21 |
Overview
Community Forums
Content Tools
Tasks