Page History

...

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

Image Added

All the fields that are present in the command manager page are explained 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. We can map the multiple devices if the command is applicable for multiple platforms. There are already the available options mentioned in the drop-down list.

Example:

• TR181: Command will be executed through TR-181. These command type is only applicable for RDK-V device models.

• DMCLI: Command will be executed through DMCLI. These command type is only applicable for RDK-B device models.

Upload a file in device

In pre-defined commands, we have an option called COPY_FILE_TO_DEVICE which is used to download the required file to specified location in device. 

Note: User should follow the procedure to use the above mentioned command. 

1. Click Parameter button and select file from AutoVault. If file not uploaded already, use Upload option in the same page to upload your file and select the same
2. Select the validation type as EQUALS.
3. In expected output as true

5. Command:

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

6. Validation Type:

User can select how the output of the command executed should be validated. All the available validation types are shown and explained below,

Image Added

• • • BETWEEN: If the command output must be in between two values the user can select Between as validation type. User should enter expected output separated by comma as lower_value,upper_value both the values are included.
    • CONTAINS: If the command output must contain the expected output then user can select Contains as validation type.
    • EQUALS: If the command output should be exactly equal to expected output then user can select Equals as validation type.
    • GREATER: If the command output must be greater than the expected output then user can select Greater as validation type.
    • LESSER: If the command output must be lesser than the expected output then user can select Lesser as validation type.
    • MATCHES: If the validation must be done with the regex pattern then user can select Matches. If the expected output matches in the command output then it is success.
    • NA: If the validation is not required for the executed command then user can select NA.
    • NOT CONTAINS: If the command output must not contain the expected output then user can select Not Contains as validation type.
    • NOT EQUALS: If the command output can be anything other than expected output then user can select Not Equals as validation type.
    • NOT MATCHES: It is same as Matches but here expected output should not match in the command output then it is success.
    • NOT NULL: If the command output can be anything other than NULL then user can select NOT NULL as validation type. 
    • NULL: If the command output must be null then user can select NULL as validation type.

7. Expected Pattern / Output:

The expected pattern/output of the command should be given in this field.

8. Device Model:

User can select all the device models to which the command will be applicable.

• • • After entering all the details of the command, need to click on the Action(+) button.
    • User can verify once whether all the details are valid and then click on the Save Command button. 
    • Now the command is saved, and user can see the newly added command in the Test Step Management table. 

Edit:

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