Versions Compared

Key

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

...

Note:- Before adding a new command, user needs to check the command to be added is already exist or not by filtering all the commands displayed using search box. If the command is already existing, then use that command instead creating the same. 



 




Once the add configuration button is clicked then user will be navigated to the Command Manager page as shown below,

...

             To add test constant in test case we need to use {{as the trigger. When user enters {{then all the test constants are listed under as shown below.
             Test constants always starts with TC$ and user can select the test constant as per the requirement

...

For triggering the test cases and verify the test results it will be available inside




Manage Test Trigger

...

Manage Test Trigger tab has following devices-> RDK-V, RDK-B, RDK-C For these devices we can Trigger our testcases and Scheduled Triggering part as a sub tabs.

Image Removed

...

Image Removed

By default, End Point will be as DESK BOX. we can select based other option based on the Rack setup. Based on the test type we need to mention the Device Group. For Build name should be exact Select Service name default it will be Functional Verification if user wants he can select CI verification based on the requirement.Build name should be the same one that is available inside the particular device. Build Appenders field is mandatory one If user wants, they can select this field. If user want to execute testcases from one or more test suites user can select the particular test cases. Based on the selected test suites, testcases will be listed in the next page. Iteration method is not a mandatory field. Iteration count needs to be provided by default it will be 1. For Post iteration it should be in seconds. By default Skip QT will be selected if not applicable for test case we can unselect the box. If skip QT is unchecked, then all the quick tests for that environment type will be listed in the drop-down list. Select the required quick test case. For Skip clean up user can enable this option to skip the cleanup of boxes before starting the test. If it’s not checked then all the boxes under test will get cleaned before test. By default, skip cleanup option is not checked, cleaning the boxes before the test is preferred way. if required then only enable the skip cleanup option. Once all the fields added successfully click on the Next button.

Then new page will come as shown below.

Image Removed

Testcase will be listed inside the Available Test cases. We can check our Test case in the Filter Field. After Click '>' to move the selected test cases to Selected Test Cases column. Click on Next button. 

We need to select the required boxes for executing our Test cases. Multiple boxes we select for Execution.

box details. Endpoint should be either Desk box or Rack device. Partner Test is not the mandatory one.If we want we can select the box and add COMCAST. Test types needs to be selected based on the hours and days execution time. Environment type should be either RDKV,RDKB,RDKC.Is Quick Test required it will selected as a default one . We can disable that if we are not using QT .


Image Added

Once all the details added successfully User will be navigate to the Following page.

Image Added


In Automation ID user needs to select the Automation ID . Once the ID selected it will available inside Short-listed Automation Ids. Click on Next button. It will be navigated to the Trigger Execution manually.

Image Added

For Mac address select check box Image Added E.g 00-xx-xx-xx-xx-xx and for good devices click on ->Image Added . . It will list the good devices. We can have Schedule trigger option also available, and the time needs to be mentioned. Device Group we can select based on the Automation ID. Build Appender and Notification mail will be mandatory. Source Repo needs to be mentioned based on the repo's available in the repository.Once all the details mentioned user Should click on the Trigger Job button. Once done Trigger will start successfully and via Job manager Tab.

Image AddedImage Removed