You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Test Execution in Raspberry Pi device

There are generic test cases that can be executed on Raspberry Pi device loaded with RDKB stack. This helps partners to familiarize with the Automatics system and helps to validate basic features in RDKB.

To execute tests on Raspberry Pi device, partner has to ensure below setups are done.

  • Automatics system (Includes Automatics Orchestration, Automatics Properties, Device Manager, Jenkins)
  • Automatics Core and RDKB Utils maven artifacts deployed in self hosted artifactory repository
  • Configure Raspberry Pi device in Device Manager, Automatics Orchestration and Automatics Properties
  • Configure the test scripts in Automatics Orchestration
  • Maven Deploy generic Raspberry Pi Provider Implementation provided by RDKM or partner specific Raspberry Pi Provider Implementation to self hosted artifactory repository.
  • Configure Raspberry Pi Provider Implementation artifact details in jenkins job.


Detailed Steps for Raspberry Pi Test Setup

Partners can follow detailed steps as given below for test execution.

Below steps can be followed to setup Automatics and execute RDKB tests on RPI device.

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

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

  • 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  
  • Test related config <Alan>





  • No labels