Test Step Generator

•  For adding steps in Test Step Generator User add all the commands and Test steps commands should be executed through this Test Step Generator tab.
•  Once user clicks -> Test Step Generator tab then already added commands &Test steps will be exposed.
•  If user wants to add any new command (or) Test step it should be added via Automatics 3.0 then user must be click -> Add Configuration button as in the picture shown below.

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,

Command name should be meaningful and provided in the command name filed. In Description field user should mention the proper explanation about the command name. User should select the platforms to which the command is applicable. We need to map the command to the corresponding devices RDK-V, RDK-B, RDK-C and Select All. Once done the user can map the multiple devices if the command is applicable for multiple platforms. Validation type needs to be provided based on command name. Expected output or pattern should be correct otherwise Testcase will fail. After entering all the details of the command, need to click on the Action (+) button and Save button should be clicked and command name will be added successfully.

NOTE

If user wants to make any change in the entered details, then click the pencil icon in the Action column it will be navigated to the Command Manager page and can edit the entered details then click on Save Command button to save the changes.

Test Case Generator

To add the testcase and steps will be available inside Testcase Generator.

The test case generator tab will be as shown below:

To add a new testcase user should add the unique Id and Description should be correct based on the testcase Id. Environment Type needs to be selected based on the testcase (RDKV.RDKC,RDKB). User Should mention the test type either Functional or Custom. Run on models needs to select based on the devices that is applicable for the testcase. Test Priority, Regression label and RDK component should be selected based on the testcase. Once done Click on → Next button it will navigate to the Test Case Generator page as shown below.

To upload the steps, we can click and add Excel file and able to import test steps from other testcases.

Users can mention the values of Persist flag, Raise defect, Break on failure, Pre wait(sec), Post wait(sec), Execution thread in the excel file. That will be automatically updated in Summary page. Or the user can see all the available steps in the box. By using Filter, the user can find the added test step directly from the UI (Saved in a test step generator page).

Edit ,Clone. Delete Test Case 

user wants to edit the test case details, then click the pencil icon in the Action column in the Available test cases table. Then the user can edit the entered details then click on the Save button to save the changes or by clicking the Next button user can add/remove test steps from the selected steps column and click the Next → Next → Save button to save the changes. For Cloning clone or get a copy of a test case, then click the copy/clone icon in the Action column in the Available test cases table. Then user should provide a unique test case id, and user can edit the existing details and can add/remove the test steps. By clicking the Save button the cloned test case will be added in Available test cases table and it will not change the existing test case. By clicking the delete icon in Action column in Available test cases table, user can delete the test case. 

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 Keywords, we can search for (Ex: channel tune) it will expose all channel related API's.

API's can be verified via 

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

Build Test Case

The build test case tab will be as shown below:

For Build test case the Test case Id should be unique and Test Description should be correct.