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

Compare with Current View Page History

« Previous Version 11 Next »

Test Planning

CMFLAB Dashboard

CMFLAB Backlog


Template Tickets (these are cloned for each task)

TaskTemplate Ticket
TDK Intake

CMFLAB-1125 - Getting issue details... STATUS

RDK-B Iteration/Release

CMFLAB-552 - Getting issue details... STATUS

RDK-V Iteration/Release

CMFLAB-365 - Getting issue details... STATUS

RDK-B CODEMGMT Iteration

CODEMGMT-238 - Getting issue details... STATUS

RDK-B CODEMGMT Quarterly Release

CODEMGMT-425 - Getting issue details... STATUS

RDK-V CODEMGMT Iteration

CODEMGMT-180 - Getting issue details... STATUS

RDK-V CODEMGMT Quarterly Release

CODEMGMT-554 - Getting issue details... STATUS


Sanity Test Frameworks

Sanity Test Descriptions

Sanity Test Build Trend



Sanity Test Flows

DUTJenkins Sanity Test Flow JobComments
EMU-Bhttps://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-rdkb-emulator-wifi-flow/
RPI-Bhttps://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-rdkb-raspberrypi-wifi-flow/
EMU-Vhttps://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-hv04-emulators/
RPI-Vhttps://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-rdkv-raspberrypi-flow/
RPI RefApphttps://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-raspberrypi-refapp-flow/
RPI Westeroshttps://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-oss-raspberrypi-flow/
  • Deprecated ?

xg1v3

xi3v2

https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-hv04-platforms/
  • Deprecated

TDK Test Frameworks


TDK Testing is done using 3 frameworks (2 in active use):


DUT TDK FrameworkJenkins FlowTDK ManagerComments
EMU-BATF

https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-atf-start-flow-emub/

http://192.168.32.63/rdk-test-tool/?targetUri=%2Fexecution%2Fcreate
RPI-BATF

https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-atf-start-flow-rpib/

http://192.168.32.69/rdk-test-tool/?targetUri=%2Fexecution%2Fcreate
RPI-VATF

https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-atf-start-flow-rpiv/

http://192.168.32.70/rdk-test-tool/?targetUri=%2Fexecution%2Fcreate
EMU-VRDKV-EMU

https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-emu-start-flow/ 

see section "Access EMU-V TDK VM's on browser" in Useful Tips

xg1v3

xi3v2

RDKV-Platforms

https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-platforms-start-flow/


  • uses ATF for test list creation and report generation
  • Deprecated since 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.

TDK Test Metrics

Test MetricsLink
Nightly CMF Nightly Test Metrics
IterationCMF Iteration Test Metrics
QuarterlyCMF Release Test Metrics

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/cmf_testbed/tools/builds/  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


Useful Tips

Debugging RDKB

ifconfig
iwconfig
systemctl | grep -i ccsp <- see attached for list of key ccsp services that should be running
systemctl -l status <service>
journalctl -u <service>
ps -axf | grep hostapd <- check hotspot
  • If groups of tests failing, likely issue with one service
  • Some services have dependancies so not unusual for a few of them to be in bad state
  • Can take a few minutes for all services to start

Debugging RDKV

systemctl
systemctl -l status <service>
journalctl -u <service>
ps -axf | grep rmfstreamer
  • If E2E/RMF tests failing check if rmfStreamer is running

TDK EMU-B VM

on griffen:

get_vpc_key -i 192.168.32.74 -u <username> griffen
sudo su jenkins

# general info commands
vboxmanage list vms
vboxmanage list runningvms
vboxmanage showvminfo "rdkb-emu-tdk"
vboxmanage list usbhost

# restart vm
vboxmanage startvm "rdkb-emu-tdk" --type headless

# if above restart doesn't work power it off first
vboxmanage controlvm rdkb-emu-tdk poweroff 
vboxmanage startvm "rdkb-emu-tdk" --type headless

# destroy VM
vboxmanage controlvm rdkb-emu-tdk poweroff
vboxmanage unregistervm "rdkb-emu-tdk" --delete

# rdp session for RDK-B Emulator, run following ssh command then on RDP client connect to localhost:3388 
ssh -o "PasswordAuthentication=no" -L 3388:192.168.32.74:3388 -i ~/.griffen-<username>.rsa <username>@192.168.32.74


Access EMU-V TDK VM's on browser

# do get vps on heron first
get_vpc_key -i 192.168.32.76 -u <username> heron

# ssh and tunnel through local port for the TDK Manager your interested in
ssh -L 8085:192.168.21.31:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8086:192.168.21.32:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8087:192.168.21.33:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8088:192.168.21.34:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8089:192.168.21.35:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8090:192.168.21.36:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8091:192.168.21.38:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
ssh -L 8092:192.168.21.39:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76

# now you can access any of the 8 TDK EMU-V TDK Managers in your browser via
http://localhost:<port>/rdk-test-tool/execution/create

# e.g.
ssh -L 8085:192.168.21.31:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76
http://localhost:8086/rdk-test-tool/execution/create


TDK Manger Tips

# Manually start TDK TFTP Server
sudo python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/ &



  • No labels