RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
SI No | Automation ID | Steps | Summary | Revision |
---|---|---|---|---|
1 | TC-TLMTRY-3009 | 4 | Verify log upload to repository | Revision 13 |
2 | TC-TLMTRY-3023 | 7 | Generic test To Validate the sanity telemetry markers | Revision 14 |
3 | TC-TLMTRY-3022 | 6 | Test to verify telemetry run post reboot for previous logs | Revision 14 |
4 | TC-TLMTRY-3021 | 5 | Test case to verify ping test telemetry feature | Revision 15 |
5 | 3DOTO-TC-TELEMETRY-V2-RDKV-024 | 6 | Telemetry t2 negative checks | Revision 16 |
6 | 3DOTO-TC-MTLS-1001 | 7 | Testcase to verify telemetry 2.0 multiple profile | Revision 17 |
7 | 3DOTO-TC-TELEMETRY-V2-RDKV-023 | 6 | verify Profile Name check | Revision 17 |
8 | 3DOTO-TC-TELEMETRY-V2-RDKV-006 | 6 | GenerateNow parameter check | Revision 17 |
9 | 3DOTO-TC-TELEMETRY-V2-008 | 4 | T2 module MUST support self heal. | Revision 17 |
10 | 3DOTO-TC-TELEMETRY-V2-RDKV-002 | 5 | Test to verify telemetry 2.0 multiple profile | Revision 19 |
11 | 3DOTO-TC-TELEMETRY-V2-RDKV-015 | 7 | Telemetry data Model check | Revision 19 |
12 | TC-TELEMETRY-2020 | 1 | Validate Telemetry integrity check with respect to DCM | Revision 20 |
13 | 3DOTO-TC-REBOOT-1010 | 2 | Verify if there is duplicate data for prev_reboot_split marker uploaded to Telemetry | Revision 20 |
14 | 3DOTO-TC-TELEMETRY-V2-RDKV-1000 | 11 | Validating Telemtry 2.0 set profile | Revision 20 |
15 | 3DOTO-TC-TELEMETRY-WIFI-1001 | 6 | Test case to verify whether WIFI telemetry stats logs retrieved successfully or not | Revision 20 |
16 | 3DOTO-TC-TLMTRY-OI-1001 | 5 | Enable Telemetry 2.0 and check whether the logs are being uploaded to correct url | Revision 20 |
17 | TC-TLMTRY-3018 | 4 | Test To Validate the Telemetry request being sent | Revision 21 |
18 | 3DOTO-TC-TELEMETRY-V2-RDKV-005 | 6 | Profile Deletion Check | Revision 21 |
19 | 3DOTO- TC-TELEMETRY-V2-RDKV-003 | 6 | Different ReportingIntervals and ActivationTimeOut check | Revision 22 |
20 | 3DOTO- TC-TELEMETRY-V2-RDKV-004 | 7 | Same ReportingIntervals and ActivationTimeOut check | Revision 22 |
21 | 3DOTO- TC-TELEMETRY-V2-RDKV-018 | 8 | Profile persist after Reboot | Revision 22 |
22 | 3DOTO-TC-TELEMETRY-RDKV-1034 | 10 | Test to verify non-root privileges in RBUS mode | Revision 22 |