RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
<Work In Progress>
Following diagram shows interaction of Orchestration tool with CD Router Automation Engine via CD Router Service.
Advantage: No Jenkins resources are needed for triggering test execution.
Trigger CD Router Tests from Automatics
Following diagram shows the interaction among Automatics CD Router service and CD Router Automation Engine
CDRouter Rest APIs
Execution side
APIs available
- To trigger an execution job in CDRouter, we can use webAPI mentioned in below link.
Inputs to be passed are package name, device config and test config
On success, it will return 200 response code and status of execution will be Pending initially.
- To get the status of job, we can use the below rest endpoint
We can think of background thread checking for updates of running jobs from cdrouter.
https://support.qacafe.com/cdrouter/cdrouter-web-api/jobs#get-a-job
3. To get execution result of job, we can use webAPI mentioned in below link. The input to the rest api result id and in output we overall status count of all test cases.
"loops": 5, "tests": 2552, "pass": 0, "fail": 1150APIs required
- Requires an endpoint to get details of test cases/test names configured in a pacakage
- Requires an endpoint to get result status and logs separate for each test case in a package
Test Configuration side
APIs available
- To get the list of packages configured in CDRouter, we can use webAPI mentioned in below link
https://support.qacafe.com/cdrouter/cdrouter-web-api/packages#list-packages
2. To get the list of test scripts/test names in a package, we can use webAPI mentioned in below link
https://support.qacafe.com/cdrouter/cdrouter-web-api/packages#get-a-package
3.To get the device configs, we can use webAPI mentioned in below link
https://support.qacafe.com/cdrouter/cdrouter-web-api/devices#list-devices
4.To get the test configs, we can use webAPI mentioned in below link
https://support.qacafe.com/cdrouter/cdrouter-web-api/configs#list-configs
CD Router and Automatics in CI/CD Pipeline
Use Case
Changes in Existing Screens
| Existing Pages | Purpose | Changes Expected |
|---|---|---|
E2E RDK Request Filter Page | Configure CD Packages for CI executions | New Tab for selecting CD Router Tests |
| Trigger Execution Manually Page | User can select CDRouter packages trigger executions | New Tab for selecting CD Router Tests |
| Job Manager Page | User can view the progress of CD Router package executions - Each job will show the status of single package | Change in actions button since Jenkins is not needed |
| Execution Results Page | To view overall execution results like Total script count, and its pass and fail count | No change in UI |
| Detailed Execution Results Page | To view the execution results of each test script (in cd router each test case contains only one step) | No change in UI |
| Manage script page | To map cdrouter package with automatics automation id | Change in components that are displayed, new fields to come in |
E2E RDK Request Filter Page
In the request filter page, new tab CDRouter Tests will be coming where user can select CDRouter Tests for CI/CD integration
After CDRouter automation ids are selected, they are displayed in the main page of E2E RDK Request Filter Page.
Trigger Execution Manually Page
From the Trigger Execution Manually Page, user can select the CDRouter tests for execution.
DB Structure
Adding 2 new tables to automatics DB:
Reference CD Router Web APIs:
Overview
Community Forums
Content Tools
Tasks