...
For a list of Sanity Tests see Sanity Test Description
Sanity Test Flows
TDK Test Frameworks
draw.io Diagram |
---|
border | true |
---|
viewerToolbar | true |
---|
| |
---|
fitWindow | false |
---|
diagramName | TDK Test Frameworks |
---|
simpleViewer | false |
---|
width | |
---|
diagramWidth | 1768 |
---|
revision | 2 |
---|
|
...
- 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
Code Block |
---|
|
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
Code Block |
---|
|
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:
Code Block |
---|
|
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
Code Block |
---|
|
# 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
Code Block |
---|
|
# 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/ & |