• API Explorer
• Build Utility
• Build Test Case
• Manage scripts
• Test Constants

API Explorer

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

     Select appropriate environment (for E.g. select RDKV for Video devices, RDKB for broadband devices and RDKC for Cameras). For API's Category we can verify the category of the API's.

Using      Using Keywords, we can search for (Ex: channel tune) it will expose all channel related API's.

...

• BTC: Test cases created in Build Test Case page.
• TCG: Test cases created in Test Case Generator page.

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

Create Test Utility

              Build utility can be created in the same way as build test case.
              User can create build utility by clicking Build Utility tab under settings a shown below,
              Settings --> Build Utility

Image Added

Steps to include Build Utility in Test cases

             First user should create the repeated steps as utility as shown above.

             Then user can add that utility as a step while creating the test case as shown below,

Image Added

 If user want to include the utility in test case below steps should be followed,

• • 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

The build test case tab will be as shown below:

Image RemovedImage Added

For Build test case the Test case Id should be unique and different, and Test Description should be correct way based on the Testcase ID. In Environment Type Field Select appropriate environment (for Eg. select RDKV for Video devices, RDKB for broadband devices and RDKC for Cameras and EXTENDER for Extender devices). Test type and Test Priority should be in the Unique way. Run on models needs to be mentioned like what are all the devices that are applicable for the Test case ID. For each test case id, we need to mention the models that needs to execute. User can verify once whether all the details are valid and then click on the Next button.

...

User should select the Operator type. The drop-down list consists of AND & OR options. For Invert Result don't select the select the NOT check  check box to invert condition. Actual Value of the condition should be given in this field. User can select how the output of the command executed should be validated. Expected value of the condition should be given in this filed. After entering all the details of the input condition,  click on the plus icon. Verify once whether all the details are valid and added successfully click on the Save button. Command/test step details added successfully.

...

user can see all the available steps created in Test Step Generator page. By using Filter., We can find the added test step (Saved in a test step generator page).In  all the available steps, we can select the required test step. After selecting the test steps, click '>'. Then user can see the required steps in Selected Steps Column. After click on the Add Steps button. Now the steps will be added in our Build your own Test case... page. After creating/adding all the test steps, click Save button to save the changes and it will be added in Available test cases table.

...

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

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

Create Test Utility

              Build utility can be created in the same way as build test case.
              User can create build utility by clicking Build Utility tab under settings a shown below,
              Settings --> Build Utility

Image Removed

Steps to include Build Utility in Test cases

             First user should create the repeated steps as utility as shown above.

             Then user can add that utility as a step while creating the test case as shown below,

Image Removed

 If user want to include the utility in test case below steps should be followed,

...

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.

...