CMF Test

Test Development Builds

The test team maintain their own build scripts which we use to build and test debug images for defect investigations. These scripts are run on personal build slaves and can be used to build on any branch we support in CMF.

The scripts will upload the images to an s3 bucket and can also be used to automatically smoke test the image.

The scripts are maintained in the cmf test git repository https://code.rdkcentral.com/r/plugins/gitiles/cmf/test/+/master/cmf_testbed/tools/builds/

1) launch build slave via https://jenkins.cmf.code.rdkcentral.com/job/jenkins-reserve-slave 

2) ssh to build slave (see jenkins console o/p for IP address)

3) set up build scripts on your build slave (if not already setup)

cd ~/jenkinsroot/workspace
git clone "https://code.rdkcentral.com/r/cmf/test"
ln -s test build

4) build your image, e.g.

cd ~/jenkinsroot/workspace/build
./build_emub.sh <branch> <prepare|build>

Note follow the prompts to select what image(s) you want to build and whether you want to automatically smoke test the image

• Notes
  • if you want to apply patches or do some reverts or cherrypicks do the build in two stages
    • run script with prepare first (this will do repo init and repo sync)
    • make code changes
    • then run script with build
  • if you just want to build a branch then just run script with no prepare or build options

Test Frameworks

Testing is done using 3 frameworks:

• ATF
• RDKV-EMU
• RDKV-Platforms (Deprecated as of March 2019)

All of which are kicked off with a set of input parameters to their various Jenkins jobs. Currently supporting 4 'RUNTYPE' options – 'release', 'nightly', 'nightly-full', and 'master'. Below is each framework's instruction to run a flow job for the various RUNTYPE options and the differences those options make in regards to each phase of each flow.