RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Release Notes
RDKM Coverage Test cases (RDK-B)
Version: 3.0
12 January 2022
Revision History
Release No. | Date | Revision Description |
1.0 | 02 Nov 2021 | |
2.0 | 08 Dec 2021 | 2nd Release |
3.0 | 12 Jan 2022 | 3rd Release |
This Release Notes document details on the delivery of 60 RDKB test cases for RDK Community.Features covered in this release are
Following are the Test cases delivered in this release:
No | Test case ID | Cadence/Test Type | Steps | Description |
---|---|---|---|---|
1 | TC-RDKB-NW-CONNECTIVITY-1002 | 2DAYS | 12 | Verify the ping related default values in the device after factory resetting by SNMP |
2 | TC-RDKB-WH-SNMP-1000 | 4HOUR | 12 | Verify get SNMP for warehouse OIDs |
3 | TC-RDKB-SNMP-1007 | 4HOUR | 6 | Verification of DOCSIS Mib functionality |
4 | TC-RDKB-SNMP-5050 | 2DAYS | 32 | Verify Access Points security mode via SNMP parameter |
5 | TC-RDKB-CDL-EXCLUDE-1006 | NEW_FEATURE | 3 | To verify firmware update with AutoExcluded. Enable is true, AutoExcluded.XconfUrl is empty |
6 | TC-RDKB-NW-CONNECTIVITY-1005 | 2DAYS | 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 |
7 | TC-RDKB-NW-CONNECTIVITY-1006 | 2DAYS | 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 |
8 | TC-RDKB-SNMP-1012 | 2DAYS | 6 | Verify enabling/disabling bridge mode through SNMP v3 is successful |
9 | TC-RDKB-CDL-EXCLUDE-1001 | NEW_FEATURE | 4 | To verify firmware update with AutoExclude.Enable is false, XconfUrl is empty |
10 | TC-RDKB-CDL-EXCLUDE-1003 | NEW_FEATURE | 3 | To verify firmware update with AutoExcluded.Enable is false, AutoExcluded.XconfUrl is CI XCONF URL |
11 | TC-RDKB-NW-CONNECTIVITY-1010 | 2DAYS | 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 |
12 | TC-RDKB-PARODUS-1006 | 2DAYS | 19 | Verify themis curl to acquire JWT for parodus |
13 | TC-RDKB-PARODUS-1008 | 2DAYS | 12 | Verify Integrate parodus2ccsp with Yocto |
14 | TC-RDKB-PARODUS-1007 | 2DAYS | 18 | Verify Integrate parodus2ccsp with Yocto |
15 | TC-RDKB-PARODUS-1009 | 4HOUR | 10 | Test to verify configurable parodus reboot reason |
16 | TC-RDKB-PARODUS-ENBL-1004 | 2DAYS | 8 | Verify Webpa commands when Parodus is Enabled |
17 | TC-RDKB-PARODUS-NOPOLL-1001 | 4HOUR | 8 | Test to verify parodus nopoll |
18 | TC-RDKB-SNMP-1027 | 4HOUR | 12 | Verify the cable modem SNMPv3 parameters from RDK using RFC/XConf (Broadcom RDKB platforms) |
19 | TC-RDKB-WEBPA-1013 | 2DAYS | 10 | Verify Webpa requests (GET/SET/PUT/POST/DELETE) are working fine and Webpa notifications should be sent successfully to server |
20 | TC-RDKB-SYSTEM-1021 | 4HOUR | 5 | Test to verify removal of telnet daemon |
21 | TC-RDKB-SYSTEM-5002 | 2DAYS | 7 | Verify logging for Harvester and LMLite reports |
22 | TC-RDKB-TRACE-ROUTE-1001 | 2DAYS | 4 | Test to verify trace route of the device using ipv4 address |
23 | TC-RDKB-SNMP-1021 | 2DAYS | 2 | Test to Verify that the device does not respond to invalid community string |
24 | TC-RDKB-SNMP-1022 | 2DAYS | 2 | Validate that the device does not give valid SNMP response for invalid MTA community String |
25 | TC-RDKB-SNMP-1010 | 2DAYS | 8 | Verify Configuring the AAA server Primary/Secondary IP address for 2.4 and 5GHz |
26 | TC-RDKB-SYSTEM-5007 | 2DAYS | 3 | Verify Xconf default value,Hardware version,Linux kernel upgrade version from logs |
27 | TC-RDKB-REBOOT-5001 | 4HOUR | 6 | Test case to verify the docsdevresetnow mib functionality |
28 | TC-RDKB-FS-LAYOUT-1001 | SUPPLEMENTARY | 2 | nvram file system layout validation |
29 | TC-RDKB-FS-LAYOUT-1002 | SUPPLEMENTARY | 2 | nvram2 file system layout validation |
30 | TC-RDKB-FS-LAYOUT-1003 | SUPPLEMENTARY | 3 | tmp file system layout validation |
31 | TC-RDKB-FS-LAYOUT-1004 | SUPPLEMENTARY | 3 | minidumps file system layout validation |
32 | TC-RDKB-FS-LAYOUT-1005 | SUPPLEMENTARY | 2 | rdklogs file system layout validation |
33 | TC-RDKB-FS-LAYOUT-1006 | SUPPLEMENTARY | 3 | cron and etc file system layout validation |
34 | TC-RDKB-FS-LAYOUT-1007 | SUPPLEMENTARY | 2 | dhcp_static_hosts file system layout validation |
35 | TC-RDKB-FS-LAYOUT-1008 | SUPPLEMENTARY | 2 | xupnp file system layout validation |
36 | TC-RDKB-FS-LAYOUT-1009 | SUPPLEMENTARY | 2 | Dibbler file system layout validation |
37 | TC-RDKB-PARODUS-1001 | 2DAYS | 3 | Removal of parodus start shell script changes from yocto |
38 | TC-RDKB-WEBPA-PARALLEL-1006 | 4HOUR | 1 | Verify multiple WEBPA requests in parallel |
39 | TC-RDKB-SECURITY-1001 | 2DAYS | 5 | Test to verify the latest OpenSSL version in RDKB devices |
40 | TC-RDKB-SECURITY-2203 | 4HOUR | 16 | Verify third party tracker is blocked after firewall restart |
41 | TC-RDKB-WIFI-RESTORE-1001 | 4HOUR | 21 | 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 webpa command for doing WIFI settings reset |
42 | TC-RDKB-TELEMETRY-VER2-1001 | 2DAYS | 6 | Verify default values for T2 component TR-181 parameters |
43 | TC-RDKB-TELEMETRY-VER2-1002 | 2DAYS | 15 | Verify T2 component log files, process and other basic checks |
44 | TC-RDKB-WEBPA-1008 | 2DAYS | 17 | Verify all reports for Harvester and LMLite are enabled and Verify CcspWebpaadapter responds to WEBPA GET, SET requests. |
45 | TC-RDKB-XCONF-CDL-1002 | 2DAYS | 10 | Access SSR and Xconf CDL Via Direct Communication |
46 | TC-RDKB-CDL-5003 | 2DAYS | 9 | Enhance TC-RDKB-CDL-502 to include code download using HTTPS |
47 | TC-RDKB-SYSTEM-1031 | 4HOUR | 10 | Verify no zombie dnsmasq process detected by self heal |
48 | TC-RDKB-MESH-WIFI-1004 | 4HOUR | 2 | Verify enabling MESH when the Bridge Mode is enabled. |
49 | TC-RDKB-TRACE-ROUTE-1002 | SUPPLEMENTARY | 4 | Test to verify trace route of the device using ipv6 address |
50 | TC-RDKB-CDL-EXCLUDE-1008 | NEW_FEATURE | 4 | To verify firmware update with AutoExcluded.Enable is true, AutoExcluded.XconfUrl is MOCK XCONF URL |
51 | TC-RDKB-CDL-EXCLUDE-1007 | NEW_FEATURE | 3 | To verify firmware update with AutoExcluded.Enable is true, AutoExcluded.XconfUrl is CI XCONF URL |
52 | TC-RDKB-CDL-EXCLUDE-1005 | NEW_FEATURE | 4 | To verify firmware update with AutoExcluded.Enable is true, AutoExcluded.XconfUrl is empty |
53 | TC-RDKB-CDL-EXCLUDE-1002 | 2DAYS | 3 | To verify firmware update with AutoExcluded.Enable is false, AutoExcluded.XconfUrl is empty |
54 | TC-RDKB-SYSTEM-5502 | 4HOUR | 2 | Verify the data only partition /nvram is mounted as non-executable |
55 | TC-RDKB-SYSTEM-5503 | 4HOUR | 2 | Verify the data only partition /nvram2 is mounted as non-executable |
56 | TC-RDKB-WEBPA-PERF-1006 | 2DAYS | 6 | Calculate the Average Response Time for two, three and four Get parameter Requests in WEBPA |
57 | TC-RDKB-TELEMETRY-VER2-1004 | 4HOUR | 4 | Verify negative scenarios for Telemetry version 2 |
58 | TC-RDKB-TELEMETRY-VER2-1005 | 4HOUR | 14 | Verify negative scenarios for Telemetry version 2 |
59 | TC-RDKB-SECURITY-2001 | 2DAYS | 2 | Upgrade Dropbear to latest version |
60 | TC-RDKB-SYSTEM-1101 | 4HOUR | 1 | Verify DBus - Overly permissive system setting |
GIT URL:
RDKB Generic Test Utils : https://code.rdkcentral.com/r/admin/repos/rdk/tools/automatics/rdkb-test-utils
RDKB Generic Tests : https://code.rdkcentral.com/r/admin/repos/rdk/tools/automatics/rdkb-tests
Branch: rdk-next
Reference RTAUTO : https://jira.rdkcentral.com/jira/browse/AUTOMATICS-23
Reference Documentation : https://wiki.rdkcentral.com/display/ASP/Automatics+Orchestration+User+Manual
Developer instructions : https://wiki.rdkcentral.com/display/ASP/Automatics+Developer+Guide
Test Case Configurations: Automatics RDK-B Test Property configuration