RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
User can also see the Execution Details of Last 4.
...
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.
To perform test execution, user needs to add test details to Automatics system. This can be done from Manage Scripts page.
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
To perform test execution, user needs to add test details to Automatics system. This can be done from Manage Scripts page.
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.
...
Following details will be displayed as shown below:
User will be able to generate the usage reports of a particular device within the required dates.
Now, click on Reports and go to Device Usage Report.
Enter the following details of Device Mac Address, Date and Time as shown below.
After the entering the details click on Generate.
The following data/details of that particular device will be generated as shown below.
User can generate the Health Report of the test scripts.
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 Mode
Now, click on 'Download Reports' button highlighted below:
Test cases results available in the tabular format will be exported to excel document.
User will be able to generate the usage reports of a particular device within the required dates.
Now, click Click on Reports and go to Script Health Device Usage Report.
Now, enter Enter the following required details of Select Start Date & End Date followed by Select Category Type as shown below and Device Mac Address, Date and Time as shown below.
After the entering the details click on Generate.
After clicking on Generate the The following data/details of that particular device will be generated as show shown below.
Also, by clicking on Download Report you can download the report to your local in order to see the data offline.
User can generate the Health Report User can generate the Execution Time Report of the test scripts for the required dates.
Click on Reports and go to Script Execution Time Health Report.
Now, enter the following required details of Select Category Type, Select Start Date, & End Date followed by Select Test Category Type as shown below and click on Generate.
After clicking on Generate the following data/details will be generated as show below.
Also, by clicking on Download Report you can download the report to your local in order to see the data offline.
RDK/CI portal sends execution requests to Automatics orchestration. Automatics based on filters configured decides if execution to be performed or not.
RDK E2E Manager has 2 sections.
User will be able to see the incoming RDK Requests from the RDK Portal from this page.
Navigate to RDK E2E Manager and click on E2E RDK Request under RDKV/RDKB.
If the request status is accepted, then execution will be triggered by Jenkins. Or else if the status is REJECTED, then no execution will be triggered.
User can configure RDK filters so that when request comes from RDK portal, Automatics can decide based on it, if execution should trigger or not.
Now, navigate to RDK E2E Manager and click on E2E RDK Request Filter under RDKV/RDKB.
User can generate the Execution Time Report of the test scripts for the required dates.
Click on Reports and go to Script Execution Time Report.
Now, enter the following details of Select Category Type, Select Start Date, End Date followed by Select Test Type as shown below and click on Generate.
After clicking on Generate the following data/details will be generated as show below.
Also, by clicking on Download Report you can download the report to your local in order to see the data offline.
RDK/CI portal sends execution requests to Automatics orchestration. Automatics based on filters configured decides if execution to be performed or not.
RDK E2E Manager has 2 sections.
...
User will be able to see the existing RDK Request Filters, if any present already like the above screen having.
We can Enable/Disable the Request Filters by clicking on the below Enable Selected Records/ Disable Selected Records. Only enabled filters will be considered by Automatics.
Also, we can show/hide the params of the request filter by clicking on Show/Hide Filter Params button above.
Edit Request Filter Details
We can Edit the Request Filter, by clicking on Edit Request Filter Details under the Action column.
Edit the required details of the request filter and click on Save Results.
Add new Request Filter Details
We can add a new Request Filter, by clicking on Add Request Filter Details button above.
incoming RDK Requests from the RDK Portal from this page.
Navigate to RDK E2E Manager and click on E2E RDK Request under RDKV/RDKB.
If the request status is accepted, then execution will be triggered by Jenkins. Or else if the status is REJECTED, then no execution will be triggered.
User can configure RDK filters so that when request comes from RDK portal, Automatics can decide based on it, if execution should trigger or not.
Now, navigate to RDK E2E Manager and click on E2E RDK Request Filter under RDKV/RDKB.
User will be able to see the existing RDK Request Filters, if any present already like the above screen having.
We can Enable/Disable the Request Filters by clicking on the below Enable Selected Records/ Disable Selected Records. Only enabled filters will be considered by Automatics.
Also, we can show/hide the params of the request filter by clicking on Show/Hide Filter Params button above.
Edit Request Filter Details
We can Edit the Request Filter, by clicking on Edit Request Filter Details under the Action column.
Edit the required details of the request Now, enter the required Settings details & Automation ID details of the filter and click on Save Results.
User needs to configure all device models that is going to execute from Automatics.
Add new Request Filter Details
We can add a new Request Filter, by clicking on Add Request Filter Details button above.
Now, enter the required Settings details & Automation ID details of the filter and click on Save Results.
User needs to configure all device models that is going to execute from Automatics.
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.
...
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.
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
...
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.
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.
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.
The above are the configurations which should be available in Automatics for sending emails.
New Pages are added as a part of scriptless executions Details for the following pages is provided below
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 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.
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.
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.
The above are the configurations which should be available in Automatics for sending emails.