Page History

...

• Update the Source Code Repository Details, by executing sql command on 'source_code_details' table in database.
  • Ex: insert into source_code_details (NAME, CATEGORY_TYPE, SOURCE_REPO, SOURCE_BRANCH, DELETED_DATE, UPDATED_BY, UPDATED_DATE) values ('{generic category name}','{category type}',{repo details of the project been deployed}','{branch name of the project where it is pulled}','NULL', 'admin', now());

             Job Settings

• From Automatics UI, navigate to Settings ->  Job Settings

...

Software Requirement

• JDK 1.8
• Maven 3

...

Setup

• Pull the latest AutomaticsGeneric Test project from the repository (rdk/tools/automatics/generic-automation-tests) with branch (“rdk-next”).
• Update pom.xml with partner project as a dependency.
• Merge the changes so that it will be available during tests execution.

...

Automatics Rest Implementation

• Partner needs to provide REST based implementation for APIs in device management that is consumed by Automatics orchestration.
• Other device management APIs consumed by Automatics core can be implemented using Java API or REST.
• Automatics core provides rest clients for device management and hardware providers like Power Provider. Partner can provide REST implementation for them based on API specification. Automatics core, by default, will use rest implementation. However, if partners prefers to go with Java API implementation, then in Automatics Properties, update the following properties as shown.

...

Automatics performs test execution in Jenkins. User can view the status of Jenkins execution from Job Manager page of Automatics. The final execution status will be updated back to Automatics.

Set upSetup

Steps to be taken care during Jenkins configuration

...

To perform test execution, user needs to add test details to Automatics system. This can be done from Manage Scripts page.

2.1 Add 1   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.

...

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

...

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

...