You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Enable CDRouter testcases in Automatics

1. Navigate to Manage scripts page by selecting 'Manage scripts' under Test Manager drop down.

2. Under Filter drop down scroll till 'Select Test Source' tab and select 'CDRouter' from the drop down and click on filter button.image.png

3.User can see all the CDRouter testcases that are present.

image (1).png

4. Click on the Edit Script Details Icon corresponding to the testcase to be edited and check all the mandatory fields to entered/changed. update the corresponding fields and click on next button.

6.Configure device model for the testcase selected and Click Next button and Save it.

8.After Saving the testcase User need to enable the testcase by clicking this icon corresponding to testcase which user need to trigger.

image (1).png

9.Select the Reason and save it


Trigger CDRouter Testcases from Automatics


1.Now Navigate to 'Trigger Execution Manually' from the 'Manage Test trigger' of side bar.

2.Enter the build name and Select the Execution Environment Type, quick test if needed and test source as 'CDROUTER'. Click on next button if all the mandatory fields are added.

image2024-1-10_11-22-53.png

3.Select the corresponding Automation ID and click on Next button.

Screenshot (63).png

4.Specify the device mac address that used for testing and click on 'Trigger Job' button. You can see a pop-up that execution is triggered successfully.

Screenshot (65).png

Monitor CD Router Executions from Automatics

1. Navigate to the Manage Test Trigger page, Expand RDKB dropdown and selecting the Job Manager button user can able to see the triggered Job.

image2023-12-12_12-38-32.png

15.Job manger will appear like below where user can find the execution status ,logs etc.
image2023-12-12_12-50-16.png

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

17.User can navigate to Html logs or Console logs after clicking the MAC address .


  • No labels