Versions Compared

Old Version 13

changes.mady.by.user Radhika Sudhakaran

Saved on

compared with

New Version 14

changes.mady.by.user Radhika Sudhakaran

Saved on

Key

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

...

Existing PagesPurposeChanges Expected

E2E RDK Request Filter Page

Configure CD Packages for CI executionsNew Tab for selecting CD Router Tests
Trigger Execution Manually PageUser can select CDRouter packages trigger executionsNew Tab for selecting CD Router Tests
Job Manager PageUser can view the progress of CD Router package executions - Each job will show the status of single packageChange in actions button since Jenkins is not needed
Execution Results PageTo view overall execution results like Total script count, and its pass and fail countNo change in UI
Detailed Execution Results PageTo view the execution results of each test script (in cd router each test case contains only one step)No change in UI
Manage script pageTo map cdrouter package with automatics automation idChange in components that are displayed, new fields to come in

E2E RDK Request Filter Page

...

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

New UI Screens 

Following UI Screens are required to be added in Orchestration

...

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 On success, it will return 200 response code and status of execution will be Pending initially.

  2. 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 linkImage Removed


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.

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


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

...