Page History

...

• Setup and configure Device Manager - Device Manager Deployment Document
• Setup and configure Automatics Orchestration - Automatics Orchestration Setup
• Setup and configure Automatics Properties - Automatics Properties
• Setup and configure Jenkins jobs for test execution - Automatics Jenkins Setup
• Deploy maven artifact of Automatics Core in self hosted maven artifact repository- https://wiki.rdkcentral.com/display/ASP/Automatics+Core+%3A+Jenkins+Deployment+Job+configuration
• Deploy maven artifact of RDKB Utils in self hosted maven artifact repository - RDKB Utils : Jenkins Deployment Job
• Deploy maven artifact of Raspberry Pi Partner Provider Implementation in self hosted maven artifact repository - RPi Java API Provider : Jenkins Deployment Job

3. Configure Raspberry Pi Partner Provider Artifact Details in Jenkins Test Execution Job

As part of executing RDKB tests in partner environment , partner has to update rdkb-test project pom file to point to the Raspberry Pi Provider implementation (it will vary for partners)
We have added a supporting shell script , which can be configured to the Jenkins Job, so it will add the RPi Provider dependency to the rdkb-test project pom.xml during run time. And, this can be done by configuring Build Step under Build Section in Test Execution Jenkins Job. 

• • In Test Execution Jenkins Job, under Build Section, please configure 'Shell Script' referring Jenkins Job for Test Execution#ConfigureShellScriptforPartnerJavaAPIdependency 

Jenkins Job → Build Section → Shell Script. 

• • Update command with parameter values as below

/mnt/scripts/pre-test-config.sh -g 'com.automatics.providers' -a 'rpi-provider-impl' -v '0.0.1-SNAPSHOT'

3. Configure Device in Automatics

After the setup is ready, partner has to configure the device model and device details in Automatics and its details are available at Device Configuration in Automatics.

...

• Download the script file RPi_RDKB_TEST_CASE.xls to your machine.
• Open the excel in edit mode and update the column 'RUN ON MODELS' for each test script with the Raspberry Pi device model name.
• Import the updated test script to Orchestration following details available at Automatics Orchestration ImportTestScriptandSteps

• Setup Automatics system referring Automatics System Setup and ensure that system is up and running.
• Ensure that RPI device is loaded with RDKB stack.
• Configure RDKB RPI device. Detailed steps for device configuration at Device Configuration in Automatics.
• Deploy RPi Java API Provider implementation to maven artifact repository.
  • Artifact deployment for RPi Java provider implementation can be automated using jenkins job. The details for the configuration can be found in this link
• Deploy RDKB Utils project to maven artifact repository.
  • Documentation on how to configure RDKB Artifact deployment using Jenkins job can be found here.
• RPI Provider dependency management
  As part of executing the test in partner environment , partner has to update rdkb-test project pom file to point to the partner provider implementation (it will vary for partners)
  For RPI we have added a supporting shell script , which can be configured to the Jenkins Job, so it will add the RPI generic provider dependency to the rdkb-test project pom.xml during run time. And, this can be done by configuring build step under Build Section in Test Execution Jenkins Job. 
  • In Test Execution Jenkins Job, under Build Section, please configure 'Shell Script' referring Jenkins Job for Test Execution#ConfigureShellScriptforPartnerJavaAPIdependency 

Jenkins Job → Build Section → Shell Script. 

• • Update command with parameter values as below

/mnt/scripts/pre-test-config.sh -g 'com.automatics.providers' -a 'rpi-provider-impl' -v '0.0.1-SNAPSHOT'

...

Configure test case in Automatics Orchestration via Excel

• Sample TEST_CASE XML : RPi_RDKB_TEST_CASE.xls

...

Map Test script to device. 

• To add new RPi device, Open ManageScripts page → Click Run On Models → Enter the Device and image name
• For mapping the device to the Test script, Filter the test script using Filter option from Manage Scripts page → Click Edit Script Details → Click Next → Add the RPi device to the Run On Models option and save  

6. Trigger Execution

After the test scripts are configured, partner can trigger test execution from Orchestration via Trigger Execution Manually page.

While triggering execution, Quick Test(Image Upgrade) should be skipped by un-selecting option 'Is Quick Test Required' in Trigger Execution Manually page. Steps to trigger execution is available at Automatics Orchestration-TriggerTestExecution.

Test Execution Results will be available at Execution Results page. Details are available at Automatics Orchestration-ExecutionResults 

...