diff options
Diffstat (limited to 'manual/generic/linux')
34 files changed, 1232 insertions, 0 deletions
diff --git a/manual/generic/linux/bluetooth-audio-ui.yaml b/manual/generic/linux/bluetooth-audio-ui.yaml new file mode 100644 index 0000000..ae35bfd --- /dev/null +++ b/manual/generic/linux/bluetooth-audio-ui.yaml @@ -0,0 +1,31 @@ +metadata: + name: bluetooth-audio-ui + format: "Manual Test Definition 1.0" + description: "Test bluetooth audio streaming from UI on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash any UI enabled Xfce based build, power on the board until boot up successfully. + - Make sure mouse and/or keyboard is connected to the board. + - Make sure some bluetooth audio device (speaker, headset) is turned on and within the range. + - Click on BT icon an select "Setup a new device" option. Click continue to search devices. + - Change "Device type" to "Headphones, headsets and other audio devices" to only display audio devices. + - Select the audio device and pair it. + - Download audio file "http://samplemedia.linaro.org/Audio/big_buck_bunny_MP3_2Channel_44.1k_128K_short.MP3" + - Open sound option and select output as the conected BT audio device. + - Play the audio file. + + expected: + - Audio device can be connected and paired. + - Proper sound can be heard from audio device when music file is played. diff --git a/manual/generic/linux/bluetooth-audio.yaml b/manual/generic/linux/bluetooth-audio.yaml new file mode 100644 index 0000000..d1ba41a --- /dev/null +++ b/manual/generic/linux/bluetooth-audio.yaml @@ -0,0 +1,46 @@ +metadata: + name: linux-bluetooth-audio + format: "Manual Test Definition 1.0" + description: "Test if Bluetooth audio works well" + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Boot the board to console + - Make sure at least one BT A2DP (speaker, headset) device is available in the radio range and in discoverable mode. + - "$ sudo bluetoothctl -a" + - "[bluetooth]# pairable on" + - "[bluetooth]# scan on" + - "[bluetooth]# connect <mac_id>" + - "[bluetooth]# quit" + - Use paplay to play .WAV file. Run + - "$ pactl list" + - If the active profile isn't A2DP, then set it or else skip. + - "$ pactl set-card-profile 0 a2dp" + - Play sound and should be able to hear on speaker. + - "$ paplay -d bluez_sink.<mac_id> /usr/share/sounds/alsa/Front_Center.wav" + - Play .MP3/.OGG file via xmms. Start xmms2, add files to the default playlist and play. + - "$ xmms2" + - "xmms2> add file.mp3" + - "xmms2> add file.ogg" + - "xmms2> play" + - Set volume via xmms2 + - "xmms2> server volume [0..100]" + + expected: + - Scanning works and device MAC addresses are displayed + - It is possible to connect to audio device + - Playback works well with no bad sound artifacts + - Setting volume works well + - No kernel errors crashes occur diff --git a/manual/generic/linux/bluetooth-file-transfer-ui.yaml b/manual/generic/linux/bluetooth-file-transfer-ui.yaml new file mode 100644 index 0000000..cd07f60 --- /dev/null +++ b/manual/generic/linux/bluetooth-file-transfer-ui.yaml @@ -0,0 +1,29 @@ +metadata: + name: bluetooth-file-transfer-ui + format: "Manual Test Definition 1.0" + description: "Test Bluetooth file transfer on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash any UI enabled Xfce based build, power on the board until boot up successfully. + - Make sure mouse is connected to the board. + - Make sure some bluetooth device (laptop, phone, tablet) is turned on, within the range and supports BT FTP profile. + - Click the BT icon, turn on bluetooth and select "send files to device" option. + - Select the device to transfer file to and click ok (some devices need to be paired before sending files). + - Select the file to transfer and click send. + - The receiving device has to accept incoming file transfer. + + expected: + - Bluetooth file transfer can be performed successfully. + - No kernel or driver crash occurs. diff --git a/manual/generic/linux/bluetooth-pair-ui.yaml b/manual/generic/linux/bluetooth-pair-ui.yaml new file mode 100644 index 0000000..90dfeba --- /dev/null +++ b/manual/generic/linux/bluetooth-pair-ui.yaml @@ -0,0 +1,29 @@ +metadata: + name: bluetooth-pair-ui + format: "Manual Test Definition 1.0" + description: "Test bluetooth pairing from UI on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash any UI enabled Xfce based build, power on the board until boot up successfully. + - Make sure mouse and keyboard is connected to the board. + - Make sure some bluetooth keyboard is turned on and within the range. + - Click on BT icon and select "Setup a new device" and continue to scan device. + - Select the device from device list to connect and click continue. + - Host machine will show a pin number to pair. + # some devices don't require PIN to be connected + - Enter the pin number on the BT device (keyboard) to connect. + + expected: + - Bluetooth device is connected and pairing is successful. diff --git a/manual/generic/linux/bluetooth-pair.yaml b/manual/generic/linux/bluetooth-pair.yaml new file mode 100644 index 0000000..6e0750f --- /dev/null +++ b/manual/generic/linux/bluetooth-pair.yaml @@ -0,0 +1,36 @@ +metadata: + name: linux-bluetooth-scan + format: "Manual Test Definition 1.0" + description: "Test if Bluetooth scan, pairing and file transfer works." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Boot the board to console + - Make sure at least one BT keyboard device is available in the radio range and in discoverable mode. + - "$ sudo su" + - "# bluetoothctl -a" + - "[bluetooth]# pairable on" + - "[bluetooth]# scan on" + - Note MAC-ID of desired device to Connect. + - "[bluetooth]# default-agent" + - "[bluetooth]# pair <MAC-ID>" + - "[bluetooth]# trust <MAC-ID>" + - "[bluetooth]# quit" + - Type on the BT keyboard. + expected: + - Scanning works and device MAC addresses are displayed + - Pairing works and bluetoothctl displays proper message + - Keyboard works and typed characters appear in console + - No kernel errors crashes occur diff --git a/manual/generic/linux/bluetooth-scan-ui.yaml b/manual/generic/linux/bluetooth-scan-ui.yaml new file mode 100644 index 0000000..3d729a5 --- /dev/null +++ b/manual/generic/linux/bluetooth-scan-ui.yaml @@ -0,0 +1,27 @@ +metadata: + name: bluetooth-scan-ui + format: "Manual Test Definition 1.0" + description: "Test Bluetooth scanning feature on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash any UI enabled Xfce based build, power on the board until boot up successfully. + - Make sure mouse is connected to the board. + - Make sure some bluetooth device (mouse, keyboard, speaker) is turned on and within the range. + - Click the BT icon and select "setup a new device" option. + - Click on continue to search for available bluetooth devices. + + expected: + - Bluetooth can be enabled and devices show up when scanned. + - No kernel ir driver crash occurs diff --git a/manual/generic/linux/bluetooth-scan.yaml b/manual/generic/linux/bluetooth-scan.yaml new file mode 100644 index 0000000..1564f4c --- /dev/null +++ b/manual/generic/linux/bluetooth-scan.yaml @@ -0,0 +1,29 @@ +metadata: + name: linux-bluetooth-scan + format: "Manual Test Definition 1.0" + description: "Test if Bluetooth scan, pairing and file transfer works." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Boot the board to console + - Make sure at least one BT device is available in the radio range and in discoverable mode. + - "$ sudo su" + - "# bluetoothctl -a" + - "[bluetooth]# pairable on" + - "[bluetooth]# scan on" + - "[bluetooth]# quit" + expected: + - Scanning works and device MAC addresses are displayed + - No kernel errors crashes occur diff --git a/manual/generic/linux/display-blanking.yaml b/manual/generic/linux/display-blanking.yaml new file mode 100644 index 0000000..dd97908 --- /dev/null +++ b/manual/generic/linux/display-blanking.yaml @@ -0,0 +1,28 @@ +metadata: + name: display-blanking + format: "Manual Test Definition 1.0" + description: "Test display blanking on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash any UI enabled Xfce based build, power on the board until boot up successfully. + - Make sure mouse and/or keyboard is connected to the board. + - Open "Brightness & lock" from system settings. + - Change "Turn screen off when inactive for" setting to 1 minute. + - Wait for screen to go blank. + - Move mouse/keywboard to get display back. + + expected: + - "Blanking and un-blanking should work fine." + - "No kernel panic or severe error observed." diff --git a/manual/generic/linux/ds5-remote-debug.yaml b/manual/generic/linux/ds5-remote-debug.yaml new file mode 100644 index 0000000..2b30006 --- /dev/null +++ b/manual/generic/linux/ds5-remote-debug.yaml @@ -0,0 +1,26 @@ +metadata: + name: ds5-remote-debug + format: "Manual Test Definition 1.0" + description: "Test remote debug feature in ARM DS-5 for hardware board." + maintainer: + - botao.sun@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + environment: + - manual-test + +run: + steps: + - "Power on the board until boot up successfully." + - "Follow this WiKi page to perform the debug procedures: https://wiki.linaro.org/Platform/DevPlatform/DS5#Application_debugger_validation" + - "This test depends on test 'ds5-ssh'" + expected: + - "'ds5-ssh' test should be done successfully as a pre-condition." + - "After debug view shows, by clicking F5, F6 and F7, the feature should work well." diff --git a/manual/generic/linux/ds5-ssh.yaml b/manual/generic/linux/ds5-ssh.yaml new file mode 100644 index 0000000..4d37e3c --- /dev/null +++ b/manual/generic/linux/ds5-ssh.yaml @@ -0,0 +1,25 @@ +metadata: + name: ds5-ssh + format: "Manual Test Definition 1.0" + description: "Test SSH connection in ARM DS-5 for hardware board." + maintainer: + - botao.sun@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + environment: + - manual-test + +run: + steps: + - "Power on the board until boot up successfully." + - "Follow this WiKi page to establish the SSH connection: https://wiki.linaro.org/Platform/DevPlatform/DS5#RSE_validation" + expected: + - "The SSH connection in ARM DS-5 between host PC and target board should be established successfully." + - "Remote terminal console can be launched successfully in DS-5." diff --git a/manual/generic/linux/hdmi-resolution-switching-cmd.yaml b/manual/generic/linux/hdmi-resolution-switching-cmd.yaml new file mode 100644 index 0000000..c374007 --- /dev/null +++ b/manual/generic/linux/hdmi-resolution-switching-cmd.yaml @@ -0,0 +1,31 @@ +metadata: + name: hdmi-resolution-switching-cmd + format: "Manual Test Definition 1.0" + description: "Check if switching HDMI resolution on monitor works from Terminal." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board. + - Wait until board boots up successfully. + - To get HDMI output name and available resolutions, run "$ xrandr" + - To switch resolution, run "$ xrandr --output <HDMI_output_name> --mode <available_modes>" + - Change to different resolutions couple of times. + + expected: + - "Switching HDMI resolutions from Terminal should work well." + - "No Kernel panic, crash, hang or any other severe error observed during reolution switching." diff --git a/manual/generic/linux/hdmi-resolution-switching.yaml b/manual/generic/linux/hdmi-resolution-switching.yaml new file mode 100644 index 0000000..bcc99bf --- /dev/null +++ b/manual/generic/linux/hdmi-resolution-switching.yaml @@ -0,0 +1,32 @@ +metadata: + name: hdmi-resolution-switching + format: "Manual Test Definition 1.0" + description: "Check if switching HDMI resolution on monitor works." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board. + - Wait until board boots up successfully. + - To switch HDMI resolution from UI, open Displays from system settings. + - Select 'HDMI Display' from Displays option. + - Select a different resolution available from drop-down menu. + - Repeat switching resolutions couple of times. + + expected: + - "Switching HDMI resolutions from UI should work well." + - "No Kernel panic, crash, hang or any other severe error observed." diff --git a/manual/generic/linux/ip_forwarding.yaml b/manual/generic/linux/ip_forwarding.yaml new file mode 100644 index 0000000..6331b46 --- /dev/null +++ b/manual/generic/linux/ip_forwarding.yaml @@ -0,0 +1,49 @@ +metadata: + name: IP forwarding + format: "Manual Test Definition 1.0" + description: "Test if Kernel IP forwarding works." + maintainer: + - chase.qi@linaro.org + os: + - debian + - centos + scope: + - functional + devices: + - d02 + - overdrive + environment: + - manual-test + +run: + steps: + - SUT(system under test) should has at least two Ethernet ports. Assume you use SUT_eth0 and SUT_eth1 here. + - Make sure iptables package installed on SUT. + - Boot SUT and test client to OS. + - Run "sudo su -" to switch to root user. + - Run "ip addr show" to check if the ports used for testing are detected. + - Do the following steps on SUT to set test environment and enable ip_forward. + - Connect SUT_eth1 to router0 that connected to internet. Assume the gateway IP is 10.0.0.1. + - Connect SUT_eth0 to router1 that used for private network. + - Execute "dhclient eth1" to get a IP address or set IP for it manually. + - Execute "ping -I eth1 10.0.0.1" and "ping -I eth1 8.8.8.8" to check if eth1 is set properly. + - "ip link set eth0 down" + - "ip addr add 192.168.1.1/24 dev eth0" + - "ip link set eth0 up" + # Enable ip_forward from Linux Kernel. + - "echo 1 > /proc/sys/net/ipv4/conf/all/forwarding" + # Enable NAT(network address translation) + - "iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE" + - "iptables -A FORWARD -i eth0 -j ACCEPT" + - Do the following steps on test client to test if Kernel IP forwarding works. + - Connect test client eth0 port to the private route1. + - "ip link set eth0 down" + - "ip addr add 192.168.1.2/24 dev eth0" + - "ip link set eth0 up" + - "ip route add default via 192.168.1.1" + - "ping 10.0.0.1" + - "ping 8.8.8.8" + + expected: + - ip_forward and NAT can be enabled successfully. + - ping tests from test client to router0 and Google DNS server are successful. diff --git a/manual/generic/linux/kvm-arm32-guest-on-arm64-host.yaml b/manual/generic/linux/kvm-arm32-guest-on-arm64-host.yaml new file mode 100644 index 0000000..1750034 --- /dev/null +++ b/manual/generic/linux/kvm-arm32-guest-on-arm64-host.yaml @@ -0,0 +1,44 @@ +metadata: + name: kvm-arm32-guest-on-arm64-host + format: "Manual Test Definition 1.0" + description: "Test kvm running on arm32 bit guest on arm64 bit host" + maintainer: + - naresh.kamboju@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + environment: + - manual-test + +install: + deps: + - qemu-system + - wget + - xz-utils +run: + steps: + - Boot arm64 bit board + - After boot success check for "ls /dev/kvm" kvm device entry + - If /dev/kvm not found, mark test case as not applicable and exit + - Else continue below steps for installation of required packages + - Run "sudo apt-get update" + - Run "sudo apt-get install qemu-system wget xz-utils" + - Download armv7 kernel Image from linaro snapshots + - Note: please double check latest in the below link it may be build number + - "wget http://snapshots.linaro.org/ubuntu/images/kvm/arndale/latest/zImage-armv7" + - Download arm minimal rootfs from linaro snapshots + - Note: please double check latest in the below link it may be build number + - "wget http://snapshots.linaro.org/ubuntu/images/kvm-guest/53/armhf/kvm-armhf.qcow2.xz" + - "xz -d kvm-armhf.qcow2.xz" + - Test arm32 guest Image on arm64 host + - Run "qemu-system-aarch64 -smp 2 -m 512 -cpu host,aarch64=off -M virt -kernel ./zImage-armv7 -append 'root=/dev/vda2 rw rootwait mem=512M console=ttyAMA0,38400n8' -device virtio-blk-device,drive=image -drive if=none,id=image,file=kvm-armhf.qcow2 -nographic -enable-kvm 2>&1 | tee kvm-arm32.log" + - Wait for couple of minutes let the qemu start booting guest kernel + + expected: + - qemu should start booting the given guest kernel + - qeme guest kernel boot should be successful + - Run "uname -a" to check system information diff --git a/manual/generic/linux/kvm-arm64-guest-on-arm64-host.yaml b/manual/generic/linux/kvm-arm64-guest-on-arm64-host.yaml new file mode 100644 index 0000000..8d720ca --- /dev/null +++ b/manual/generic/linux/kvm-arm64-guest-on-arm64-host.yaml @@ -0,0 +1,47 @@ +metadata: + name: kvm-arm64-guest-on-arm64-host + format: "Manual Test Definition 1.0" + description: "Test kvm running on arm64 bit guest on arm64 bit host" + maintainer: + - naresh.kamboju@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + environment: + - manual-test + +install: + deps: + - qemu-system + - wget + - xz-utils +run: + steps: + - Boot arm64 bit board + - After boot success check for "ls /dev/kvm" kvm device entry + - If /dev/kvm not found, mark test case as not applicable and exit + - Else continue below steps for installation of required packages + - Run "sudo apt-get update" + - Run "sudo apt-get install qemu-system wget xz-utils" + - Use arm64 kernel Image from /boot + - "cp /boot/vmlinuz-`uname -r` Image" + - Use arm64 initrd.img from /boot + - Note: please double check is it Debian initrd image or CentOS initrd + - Note: please check the name of initrd file under /boot and kernel version appended to file name + - "cp /boot/initrd.img-`uname -r` initrd.img" + - Download arm64 minimal rootfs from linaro snapshots + - Note: please double check latest in the below link it may be build number + - "wget http://snapshots.linaro.org/ubuntu/images/kvm-guest/latest/arm64/kvm-arm64.qcow2.xz" + - "xz -d kvm-arm64.qcow2.xz" + - Test arm64 guest Image on arm64 host + - Run "qemu-system-aarch64 -smp 2 -m 512 -cpu host -machine type=virt,gic-version=host -kernel Image -initrd initrd.img -append 'root=/dev/vda2 rw rootwait console=ttyAMA0,38400n8 earlycon=pl011,0x9000000' -device virtio-blk-device,drive=image -drive if=none,id=image,file=kvm-arm64.qcow2 -nographic -enable-kvm 2>&1 | tee tee kvm-arm64.log" + - Wait for couple of minutes let the qemu start booting guest kernel + + expected: + - qemu should start booting the given guest kernel + - qeme guest kernel boot should be successful + - Run "uname -a" to check system information diff --git a/manual/generic/linux/multi-nic-download.yaml b/manual/generic/linux/multi-nic-download.yaml new file mode 100644 index 0000000..37aa7e3 --- /dev/null +++ b/manual/generic/linux/multi-nic-download.yaml @@ -0,0 +1,34 @@ +metadata: + name: multi-nic-download + format: "Manual Test Definition 1.0" + description: "Test if download can be performed by selecting an interface from multiple available interfaces." + maintainer: + - amit.khare@linaro.org + - chase.qi@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash the board and boot succesfully. + - Make sure "curl" and "iftop" utilities are installed, and at least two interfaces are configured and connected to the board. + - Run, "sudo su" to become root. + - Run, "ifconfig" to check both interfaces (going to be used for this test) are connected and IP address is assigned. + - Run the following two commands to make sure that rp_filter is set to 0. + - "echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter" + - "echo 0 > /proc/sys/net/ipv4/conf/default/rp_filter" + - Run, "sysctl -a |grep rp_filter" to check arp setting. + - Run, "curl -O --interface interface-1-ip http://samplemedia.linaro.org/MPEG4/big_buck_bunny_1080p_MPEG4_MP3_25fps_7600K_short.AVI" + - Run, "curl -O --interface interface-2-ip http://samplemedia.linaro.org/MPEG4/big_buck_bunny_1080p_MPEG4_MP3_25fps_7600K_short.AVI" + - Use "iftop" to verify that Curl is using the correct interface to download file in both cases. + + expected: + - File can be successfully downloaded with both interfaces. + - The correct interface was used to download file. diff --git a/manual/generic/linux/opengl-fps.yaml b/manual/generic/linux/opengl-fps.yaml new file mode 100644 index 0000000..3ca566a --- /dev/null +++ b/manual/generic/linux/opengl-fps.yaml @@ -0,0 +1,30 @@ +metadata: + name: opengl-fps + format: "Manual Test Definition 1.0" + description: "Measure OpenGL FPS with glxgears and Tux Racer." + maintainer: + - chase.qi@linaro.org + os: + - debian + scope: + - benchmark + devices: + - hi6220-hikey + - db410c + - Bubblegum + environment: + - manual-test + +run: + steps: + - Install glxgears and Tux Racer with the following command. + - "# apt-get install mesa-utils extremetuxracer" + - Run glxgears with the following command and record FPS. + - "# glxgears" + - "Start Tux Racer by clicking 'Games' -> 'Extreme Tux Racer' in system application menu." + - "Display FPS in Tux Racer by selecting 'Configuration' -> 'Graphics' -> 'Display FSP'." + - Play Tux Racer and record FPS. + + expected: + - glxgears and Tux Racer works. + - glxgears and Tux Racer print FPS numbers. diff --git a/manual/generic/linux/power-off-cmd.yaml b/manual/generic/linux/power-off-cmd.yaml new file mode 100644 index 0000000..0d22ba7 --- /dev/null +++ b/manual/generic/linux/power-off-cmd.yaml @@ -0,0 +1,29 @@ +metadata: + name: power-off-cmd + format: "Manual Test Definition 1.0" + description: "Check 'Power OFF' feature from console." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board until boot up successfully. + - After command line prompt shows in serial console, run + - "$ sudo poweroff" + + expected: + - "The board should can be shut down successfully, no display shows and no activity in serial console." + - "No Kernel panic, crash, hang or any other severe error observed." diff --git a/manual/generic/linux/power-off.yaml b/manual/generic/linux/power-off.yaml new file mode 100644 index 0000000..96ec3ff --- /dev/null +++ b/manual/generic/linux/power-off.yaml @@ -0,0 +1,29 @@ +metadata: + name: power-off + format: "Manual Test Definition 1.0" + description: "Check 'Power OFF' function on hardware board." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board. + - Wait until board boots up successfully to UI. + - Shutdown the board using UI power-off option. + + expected: + - "The board should can be shut down successfully, no display shows and no activity in serial console." + - "No Kernel panic, crash, hang or any other serve error observed." diff --git a/manual/generic/linux/reboot-ui.yaml b/manual/generic/linux/reboot-ui.yaml new file mode 100644 index 0000000..23c4a3e --- /dev/null +++ b/manual/generic/linux/reboot-ui.yaml @@ -0,0 +1,29 @@ +metadata: + name: power-off + format: "Manual Test Definition 1.0" + description: "Check 'Re-boot' function from UI." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board. + - Wait until board boots up successfully to UI. + - Reboot the board using UI reboot option. + + expected: + - "The board should can be rebooted successfully." + - "No Kernel panic, crash, hang or any other severe error observed." diff --git a/manual/generic/linux/reboot.yaml b/manual/generic/linux/reboot.yaml new file mode 100644 index 0000000..cdcfca6 --- /dev/null +++ b/manual/generic/linux/reboot.yaml @@ -0,0 +1,28 @@ +metadata: + name: reboot + format: "Manual Test Definition 1.0" + description: "Check the board can be rebooted or not" + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board until boot up successfully. + - Reboot the board from terminal. Run + - "$ sudo shutdown -r now" + + expected: + - "Reboot should be done successfully from terminal, without kernel panic, crash, hang or any other serve error observed." diff --git a/manual/generic/linux/sd-mmc.yaml b/manual/generic/linux/sd-mmc.yaml new file mode 100644 index 0000000..0945691 --- /dev/null +++ b/manual/generic/linux/sd-mmc.yaml @@ -0,0 +1,31 @@ +metadata: + name: sd-mmc + format: "Manual Test Definition 1.0" + description: "Test if the SD/MMC cards are properly registered by kernel" + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - vexpress-a9 + - vexpress-tc2 + - arndale + - ifc6410 + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board until boot successfully + - In serial console, run + - "$ dmesg | grep error" + + expected: + - "There should be no 'I/O' error shown in std output." diff --git a/manual/generic/linux/sdcard-cold-boot.yaml b/manual/generic/linux/sdcard-cold-boot.yaml new file mode 100644 index 0000000..0ce58b3 --- /dev/null +++ b/manual/generic/linux/sdcard-cold-boot.yaml @@ -0,0 +1,44 @@ +metadata: + name: sdcard-cold-boot + format: "Manual Test Definition 1.0" + description: "Test sd-card cold boot on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash debian build. + - Make sure SD card is plugged before booting the board. + - Power on the board until boot up successfully. + - On terminal/serial console run: + - lsblk + - Check the name of SD card and mount it. + - sudo mount /dev/mmcblk0 /media/ + - cd /media + - ls + - cd .. + - umount /media + + expected: + - Output of "lsblk" should be similar to this. + NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT + sda 8:0 0 465.8G 0 disk + ├─sda1 8:1 0 1.5G 0 part + ├─sda2 8:2 0 116G 0 part + ├─sda4 8:4 0 1K 0 part + ├─sda5 8:5 0 38G 0 part [SWAP] + └─sda6 8:6 0 176.2G 0 part / + sr0 11:0 1 601.5M 0 rom + mmcblk0 179:0 0 7.5G 0 disk + └─mmcblk0p1 179:1 0 7.5G 0 part /media/40F0-07C2 + - SD card is mounted/unmounted and content of SD card shows up with "ls" command. + - No kernel panic or crash is observed on serial console. diff --git a/manual/generic/linux/sdcard-hot-plug.yaml b/manual/generic/linux/sdcard-hot-plug.yaml new file mode 100644 index 0000000..2d2b848 --- /dev/null +++ b/manual/generic/linux/sdcard-hot-plug.yaml @@ -0,0 +1,44 @@ +metadata: + name: sdcard-cold-boot + format: "Manual Test Definition 1.0" + description: "Test sd-card cold boot on Debian." + maintainer: + - amit.khare@linaro.org + os: + - debian + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Flash debian build. + - Power on the board until boot up successfully. + - Plug SD card into the slot on board after after boot is complete. + - On terminal/serial console run: + - lsblk + - Check the name of SD card and mount it. + - sudo mount /dev/mmcblk0 /media/ + - cd /media + - ls + - cd .. + - umount /media + + expected: + - Output of "lsblk" should be similar to this. + NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT + sda 8:0 0 465.8G 0 disk + ├─sda1 8:1 0 1.5G 0 part + ├─sda2 8:2 0 116G 0 part + ├─sda4 8:4 0 1K 0 part + ├─sda5 8:5 0 38G 0 part [SWAP] + └─sda6 8:6 0 176.2G 0 part / + sr0 11:0 1 601.5M 0 rom + mmcblk0 179:0 0 7.5G 0 disk + └─mmcblk0p1 179:1 0 7.5G 0 part /media/40F0-07C2 + - SD card is mounted/unmounted and content of SD card shows up with "ls" command. + - No kernel panic or crash is observed on serial console. diff --git a/manual/generic/linux/secondary-video-out.yaml b/manual/generic/linux/secondary-video-out.yaml new file mode 100644 index 0000000..d1de364 --- /dev/null +++ b/manual/generic/linux/secondary-video-out.yaml @@ -0,0 +1,25 @@ +metadata: + name: secondary-video-out + format: "Manual Test Definition 1.0" + description: "Test the secondary video output on hardware board." + maintainer: + - botao.sun@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + environment: + - manual-test + +run: + steps: + - "Using HDMI cable to connect the hardware board to a display device, usually an external monitor." + - "Power on the board until boot up successfully." + - "For TI Panda 4430 and 4460, the secondary video output is the DVI-D port." + expected: + - "The video output should show up on that display device, for example, the boot log and command prompt can be seen on screen." diff --git a/manual/generic/linux/usb-3.0-arndale5250.yaml b/manual/generic/linux/usb-3.0-arndale5250.yaml new file mode 100644 index 0000000..59ca59e --- /dev/null +++ b/manual/generic/linux/usb-3.0-arndale5250.yaml @@ -0,0 +1,121 @@ +metadata: + name: usb-3.0-arndale5250 + format: "Manual Test Definition 1.0" + description: "Check enablement of USB 3.0 on Samsung Arndale 5250 board." + maintainer: + - botao.sun@linaro.org + os: + - ubuntu + scope: + - functional + devices: + - arndale + environment: + - manual-test + +run: + steps: + - "Plug an external USB storage device to on-board USB 3.0 slot." + - "Power on the board until boot up successfully." + - "In serial console, run: + # fdisk -l + # mount /dev/sda1 /media + # cd /media + # ls -l + # lsusb + # lsusb -t + # cd .. + # umount /media" + expected: + - "the output of command line 'fdisk -l' should look like this: + # fdisk -l + + Disk /dev/mmcblk0: 4001 MB, 4001366016 bytes + 4 heads, 16 sectors/track, 122112 cylinders, total 7815168 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x00000000 + + Device Boot Start End Blocks Id System + /dev/mmcblk0p1 3031424 7815167 2391872 c W95 FAT32 (LBA) + /dev/mmcblk0p2 31168 1031295 500064 83 Linux + /dev/mmcblk0p3 1031296 2031359 500032 83 Linux + /dev/mmcblk0p4 2031360 3031423 500032 83 Linux + + Partition table entries are not in disk order + + Disk /dev/mmcblk0rpmb: 0 MB, 131072 bytes + 4 heads, 16 sectors/track, 4 cylinders, total 256 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x00000000 + + Disk /dev/mmcblk0rpmb doesn't contain a valid partition table + + Disk /dev/mmcblk0boot1: 1 MB, 1048576 bytes + 4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x00000000 + + Disk /dev/mmcblk0boot1 doesn't contain a valid partition table + + Disk /dev/mmcblk0boot0: 1 MB, 1048576 bytes + 4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0xea000790 + + Disk /dev/mmcblk0boot0 doesn't contain a valid partition table + + Disk /dev/mmcblk1: 7948 MB, 7948206080 bytes + 128 heads, 32 sectors/track, 3790 cylinders, total 15523840 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x00000000 + + Device Boot Start End Blocks Id System + /dev/mmcblk1p1 1 8191 4095+ da Non-FS data + /dev/mmcblk1p2 * 8192 114687 53248 c W95 FAT32 (LBA) + /dev/mmcblk1p3 114688 2097151 991232 83 Linux + + Disk /dev/sda: 7948 MB, 7948206080 bytes + 81 heads, 10 sectors/track, 19165 cylinders, total 15523840 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x00000000 + + Device Boot Start End Blocks Id System + /dev/sda1 8192 15523839 7757824 b W95 FAT32 + #" + + - "command line 'mount /dev/sda1 /media' should be executed successfully, the contents on USB external storage device should be shown after run 'ls -l'" + + - "the output of 'lsusb' and 'lsusb -t' should look like this: + # lsusb + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 002: ID 05e3:0717 Genesys Logic, Inc. All-in-1 Card Reader + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 004: ID 0b95:772a ASIX Electronics Corp. AX88772A Fast Ethernet + Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub + Bus 001 Device 002: ID 0424:3503 Standard Microsystems Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + # + + # lsusb -t + /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M + /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M + |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M + |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M + |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M + |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=asix, 480M + #" diff --git a/manual/generic/linux/usb-camera.yaml b/manual/generic/linux/usb-camera.yaml new file mode 100644 index 0000000..7ac8c49 --- /dev/null +++ b/manual/generic/linux/usb-camera.yaml @@ -0,0 +1,34 @@ +metadata: + name: usb-camera + format: "Manual Test Definition 1.0" + description: "Test if USB camera works on Linux" + maintainer: + - chase.qi@linaro.org + os: + - linux + scope: + - functional + devices: + - panda + - panda-es + - vexpress-a9 + - vexpress-tc2 + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Login as root and plug in your USB camera. + - Run "apt-get install cheese" to install Cheese. + - Open Cheese, go to its preference and select your USB camera. + - Take a photo and a video. + - Open the photo and play the video. + + expected: + - In Cheese preference, USB camera appears in the device list. + - Photo and video taking are successful. + - The photo and the video look good. + - No crash observed. diff --git a/manual/generic/linux/usb-ethernet.yaml b/manual/generic/linux/usb-ethernet.yaml new file mode 100644 index 0000000..7d73a72 --- /dev/null +++ b/manual/generic/linux/usb-ethernet.yaml @@ -0,0 +1,33 @@ +metadata: + name: usb-ethernet + format: "Manual Test Definition 1.0" + description: "Test if USB Ethernet works on Linux" + maintainer: + - chase.qi@linaro.org + os: + - linux + scope: + - functional + devices: + - panda + - panda-es + - vexpress-a9 + - vexpress-tc2 + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Login as root and plug in your USB Ethernet gadget. + - Run "dmesg" to find the device ID. Take "eth0" for example. + - Run "ifconfig eht0" to check if IP address assigned by DHCP server. If not, run "dhclient eth0" to get an IP address. + - "ping www.google.com" + - "wget http://testdata.validation.linaro.org/media_codec/vpx_streams/vp90-2-tos_1280x534_tile_1x4_1306kbps.webm" + + expected: + - USB Ethernet obtains an IP address successfully. + - ping and file download tests are successful. + - No crash observed from serial console. diff --git a/manual/generic/linux/usb-keyboard.yaml b/manual/generic/linux/usb-keyboard.yaml new file mode 100644 index 0000000..8a4391a --- /dev/null +++ b/manual/generic/linux/usb-keyboard.yaml @@ -0,0 +1,30 @@ +metadata: + name: usb-keyboard + format: "Manual Test Definition 1.0" + description: "Basic test for USB keyboard functionality" + maintainer: + - botao.sun@linaro.org + os: + - android + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - vexpress-a9 + - vexpress-tc2 + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - "Plug USB keyboard into an on-board USB slot." + - "Power on the board until boot up successfully." + - "After command line prompt shows in serial console, type 'ls -l' then click enter key." + expected: + - "String 'ls -l' should show up in serial console, after click enter key, files with detail should be listed." diff --git a/manual/generic/linux/usb-storage.yaml b/manual/generic/linux/usb-storage.yaml new file mode 100644 index 0000000..db0367b --- /dev/null +++ b/manual/generic/linux/usb-storage.yaml @@ -0,0 +1,76 @@ +metadata: + name: usb-storage + format: "Manual Test Definition 1.0" + description: "Basic test for USB keyboard functionality" + maintainer: + - botao.sun@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - panda + - panda-es + - arndale + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - "Plug an external USB storage device into an on-board USB 2.0 slot." + - "Power on the board until boot up successfully." + - "In serial console, run: + # fdisk -l + # mount /dev/sda1 /media + # cd /media + # ls -l + # lsusb + # lsusb -t + # cd .. + # umount /media" + expected: + - "the output of command line 'fdisk -l' should look like this: + # fdisk -l + Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes + 128 heads, 32 sectors/track, 1890 cylinders, total 7744512 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x00000000 + + Device Boot Start End Blocks Id System + /dev/mmcblk0p1 1 8191 4095+ da Non-FS data + /dev/mmcblk0p2 * 8192 114687 53248 c W95 FAT32 (LBA) + /dev/mmcblk0p3 114688 2097151 991232 83 Linux + + Disk /dev/sda: 7973 MB, 7973371904 bytes + 246 heads, 62 sectors/track, 1021 cylinders, total 15572992 sectors + Units = sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disk identifier: 0x0005c5d3 + + Device Boot Start End Blocks Id System + /dev/sda1 62 15572291 7786115 c W95 FAT32 (LBA)" + - "command line 'mount /dev/sda1 /media' should be executed successfully, the contents on USB external storage device should be shown after run 'ls -l'" + - "the output of 'lsusb' and 'lsusb -t' should look like this: + # lsusb + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 004: ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277] + Bus 001 Device 005: ID 046d:c31d Logitech, Inc. + Bus 001 Device 008: ID 05e3:0717 Genesys Logic, Inc. All-in-1 Card Reader + + # lsusb -t + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=s5p-ehci/3p, 480M + |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M + |__ Port 2: Dev 4, If 0, Class=vend., Driver=asix, 480M + |__ Port 3: Dev 5, If 0, Class=HID, Driver=usbhid, 1.5M + |__ Port 3: Dev 5, If 1, Class=HID, Driver=usbhid, 1.5M + |__ Port 4: Dev 8, If 0, Class=stor., Driver=usb-storage, 480M" + - "Command 'umount /media' should be executed successfully" diff --git a/manual/generic/linux/wifi-large-download.yaml b/manual/generic/linux/wifi-large-download.yaml new file mode 100644 index 0000000..bf2870b --- /dev/null +++ b/manual/generic/linux/wifi-large-download.yaml @@ -0,0 +1,24 @@ +metadata: + name: wifi-large-downlaod + format: "Manual Test Definition 1.0" + description: "Test if large file can be downloaded via WiFi." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Boot the board successfully to UI. + - Check available wireless network and connect. + - Open browser and download this file "http://samplemedia.linaro.org/H264/tears_of_steel_1080p_H264_24fps.mov" + + expected: + - Downloading tears_of_steel_1080p_H264_24fps.mov file completes without any issues. diff --git a/manual/generic/linux/wifi-small-download.yaml b/manual/generic/linux/wifi-small-download.yaml new file mode 100644 index 0000000..6f3e09a --- /dev/null +++ b/manual/generic/linux/wifi-small-download.yaml @@ -0,0 +1,24 @@ +metadata: + name: wifi-small-downlaod + format: "Manual Test Definition 1.0" + description: "Test if small file can be downloaded via WiFi." + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Boot the board successfully to UI. + - Check available wireless network and connect. + - Open browser and download this file "http://samplemedia.linaro.org/MPEG4/big_buck_bunny_1080p_MPEG4_MP3_25fps_7600K_short.AVI" + + expected: + - Downloading big_buck_bunny_1080p_MPEG4_MP3_25fps_7600K_short.AVI file completes without any issues. diff --git a/manual/generic/linux/wifi-teminal.yaml b/manual/generic/linux/wifi-teminal.yaml new file mode 100644 index 0000000..490750c --- /dev/null +++ b/manual/generic/linux/wifi-teminal.yaml @@ -0,0 +1,31 @@ +metadata: + name: linux-wifi-terminal + format: "Manual Test Definition 1.0" + description: "Test if WiFi works well from Terminal" + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Power on the board and wait till it boots succesfully. + - To scan for WiFi, run "$ iwlist wlan0 scan" + - Note ESSID of the access point to connect. + - If the network is open, run "$ iwconfig wlan0 essid NAME_OF_ACCESS_POINT" + - If network requires password, run "$ iwconfig wlan0 essid NAME_OF_ACCESS_POINT key PASSWORD" + - To accquire IP address, run "$ dhclient wlan0" + - To check if IP address is assigned, run "$ ifconfig wlan0" + - To check WiFi connection, run "ping www.google.com" + + expected: + - "Should be able to connect to available WiFi network." + - "Ping command works and should not show any data loss." diff --git a/manual/generic/linux/wifi.yaml b/manual/generic/linux/wifi.yaml new file mode 100644 index 0000000..44ffe51 --- /dev/null +++ b/manual/generic/linux/wifi.yaml @@ -0,0 +1,27 @@ +metadata: + name: linux-wifi-ui + format: "Manual Test Definition 1.0" + description: "Test if WiFi works well from UI" + maintainer: + - amit.khare@linaro.org + os: + - ubuntu + - openembedded + scope: + - functional + devices: + - hi6220-hikey + - apq8016-sbc + environment: + - manual-test + +run: + steps: + - Boot the board successfully to UI. + - Check available wireless network from UI. + - Connect to available SSID(Open, WEP, WPA2). + - Open 'www.google.com' in browser to check WiFi connection. + + expected: + - "Should be able to connect to available WiFi network from UI and Terminal." + - "Google main page should be shown up successfully." |