Page History

...

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

...

Link to the page: <APi Explorer URL>

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

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

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

...

The detailed steps of configuring device models in each component is given shared below.

1. Configure device model in Device Manager.

Devices to be used in the Automatics System should be configured in Device Manager. These devices are provided to Automatics Orchestration during test execution. Follow the  the below steps to  to add device details to the device manager database.

To Invoke the API defined for Device Manager application using Swagger UI tool which is integrated with Device Manager application.

...

Automatics identifies a device model from its build name. For this, admin user has to configure device model and its it's corresponding build name. It requires only to map the device model and initial starting sub string of build name. The starting few letters(image prefix) in the build name should be unique to a device model and this should be added in 'Image Name Prefix' text.

...

Devices to be used in the Automatics System should be configured in Device Manager. These devices are provided to Automatics Orchestration during test execution. Follow the  the below steps to  to add device details to the device manager database.

...

• Navigate to {protocol}://{host:port}/DeviceManager/swagger-ui.html.
• Navigate to Device API and try to execute POST /device/add  API to adds new device to the Device Manager database by providing valid input parameters for deviceDetailsRequest as defined in Device Manager API Documentation#DeviceDetailsRequest.
• POST /deviceModel/add API will return response as "SUCCESS" on successfully adding the device details to the device manager database.G
• Refer Device Manager API Documentation#Device page to get more details on the parameters provided and type of responses received for POST /device/add API.
• SSH login details can be configured through POST/device/add  API .It is 's possible to add ssh connection details in extraproperties section of this API.
• The SSH connection details configured of particular ipAddress can be obtained by by POST/device/sshDetailsByIpAddress API .
• Refer Device Manager API Documentation#Device page to get more details on the parameters provided and type of responses received for POST /device/sshDetailsByIpAddress API.

...

Step No will be in non-editable one. Description should be clear based on the test step. User can select the Command Type based on each step. Based on the API's the methods will be applicable for each step.By clicking the settings icon in the Input filed, User will be navigated → Input Configuration page.

For Command User command user needs to add the command inside the command field. User can select how the output of the command executed should be validated. Select all the device models to which the command will be applicable. The expected output of the command should be given in this field. 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, we need to click → Add button. User can verify once whether all the details are valid and then click on the Submit  button.Now command and Test step added successfully. If user wants to edit, user can click on edit button. If user want to change the declaration part, click on delete button. Once all the details are added click on the submit button.

...

user can see all the available steps created in Test Step Generator page. By using Filter., We can can find the added test step (Saved in a test step generator page).In  all 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.

•   From Import steps we can import a test step from the same testcase by clicking the Import Steps Button in Action.  By providing the Step Number(case-sensitive) in the given textbox and and                  click Import, given step will be cloned/imported.

...

EDIT,CLONE& DELETE Test case

For Editing the Testcase

For Editing the test case details, then click the pencil icon in Action column in Available test cases table. Then user can edit the entered details then click on Save button to save the changes or by clicking the Next button user can add/remove/edit test steps details and click Save button to save the changes.

...

 Toclone or get a copy of a test case, then click the copy/clone icon in Action column in Action column in Available test cases table. Then user should provide a unique test case id, and user can edit the existing details and can and       can add/remove/edit the test step details. By clicking the Save button the Save button the cloned test case will be added in Available test cases table, and it will not change the existing test case.

...

For Mac address select check box E.g 00-xx-xx-xx-xx-xx and for good devices click on -> . . It will list the good devices. We can have Schedule trigger option also available, and the time needs to be mentioned. Device Group we can select based on the Automation ID. Build Appender and Notification mail will be mandatory. Source Repo needs to be mentioned based on the repo's available in the repository.Once all the details mentioned user Should click on the Trigger Job button. Once done Trigger will start successfully and via Job manager Tab.

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