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-WEBPA-1012 | 5 | Verify reboot reason notifications sent for different types of reboot | Revision 14 |
2 | 3DOTO-TC-XCAST-1001 | 5 | CDL Curl error 404, Received HTTPS 404 Response from Xconf Server. Retry logic not needed | Revision 14 |
3 | 3DOTO-TC-XCAST-1002 | 10 | Test case to verify Dial App casting | Revision 14 |
4 | TC-RFCWAIT-1001 | 5 | Test case to verify post reboot rfc-config.service start | Revision 16 |
5 | TC-RFC-1202 | 5 | Test to verify all the PROD deployed RFC features | Revision 16 |
6 | TC-RFC-3001 | 5 | Verifying Default/built-in RFC config from DCM | Revision 17 |
7 | TC-RFC-3020 | 11 | Test case to verify tr181 params defined in single datamodel file | Revision 19 |
8 | TC-RFC-3017 | 6 | Test to verify config change time parameter in tr181store file | Revision 19 |
9 | TC-RFC-3005 | 11 | Test class to verify whether Set operation is successful or not for TR181 params through RFC | Revision 20 |
10 | TC-RFC-3010 | 10 | Test Case to Verify RFC client to use get/test/set for TR-181 parameters | Revision 20 |
11 | TC-RFC-3015 | 5 | Verify RFC parameter retrieval using new tr181 utility for read-only parameters | Revision 20 |
12 | TC-RFC-3012 | 16 | Test case to Verify RFC response verification support | Revision 20 |
13 | TC-RFC-3002 | 10 | Test Case to verify feature Enable/Disable via DCM | Revision 20 |
14 | TC-RFC-3014 | 9 | Verify RFC parameter retrieval using new tr181 utility for readWrite parameters | Revision 18 |
15 | TC-RFC-3011 | 7 | Verify RFC Request | Revision 17 |
16 | TC-RFC-3013 | 6 | Verify RFC parameter retrieval using the new tr181 utility for read-only parameters | Revision 18 |
17 | TC-RFC-1007 | 10 | Test case to verify configurable service end-points for RDK connections using tr181 param | Revision 23 |
18 | 3DOTO-TC-RFC-1008 | 5 | Test case to verify defaultRFC settings | Revision 27 |
19 | TC-RFC-1015 | 12 | To verify Remove/opt/RFC location andcontent | Revision 27 |
20 | TC-RFC-1005 | 8 | Test case to verify Feature Instance name in telemetry new enpoint RFC payload data | Revision 28 |
21 | TC-RFC-1009 | 19 | Configurable service end-points for RDK connections Phase 3 | Revision 28 |
22 | 3DOTO_RDKE-NO_LOG_UPL_SCH_DISABLE | 8 | Upload on reboot is false and scheduled reboot RFC is false then the log should not be uploaded | Revision 31 |
23 | 3DOT0-TC-LOG_UPLO_ON_UNSC_REBOOT_DISABLE | 8 | Upload on reboot is true and unscheduled reboot RFC is false in this scenario log should be uploaded | Revision 31 |
24 | 3DOTO-RDKE-NO_LOG_UPL_UNSCH_ENABLE | 8 | upload on reboot is false : unschedule reboot : rfc is true--> log should not be uploaded | Revision 31 |
25 | 3DOTO-TC-RDKE-LOG_UPL_SCH_ENABLE | 8 | upload on reboot is true : scheduled reboot : rfc is true--> log should be uploaded | Revision 31 |