• Automatics Login
• API Explorer
• Device Configuration.
• Build Utility
• Build Test Case
• Manage scripts
• Test Constants

Automatics Login

User can login into Automatics through any one of the two authentication modes - Self-Authentication or LDAP Authentication.

<Automatics Login URL>

Image Modified

API Explorer

Link to the page: <APi Explorer URL>

      For API's Explorer we can verify via Environment Type & API Category & Keywords.

...

Device Manager UI User Manual#EditDeviceExtraProperties

Build Test Utility

Link to Build Test Utility : <Build Test Utility>

               Build utility in automatics is creating the frequently used steps as utility. The same utility can be injected in to any other testcases. 
               For example, if 4 steps are used in common for multiple testcases then user can club those steps into a build utility and then user can insert that utility into any other test cases.
               The advantages of build utility are reuse and it decreases the effort for user to create the same steps again and again

...

• • Select command type as USER_DEFINED_UTILITY and then automatically all the build utilities created will be loaded.
  • Then user can select the utility that must be included in the testcase as shown above

Build Test Case

Link to Build Test case : <Build Test case>

The build test case tab will be as shown below:

...

By clicking the delete icon in Action column in Available test cases table, user can delete the test case. 

Test Constants

Link For Test Constants :<Test Constants>

               Test constant here in automatics means the command or log file or any string that gets used more frequently is called as a test constant
               We can declare the test constant once and can use the same in multiple places.

...

             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

Manage Test Trigger

Link for Manage Test Trigger :

<Manage Test Trigger>

For Both RDKV & RDKB same job trigger page

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

...