CMF
RDK Releases
Documentation
CMF Videos
Support
Support for CMF is provided by the RDK Support group.
To contact RDK Support:
Enter a ticket: https://jira.rdkcentral.com/
or
E-mail: support@rdkcentral.com
CMF perform fully automated sanity testing of multiple video reference platforms on both Gerrit and Github contributions and on nightly branches.
Testing can also be performed on tip dunfell/rdk-next on demand.CMF Video Sanity Tests
CMF Sanity Tests are command line driven (e.g. gst-launch, aampcli) as well as UI driven. We have UI tests for the following UI's:
CMF Video Sanity Tests use the StormTest product to do image comparison, video and audio detection, OCR etc..
CMF currently support the following platforms and profiles for contribution and nightly branch CI.
Platform | Profiles | Testing | Comment |
---|---|---|---|
RPI 3 Hybrid | Video Accelerator UI LGI Refapp2 | Contribution Nightly Contribution Nightly | |
RPI 3 Mediaclient | Video Accelerator UI | Contribution Nightly | |
RPI 3 IP Client | Video Accelerator UI | Nightly | |
RPI 4 Hybrid 32 Bit | Video Accelerator UI | Nightly | |
RPI 4 Mediaclient 32 Bit | Video Accelerator UI | Nightly | |
BRCM972180HB | Video Accelerator UI LGI Refapp2 | Contribution Nightly Contribution Nightly | contribution builds are meta layers only |
BRCM972180HB | DTVKit DVB UI | Nightly | Currently Not Run: BCM72180-135 - Getting issue details... STATUS |
AMLOGIC AH212 IP Client | Video Accelerator UI | Contribution Nightly | contribution builds are meta layers only |
AMLOGIC AT301 TV Profile | Video Accelerator UI | Contribution Nightly | contribution builds are meta layers only |
REALTEK | Video Accelerator UI | WIP |
Each sanity test flow follows the same principle:
Aim is to keep each sanity test flow to <= 30 minutes.
All interaction with the DUT is done via serial and ssh.
Some examples of the automated flows:
Automated Flow Examples |
---|
There are no images attached to this page. |
Tests are split between command line and UI based tests.
A global appState variable is used to determine if the app should be stopped/started or is running based on the test being run.
Test | Short Description | RPI 3 Hybrid | RPI 3 Mediaclient | RPI 3 | RPI 3 Refapp2 | RPI 4 Hybrid 32 Bit | RPI 4 Mediaclient 32 Bit | BRCM VA | BRCM Refapp2 | AMLOGIC AH212 | AMLOGIC AT301 | REALTEK |
---|---|---|---|---|---|---|---|---|---|---|---|---|
gst-play-1.0 | play a H264 or MPEG 2 local transport stream | |||||||||||
gst-launch uri=aamp | test playback using gst-launch with aamp uri using HLS manifest | |||||||||||
aamp-cli HLS | HLS (.m3u8) video streaming using aamp-cli | |||||||||||
aamp-cli DASH | DASH (.mpd) video streaming using aamp-cli | |||||||||||
aamp-cli PLAYREADY_DRM | Encrypted Playready Playback with aamp-cli | |||||||||||
aamp-cli WIDEVINE_DRM | Encrypted Widevine Playback with aamp-cli | |||||||||||
rmfApp | test streaming from hybrid to client | |||||||||||
rdkShellServicesCITest | RDK Shell CI tests which test RDK Shell/Services API's | |||||||||||
aampCI Tests | Launches AAMP based unified player URL in a webkit instance and runs the embedded tests |