RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Children Display |
---|
CDRouter is a comprehensive test tool for Cable/DSL/SOHO/Edge and wireless routers and other similar IP devices. The test suite contains several types of tests including functional, conformance, negative, denial of service, and scaling. CDRouter test suite simulates a networking environment by creating LAN clients, providing an ISP connection to the device under test, and exercising different protocol and traffic flows. CDRouter can create IP hosts and services that appear to be operating out in the Internet.
Previously, we utilized the CDRouter UI to trigger CDRouter test executions and review CDRouter execution results. However, after the integration of CDRouter into Automatics, we now have the capability to execute all 1.0 ,3.0 test cases and CDRouter test cases exclusively through Automatics.
<Work In Progress>
Table of Contents |
---|
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.
Following diagram shows the interaction among Automatics CD Router service and CD Router Automation Engine
APIs available
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.
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": 1150
APIs required
APIs available
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
...
...
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.
From the Trigger Execution Manually Page, user can select the CDRouter tests for execution.
Adding 2 new tables to automatics DB:
...
1. Navigate to the URL "", login and select 'Trigger Execution Manually' from the 'Manage Trigger Dropdown'.
2. Enter the build name and Select the Execution Environment Type, quick test if needed. Click on next button if all the mandatory fields are added.
...
3. User can see all the CDRouter testcases that are present.
...
2. Now click on the Edit Script Details Icon corresponding to the testcase to be edited.
3. Now user can see a pop-up, check all the mandatory fields to entered/changed. update the corresponding fields and click on next button
4. Under 'Select Test Source' drop down user should select CDrouter.
5. User should enter the mandatory fields and and click save button to save the changes.
Job Manager
When the user triggers the job and navigating to the Manage Test Trigger page, user can verify the job status depending on their testcase (RDKV or RDKB) and selecting the Job Manager button can able to see the triggered Job.
To find the execution results by clicking this button Once testcase triggered successfully. Following image will be available.
User can find the full execution logs by clicking this button. . User can get the full execution logs and find out the pass and failure steps in detail.
By clicking this icon we can see the child Jobs name. After that click on this icon . Then CDRouter Execution logs will be available in the Jenkins icon. We can verify pass and failures of all the steps.
Configuration Changes in Orchestration
1.User should make the following changes
1.1 Setting Pagination Limit
Pagination Limit:
user should be able to set the pagenation limit from master_config table. ( User should set CDROUTER_PAGINATION_LIMIT from MASTER_CONFIG table in )
1.2 Setting CD Routers url
user should set the urls for different CDRouters available in MASTER_CONFIG table. If more than one CDRouters are available also user has to set the urls according in the master_config table under CDROUTERS column.
Example : (CDROUTERS master config value:
[{"name":"CDRouter1","url":"http://123.456.789.012"},{"name":"CDRouter2","url":"http://987.654.321.012"}] )
1.3 Setting CDRouter base Url:
user should set the base CD router url in master-config table under CDROUTER_SERVICE_BASE_URL column.
Example: http://localhost:8080/api/cdrouter/service
2.Adding a new test type as CDROUTER
...
3. user should add 'CDROUTER' in the configuration value and click on save changes to save the new test_type.
3.Creating a New Job as AUTO_CDROUTER_TEST_JOB
2. Click on add new job on the right top corner as shown below.
...
Configuration Changes in MicroService
1.Java Version
This microservice needs JAVA 11 to run. User should use Java 11 to make this microservice up.
1.2 Automatics base url
In CDrouter service user should navigate to application.properties and update automatics.url with proper automatics url.
...