Versions Compared

Key

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

Table of Contents

POC - Scenario 

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.

New UI Screens 

Following UI Screens are required to be added in Orchestration

CD Router Test Trigger Page

  • To trigger an execution job in CDRouter, we can use webAPI mentioned in below link.  

On success, it will return 200 response code and status of execution will be Pending initially.

Image Added


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:

Image Added

Image Added


 CD Router Results Page

Image AddedImage Added

Config Manage Page

From this page, user can view configs in CD Router

Image Added

Image Added



 Package Manage Page

From this page, user can view packages in CD Router

Image Added

Image Added

Image Added



Use Case

Image Added


Image Added

 DB Structure

Adding 2 new tables to automatics DB:

Image Added

Image Added


 

Reference CD Router Web APIs:

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