...

User can also see the Execution Details of Last 4.

Manage

...

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.

Image Added

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.

Image Added

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.

Image Removed

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.

Image Removed

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:

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 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.

Image Removed

Script Health Report

User can generate the Health Report of the test scripts.

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 Mode

Now, click on 'Download Reports' button highlighted below:

Image Added

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 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.

Image Removed

Also, by clicking on Download Report you can download the report to your local in order to see the data offline.

Script Execution Time Report

Image Added

Script Health Report

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.

Image RemovedImage Added

Also, by clicking on Download Report you can download the report to your local in order to see the data offline.

RDK E2E Manager

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.

• E2E RDK Request
• E2E RDK Request Filter

E2E RDK Request

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.

Image Removed  

E2E RDK Request Filter

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.

Script Execution Time 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 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.

Image Added

Also, by clicking on Download Report you can download the report to your local in order to see the data offline.

RDK E2E Manager

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.

• E2E RDK Request
• E2E RDK Request Filter

E2E RDK Request

...

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.

Image Removed

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.

Image Removed

Image Removed

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.

Image Removed

Image Removed

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.

Image Added  

E2E RDK Request Filter

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.

Image Added

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.

Image Added

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.

Image Added

Image Added

Edit the required details of the request Now, enter the required Settings details & Automation ID details of the filter and click on Save Results.

Device Models

Add new Request Filter Details

We can add a new Request Filter, by clicking on Add Request Filter Details button above.

Image Added

Image Added

Now, enter the required Settings details & Automation ID details of the filter and click on Save Results.

Configure Device Model

User needs to configure all device models 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.

Image Modified

• • 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.

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 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.

Image Added

• • 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.

Image Added

• • 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.

Image Added

• 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

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.

1. Open catalina.sh file of the tomcat server in which Automatics is deployed.
2. Add the required properties like "-Dmail.smtp.ssl.protocols=TLSv1.2" needs to be added under the variable JAVA_OPTS.
3. 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.

1. Open catalina.sh file of the tomcat server in which Automatics is deployed.
2. Add the required properties like "-Dmail.smtp.ssl.protocols=TLSv1.2" needs to be added under the variable JAVA_OPTS.
3. Restart the server to take effect.

The above are the configurations which should be available in Automatics for sending emails.