Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

<Work In Progress>

Children Display

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.

Image Removed

Trigger CD Router Tests from Automatics

Following diagram shows the interaction among Automatics CD Router service and CD Router Automation Engine

Image Removed

CD Router and Automatics in CI/CD Pipeline

...

Use Case

Image Removed

Changes in Existing Screens

...

E2E RDK Request Filter Page

...

Introduction

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.

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

Image Removed

After CDRouter automation ids are selected, they are displayed in the main page of E2E RDK Request Filter Page.

Image Removed

Trigger Execution Manually Page

From the Trigger Execution Manually Page, user can select the CDRouter tests for execution.

Image Removed

CDRouter Rest APIs 

Execution side

APIs available

  1. 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.

  1. 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": 1150

APIs required

  1. Requires an endpoint to get details of test cases/test names configured in a pacakage
  2. Requires an endpoint to get result status and logs separate for each test case in a package

           

Test Configuration side

APIs available

  1. To get the list of packages configured in CDRouter 

we can use webAPI mentioned in below link

CD Router Job Manager Screen

We can use API mentioned in below link, to get the status of jobs. When execution status changes to running, in the response of this API, we will get the result id. Using result id, we can get the result details of the job.

To download execution logs, we can use API mentioned in below link:

Image Removed

 CD Router Results Page

Image Removed

Config Manage Page

From this page, user can view configs in CD Router

Image Removed

Package Manage Page

From this page, user can view packages in CD Router

Image Removed

DB Structure

Adding 2 new tables to automatics DB:

Image Removed

Reference CD Router Web APIs:

https://support.qacafe.com/cdrouter/cdrouter-web-api/