...

API Explorer

...

User can get to know the API's information such as API category, Class name, API name, Applicable for, description and parameter details.

User can explore the APIs present in the Automatics by 2 ways:

•                 Using Environment Type & API Category

...

• .
•                 Using Keywords.

...

Using Environment Type & API Category

         Environment Type: Select appropriate environment (for

...

Eg.

...

select RDKV for Video devices, RDKB for broadband devices and RDKC

...

 for Cameras)

         API Category: Category of the API user want to explore.

Using Keywords

         Keywords: Name of the API. (For eg: keyword='CHANNEL_TUNE' it will list out the API names which contains the word CHANNEL_TUNE)

Image Added

Other than that user can find out the Test cases(with Step Information) that is using the specific API:        

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

Image Removed

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 Utility

Link to Build Test Utility : <<Build Test Utility>>

...

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). Test type can be FUNCTIONAL OR QUICK. Select the appropriate test priority. 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 is applicable for the test case. User can verify once whether all the details are valid and then click on the Next button.

 Then user will be navigated to Build your own Test case ... page as shown below.

Image RemovedImage Added

For Build our Own Test case 

To build our own test case,

we can we need to add three steps ;

• Add Pre-Step
• Step
• Add Post-Step

...

Step option will create a plain step as shown below.

The fields are explained below,

1. Step No.: 

Step number will be a non-editable text box.

2. Description:

The user should enter a detailed description of the test step.

3. Command Type:

Users should select the command type according to the way in which the command should be executed. The drop-down contains all the commands including SSH, WEBPA, SNMP, and all the PRE-DEFINED commands.

4. Avail. Method:

User should select the available method. The drop down contains all the methods which the selected command type will be applicable.

5. Input:

By clicking the settings icon in the Input filed, User will be navigated to Input Configuration page as shown below.

* Command: Command that should be executed must be added in the command field.

* Validation Type: User can select how the output of the command executed should be validated. All the available validation types are explained above (in Test Step Generator) 

* Applicable Models: User can select all the device models to which the command will be applicable.

* Expected Output: The expected output of the command should be given in this field.

* Execute On Connected Client: If the selected execution mode of the test case is Connected Client, then user can select Device-Config and Clients. 

After entering all the details of the input command, need to click on the Add button. User can verify once whether all the details are valid and then click on the Submit button. Now the command/test step detail is added. If user wants to edit, user can click on Image Modifiededit button. If user want to change the declaration part, click on Image Modified delete button. Once all the details are added click on the submit button.

6. Step Output:

The step output of the step should be given in this field.

7. Action:

* Additional Values: 

By clicking external-link icon, User will get Additional Values window as shown below.

is Primary Step?  if selected as false, the step will not be considered as primary and step status will not be updated.

Force Update Parent Status: By setting this value to 'Yes' user can update the status of the current step to the parent step without considering the previous step's status.

Disable Step: will be used for test case developer to disable the step. So, that specific step will not get executed during the execution.

Add Polling: if option yes selected then we have two options for polling 1. duration, 2. Iteration

Custom Error Message: By using this option, user can add a custom failure message for a step failure which will be displayed in result page after test execution.

After entering all the additional values, need to click on Save button.

* Child Steps: By clicking the plus icon, User can create child steps.

* Delete Step: By clicking the delete icon, User can delete the particular test step

• Iterational

Iterational option will create a iteration step as shown below.

The fields are explained below,

1. Step No.: 

Step number will be non editable text box.

2. Description:

User should enter the detailed description about the test step.

3. Test Type:

User should select the test type. The drop down contains LOOP and EXIT-LOOP.

4. Input:

By clicking the settings icon in the Action filed, User will be navigated to Add Iteration or Duration page as shown below.

We need to provide either Iteration Count or Duration in Seconds and click -> Save button. Now the Command / Test step added successfully.

...

Conditional option will create a condition step as shown below.

The fields are explained below,

1. Step No.: 

Step number will be non editable text box.

2. Description:

User should enter the detailed description about the test step.

3. Test Type:

User should select the test type. The drop down contains IF, ELSE-IF and ELSE.

4. Input:

By clicking the settings icon in the Action filed, User will be navigated to Add Condition page as shown below.

* Operator: User should select the Operator type. The drop down contains AND and OR options.

* Invert Result: User should select the NOT check box to invert condition.

* Actual Value: Actual Value of the condition should be given in this field.

* Validation Type: User can select how the output of the command executed should be validated. 

* Expected Value: Expected value of the condition should be given in this filed.

After entering all the details of the input condition, need to click on the plus icon. User can verify once whether all the details are valid and then click on the Save button. Now the command/test step detail is added.  

• Check Point

Check point option will create a check point step as shown below.

Image Added

The fields are explained below,

1. Step No: 

Step number will be a non-editable text box.

2. Description:

The user should enter a detailed description of the test step

  3. Expected Result:

           User should enter expected result of the step

  4. Impact:

            User should enter the impact of the step

  5. Action:

             This field is explained above under Step.

• Import Steps

User can import a test step from the same testcase by clicking the Import Steps Button in Action.

...

 We can enable, edit, clone, update step details of the testcase using these butttons.  

Manage Test Trigger

Link for Manage Test Trigger :<Manage Test Trigger>

...

By clicking this icon we can see the child Jobs name . After that click on thsi this icon .Then Jenkins Execution logs will be available . We can verify pass and failures of all the steps.