RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Released Automatics Telemetry Related Test Cases - 72
Test Case Type | Total Count |
---|---|
1 DOT0 | 24 |
3 DOT0 | 48 |
Features Covered
SI NO | Automation ID | Steps | Summary | Release | Contributor | Test Case Type |
---|---|---|---|---|---|---|
1 | TC-RDKB-TELEMETRY-VER2-1001 | 6 | Verify default values for T2 component TR-181 parameters | Release 3 | RDKM | 1 DOT0 |
2 | TC-RDKB-TELEMETRY-VER2-1002 | 15 | Verify T2 component log files, process and other basic checks | Release 3 | RDKM | 1 DOT0 |
3 | TC-RDKB-TELEMETRY-VER2-1004 | 4 | Verify negative scenarios for Telemetry version 2 | Release 3 | RDKM | 1 DOT0 |
4 | TC-RDKB-TELEMETRY-VER2-1005 | 14 | Verify negative scenarios for Telemetry version 2 | Release 3 | RDKM | 1 DOT0 |
5 | TC-RDKB-TELEMETRY-VER2-1003 | 15 | Verify telemetry 2 configurations persist over a device upgrade | Release 4 | RDKM | 1 DOT0 |
6 | TC-RDKB-TELEMETRY-1004 | 12 | Verify TR-181 message-bus as new data source for telemetry | Release 6 | RDKM | 1 DOT0 |
7 | TC-RDKB-WIFI-TELEMETRY-1004 | 10 | Validate CPU & Memory usage for Maximum Tx&Rx rate | Release 6 | RDKM | 1 DOT0 |
8 | TC-RDKB-WIFI-TELEMETRY-1008 | 13 | Verify enhanced Wi-Fi logging in Telemetry for 2.4ghz public Wi-Fi parameters | Release 6 | RDKM | 1 DOT0 |
9 | TC-RDKB-WIFI-TELEMETRY-1009 | 13 | Verify enhanced Wi-Fi logging in Telemetry for 5ghz Public Wi-Fi parameters | Release 6 | RDKM | 1 DOT0 |
10 | TC-RDKB-TELEMETRYENDPOINT-2250 | 10 | Test to verify Use new telemetry endpoint | Release 6 | RDKM | 1 DOT0 |
11 | TC-RDKB-TELEMETRY-CC-1006 | 12 | Test to verify telemetry Logging for Wi-Fi Connected devices | Release 6 | RDKM | 1 DOT0 |
12 | TC-RDKB-TELEMETRY-CC-1005 | 12 | Test to verify telemetry Logging for Ethernet Connected devices | Release 6 | RDKM | 1 DOT0 |
13 | TC-RDKB-WIFI-TELEMETRY-1005 | 11 | Verify enhanced Wi-Fi logging in Telemetry for 5ghz private Wi-Fi parameters | Release 6 | RDKM | 1 DOT0 |
14 | TC-RDKB-WIFI-TELEMETRY-1001 | 12 | Validate telemetry markers for Maximum Tx&Rx rate for each wifi clients | Release 7 | RDKM | 1 DOT0 |
15 | TC-RDKB-TELEMETRY-1006 | 9 | Verify telemetry/logging for memory fragmentation details | Release 7 | RDKM | 1 DOT0 |
16 | TC-RDKB-GWCONFIG-TLMTRY-5002 | 12 | Verify the telemetry marker & log messages for Gateway Configuration with the different SSID Name set for both 2.4 GHz & 5 GHz Radios | Release 7 | RDKM | 1 DOT0 |
17 | TC-RDKB-GWCONFIG-TLMTRY-5001 | 12 | Verify the telemetry marker & log messages for Gateway Configuration with the same SSID Name set for both 2.4 GHz & 5 GHz Radios | Release 7 | RDKM | 1 DOT0 |
18 | TC-RDKB-WIFI-TELEMETRY-1000 | 10 | Verify enhanced Wifi logging in Telemetry for 2.4ghz private wifi parameters | Release 7 | RDKM | 1 DOT0 |
19 | TC-RDKB-TELEMETRY-1003 | 30 | Verify configurable telemetry tag functionality | Release 8 | RDKM | 1 DOT0 |
20 | TC-RDKB-TMTRY_UPLD_RCVRY-1015 | 30 | Telemetry upload failure recovery | Release 9 | RDKM | 1 DOT0 |
21 | TC-RDKB-NONROOT-T2-1000 | 13 | Verify Running Telemetry 2.0 process as non-root Previllages | Release 11 | RDKM | 1 DOT0 |
22 | TC-RDKB-WIFI-WIFI-RDKB-TELE-5001 | 28 | Verify the RDKB telemetry logs in Gateway connected with Private WiFi,XHS,Xfinity | Release 11 | RDKM | 1 DOT0 |
23 | TC-RDKB-TELEMETRY-1500 | 17 | To Collect network latency and metadata | Release 11 | RDKM | 1 DOT0 |
24 | TC-RDKB-ACTV-TMTRY-5001 | 11 | validate the Activation Journey including various events with log Messages | Release 13 | RDKM | 1 DOT0 |
25 | 3DOT0-TC-RDKB-TELEMETRY-RBUS-1002 | 29 | Test to verify T2 does not do retries when protocol is RBUS_METHOD and allow empty Parameter[] in profiles | Release 16 | RDKM | 3 DOT0 |
26 | 3DOT0-TC-RDKB-MTLS-1005 | 7 | Testcase to verify telemetry 2.0 multiple profile | Release 16 | RDKM | 3 DOT0 |
27 | 3DOT0-TC-RDKB-MTLS-1006 | 9 | Testcase to verify telemetry 2.0 multiple profile | Release 16 | RDKM | 3 DOT0 |
28 | 3DOT0-TC-RDKB-RBUS-1003 | 6 | Add Support to RBUS Subscribe API to get Initial Value | Release 16 | RDKM | 3 DOT0 |
29 | 3DOT0-TC-RDKB-TELEMETRY_WIFI-1001 | 12 | Test case to verify wifihealth markers telemetry 2.0 upload | Release 16 | RDKM | 3 DOT0 |
30 | 3DOT0-TC-RDKB-WEBPA_SIZE_RBUS-1012 | 17 | Verify string size limit increased with RBUS enable. | Release 16 | RDKM | 3 DOT0 |
31 | 3DOT0-TC-RDKB-MESHAGENT-1001 | 33 | Test to verify Telemetry 2.0 - Non CCSP Components |Mesh agent | Release 17 | RDKM | 3 DOT0 |
32 | 3DOT0-TC-RDKB-MTLS-1002 | 7 | Testcase to verify telemetry 2.0 multiple profile | Release 17 | RDKM | 3 DOT0 |
33 | 3DOT0-TC-RDKB-TELEMETRY-1026 | 42 | [Telemetry 2] Short-lived Report Profiles | Release 17 | RDKM | 3 DOT0 |
34 | 3DOT0-TC-RDKB-TELEMETRY-1028 | 29 | [Telemetry Framework] Flexible Reporting Adjustments - Part 1 | Release 17 | RDKM | 3 DOT0 |
35 | 3DOT0-TC-RDKB-TELEMETRY-RBUS-1009 | 29 | [Telemetry Framework] Profile processing changes for reports using RBUS_METHOD | Release 17 | RDKM | 3 DOT0 |
36 | 3DOT0-TC-RDKB-RBUSCLI-1001 | 18 | Executing the RBUSCLI command in Interactive mode | Release 17 | RDKM | 3 DOT0 |
37 | 3DOT0-TC-RDKB-TELEMETRY_ETH-1001 | 41 | Test to verify Telemetry for Ethernet Connected Clients | Release 18 | RDKM | 3 DOT0 |
38 | 3DOT0-TC-RDKB-TELEMETRY-1027 | 44 | Short-lived Report Profiles controls (Failure in S7 can be traced in the open ticket https://ccp.sys.comcast.net/browse/RTAUTO-41820) | Release 18 | RDKM | 3 DOT0 |
39 | 3DOT0-TC-RDKB-TELEMETRY-RBUS-1001 | 29 | Test to verify Support inclusion of rbus event data in T2 reports | Release 18 | RDKM | 3 DOT0 |
40 | 3DOT0-TC-RDKB-TELEMETRY2_RBUS-1001 | 25 | Test case to verify new protocols supported by telemetry 2 | Release 18 | RDKM | 3 DOT0 |
41 | 3DOT0-TC-RDKB-MTLS-1003 | 17 | Test to check that T2 shall use static xPKI certs available in firmware whenever dynamic xPKI certs are not available. | Release 19 | RDKM | 3 DOT0 |
42 | 3DOT0-TC-RDKB-RBUS-MP-RPLMT-1001 | 17 | Verify profile replacement check in RBUS mode | Release 20 | RDKM | 3 DOT0 |
43 | 3DOT0-TC-RDKB-TELEMETRY_WIFI-1002 | 22 | Test to verify the 2.4ghz and 5ghz channel values between telemetry and wifi health | Release 20 | RDKM | 3 DOT0 |
44 | 3DOT0-TC-RDKB-RBUS-T2-MP-1001 | 25 | Verify updating profiles with different configurations like ReportingInterval, ActivationTimeOut. | Release 20 | RDKM | 3 DOT0 |
45 | 3DOT0-TC-TELEMETRY-V2-002 | 7 | Testcase to verify telemetry 2.0 multiple profile | Release 21 | RDKM | 3 DOT0 |
46 | 3DOT0-TC-TELEMETRY-V2-004 | 9 | Same ReportingIntervals and ActivationTimeOut check | Release 21 | RDKM | 3 DOT0 |
47 | 3DOT0-TC-TELEMETRY-V2-023 | 8 | Verify Profile Name check | Release 21 | RDKM | 3 DOT0 |
48 | 3DOT0-TC-TELEMETRY-V2-015 | 6 | Telemetry data Model check | Release 21 | RDKM | 3 DOT0 |
49 | 3DOT0-TC-TELEMETRY-V2-003 | 7 | Different ReportingIntervals and ActivationTimeOut check | Release 21 | RDKM | 3 DOT0 |
50 | 3DOT0-TC-TELEMETRY-V2-005 | 8 | Profile Deletion Check | Release 21 | RDKM | 3 DOT0 |
51 | 3DOT0-TC-TELEMETRY-V2-018 | 8 | Profile persist after Reboot | Release 21 | RDKM | 3 DOT0 |
52 | 3DOT0-TC-TELEMETRY-V2-1024 | 19 | Test to verify telemetry2_0 process with non-root privilege | Release 22 | RDKM | 3 DOT0 |
53 | 3DOT0-TC-TELEMETRY-V2-024 | 7 | Telemetry t2 negative checks | Release 22 | RDKM | 3 DOT0 |
54 | 3DOT0-TC-TELEMETRY-V2-1031 | 11 | Test to verify T2 Ad hoc Checks | Release 22 | RDKM | 3 DOT0 |
55 | 3DOT0-TC-RDKB-RBUS-T2-SWP-1001 | 17 | Verify if T2 component supports more than 800 parameters per profile | Release 23 | RDKM | 3 DOT0 |
56 | 3DOT0-TC-TELEMETRY-V2-001 | 10 | Test case to verify telemetry 2.0 with multiple profile | Release 25 | RDKM | 3 DOT0 |
57 | 3DOT0-TC-TELEMETRY-V2-006 | 6 | GenerateNow parameter check | Release 25 | RDKM | 3 DOT0 |
58 | 3DOT0-TC-TELEMETRY-V2-1034 | 11 | Test to verify non-root privileges in RBUS mode | Release 25 | RDKM | 3 DOT0 |
59 | 3DOT0-TC-TELEMETRY-UTOPIA-1001 | 30 | Test to verify telemetry2_0 btime markers | Release 25 | RDKM | 3 DOT0 |
60 | 3DOT0-TC-RDKB-TELEMETRY-PROFILE-1001 | 40 | Verify device allow built-in T2 Report Profiles as part of RDK image | Release 25 | RDKM | 3 DOT0 |
61 | 3DOT0-TC-RDKB-TELEMETRY-ACCUM-1001 | 12 | [Telemetry 2] Support value accumulation markers | Release 28 | RDKM | 3 DOT0 |
62 | 3DOT0-TC-TELEMETRY-UTOPIA-1003 | 29 | Test to verify telemetry2_0 Sys info utopia markers | Release 28 | RDKM | 3 DOT0 |
63 | 3DOTO-TC-RDKB-TELEMETRY_ROOTNAME-1001 | 26 | To verify T2 reports to have configurable JSON root name | Release 30 | RDKM | 3 DOTO |
64 | 3DOTO-TC-RDKB-MTLS-1004 | 10 | Set junk URL and make sure T2 shall always connect to XConf URL configured | Release 31 | RDKM | 3 DOT0 |
65 | 3DOTO-TC-RDKB-MTLS-1001 | 5 | Testcase to verify telemetry 2.0 multiple profile | Release 31 | RDKM | 3 DOTO |
66 | 3DOTO-TC-RDKB-TELEMETRY-XCONF-1001 | 10 | Test case to verify telemetry2 is fetching the markers for the configured T2 profile in XCONF, when T2 is enabled | Release 33 | RDKM | 3 DOTO |
67 | 3DOTO-TC-RDKB-TELEMETRY-WEBCONFIG-1000 | 12 | Webconfig feature - Telemetry Multiprofile Validation | Release 33 | RDKM | 3 DOT0 |
68 | 3DOTO-TC-RDKB-TELEMETRY-V2-1030 | 7 | Validate reporting of Telemetry grep markers | Release 33 | RDKM | 3 DOTO |
69 | 3DOTO-TC-RDKB-TELEMETRY-V2-1032 | 5 | Validate reporting of Telemetry data model markers | Release 33 | RDKM | 3 DOT0 |
70 | 3DOTO-TC-RDKB-BHT-TELEMETRY-1000 | 26 | Verification of telemetry feature | Release 33 | RDKM | 3 DOTO |
71 | 3DOTO-TC-RDKB-TELEMETRY-SCHEDULING-1000 | 26 | Validate telemetry 2.0 properties - ReportingInterval, ActivationTimeOut and GenerateNow | Release 34 | RDKM | 3 DOT0 |
72 | 3DOTO-TC-RDKB-TELEMETRY-V2-1005 | 22 | Process T2 Report Profiles received in msgPack format | Release 34 | RDKM | 3 DOTO |