RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
...
User can also see the Execution Details of Last 4.
Manage
...
To perform test execution, user needs to add test details to Automatics system. This can be done from Manage Scripts page.
Add Script
User Group Access
For user to execute the test cases on the devices need to have permissions to access the device group. Admin user can map device groups to users so that only those users mapped to device group can execute tests on device.
- From Automatics UI, navigate to Settings -> User Management
- Click on User Group Module Access
- Select the User Group and click on Fetch Access Rights.
- Select the access right checkbox of the Module Name, you want to provide access.
- Click on Save.
Manage Scripts
To perform test execution, user needs to add test details to Automatics system. This can be done from Manage Scripts page.
Add Script
Script Details
To add a new script, user can click on “Add New” link on the right top of page. Field “Automation Id” should be unique name that identifies an automated test. This id should match with the automation id in automated test case. Automatics considers RDK builds in any of the 3 categories ‘Sprint’, “Stable” and “Release”. A test case can be mapped to execute in any or all of the build types.
On Next page, Environment can be selected. In the screen shown below, the test is RDKV device related. So mapping the test against RDKV environment. Next applicable device model/s can be selected. End point “RACK_DEVICE” refers to devices
Script Details
To add a new script, user can click on “Add New” link on the right top of page. Field “Automation Id” should be unique name that identifies an automated test. This id should match with the automation id in automated test case. Automatics considers RDK builds in any of the 3 categories ‘Sprint’, “Stable” and “Release”. A test case can be mapped to execute in any or all of the build types.
On Next page, Environment can be selected. In the screen shown below, the test is RDKV device related. So mapping the test against RDKV environment. Next applicable device model/s can be selected. End point “RACK_DEVICE” refers to devices managed by rack system and “DESK DEVICE” refers to desk devices. Head end field refers to device head end. If head end is provided, then during execution, Automatics can request for devices from given head end.
...
An export feature is added to Automatics to help user to export the existing test script and its steps in bulk, which could be used to add the test cases to new or a different server of Automatics. The excel sheet with the test cases could be exported from Manage scripts page using Export/Import options menu. Please There is an option to export all Test cases or Filter the Test cases to be exported using the Filter option. Please see the below image for details
...
Following details will be displayed as shown below:
Device Usage Report
To download Test Case Level Execution Results
User can export test cases level execution results using 'Download Reports' button located in Execution Results – TC page.
Follow the steps mentioned in Execution Results – TC section to navigate to Execution Results – TC page.
Select required date and below filter options for the required test result details:
Regular Test Types, CI Test Types and Execution ModeUser will be able to generate the usage reports of a particular device within the required dates.
Now, click on 'Download Reports' button highlighted below:
Test cases results available in the tabular format will be exported to excel document.
Device Usage Report
User will be able to generate the usage reports of a particular device within the required dates.
Now, click on Reports and go to Reports and go to Device Usage Report.
Enter the following details of Device Mac Address, Date and Time as shown below.
...
Now, enter the required Settings details & Automation ID details of the filter and click on Save Results.
Email Server configuration - SMTP
Automatics orchestration has the functionality to send email notifications. For sending an email notification an SMTP server is required. One an SMTP server is available the below are the configuration which need to be configured for sending email notification's from Automatics Orchestration. The configuration can be added via "System Configuration" page under "Settings" menu
...
Configure Device Model
User needs to configure all device models that is going to execute from Automatics.
- From Automatics UI, navigate to Settings -> Manage Scripts -> Run on Models
Automatics identifies a device model from its build name. For this, admin user has to configure device model and its 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 build name should be unique to a device model and this should be added in 'Image Name Prefix' text.
- Click on Add Device Name
- Enter the Device Name.
- Enter the Image Prefix Name. The build name prefix which will be unique to identify a device model. Automatics identify a device model from the build name.
- Select the device category.
- Check-in isClientDevice, if the device is a RDKV client device.
Configure Device Group
- From Automatics UI, navigate to Settings -> Device Groups
For Automatics to use devices from partner's inventory, device groups have to be configured. The device group name in inventory should be added here so that user can execute tests on devices within these groups only. Admin user can map device groups to users so that only those users mapped to device group can execute tests on device.
- Go to Settings -> Device Groups
- Click on Add New Device Group Name
- Enter the Device Group Name. Devices should be present in this Group Name.
Configure Job Settings
For each test type in Automatics, job will be created during test execution. The jobs are created based on job templates. For each test type, a job template need to be created.
- Click on Add New Job
- Enter Job Name: Enter the Job Name with the prefix of AUTO followed by TEST_TYPE and JOB, all are separated by “_”.
Eg: AUTO_1HOUR_JOB. Quick Test is configured as parent of all other jobs. Child jobs are executed in the order of priority set for the job.
- Please update the default value for each field here.
- For CI integration, if results of test execution to be updated to CI portal, then set 'updateRdkPortal' to true here.
- Click on Save.
Email Server configuration - SMTP
Automatics orchestration has the functionality to send email notifications. For sending an email notification an SMTP server is required. One an SMTP server is available the below are the configuration which need to be configured for sending email notification's from Automatics Orchestration. The configuration can be added via "System Configuration" page under "Settings" menu
| Configuration Name | Description |
|---|---|
| SMTP_PROTOCOL | It is the protocol used for sending email. The value can either be SMTP or SMTPS. If the SMTP server connection should SSL enabled but not TLS then the value should be configured as SMTPS. In all other scenarios SMTP should be configured. |
| SMTP_HOST | It is the IP address or domain of the SMTP server. |
| SMTP_PORT | It is the PORT of SMTP server. |
| SMTP_AUTHENTICATION | A Boolean field, this needs to be configured as true when the SMTP server has authentication. If the SMTP server do not have an authentication then this needs to be configured as false and there is no need to configure SMTP_USERNAME and SMTP_PASSWORD. |
| SMTP_USERNAME | Username of the SMTP server which is used to login and send email from an application |
| SMTP_PASSWORD | Password of the SMTP server. |
| SMTP_AUTH_TYPE | The value of this configuration can either be "SSL" or "TLS". If the SMTP server is enabled with STARTTLS then it should be configured as TLS or else it should be configured as SSL |
Apart from the above configurations if any other properties are required for connecting to a SMTP server then those SMTP mail properties can be added as JAVA_OPTS in the server. For doing the same follow the below steps.
- Open catalina.sh file of the tomcat server in which Automatics is deployed.
- Add the required properties like "-Dmail.smtp.ssl.protocols=TLSv1.2" needs to be added under the variable JAVA_OPTS.
- Restart the server to take effect.
The above are the configurations which should be available in Automatics for sending emails.
Automatics 3.0
New Pages are added as a part of scriptless executions Details for the following pages is provided below
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.
Please refer Automatics 3.0 User Manual#APIExplorer for more details.
Build Test Utility
Build Test Utility is creating the set of steps frequently used in test cases which helps in reducing the user efforts while creating test cases.
Please refer Automatics 3.0 User Manual#BuildTestUtility for more details.
Test Constants
Tests Constants in automatics 3.0 is used to provide a feasible option for test developer to add a key value pair where the value can accessed any where in the test case by providing the key value.
Please refer Automatics 3.0 User Manual#TestConstants for more details on how to create and use test constants in test cases.
Build Test Case
Scriptless test cases can be build in Build test case page.
Please refer Automatics 3.0 User Manual#BuildTestCase for more details on how to build 3.0 test cases
Apart from the above configurations if any other properties are required for connecting to a SMTP server then those SMTP mail properties can be added as JAVA_OPTS in the server. For doing the same follow the below steps.
- Open catalina.sh file of the tomcat server in which Automatics is deployed.
- Add the required properties like "-Dmail.smtp.ssl.protocols=TLSv1.2" needs to be added under the variable JAVA_OPTS.
- Restart the server to take effect.
The above are the configurations which should be available in Automatics for sending emails.
Overview
Community Forums
Content Tools
Tasks