summaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorMilosz Wasilewski <milosz.wasilewski@linaro.org>2016-10-20 14:38:58 +0100
committerMilosz Wasilewski <milosz.wasilewski@linaro.org>2016-10-20 14:38:58 +0100
commitd341c22fae0e9ebbb27cf1a1d2629c6c011f7d23 (patch)
treed828ef6c6052d0ae2d95b1743d28f556848415c3 /manual
parentd1b6521e96da63cb212a2e18c4a02791bf5e07cb (diff)
downloadtest-definitions-pipe-d341c22fae0e9ebbb27cf1a1d2629c6c011f7d23.tar.gz
Moved manual tests to separate directory
Change-Id: I1092ce929d4d257dfd596034c605b4be5b0189a0 Signed-off-by: Milosz Wasilewski <milosz.wasilewski@linaro.org>
Diffstat (limited to 'manual')
-rw-r--r--manual/dragon410c/dragon410c-user-led.yaml31
-rw-r--r--manual/generic/96boards/hikey-bluetooth-status-led.yaml24
-rw-r--r--manual/generic/96boards/hikey-wifi-status-led.yaml24
-rw-r--r--manual/generic/96boards/status-led-bluetooth.yaml25
-rw-r--r--manual/generic/96boards/status-led-wifi.yaml25
-rw-r--r--manual/generic/android/adb-over-ethernet.yaml37
-rw-r--r--manual/generic/android/adb-over-usb.yaml39
-rw-r--r--manual/generic/android/android-hardware-usb.yaml33
-rw-r--r--manual/generic/android/android-input-method-service.yaml32
-rw-r--r--manual/generic/android/android-ui-auto-mount.yaml29
-rw-r--r--manual/generic/android/android-version.yaml28
-rw-r--r--manual/generic/android/angrybirds.yaml31
-rw-r--r--manual/generic/android/arm-browser-benchmark.yaml44
-rw-r--r--manual/generic/android/audio-jack.yaml32
-rw-r--r--manual/generic/android/bluetooth-audio.yaml25
-rw-r--r--manual/generic/android/bluetooth-ftp.yaml34
-rw-r--r--manual/generic/android/bluetooth-pair.yaml28
-rw-r--r--manual/generic/android/bluetooth-scan.yaml27
-rw-r--r--manual/generic/android/bluetooth-tethering.yaml27
-rw-r--r--manual/generic/android/browser-app.yaml28
-rw-r--r--manual/generic/android/device-tree.yaml28
-rw-r--r--manual/generic/android/display-blanking.yaml34
-rw-r--r--manual/generic/android/download-install-apk.yaml30
-rw-r--r--manual/generic/android/ds-5.yaml39
-rw-r--r--manual/generic/android/ethernet.yaml38
-rw-r--r--manual/generic/android/gallery-app.yaml30
-rw-r--r--manual/generic/android/google-hangouts.yaml34
-rw-r--r--manual/generic/android/hardware-graphics-acceleration.yaml29
-rw-r--r--manual/generic/android/hardware-video.yaml30
-rw-r--r--manual/generic/android/hwgfx.yaml113
-rw-r--r--manual/generic/android/installation-instructions.yaml24
-rw-r--r--manual/generic/android/large-wifi-file-transfer.yaml25
-rw-r--r--manual/generic/android/linaro-android-build-command.yaml38
-rw-r--r--manual/generic/android/linaro-kernel-build-command.yaml26
-rw-r--r--manual/generic/android/monkeyrunner-test.yaml36
-rw-r--r--manual/generic/android/open-accessory.yaml46
-rw-r--r--manual/generic/android/perf.yaml42
-rw-r--r--manual/generic/android/pm-qa.yaml159
-rw-r--r--manual/generic/android/powerdebug.yaml28
-rw-r--r--manual/generic/android/powertop.yaml32
-rw-r--r--manual/generic/android/pre-built.yaml33
-rw-r--r--manual/generic/android/primary-video-out-vga.yaml28
-rw-r--r--manual/generic/android/reboot.yaml27
-rw-r--r--manual/generic/android/sd-mmc.yaml28
-rw-r--r--manual/generic/android/secondary-video-output.yaml27
-rw-r--r--manual/generic/android/shutdown-console.yaml27
-rw-r--r--manual/generic/android/shutdown.yaml29
-rw-r--r--manual/generic/android/small-wifi-file-transfer.yaml25
-rw-r--r--manual/generic/android/toolchain-version.yaml27
-rw-r--r--manual/generic/android/usb-camera-record.yaml33
-rw-r--r--manual/generic/android/usb-camera.yaml31
-rw-r--r--manual/generic/android/usb-ethernet.yaml33
-rw-r--r--manual/generic/android/usb-host-keyboard.yaml27
-rw-r--r--manual/generic/android/usb-host-mouse.yaml28
-rw-r--r--manual/generic/android/usb-host-storage.yaml31
-rw-r--r--manual/generic/android/usb-tethering.yaml46
-rw-r--r--manual/generic/android/wifi.yaml31
-rw-r--r--manual/generic/android/youtube.yaml28
-rw-r--r--manual/generic/hdmi-audio.yaml35
-rw-r--r--manual/generic/hdmi-input-switch.yaml36
-rw-r--r--manual/generic/kernel-version.yaml32
-rw-r--r--manual/generic/linux/bluetooth-audio-ui.yaml31
-rw-r--r--manual/generic/linux/bluetooth-audio.yaml46
-rw-r--r--manual/generic/linux/bluetooth-file-transfer-ui.yaml29
-rw-r--r--manual/generic/linux/bluetooth-pair-ui.yaml29
-rw-r--r--manual/generic/linux/bluetooth-pair.yaml36
-rw-r--r--manual/generic/linux/bluetooth-scan-ui.yaml27
-rw-r--r--manual/generic/linux/bluetooth-scan.yaml29
-rw-r--r--manual/generic/linux/display-blanking.yaml28
-rw-r--r--manual/generic/linux/ds5-remote-debug.yaml26
-rw-r--r--manual/generic/linux/ds5-ssh.yaml25
-rw-r--r--manual/generic/linux/hdmi-resolution-switching-cmd.yaml31
-rw-r--r--manual/generic/linux/hdmi-resolution-switching.yaml32
-rw-r--r--manual/generic/linux/ip_forwarding.yaml49
-rw-r--r--manual/generic/linux/kvm-arm32-guest-on-arm64-host.yaml44
-rw-r--r--manual/generic/linux/kvm-arm64-guest-on-arm64-host.yaml47
-rw-r--r--manual/generic/linux/multi-nic-download.yaml34
-rw-r--r--manual/generic/linux/opengl-fps.yaml30
-rw-r--r--manual/generic/linux/power-off-cmd.yaml29
-rw-r--r--manual/generic/linux/power-off.yaml29
-rw-r--r--manual/generic/linux/reboot-ui.yaml29
-rw-r--r--manual/generic/linux/reboot.yaml28
-rw-r--r--manual/generic/linux/sd-mmc.yaml31
-rw-r--r--manual/generic/linux/sdcard-cold-boot.yaml44
-rw-r--r--manual/generic/linux/sdcard-hot-plug.yaml44
-rw-r--r--manual/generic/linux/secondary-video-out.yaml25
-rw-r--r--manual/generic/linux/usb-3.0-arndale5250.yaml121
-rw-r--r--manual/generic/linux/usb-camera.yaml34
-rw-r--r--manual/generic/linux/usb-ethernet.yaml33
-rw-r--r--manual/generic/linux/usb-keyboard.yaml30
-rw-r--r--manual/generic/linux/usb-storage.yaml76
-rw-r--r--manual/generic/linux/wifi-large-download.yaml24
-rw-r--r--manual/generic/linux/wifi-small-download.yaml24
-rw-r--r--manual/generic/linux/wifi-teminal.yaml31
-rw-r--r--manual/generic/linux/wifi.yaml27
-rw-r--r--manual/generic/primary-video-out-hdmi.yaml34
-rw-r--r--manual/generic/sdcard-speed-test.yaml37
-rw-r--r--manual/generic/serial-console.yaml41
-rw-r--r--manual/generic/usb-hid-device.yaml35
-rw-r--r--manual/generic/usb-storage.yaml36
-rw-r--r--manual/hikey/hikey-power-button.yaml30
-rw-r--r--manual/hikey/hikey-user-led.yaml30
102 files changed, 3581 insertions, 0 deletions
diff --git a/manual/dragon410c/dragon410c-user-led.yaml b/manual/dragon410c/dragon410c-user-led.yaml
new file mode 100644
index 0000000..cf9147d
--- /dev/null
+++ b/manual/dragon410c/dragon410c-user-led.yaml
@@ -0,0 +1,31 @@
+metadata:
+ name: dragon410c-user-led
+ format: "Manual Test Definition 1.0"
+ description: "Test if user LED working on Dragonboard 410c."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board successfuly.
+ - The four user LEDs on board are apq8016-sbc:green:user0, apq8016-sbc:green:user1, apq8016-sbc:green:user2 and apq8016-sbc:green:user3.
+ - To turn on specific LED, run "echo 1 > /sys/class/leds/<led_dir>/brightness"
+ - To turn off specific LED, run "echo 0 > /sys/class/leds/<led_dir>/brightness"
+ - Run "cat /sys/class/leds/<led_dir>/trigger" to show all the triggers available for a particular LED.
+ - To assign a trigger to any LED, run "echo trigger_name > /sys/class/leds/<led_dir>/trigger"
+ - example: to assign "heartbeat" trigger to apq8016-sbc:green:user3
+ - run "echo heartbeat > /sys/class/leds/apq8016-sbc\:green\:user3/trigger"
+ - To remove trigger for any LED, run "echo none > /sys/class/leds/<led_dir>/trigger"
+
+ expected:
+ - LEDs can be turned on and off.
+ - Triggers can be assigned/removed to/from any LEDs.
diff --git a/manual/generic/96boards/hikey-bluetooth-status-led.yaml b/manual/generic/96boards/hikey-bluetooth-status-led.yaml
new file mode 100644
index 0000000..67dfc33
--- /dev/null
+++ b/manual/generic/96boards/hikey-bluetooth-status-led.yaml
@@ -0,0 +1,24 @@
+metadata:
+ name: hikey-bluetooth-status-led
+ format: "Manual Test Definition 1.0"
+ description: "Test if staus LED working on Hikey board."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board successfuly to UI.
+ - Connect the board to another BT device.
+ - Stream music or transfer files from board to the connected device.
+
+ expected:
+ - Blue BT light blinks on the board while streaming music or transfering files.
diff --git a/manual/generic/96boards/hikey-wifi-status-led.yaml b/manual/generic/96boards/hikey-wifi-status-led.yaml
new file mode 100644
index 0000000..4423df8
--- /dev/null
+++ b/manual/generic/96boards/hikey-wifi-status-led.yaml
@@ -0,0 +1,24 @@
+metadata:
+ name: hikey-wifi-status-led
+ format: "Manual Test Definition 1.0"
+ description: "Test if WiFi staus LED working on Hikey board."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board successfuly to UI.
+ - Connect the board to available WiFi.
+ - Tansfer files to another device or open browser and download small file from "http://samplemedia.linaro.org/"
+
+ expected:
+ - Yellow WiFi light blinks on the board while transfering files or downloading.
diff --git a/manual/generic/96boards/status-led-bluetooth.yaml b/manual/generic/96boards/status-led-bluetooth.yaml
new file mode 100644
index 0000000..cab7ba3
--- /dev/null
+++ b/manual/generic/96boards/status-led-bluetooth.yaml
@@ -0,0 +1,25 @@
+metadata:
+ name: status-led-bluetooth
+ format: "Manual Test Definition 1.0"
+ description: "Test if BT status LED works on 96board."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board successfuly to UI.
+ - Connect the board to another BT device.
+ - Stream music or transfer files from board to the connected device.
+
+ expected:
+ - Blue BT light blinks on the board while streaming music or transfering files.
diff --git a/manual/generic/96boards/status-led-wifi.yaml b/manual/generic/96boards/status-led-wifi.yaml
new file mode 100644
index 0000000..dc43ebc
--- /dev/null
+++ b/manual/generic/96boards/status-led-wifi.yaml
@@ -0,0 +1,25 @@
+metadata:
+ name: status-led-wifi
+ format: "Manual Test Definition 1.0"
+ description: "Test if WiFi staus LED works on 96board."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board successfuly to UI.
+ - Connect the board to available WiFi.
+ - Tansfer files to another device or open browser and download small file from "http://samplemedia.linaro.org/"
+
+ expected:
+ - Yellow WiFi light blinks on the board while transfering files or downloading.
diff --git a/manual/generic/android/adb-over-ethernet.yaml b/manual/generic/android/adb-over-ethernet.yaml
new file mode 100644
index 0000000..7bfb07c
--- /dev/null
+++ b/manual/generic/android/adb-over-ethernet.yaml
@@ -0,0 +1,37 @@
+metadata:
+ name: andriod-adb-over-ethernet
+ format: "Manual Test Definition 1.0"
+ description: "Test if ADB over ethernet works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Configure ADB over Ethernet by follow the instruction on the below webpage:
+ https://wiki.linaro.org/Platform/Android/SetupAdbOverTcp"
+ - "Run following commands(Replace the content in <> to yours):
+ $ sudo adb shell
+ $ ls
+ $ exit
+ $ sudo adb push <file_on_host_pc> /sdcard
+ $ sudo adb pull /sdcard/<file_on_host_pc> ./
+ $ sudo adb install <apk_file_on_host_pc>"
+
+ expected:
+ - "ADB shell should be launched successfully, output of \"ls\" should look good"
+ - "ADB push, pull and install should work well"
+ - "After apk installation, the app icon should be found on UI and should be launched successfully"
+ - "No hang, kernel panic or crash observed during the whole process"
+
diff --git a/manual/generic/android/adb-over-usb.yaml b/manual/generic/android/adb-over-usb.yaml
new file mode 100644
index 0000000..4b2aba8
--- /dev/null
+++ b/manual/generic/android/adb-over-usb.yaml
@@ -0,0 +1,39 @@
+metadata:
+ name: andriod-adb-over-usb
+ format: "Manual Test Definition 1.0"
+ description: "Test if ADB over USB works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Follow the instructions on the following webpages to configure ADB on host PC:
+ https://wiki.linaro.org/Platform/Android/ConfigureAndUseAdb,
+ http://developer.android.com/tools/help/adb.html"
+ - "Run following commands(Replace the content in <> to yours):
+ $ sudo adb shell
+ $ ls
+ $ exit
+ $ sudo adb push <file_on_host_pc> /sdcard
+ $ sudo adb pull /sdcard/<file_on_host_pc> ./
+ $ sudo adb install <apk_file_on_host_pc>"
+
+ expected:
+ - "ADB shell should be launched successfully and output of 'ls' command should look good."
+ - "ADB push, pull and install should work well."
+ - "After apk installation, the app icon should be found on UI and should be launched successfully."
+ - "No hang, kernel panic or crash observed during the whole process."
+
diff --git a/manual/generic/android/android-hardware-usb.yaml b/manual/generic/android/android-hardware-usb.yaml
new file mode 100644
index 0000000..95f3860
--- /dev/null
+++ b/manual/generic/android/android-hardware-usb.yaml
@@ -0,0 +1,33 @@
+metadata:
+ name: android-hardware-usb
+ format: "Manual Test Definition 1.0"
+ description: "Android hardware USB test"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen"
+ - "On host PC, in terminal, run:
+ # lava-android-test install usbhardware
+ # lava-android-test run usbhardware"
+ - "Power OFF and power on the board again to boot into Android main screen"
+ - "In serial console, run:
+ # cat /sys/class/android_usb/android0/state"
+ - "Check the return value"
+
+ expected:
+ - "LAVA Test should pass"
+ - "If the return value is \"DISCONNECTED\", then it means test failed; if the return value is \"CONFIGURED\", it means test passed"
diff --git a/manual/generic/android/android-input-method-service.yaml b/manual/generic/android/android-input-method-service.yaml
new file mode 100644
index 0000000..cc953ac
--- /dev/null
+++ b/manual/generic/android/android-input-method-service.yaml
@@ -0,0 +1,32 @@
+metadata:
+ name: android-input-method-service
+ format: "Manual Test Definition 1.0"
+ description: "Test if Android input method service works"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen"
+ - "On host PC, in terminal, run:
+ # lava-android-test install ime
+ # lava-android-test run ime"
+ - "Power OFF and power ON the board again to boot into Android main screen"
+ - "In serial console, run:
+ # /system/bin/ime list -a"
+
+ expected:
+ - "LAVA test should pass"
+ - "Input method service should be shown in output of command \"/system/bin/ime list -a\""
diff --git a/manual/generic/android/android-ui-auto-mount.yaml b/manual/generic/android/android-ui-auto-mount.yaml
new file mode 100644
index 0000000..2eca680
--- /dev/null
+++ b/manual/generic/android/android-ui-auto-mount.yaml
@@ -0,0 +1,29 @@
+metadata:
+ name: android-ui-auto-mount
+ format: "Manual Test Definition 1.0"
+ description: "Test if SD card can mounted automatically."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - apq8016-sbc
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board.
+ - Insert SD card in SD card slot on the board.
+ - From Android UI, got to Settings--> Storage&USB.
+ - Storage&USB has two options "Internal Storage" & "Portable Storage".
+ - Click on "Internal Storage" and it will show memory usage. Click on "Explore" at the bottom.
+ - Under "Portable Storage", The SD card will already be mounted. Click on it to unmount.
+ - Mount and unmount SD card couple of times.
+
+ expected:
+ - Clicking on settings--> storage&usb--> Internal storage--> Explore works fine and no crash is observed.
+ - SD card is auto mounted and can be unmounted and re-mounted from UI.
diff --git a/manual/generic/android/android-version.yaml b/manual/generic/android/android-version.yaml
new file mode 100644
index 0000000..f3d0591
--- /dev/null
+++ b/manual/generic/android/android-version.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: android-android-version
+ format: "Manual Test Definition 1.0"
+ description: "Test if the kernel version is correct"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "From UI application goto Settings"
+ - "Select 'About tablet' feature from the last options of settings"
+ - "Check Android version"
+
+ expected:
+ - "Validate the Android version matches the current tag version"
+
diff --git a/manual/generic/android/angrybirds.yaml b/manual/generic/android/angrybirds.yaml
new file mode 100644
index 0000000..5b66a56
--- /dev/null
+++ b/manual/generic/android/angrybirds.yaml
@@ -0,0 +1,31 @@
+metadata:
+ name: andriod-angrybirds
+ format: "Manual Test Definition 1.0"
+ description: "Test if Angry Birds App works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Download Angry Birds installation APK file from Internet"
+ - "Install the APK file via ADB:
+ $ sudo adb install angrybirds.apk"
+ - "After Angry Birds icon shows on screen, click it to launch the game"
+ - "Play this game for several minutes"
+
+ expected:
+ - "Angry Birds can be launched successfully"
+ - "The game should work well, both video and audio should can be played smoothly"
+ - "No freezing, kernel panic or crash observed during the game"
diff --git a/manual/generic/android/arm-browser-benchmark.yaml b/manual/generic/android/arm-browser-benchmark.yaml
new file mode 100644
index 0000000..82ffe84
--- /dev/null
+++ b/manual/generic/android/arm-browser-benchmark.yaml
@@ -0,0 +1,44 @@
+metadata:
+ name: andriod-arm-browser-benchmark
+ format: "Manual Test Definition 1.0"
+ description: "ARM browser benchmark test"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen"
+ - "Ensure there is at least one active network connection on the board"
+ - "On host PC, ensure \"lava-android-test\" exists with the latest version"
+ - "Assume host PC IP address is 192.168.1.10"
+ - "On host PC, in terminal, run:
+ /* Install methanol test on target board*/
+ $ lava-android-test install methanol -s <dev_serial_no>
+ /* Run fire.html on stock browser */
+ $ lava-android-test run methanol -O \"-b DEFAULT -d 192.168.1.10\" -O result.json -s <dev_serial_no>
+ /* Run fire-svg.html on stock browser */
+ $ lava-android-test run methanol -O \"-t svg -b DEFAULT -d 192.168.1.10\" -O result.json -s <dev_serial_no>
+ /* Run fire-smp.html on stock browser */
+ $ lava-android-test run methanol -O \"-t smp -b DEFAULT -d 192.168.1.10\" -O result.json -s <dev_serial_no>
+ /* Run fire.html on chrome browser */
+ $ lava-android-test run methanol -O \"-b CHROME -d 192.168.1.10\" -O result.json -s <dev_serial_no>
+ /* Run fire-svg.html on chrome browser */
+ $ lava-android-test run methanol -O \"-t svg -b CHROME -d 192.168.1.10\" -O result.json -s <dev_serial_no>
+ /* Run fire-smp.html on chrome browser */
+ $ lava-android-test run methanol -O \"-t smp -b CHROME -d 192.168.1.10\" -O result.json -s <dev_serial_no>"
+
+ expected:
+ - "Test can be triggered and performed successfully"
+ - "The benchmark tools runs successfully and collect the profiling data"
diff --git a/manual/generic/android/audio-jack.yaml b/manual/generic/android/audio-jack.yaml
new file mode 100644
index 0000000..53fa1b4
--- /dev/null
+++ b/manual/generic/android/audio-jack.yaml
@@ -0,0 +1,32 @@
+metadata:
+ name: andriod-audio-jack
+ format: "Manual Test Definition 1.0"
+ description: "Test if audio through jack port works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "After the board booted up successfully, plug in the headset and microphone"
+ - "Open browser and click a \"YouTube\" clip to listen the sound from headset"
+ - "Install \"Angry Birds\" and start to play the game, listen the sound from headset"
+ - "Click \"Messaging -> New Message -> Attach -> Record Audio\""
+ - "Play the recorded audio clip"
+
+ expected:
+ - "Sounds from YouTube clips and \"Angry Birds\" game should be heard clearly"
+ - "Sound record should be done successfully and should be heard clearly as original"
+ - "No hang, kernel panic and crash during the whole test process"
+
diff --git a/manual/generic/android/bluetooth-audio.yaml b/manual/generic/android/bluetooth-audio.yaml
new file mode 100644
index 0000000..8d22a2e
--- /dev/null
+++ b/manual/generic/android/bluetooth-audio.yaml
@@ -0,0 +1,25 @@
+metadata:
+ name: android-bluetooth-audio
+ format: "Manual Test Definition 1.0"
+ description: "Test if Bluetooth audio works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Power on Bluetooth audio device (A2DP supported) and set it as "discoverable".
+ - Power on the board, after it booted successfully, turn on the Bluetooth from UI.
+ - Pair the board and Bluetooth audio device and set it as the audio output device.
+ - Play a music file from the board.
+
+ expected:
+ - "The Bluetooth audio device should can be paired with the board successfully."
+ - "The music file can be played successfully, and the sound can be heard from Bluetooth audio device smoothly."
diff --git a/manual/generic/android/bluetooth-ftp.yaml b/manual/generic/android/bluetooth-ftp.yaml
new file mode 100644
index 0000000..5bfbc7a
--- /dev/null
+++ b/manual/generic/android/bluetooth-ftp.yaml
@@ -0,0 +1,34 @@
+metadata:
+ name: android-bluetooth-ftp
+ format: "Manual Test Definition 1.0"
+ description: "Test if Bluetooth file transfer works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - After the board booted successfully, enable Bluetooth by click Settings -> Wireless and Networks -> Bluetooth.
+ - After Bluetooth turned ON and surround devices (if any) showed up, turn Bluetooth OFF.
+ - Perform above ON and OFF procedures again.
+ - Make sure BT enabled device (mobile phone, laptop) is in the radio range and in discovery mode
+ - Pair the nearby device (enter PIN if needed)
+ - Send a picture from the board to another Bluetooth device (mobile phone or laptop).
+ - Send another picture from supporting device to the board under test.
+ - View the picture on both devices.
+ expected:
+ - Bluetooth feature should can be continuously enabled and disabled at least twice without any error
+ - Nearby devices should be shown in the discoveried device list on the board
+ - Pairing should be done successfully
+ - Picture file should can be transfered from the board to another paired Bluetooth device
+ - Picture file should can be transfered from another Bluetooth enabled device to the board under test
+ - Picture file should be displayed successfully on both paired devices
diff --git a/manual/generic/android/bluetooth-pair.yaml b/manual/generic/android/bluetooth-pair.yaml
new file mode 100644
index 0000000..9be8aca
--- /dev/null
+++ b/manual/generic/android/bluetooth-pair.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: android-bluetooth-pair
+ format: "Manual Test Definition 1.0"
+ description: "Test if Bluetooth pairing works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - After the board booted successfully, enable Bluetooth by click Settings -> Wireless and Networks -> Bluetooth.
+ - After Bluetooth turned ON and surround devices (if any) showed up, turn Bluetooth OFF.
+ - Perform above ON and OFF procedures again.
+ - Make sure BT enabled device is in the radio range and in discovery mode
+ - Pair the nearby device (enter PIN if needed)
+ expected:
+ - Bluetooth feature should can be continuously enabled and disabled at least twice without any error
+ - Nearby devices should be shown in the discoveried device list on the board
+ - Pairing should be done successfully
diff --git a/manual/generic/android/bluetooth-scan.yaml b/manual/generic/android/bluetooth-scan.yaml
new file mode 100644
index 0000000..fd254c5
--- /dev/null
+++ b/manual/generic/android/bluetooth-scan.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: android-bluetooth-scan
+ format: "Manual Test Definition 1.0"
+ description: "Test if Bluetooth scanning works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - After the board booted successfully, enable Bluetooth by click Settings -> Wireless and Networks -> Bluetooth.
+ - After Bluetooth turned ON and surround devices (if any) showed up, turn Bluetooth OFF.
+ - Perform above ON and OFF procedures again.
+ - Make sure BT enabled device is in the radio range and in discovery mode
+ - Enable BT on device under test and wait for updating the list of nearby devices
+ expected:
+ - Bluetooth feature should can be continuously enabled and disabled at least twice without any error
+ - Nearby devices should be shown in the discoveried device list on the board
diff --git a/manual/generic/android/bluetooth-tethering.yaml b/manual/generic/android/bluetooth-tethering.yaml
new file mode 100644
index 0000000..9c8e0c8
--- /dev/null
+++ b/manual/generic/android/bluetooth-tethering.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: andriod-bluetooth-tethering
+ format: "Manual Test Definition 1.0"
+ description: "Test if Bluetooth tethering works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Select another Android device as device B and the target Android device A (Samsung Galaxy Nexus)"
+ - "Remove SIM card on device A, power on both devices until boot up succeeded"
+ - "Ensure device B can access Internet successfully (launch Browser to test it), turn on Bluetooth, then go to Settings->More->Portable hotspot & tethering->enable Bluetooth tethering"
+ - "On Device A, disconnect WiFi, also disable \"Data enabled\" from Settings -> More -> Mobile networks"
+ - "Turn on Bluetooth on Device A and pair with Device B"
+ - "After pairing successfully, launch Browser on device A to access Internet"
+
+ expected:
+ - "Device A should can access Internet successfully via device B"
diff --git a/manual/generic/android/browser-app.yaml b/manual/generic/android/browser-app.yaml
new file mode 100644
index 0000000..953560b
--- /dev/null
+++ b/manual/generic/android/browser-app.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-browser-app
+ format: "Manual Test Definition 1.0"
+ description: "Test if Browser App works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Browser app should be available and shown after the board booted successfully"
+ - "Launch Browser app"
+ - "Type \"www.google.com\" in address bar and press \"Enter\" key"
+
+ expected:
+ - "Browser app should can be launched successfully"
+ - "Google main page should be shown successfully"
diff --git a/manual/generic/android/device-tree.yaml b/manual/generic/android/device-tree.yaml
new file mode 100644
index 0000000..d80c195
--- /dev/null
+++ b/manual/generic/android/device-tree.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-device-tree
+ format: "Manual Test Definition 1.0"
+ description: "Device tree test"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board until boot succeeded"
+ - "In serial console, run:
+ # cat /proc/device-tree/model"
+
+ expected:
+ - "The string \"Flattened Device Tree blob\" should be shown in boot log"
+ - "Board model name should be shown after the command ran"
diff --git a/manual/generic/android/display-blanking.yaml b/manual/generic/android/display-blanking.yaml
new file mode 100644
index 0000000..4496411
--- /dev/null
+++ b/manual/generic/android/display-blanking.yaml
@@ -0,0 +1,34 @@
+metadata:
+ name: display-blanking
+ format: "Manual Test Definition 1.0"
+ description: "Test display blanking."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - juno
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board with android and meake sure mouse and/or keyboard is connected.
+ - Go to "settings->About phone" and click 3 times on "build Number" to activate "Developer options".
+ - Go to "settings->developer options->stay awake" and disable it.
+ - Go to "settings->Display" and select minimum time(usually 15 sec).
+ - Wait till display goes blank.
+ - Move connected mouse or press any key on keyboard to get the display back.
+
+ expected:
+ - Diplay blanking and un-blanking works well.
+ - No Kernel panic, crash, hang or any other severe error observed when display is back.
diff --git a/manual/generic/android/download-install-apk.yaml b/manual/generic/android/download-install-apk.yaml
new file mode 100644
index 0000000..8783e88
--- /dev/null
+++ b/manual/generic/android/download-install-apk.yaml
@@ -0,0 +1,30 @@
+metadata:
+ name: andriod-download-install-apk
+ format: "Manual Test Definition 1.0"
+ description: "Test if APK can be downloaded and installed successfully"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen, ensure there is at least one active network connection, Ethernet or WiFi"
+ - "Launch browser, visit http://www.whatsapp.com/android/"
+ - "Click \"Download Now\" button"
+ - "After the APK downloaded successfully, click Settings -> Security, then enable the \"Unknown Sources\""
+ - "Click \"Downloads\" app, find that APK file, then click it"
+
+ expected:
+ - "The APK file should can be downloaded successfully and shown in \"Downloads\" app"
+ - "The APK file should can be installed successfully after click it in in \"Downloads\" app"
diff --git a/manual/generic/android/ds-5.yaml b/manual/generic/android/ds-5.yaml
new file mode 100644
index 0000000..e83584d
--- /dev/null
+++ b/manual/generic/android/ds-5.yaml
@@ -0,0 +1,39 @@
+metadata:
+ name: andriod-ds-5
+ format: "Manual Test Definition 1.0"
+ description: "DS-5 gatord test"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Install ARM DS-5 on host PC"
+ - "Power on the board until it booted successfully"
+ - "In serial console, run:
+ # lsmod
+ # ps | busybox grep gatord"
+ - "Check the Ethernet or wireless connection, ensure the board can get IP address"
+ - "On host PC, launch ARM DS-5 by run (Replace \"ds5_installation_path\" to yours):
+ $ cd /ds5_installation_path/bin
+ $ ./eclipse"
+ - "After set up work space, then on eclipse main screen, from menu bar, click Window -> Show View -> Other"
+ - "Then click DS-5 -> Streamline Data -> OK"
+ - "Put the board IP address in \"Address\" filed, click \"Start Capture\""
+ - "Let the data capture running for 10 seconds, then click \"Stop\""
+
+ expected:
+ - "\"gator\" should be shown in output of \"lsmod\""
+ - "\"gatord\" should be shown in output of \"ps | busybox grep gatord\""
+ - "After clicked \"Stop\", a statistics data graph should be shown"
diff --git a/manual/generic/android/ethernet.yaml b/manual/generic/android/ethernet.yaml
new file mode 100644
index 0000000..863187b
--- /dev/null
+++ b/manual/generic/android/ethernet.yaml
@@ -0,0 +1,38 @@
+metadata:
+ name: andriod-ethernet
+ format: "Manual Test Definition 1.0"
+ description: "Test if ethernet can be configured and works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Manually Configuration: Device IP: 192.168.1.7; Router (Gateway) IP: 192.168.1.1; Google DNS Server: 8.8.8.8"
+ - "After the board booted successfully, in serial console, run:
+ # busybox ifconfig eth0 192.168.1.7 netmask 255.255.255.0 up
+ # route add default gw 192.168.1.1 dev eth0
+ # setprop net.dns1 192.168.1.1
+ # setprop net.dns2 8.8.8.8
+ # setprop net.eth0.dns1 192.168.1.1
+ # setprop net.eth0.dns2 8.8.8.8
+ # busybox ping www.google.com"
+ - "Power OFF and Power ON the board again"
+ - "After the board booted successfully, enable the Ethernet (if it is not enabled) in network manager, then back to serial console and run:
+ # busybox ifconfig -a
+ # busybox ping www.google.com"
+
+ expected:
+ - "IP address should be assigned successfully"
+ - "No data loss in ping test"
diff --git a/manual/generic/android/gallery-app.yaml b/manual/generic/android/gallery-app.yaml
new file mode 100644
index 0000000..4d19bb8
--- /dev/null
+++ b/manual/generic/android/gallery-app.yaml
@@ -0,0 +1,30 @@
+metadata:
+ name: andriod-gallery-app
+ format: "Manual Test Definition 1.0"
+ description: "Test if Gallery App works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Put some pictures and videos to SD card then boot the board"
+ - "Gallery app should be available and shown after the board booted successfully"
+ - "Launch Gallery app, and click some pictures and videos"
+
+ expected:
+ - "Gallery app should can be launched successfully"
+ - "The thumbnails of pictures and videos should be available"
+ - "Pictures should can be shown full size successfully after click it"
+ - "Video can be played successfully after click it"
diff --git a/manual/generic/android/google-hangouts.yaml b/manual/generic/android/google-hangouts.yaml
new file mode 100644
index 0000000..12e2f3f
--- /dev/null
+++ b/manual/generic/android/google-hangouts.yaml
@@ -0,0 +1,34 @@
+metadata:
+ name: andriod-google-hangouts
+ format: "Manual Test Definition 1.0"
+ description: "Test if Google Hangouts works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen"
+ - "\"Google+\" or \"Hangouts\" app should be pre-installed"
+ - "Ensure there is at least one active network on the board"
+ - "Login with \"test01\" Gmail account on the board"
+ - "Login with \"test02\" Gmail account on host PC"
+ - "From host PC, start a Google Hangout session and invite \"test01\""
+ - "After a notification shows on the board, click it to join in the Hangout session"
+ - "Check the audio and video on both host PC and board"
+
+ expected:
+ - "\"Google+\" or \"Hangouts\" app should exist"
+ - "The board can join in the Hangout session successfully"
+ - "Audio and video work well during the Hangout session"
diff --git a/manual/generic/android/hardware-graphics-acceleration.yaml b/manual/generic/android/hardware-graphics-acceleration.yaml
new file mode 100644
index 0000000..a7cfe10
--- /dev/null
+++ b/manual/generic/android/hardware-graphics-acceleration.yaml
@@ -0,0 +1,29 @@
+metadata:
+ name: hardware-graphics-acceleration
+ format: "Manual Test Definition 1.0"
+ description: "Test if hardware graphics acceleration is enabled."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - apq8016-sbc
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board.
+ - Setup ADB on host machine.
+ - Details to configure ADB "https://git.linaro.org/qa/manual-test-definitions.git/blob/HEAD:/generic/android/adb-over-usb.yaml"
+ - Download "http://testdata.validation.linaro.org/tools/hwgfx.apk"
+ - Run "adb install hwgfx.apk".
+ - Open hwgfx application on board via UI."
+ - Touch Linaro logo in the app to check if hardware graphics acceleration is enabled.
+
+ expected:
+ - hwgfx.apk is installed successfully on the board.
+ - APK is launched and gives either "True" or "False" after touching linaro logo.
diff --git a/manual/generic/android/hardware-video.yaml b/manual/generic/android/hardware-video.yaml
new file mode 100644
index 0000000..23da12a
--- /dev/null
+++ b/manual/generic/android/hardware-video.yaml
@@ -0,0 +1,30 @@
+metadata:
+ name: andriod-hardware-video
+ format: "Manual Test Definition 1.0"
+ description: "Test if hardware accelerated video works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Download \"big_buck_bunny_480p_H264_AAC_25fps_1800K.MP4\" video file from the below link and transfer it to SD card:
+ http://samplemedia.linaro.org/H264/big_buck_bunny_480p_H264_AAC_25fps_1800K.MP4"
+ - "Download \"big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4\" video file from the below link and transfer it to SD card:
+ http://samplemedia.linaro.org/H264/big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4"
+ - "After the board booted successfully, launch \"Gallery\" app to play above two video clips"
+
+ expected:
+ - "480p video should be played successfully with good quality"
+ - "1080p video should be played successfully with good quality"
diff --git a/manual/generic/android/hwgfx.yaml b/manual/generic/android/hwgfx.yaml
new file mode 100644
index 0000000..dddf84f
--- /dev/null
+++ b/manual/generic/android/hwgfx.yaml
@@ -0,0 +1,113 @@
+metadata:
+ name: andriod-hwgfx
+ format: "Manual Test Definition 1.0"
+ description: "Test hardware accelerated 3D support"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "After the board booted up successfully, click \"0xbenchmark\" to run the graphic test suites"
+ - "For STE Snowball board, run:
+ # dmesg > /sdcard/snowball_dmesg.txt 2>&1 &
+ # logcat > /sdcard/snowball_logcat.txt 2>&1 &"
+ - "For TI Panda 4430 and 4460, install hardware acceleration by following the instructions on Linaro Android Build Service page first, and then run the below command in serial console
+ # logcat > /sdcard/ti_panda_logcat.txt 2>&1 &"
+ - "For old Samsung Origen board, in serial console, run
+ # logcat > /sdcard/old_samsung_origen_logcat.txt 2>&1 &"
+
+ expected:
+ - "Graphic test in \"0xbenchmark\" should look smoothly without any characteristic tearing"
+ - "For STE Snowball board, the output similarly likes this should be observed in file \"/sdcard/snowball_dmesg.txt\":
+ [ 1.781585] Mali<2>: Inserting Mali v9 device driver.
+ [ 1.786712] Mali<2>: Compiled: Dec 19 2011, time: 07:16:47.
+ [ 1.792327] Mali<2>: Svn revision:
+ [ 1.795806] Mali<2>: MMU memory system initializing
+ [ 1.800689] Mali<2>: Rendercore: subsystem global mutex initialized
+ [ 1.806945] Mali<2>: Core: subsystem_init: Mali-400 PP
+ [ 1.812103] Mali<2>: Core: subsystem_init: Mali-400 GP
+ [ 1.817230] Mali<2>: Mali L2 cache system initializing
+ [ 1.822387] Mali<1>: Overriding arch resource[4] :
+ [ 1.827178] Mali<1>: Type: MEMORY, base: 8000000, size 2000000
+ [ 1.833251] Mali<2>: MMU registered
+ [ 1.836761] Mali<2>: MMU registered
+ [ 1.840270] Mali<2>: Mali OS memory allocator created with max allocation size of 0x7FF00000 bytes, cpu_usage_adjust 0x00000000
+ [ 1.851776] Mali<2>: Memory Validator 'Framebuffer' installed for Mali physical address base==0x00000000, size==0x7FF00000, cpu_adjust==0x00000000
+ [ 1.864959] Mali<2>: Creating Mali L2 cache: Mali-400 L2 cache
+ [ 1.870880] Mali<1>: Mali memory allocators will be used in this order of preference (lowest numbered first) :
+ [ 1.880889] Mali<1>: 0: Mali SDRAM
+ [ 1.884399] Mali<1>: 5: Linux kernel memory
+ [ 1.888916] Mali<2>: Attach mmu: 0xe6df72c0 to core: Mali-400 PP in subsystem: Mali-400 PP
+ [ 1.897216] Mali<2>: Attach mmu: 0xe6df7320 to core: Mali-400 GP in subsystem: Mali-400 GP
+ [ 1.905487] Mali<2>: Mali L2 cache system load complete
+ [ 1.910705] Mali: Mali device driver loaded
+ [ 1.915008] Mali<2>: malidrv: CONFIG=ux500 USING_OS_MEMORY=1 API_VERSION=9 REPO_URL= REVISION= CHANGED_REVISION= CHANGE_DATE= BUILD_DATE=Mon Dec 19 07:16:46 UTC 2011 BUILD=DEBUG CPU=ux500 USING_UMP=1 USING_HWMEM=1 USING_PMM=1 USING_MALI200=0 USING_MALI400=3 USING_MALI400_L2_CACHE=1 USING_GP2=0 KDIR= MALI_PLATFORM_FILE=platform/ux500/mali_platform.c OS_MEMORY_KERNEL_BUFFER_SIZE_IN_MB=6 USING_PROFILING=0 USING_GPU_UTILIZATION=1 USING_MALI_RUN_TIME_PM=1"
+ - "For STE Snowball board, the output similarly likes this should be observed in file \"snowball_logcat.txt\":
+ D/libEGL ( 1595): loaded /system/lib/egl/libGLES_android.so
+ D/libEGL ( 1595): loaded /system/lib/egl/libEGL_mali.so
+ D/libEGL ( 1595): loaded /system/lib/egl/libGLESv1_CM_mali.so
+ [ 142.400238] Mali<2>: D/libEGL ( 1595): loaded /system/lib/egl/libGLESv2_mali.soMMU session begin
+ [ 142.414825] Mali<2>: Page directory for session 0xe510b680 placed at physical address 0x09FC8000
+ [ 142.424072] Mali<2>: MMU session begin: success
+ [ 142.429168] Mali<2>: Core: session_begin: for Mali-400 PP
+ [ 142.434600] Mali<2>: Core: session_begin: for Mali-400 GP
+ I/Mali-EGL( 1595): Mali libraries compiled on Dec 8 2011, at 09:40:03
+ D/OpenGLRenderer( 1595): Enabling debug mode 0"
+ - "For TI Panda 4430 and 4460, the output similarly likes this should be observed in file \"/sdcard/ti_panda_logcat.txt\":
+ D/libEGL ( 1334): loaded /system/lib/egl/libGLES_android.so
+ D/libEGL ( 1334): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
+ D/libEGL ( 1334): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
+ D/libEGL ( 1334): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
+ W/SurfaceFlinger( 1334): ro.sf.lcd_density not defined, using 160 dpi by default.
+ I/SurfaceFlinger( 1334): EGL informations:
+ I/SurfaceFlinger( 1334): # of configs : 33
+ I/SurfaceFlinger( 1334): vendor : Android
+ I/SurfaceFlinger( 1334): version : 1.4 Android META-EGL
+ I/SurfaceFlinger( 1334): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer EGL_ANDROID_image_native_buffer
+ I/SurfaceFlinger( 1334): Client API: OpenGL ES
+ I/SurfaceFlinger( 1334): EGLSurface: 8-8-8-8, config=0x1
+ I/SurfaceFlinger( 1334): OpenGL informations:
+ I/SurfaceFlinger( 1334): vendor : Imagination Technologies
+ I/SurfaceFlinger( 1334): renderer : PowerVR SGX 540
+ I/SurfaceFlinger( 1334): version : OpenGL ES-CM 1.1 build 1.8@550175
+ I/SurfaceFlinger( 1334): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_sprite GL_OES_point_size_array GL_OES_matrix_palette GL_OES_draw_texture GL_OES_query_matrix GL_OES_texture_env_crossbar GL_OES_texture_mirrored_repeat GL_OES_texture_cube_map GL_OES_blend_subtract GL_OES_blend_func_separate GL_OES_blend_equation_separate GL_OES_stencil_wrap GL_OES_extended_matrix_palette GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_depth24 GL_OES_stencil8 GL_OES_compressed_ETC1_RGB8_texture GL_OES_mapbuffer GL_OES_EGL_image GL_OES_EGL_image_external GL_EXT_multi_draw_arrays GL_OES_required_internalformat GL_IMG_read_format GL_IMG_texture_compression_pvrtc GL_IMG_texture_format_BGRA8888 GL_EXT_texture_format_BGRA8888 GL_OES_egl_sync GL_IMG_vertex_array_object
+ I/SurfaceFlinger( 1334): GL_MAX_TEXTURE_SIZE = 2048
+ I/SurfaceFlinger( 1334): GL_MAX_VIEWPORT_DIMS = 2048 x 2048
+ I/SurfaceFlinger( 1334): flags = 00010000"
+ - "For old Samsung Origen board, the output similarly likes this should be observed in file \"/sdcard/old_samsung_origen_logcat.txt\":
+ Mali: Mali: Mali device driver loaded
+ Mali device driver loaded
+ D/libEGL ( 2094): loaded /system/lib/egl/libGLES_android.so
+ D/libEGL ( 2094): loaded /system/lib/egl/libEGL_mali.so
+ D/libEGL ( 2094): loaded /system/lib/egl/libGLESv1_CM_mali.so
+ D/libEGL ( 2094): loaded /system/lib/egl/libGLESv2_mali.so
+ W/SurfaceFlinger( 2094): ro.sf.lcd_density not defined, using 160 dpi by default.
+ E/libEGL ( 2094): eglSetSwapRectangleANDROID:1460 error 3008 (EGL_BAD_DISPLAY)
+ I/SurfaceFlinger( 2094): EGL informations:
+ I/SurfaceFlinger( 2094): # of configs : 28
+ I/SurfaceFlinger( 2094): vendor : Android
+ I/SurfaceFlinger( 2094): version : 1.4 Android META-EGL
+ I/SurfaceFlinger( 2094): extensions: EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer EGL_ANDROID_swap_rectangle EGL_NV_system_time
+ I/SurfaceFlinger( 2094): Client API: OpenGL ES
+ I/SurfaceFlinger( 2094): EGLSurface: 8-8-8-8, config=0x13
+ I/SurfaceFlinger( 2094): OpenGL informations:
+ I/SurfaceFlinger( 2094): vendor : ARM
+ I/SurfaceFlinger( 2094): renderer : Mali-400 MP
+ I/SurfaceFlinger( 2094): version : OpenGL ES-CM 1.1
+ I/SurfaceFlinger( 2094): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_size_array GL_OES_point_sprite GL_OES_texture_npot GL_OES_query_matrix GL_OES_matrix_palette GL_OES_extended_matrix_palette GL_OES_compressed_ETC1_RGB8_texture GL_OES_EGL_image GL_OES_draw_texture GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_framebuffer_object GL_OES_stencil8 GL_OES_depth24 G
+ L_ARM_rgba8 GL_OES_EGL_image_external GL_OES_EGL_sync
+ I/SurfaceFlinger( 2094): GL_MAX_TEXTURE_SIZE = 4096
+ I/SurfaceFlinger( 2094): GL_MAX_VIEWPORT_DIMS = 4096 x 4096
+ I/SurfaceFlinger( 2094): flags = 00000000"
diff --git a/manual/generic/android/installation-instructions.yaml b/manual/generic/android/installation-instructions.yaml
new file mode 100644
index 0000000..7a7e19c
--- /dev/null
+++ b/manual/generic/android/installation-instructions.yaml
@@ -0,0 +1,24 @@
+metadata:
+ name: installation-instructions
+ format: "Manual Test Definition 1.0"
+ description: "Validate Installation Instructions."
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Follow the installation instructions explicitly as it shows in \"Using the pre-built images\" section on build page"
+ expected:
+ - "Make sure that there are no missed or incorrect procedures on instructions"
diff --git a/manual/generic/android/large-wifi-file-transfer.yaml b/manual/generic/android/large-wifi-file-transfer.yaml
new file mode 100644
index 0000000..1c362b5
--- /dev/null
+++ b/manual/generic/android/large-wifi-file-transfer.yaml
@@ -0,0 +1,25 @@
+metadata:
+ name: large-wifi-file-transfer
+ format: "Manual Test Definition 1.0"
+ description: "Large file transfer over WiFi."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Flash android build, power on the board until boot up successfully.
+ - Connect WiFi to an access point. Steps to connect https://git.linaro.org/qa/manual-test-definitions.git/blob/HEAD:/generic/android/wifi.yaml
+ - Open browser from menu and type this link "http://samplemedia.linaro.org/H264/tears_of_steel_1080p_H264_24fps.mov"
+ - The file is 557MB in size and should start downloading automatically.
+
+ expected:
+ - "Downloading full MOV file completes without any error."
diff --git a/manual/generic/android/linaro-android-build-command.yaml b/manual/generic/android/linaro-android-build-command.yaml
new file mode 100644
index 0000000..9748b2f
--- /dev/null
+++ b/manual/generic/android/linaro-android-build-command.yaml
@@ -0,0 +1,38 @@
+metadata:
+ name: linaro-android-build-command
+ format: "Manual Test Definition 1.0"
+ description: "Test if Linaro Android build script works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "On host PC, download \"linaro_android_build_cmds.sh\" script from the build site which you will test"
+ - "In terminal of host PC, run:
+ $ mkdir build_test
+ $ mv linaro_android_build_cmds.sh build_test/
+ $ chmod +x linaro_android_build_cmds.sh
+ $ ./linaro_android_build_cmds.sh -h"
+ - "Copy and paste the overlay URL to browser, accept the license, download \"vendor.tar.bz2\""
+ - "In terminal of host PC, run:
+ $ mv vendor.tar.bz2 build_test/
+ $ ./linaro_android_build_cmds.sh -t -o vendor.tar.bz2"
+ - "After generated \"boot.tar.bz2\", \"system.tar.bz2\" and \"userdata.tar.bz2\", using Linaro Image Tools to flash them to SD card and boot the board"
+
+ expected:
+ - "\"linaro_android_build_cmds.sh\" can be download successfully from build web page"
+ - "\"vendor.tar.bz2\" can be downloaded successfully from overlay URL"
+ - "\"boot.tar.bz2\", \"system.tar.bz2\" and \"userdata.tar.bz2\" can be successfully generated and flashed to SD card by using Linaro Image Tools"
+ - "The target board can be booted into Android main screen and works well"
diff --git a/manual/generic/android/linaro-kernel-build-command.yaml b/manual/generic/android/linaro-kernel-build-command.yaml
new file mode 100644
index 0000000..f3bb76b
--- /dev/null
+++ b/manual/generic/android/linaro-kernel-build-command.yaml
@@ -0,0 +1,26 @@
+metadata:
+ name: andriod-linaro-kernel-build-command
+ format: "Manual Test Definition 1.0"
+ description: "Test if Linaro kernel build script works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "On host PC, download \"linaro_kernel_build_cmds.sh\" script from the build site which you will test"
+ - "TBD"
+
+ expected:
+ - "TBD"
diff --git a/manual/generic/android/monkeyrunner-test.yaml b/manual/generic/android/monkeyrunner-test.yaml
new file mode 100644
index 0000000..2e4f900
--- /dev/null
+++ b/manual/generic/android/monkeyrunner-test.yaml
@@ -0,0 +1,36 @@
+metadata:
+ name: andriod-monkeyrunner-test
+ format: "Manual Test Definition 1.0"
+ description: "Test if Monkey Runner can be triggered successfully"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "On host PC, ensure Android SDK is the latest version, \"platform-tools\" and \"tools\" have been added to system PATH or user environment"
+ - "Power on the board to boot into Android main screen"
+ - "Setup ADB over USB or ADB over Ethernet"
+ - "On host PC, in terminal, run:
+ $ git clone git://android.git.linaro.org/test/linaro/android/system.git
+ $ cd system
+ $ sudo monkeyrunner 0xbench/run.py <device serial number>
+ $ sudo monkeyrunner 3D_game/run.py <device serial number>
+ $ sudo monkeyrunner localaudio/run.py <device serial number>
+ $ sudo monkeyrunner localswvideo/run.py <device serial number>
+ $ sudo monkeyrunner localhwvideo/run.py <device serial number>
+ $ sudo monkeyrunner angrybird/run.py <device serial number>"
+
+ expected:
+ - "Monkey Runner can be triggered successfully"
diff --git a/manual/generic/android/open-accessory.yaml b/manual/generic/android/open-accessory.yaml
new file mode 100644
index 0000000..5b2191b
--- /dev/null
+++ b/manual/generic/android/open-accessory.yaml
@@ -0,0 +1,46 @@
+metadata:
+ name: andriod-open-accessory
+ format: "Manual Test Definition 1.0"
+ description: "Open accesory validation"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Execute the following commands to setup test environment on host PC
+ # apt-get source libusb
+ # apt-get install libusb-dev
+ # apt-get install libusb-1.0-0-dev"
+ - "Follow instructions on the below webpage to set up a device for development and install Android Eclipse:
+ http://developer.android.com/sdk/index.html#ExistingIDE
+ http://developer.android.com/tools/building/building-eclipse.html"
+ - "Download the accessory applications C code as a template from the below link:
+ http://android.serverbox.ch/wp-content/simplectrl.c"
+ - "Identify device PID and VID no using 'lsusb' command"
+ - "Change into the code (siplectrl.c)the VID & PID into the device appropriate VID & PID"
+ - "Connect the device using USB mini A to USB with host"
+ - "Cloning the openaccessory project from here:
+ http://staging.git.linaro.org/people/soumya.basak/accessory.git"
+ - "Run eclipse goto File > Import Select Android and Existing Android Code into Workplace > Next"
+ - "Browse the root directory"
+ - "Select the Project root directory 'Right Click' and Run As > Android Application"
+ - "It will automatically install & Launch the app into device"
+ - "Run gcc simplectrl.c -I/usr/include/ -o simplectrl -lusb-1.0 -I/usr/include/ -I/usr/include/libusb-1.0"
+
+ expected:
+ - "ADB over USB works well"
+ - "Successfully install and launch the openaccessory app into the device"
+ - "From Host run gcc simplectrl.c -I/usr/include/ -o simplectrl -lusb-1.0 -I/usr/include/ -I/usr/include/libusb-1.0 will successfully open the app into device"
+ - "From Eclipse go to Run and open Debug mode, make sure that the Bi-directional data transfer from Device to Host successfully"
diff --git a/manual/generic/android/perf.yaml b/manual/generic/android/perf.yaml
new file mode 100644
index 0000000..5a6a19b
--- /dev/null
+++ b/manual/generic/android/perf.yaml
@@ -0,0 +1,42 @@
+metadata:
+ name: andriod-perf
+ format: "Manual Test Definition 1.0"
+ description: "Test if perf utility works"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen"
+ - "In serial console, run:
+ # perf stat ls"
+
+ expected:
+ - "The output of command \"perf stat ls\" should look like this:
+ Performance counter stats for 'ls':
+
+ 0.659622 task-clock # 0.665 CPUs utilized
+ 24 context-switches # 0.036 M/sec
+ 0 CPU-migrations # 0.000 K/sec
+ 273 page-faults # 0.414 M/sec
+ 1'996'348 cycles # 3.027 GHz [78.98%]
+ 1'274'167 stalled-cycles-frontend # 63.82% frontend cycles idle
+ 1'005'419 stalled-cycles-backend # 50.36% backend cycles idle
+ 1'397'625 instructions # 0.70 insns per cycle
+ # 0.91 stalled cycles per insn
+ 277'755 branches # 421.082 M/sec
+ 7'689 branch-misses # 2.77% of all branches [28.76%]
+
+ 0.000992095 seconds time elapsed"
diff --git a/manual/generic/android/pm-qa.yaml b/manual/generic/android/pm-qa.yaml
new file mode 100644
index 0000000..db81f1d
--- /dev/null
+++ b/manual/generic/android/pm-qa.yaml
@@ -0,0 +1,159 @@
+metadata:
+ name: andriod-pm-qa
+ format: "Manual Test Definition 1.0"
+ description: "Power Management QA"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Power on the board to boot into Android main screen"
+ - "lp:~kejun-zhou/lava-android-test/pm-qa"
+ - "Power off and power on the board again to boot into Android main screen"
+ - "Ensure there is at least one active network connection on the board"
+ - "In serial console, run:
+ # cd /sdcard
+ # wget http://bazaar.launchpad.net/~linaro-validation/lava-android-test/trunk/view/head:/lava_android_test/test_definitions/pm-qa/pm-qa.sh
+ # ./pm-qa.sh"
+
+ expected:
+ - "The test result of \"cpuidle\" suite in pm-qa should look like this:
+ root@android:/ # pm-qa.sh
+ /system/xbin/pm-qa
+ /system/xbin/pm-qa/cpuidle
+ ./cpuidle_01.sh
+ cpuidle_01.0: checking 'current_driver' exists... pass
+ cpuidle_01.1: checking 'current_governor_ro' exists... pass
+ cpuidle_01.0/cpu0: checking 'desc' exists... pass
+ cpuidle_01.1/cpu0: checking 'latency' exists... pass
+ cpuidle_01.2/cpu0: checking 'name' exists... pass
+ cpuidle_01.3/cpu0: checking 'power' exists... pass
+ cpuidle_01.4/cpu0: checking 'time' exists... pass
+ cpuidle_01.5/cpu0: checking 'usage' exists... pass
+ cpuidle_01.6/cpu0: checking 'desc' exists... pass
+ cpuidle_01.7/cpu0: checking 'latency' exists... pass
+ cpuidle_01.8/cpu0: checking 'name' exists... pass
+ cpuidle_01.9/cpu0: checking 'power' exists... pass
+ cpuidle_01.10/cpu0: checking 'time' exists... pass
+ cpuidle_01.11/cpu0: checking 'usage' exists... pass
+ cpuidle_01.0/cpu1: checking 'desc' exists... pass
+ cpuidle_01.1/cpu1: checking 'latency' exists... pass
+ cpuidle_01.2/cpu1: checking 'name' exists... pass
+ cpuidle_01.3/cpu1: checking 'power' exists... pass
+ cpuidle_01.4/cpu1: checking 'time' exists... pass
+ cpuidle_01.5/cpu1: checking 'usage' exists... pass
+ cpuidle_01.6/cpu1: checking 'desc' exists... pass
+ ..."
+ - "The test result of \"cpufreq\" suite in pm-qa should look like this:
+ /system/xbin/pm-qa/cpufreq
+ ./cpufreq_06.sh
+ ./cpufreq_06.sh[107]: [: gid=1007(log): unexpected operator/operand
+ cpufreq_06.0/cpu0: checking deviation for frequency 200.0 MHz... pass
+ cpufreq_06.1/cpu0: checking deviation for frequency 400.0 MHz... pass
+ cpufreq_06.2/cpu0: checking deviation for frequency 800.0 MHz... pass
+ cpufreq_06.3/cpu0: checking deviation for frequency 1000.0 MHz... fail
+ cpufreq_06.0/cpu1: checking deviation for frequency 200.0 MHz... pass
+ cpufreq_06.1/cpu1: checking deviation for frequency 400.0 MHz... pass
+ cpufreq_06.2/cpu1: checking deviation for frequency 800.0 MHz... pass
+ cpufreq_06.3/cpu1: checking deviation for frequency 1000.0 MHz... fail
+ ./cpufreq_08.sh
+ ./cpufreq_08.sh[72]: [: gid=1007(log): unexpected operator/operand
+ cpufreq_08.0/cpu0: checking 'userspace' 200.0 MHz is fixed... pass
+ cpufreq_08.1/cpu0: checking 'userspace' 400.0 MHz is fixed... pass
+ cpufreq_08.2/cpu0: checking 'userspace' 800.0 MHz is fixed... pass
+ cpufreq_08.3/cpu0: checking 'userspace' 1000.0 MHz is fixed... pass
+ cpufreq_08.0/cpu1: checking 'userspace' 200.0 MHz is fixed... pass
+ ..."
+ - "The test result of \"cpuhotplug\" suite in pm-qa should look like this:
+ /system/xbin/pm-qa/cpuhotplug
+ ./cpuhotplug_05.sh
+ [ 340.828277] [sched_delayed] process 2310 (cpuidle_killer) no longer affine to cpu1
+ [ 340.828308] CPU1: shutdown
+ [ 340.828308] CPU1: shutdown
+ cpuhotplug_05.0/cpu1: checking offline processor not found in cpuinfo... pass
+ [ 341.087402] CPU1: Booted secondary processor
+ ./cpuhotplug_06.sh
+ [ 341.199829] CPU1: shutdown
+ [ 341.199859] CPU1: shutdown
+ cpuhotplug_06.0/cpu1: checking offline processor not found in interrupts... pass
+ [ 341.347381] CPU1: Booted secondary processor
+ ./cpuhotplug_01.sh
+ cpuhotplug_01.0: checking 'online' exists... pass
+ cpuhotplug_01.1: checking 'offline' exists... pass
+ cpuhotplug_01.2: checking 'possible' exists... pass
+ cpuhotplug_01.3: checking 'present' exists... pass
+ ..."
+ - "The test result of \"sched_mc\" suite in pm-qa should look like this:
+ /system/xbin/pm-qa/sched_mc
+ ./sched_01.sh
+ sched_01.0: checking 'sched_mc_power_savings' exists... pass
+ ./sched_03.sh
+ sched_03.0/cpu0: checking 'core_id' exists... pass
+ sched_03.1/cpu0: checking 'core_siblings' exists... pass
+ sched_03.2/cpu0: checking 'core_siblings_list' exists... pass
+ sched_03.3/cpu0: checking 'physical_package_id' exists... pass
+ sched_03.4/cpu0: checking 'thread_siblings' exists... pass
+ sched_03.5/cpu0: checking 'thread_siblings_list' exists... pass
+ sched_03.0/cpu1: checking 'core_id' exists... pass
+ sched_03.1/cpu1: checking 'core_siblings' exists... pass
+ sched_03.2/cpu1: checking 'core_siblings_list' exists... pass
+ sched_03.3/cpu1: checking 'physical_package_id' exists... pass
+ sched_03.4/cpu1: checking 'thread_siblings' exists... pass
+ sched_03.5/cpu1: checking 'thread_siblings_list' exists... pass
+ ./sched_04.sh
+ ./sched_04.sh[67]: [: gid=1007(log): unexpected operator/operand
+ sched_04.0: checking setting value to 0... pass
+ sched_04.1: checking setting value to 1... pass
+ sched_04.2: checking setting value to 2... pass
+ sched_04.3: checking setting invalid value to 3... pass
+ sched_04.4: checking setting invalid value to -1... pass
+ ./sched_02.sh
+ sched_02.0/cpu0: checking topology is enabled... pass
+ sched_02.0/cpu1: checking topology is enabled... pass
+ ..."
+ - "The test result of \"suspend\" suite in pm-qa should look like this:
+ /system/xbin/pm-qa/suspend
+ ./suspend_06.sh
+ ./suspend_06.sh: ../include/suspend.sh[301]: uid=0(root) gid=1007(log): unexpected '('
+ *** machine will suspend for 20 seconds
+ Suspend iteration 1 of 5
+ suspend_06.0: checking iteration suspend/resume stress test... test-suspend SUSPEND FAILED, did not go to sleep
+ fail
+ wait for 10 seconds...
+ Suspend iteration 2 of 5
+ suspend_06.1: checking iteration suspend/resume stress test... test-suspend SUSPEND FAILED, did not go to sleep
+ fail
+ wait for 10 seconds...
+ Suspend iteration 3 of 5
+ suspend_06.2: checking iteration suspend/resume stress test... test-suspend SUSPEND FAILED, did not go to sleep
+ fail
+ wait for 10 seconds...
+ Suspend iteration 4 of 5
+ suspend_06.3: checking iteration suspend/resume stress test... test-suspend SUSPEND FAILED, did not go to sleep
+ fail
+ wait for 10 seconds...
+ Suspend iteration 5 of 5
+ suspend_06.4: checking iteration suspend/resume stress test... test-suspend SUSPEND FAILED, did not go to sleep
+ fail
+ wait for 10 seconds...
+ ./suspend_01.sh
+ ./suspend_01.sh: ../include/suspend.sh[301]: uid=0(root) gid=1007(log): unexpected '('
+ *** no primary user (via sudo) dbus tests skipped ...
+ ./suspend_05.sh
+ ./suspend_05.sh: ../include/suspend.sh[301]: uid=0(root) gid=1007(log): unexpected '('
+ *** machine will suspend for 20 seconds
+ suspend_05.0: checking iteration variable delay suspend/resume... test-suspend SUSPEND FAILED, did not go to sleep
+ fail
+ wait for 20 seconds..."
diff --git a/manual/generic/android/powerdebug.yaml b/manual/generic/android/powerdebug.yaml
new file mode 100644
index 0000000..7facf82
--- /dev/null
+++ b/manual/generic/android/powerdebug.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-powerdebug
+ format: "Manual Test Definition 1.0"
+ description: "Test if Powerdebug utility works"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Simply run \"powerdebug\" in a ADB shell"
+ - "Then go through those 4 tabs by clicking \"Tab\" key"
+ - "Click \"Q\" to exit"
+
+ expected:
+ - "You can collect this information on all boards you test"
+ - "Releated bug: https://bugs.launchpad.net/linaro-powerdebug/+bug/1229658"
diff --git a/manual/generic/android/powertop.yaml b/manual/generic/android/powertop.yaml
new file mode 100644
index 0000000..de9c395
--- /dev/null
+++ b/manual/generic/android/powertop.yaml
@@ -0,0 +1,32 @@
+metadata:
+ name: andriod-powertop
+ format: "Manual Test Definition 1.0"
+ description: "Test if powertop utility works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "After the board booted successfully, in serial console, run:
+ # powertop"
+ - "If the output can be shown successfully, using \"Tab\" key to navigate between different tabs"
+ - "Press \"Esc\" key to exit the program"
+
+ expected:
+ - "\"powertop\" command should can be executed successfully"
+ - "Output from \"powertop\" command should can be read clearly"
+ - "Tabs can be navigated successfully"
+ - "PowerTop program can exit successfully after press \"Esc\" key"
+ - "No hang, kernel panic or other serve error during the test"
diff --git a/manual/generic/android/pre-built.yaml b/manual/generic/android/pre-built.yaml
new file mode 100644
index 0000000..6e1b2aa
--- /dev/null
+++ b/manual/generic/android/pre-built.yaml
@@ -0,0 +1,33 @@
+metadata:
+ name: andriod-pre-built
+ format: "Manual Test Definition 1.0"
+ description: "Test if the pre-build image can be installed and boot-up ok"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "On host PC, download binary \"img.bz2\" file from build page"
+ - "Extract the \"img\" file from the compressed package:
+ $ tar xjvf XXXXX.img.bz2"
+ - "Plug in SD card to host PC, in terminal, run:
+ $ sudo fdisk -l
+ $ sudo dd if=XXXXX.img of=/dev/sdX bs=4M"
+ - "After SD card flashing completed, then insert it to the board and power on"
+ - "Note: Remember to replace \"XXXXX\" and \"sdX\" to yours"
+
+ expected:
+ - "The SD card should can be flashed successfully with \"dd\" command"
+ - "The board should can boot into Android main screen and work well"
diff --git a/manual/generic/android/primary-video-out-vga.yaml b/manual/generic/android/primary-video-out-vga.yaml
new file mode 100644
index 0000000..8e5e558
--- /dev/null
+++ b/manual/generic/android/primary-video-out-vga.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-primary-video-out-vga
+ format: "Manual Test Definition 1.0"
+ description: "Test if VGA video works"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Note: For the board comes with LCD module, Primary Video Output means that LCD display"
+ - "Plug in VGA cable between the board and VGA Monitor or VGA TV"
+ - "Power on the VGA Monitor or VGA TV, switch input source to VGA if required"
+ - "Boot the board"
+
+ expected:
+ - "Display should be shown well on VGA monitor or VGA TV"
diff --git a/manual/generic/android/reboot.yaml b/manual/generic/android/reboot.yaml
new file mode 100644
index 0000000..01ff146
--- /dev/null
+++ b/manual/generic/android/reboot.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: android-reboot-console
+ format: "Manual Test Definition 1.0"
+ description: "Check the board can be rebooted from console"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ 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
+ - "$ reboot"
+
+ expected:
+ - Reboot is done successfully from terminal, without kernel panic, crash, hang or any other serve error observed.
diff --git a/manual/generic/android/sd-mmc.yaml b/manual/generic/android/sd-mmc.yaml
new file mode 100644
index 0000000..a5d4bdf
--- /dev/null
+++ b/manual/generic/android/sd-mmc.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-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:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - arndale
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board until main desktop screen shows up.
+ - In serial or ADB console, run these commands.
+ - "$echo $EXTERNAL_STORAGE"
+ - "df"
+ - For HiKey board, test with SD,SDHC and SDXC cards with all classes (2, 4, 6 and 10).
+
+ expected:
+ - "The return string of 'echo $EXTERNAL_STORAGE' should be in output of 'df' command."
diff --git a/manual/generic/android/secondary-video-output.yaml b/manual/generic/android/secondary-video-output.yaml
new file mode 100644
index 0000000..56e0352
--- /dev/null
+++ b/manual/generic/android/secondary-video-output.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: andriod-secondary-video-output
+ format: "Manual Test Definition 1.0"
+ description: "Test if secondary video output works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "If the board support the secondary display output, then connect it to a monitor or TV"
+ - "Power on the monitor or TV, assign input source properly"
+ - "Boot the board"
+
+ expected:
+ - "The display should be shown well on monitor or TV"
diff --git a/manual/generic/android/shutdown-console.yaml b/manual/generic/android/shutdown-console.yaml
new file mode 100644
index 0000000..71f3fb6
--- /dev/null
+++ b/manual/generic/android/shutdown-console.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: android-shutdown-console
+ format: "Manual Test Definition 1.0"
+ description: "Check 'Power OFF' feature from console."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - arndale
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Power on the board until boot up successfully.
+ - After command line prompt shows in serial console, run
+ - "$ reboot -p"
+
+ expected:
+ - The board is 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/android/shutdown.yaml b/manual/generic/android/shutdown.yaml
new file mode 100644
index 0000000..08b41cf
--- /dev/null
+++ b/manual/generic/android/shutdown.yaml
@@ -0,0 +1,29 @@
+metadata:
+ name: android-shutdwon
+ format: "Manual Test Definition 1.0"
+ description: "Check 'Power OFF' feature from UI"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - arndale
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Make sure the board is connected to the display
+ - Power on the board until boot up successfully.
+ - Press and release "Power" button
+ - Tap/click "Shutdown" on the on-screen menu
+
+ expected:
+ - On-screen "Shutdown" meny is displayed
+ - The board is 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/android/small-wifi-file-transfer.yaml b/manual/generic/android/small-wifi-file-transfer.yaml
new file mode 100644
index 0000000..e343a23
--- /dev/null
+++ b/manual/generic/android/small-wifi-file-transfer.yaml
@@ -0,0 +1,25 @@
+metadata:
+ name: small-wifi-file-transfer
+ format: "Manual Test Definition 1.0"
+ description: "Small file transfer over WiFi."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Flash android build, power on the board until boot up successfully.
+ - Connect WiFi to an access point. Steps to connect https://git.linaro.org/qa/manual-test-definitions.git/blob/HEAD:/generic/android/wifi.yaml
+ - Open browser from menu and type this link "http://samplemedia.linaro.org/MPEG4/big_buck_bunny_720p_MPEG4_MP3_25fps_3300K_short.AVI"
+ - The file is 1.8MB in size and should start downloading automatically.
+
+ expected:
+ - "Downloading full AVI file completes without any error."
diff --git a/manual/generic/android/toolchain-version.yaml b/manual/generic/android/toolchain-version.yaml
new file mode 100644
index 0000000..d5f9ae5
--- /dev/null
+++ b/manual/generic/android/toolchain-version.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: android-toolchain-version
+ format: "Manual Test Definition 1.0"
+ description: "Test if the toolchain version is correct"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "dmesg | busybox grep gcc > /sdcard/log.txt 2>&1 &"
+ - "Check the log.txt for toolchain version matches the version displayed on the build page"
+
+ expected:
+ - "Toolchain version matches the version on build page"
+
diff --git a/manual/generic/android/usb-camera-record.yaml b/manual/generic/android/usb-camera-record.yaml
new file mode 100644
index 0000000..7235b97
--- /dev/null
+++ b/manual/generic/android/usb-camera-record.yaml
@@ -0,0 +1,33 @@
+metadata:
+ name: andriod-usb-camera-record
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB camera record feature works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Note: This test is not applicable for Android Jelly Bean"
+ - "Plug in external USB camera"
+ - "Power on the board, Camera App should be pre-installed"
+ - "Launch Camera App, switch to the video record mode"
+ - "Start to record an video clip and stop"
+ - "Play the video in Gallery App"
+
+ expected:
+ - "Camera App should exist"
+ - "Camera App can be launched successfully with the view mode of USB camera"
+ - "Video clip can be recorded and saved successfully"
+ - "Video clip can be played in Gallery App successfully"
diff --git a/manual/generic/android/usb-camera.yaml b/manual/generic/android/usb-camera.yaml
new file mode 100644
index 0000000..2bc9513
--- /dev/null
+++ b/manual/generic/android/usb-camera.yaml
@@ -0,0 +1,31 @@
+metadata:
+ name: andriod-usb-camera
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB camera can be detected and works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Note: This test is not applicable for Android Jelly Bean"
+ - "Plug in external USB camera"
+ - "Power on the board, Camera App should be pre-installed"
+ - "Launch Camera App, take a picture"
+ - "View the picture in Gallery App"
+
+ expected:
+ - "Camera App should exist"
+ - "Camera App can be launched successfully with the view mode of USB camera"
+ - "Pictures can be taken in Camera App and viewed in Gallery App"
diff --git a/manual/generic/android/usb-ethernet.yaml b/manual/generic/android/usb-ethernet.yaml
new file mode 100644
index 0000000..8c8f4fe
--- /dev/null
+++ b/manual/generic/android/usb-ethernet.yaml
@@ -0,0 +1,33 @@
+metadata:
+ name: usb-ethernet
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB Ethernet works on Android"
+ maintainer:
+ - chase.qi@linaro.org
+ os:
+ - android
+ 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 "getprop dhcp.eth0.ipaddress" to check if IP address assigned. If not, run "dhcpcd eth0" to get an IP address.
+ - Open web broswer and type "http://testdata.validation.linaro.org/media_codec/vpx_streams/" and press enter.
+ - Click "vp90-2-tos_1280x534_tile_1x4_1306kbps.webm" to download it to local storage.
+
+ expected:
+ - USB Ethernet obtains an IP address successfully
+ - File download test is successful
+ - No crash observed.
diff --git a/manual/generic/android/usb-host-keyboard.yaml b/manual/generic/android/usb-host-keyboard.yaml
new file mode 100644
index 0000000..3527ebc
--- /dev/null
+++ b/manual/generic/android/usb-host-keyboard.yaml
@@ -0,0 +1,27 @@
+metadata:
+ name: andriod-usb-host-keyboard
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB keyboard can be detected and works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Connect USB keyboard to USB OTG port on device and boot"
+ - "After the board booted up, press \"F1\" key"
+
+ expected:
+ - "USB Mouse should be detected successfully"
+ - "Navigation on UI is possible using USB keyboard"
diff --git a/manual/generic/android/usb-host-mouse.yaml b/manual/generic/android/usb-host-mouse.yaml
new file mode 100644
index 0000000..fc8c442
--- /dev/null
+++ b/manual/generic/android/usb-host-mouse.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-usb-host-mouse
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB mouse can be detected and works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Connect USB mouse to USB OTG port on device and boot"
+ - "Click \"Calculator\" app"
+ - "Click right button of the mouse"
+
+ expected:
+ - "USB Mouse should be detected successfully"
+ - "Navigation and app selection via USB Mouse should work well"
diff --git a/manual/generic/android/usb-host-storage.yaml b/manual/generic/android/usb-host-storage.yaml
new file mode 100644
index 0000000..4bdad87
--- /dev/null
+++ b/manual/generic/android/usb-host-storage.yaml
@@ -0,0 +1,31 @@
+metadata:
+ name: andriod-usb-host-storage
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB storage device can be mounted and works properly"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Connect a USB storage device (e.g: USB Flash device or Pen drive)"
+ - "Type following commands in serial or ADB console:
+ # mkdir /mnt/msc
+ # mount -t vfat /dev/block/sda1 /mnt/msc
+ # cd /mnt/msc
+ # ls"
+
+ expected:
+ - "USB storage device mounted successfully"
+ - "Content in USB storage drive should be shown successfully in serial or ADB console after \"ls\" command executed."
diff --git a/manual/generic/android/usb-tethering.yaml b/manual/generic/android/usb-tethering.yaml
new file mode 100644
index 0000000..9b62efa
--- /dev/null
+++ b/manual/generic/android/usb-tethering.yaml
@@ -0,0 +1,46 @@
+metadata:
+ name: andriod-usb-tethering
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB tethering works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Ensure there is no active network connection on host PC, plug out Ethernet cable or disable wireless adapter (if any)"
+ - "Plug in USB cable to USB OTG port on the board, then plug the other side to host PC"
+ - "Power on the board to boot into Android main screen"
+ - "Ensure network works well, in serial console, run:
+ # busybox ping www.google.com"
+ - "Click Settings->More->USB Tethering-> Enable (If \"USB Tethering\" exists)"
+ - "In serial console, run:
+ # busybox ifconfig -a"
+ - "On host PC, in terminal, run:
+ $ ifconfig -a
+ $ ping <Board_IP_Address>"
+ - "Terminate the ping command on host PC by press \"Ctrl+C\""
+ - "In serial console, run:
+ # busybox ping <Host_PC_IP_Address>"
+ - "Terminate the ping command in serial console by press \"Ctrl+C\""
+ - "On host PC, launch browser, access www.google.com"
+
+ expected:
+ - "\"USB Tethering\" item should exist"
+ - "The network should work well before tethering enable, no data loss in \"ping\" test"
+ - "In serial console, a new network interface should be shown in output of \"busybox ifconfig -a\", the board should get a sub network IP address successfully on that interface after tethering enabled. This sub network IP address should be different with the one which the board got before tethering enable."
+ - "In terminal on host PC, a new network interface should be shown in output of \"ifconfig -a\", the host PC should get a sub network IP address successfully on that interface after the tethering enabled on the board. This sub network IP address should be in the same network segment as the board's"
+ - "\"ping\" test from host PC to the board should be done successfully, no data loss"
+ - "\"ping\" test from the board to host PC should be done successfully, no data loss"
+ - "The host PC now can access Internet, Google main page should be shown well"
diff --git a/manual/generic/android/wifi.yaml b/manual/generic/android/wifi.yaml
new file mode 100644
index 0000000..a539241
--- /dev/null
+++ b/manual/generic/android/wifi.yaml
@@ -0,0 +1,31 @@
+metadata:
+ name: andriod-wifi
+ format: "Manual Test Definition 1.0"
+ description: "Test if wifi module works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Plug out Ethernet cable if any, boot the board.
+ - After the board booted successfully, enable WiFi via "Settings -> Wireless and Networks -> WiFi"
+ - Connect to an access point(Open,WEP,WPA2).
+ - To check if IP address is assigned(ADB should be connected), run "$ adb shell ifconfig wlan0"
+ - To check ping command, run "$ adb shell ping www.google.com"
+ - Launch web browser, access "www.google.com"
+
+ expected:
+ - "WiFi should be enabled successfully."
+ - "IP address should be shown successfully in output of 'ifconfig wlan0' command."
+ - "Ping test should work fine and should not show any data loss."
+ - "Google main page should be open successfully in browser."
diff --git a/manual/generic/android/youtube.yaml b/manual/generic/android/youtube.yaml
new file mode 100644
index 0000000..6ef294c
--- /dev/null
+++ b/manual/generic/android/youtube.yaml
@@ -0,0 +1,28 @@
+metadata:
+ name: andriod-youtube
+ format: "Manual Test Definition 1.0"
+ description: "Test if Youtube App works well"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "Enable Ethernet or WiFi, plug in 3.5mm headset or HDMI cable"
+ - "Launch web browser to access www.google.com"
+ - "Click YouTube link on the top left bar of the Google main page"
+ - "Click any video clip to play"
+
+ expected:
+ - "Video and Audio should be played smoothly and synchronously"
diff --git a/manual/generic/hdmi-audio.yaml b/manual/generic/hdmi-audio.yaml
new file mode 100644
index 0000000..2808ec9
--- /dev/null
+++ b/manual/generic/hdmi-audio.yaml
@@ -0,0 +1,35 @@
+metadata:
+ name: andriod-audio-hdmi
+ format: "Manual Test Definition 1.0"
+ description: "Test if HDMI audio works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - ubuntu
+ - openembedded
+ - debian
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - ifc6410
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Plug out headset and microphone from the board if applicable.
+ - Plug in HDMI cable to connect the board with a monitor or TV which comes with speakers (supports HDMI audio)
+ - Download a music file from "http://samplemedia.linaro.org/Audio/" and then transfer it to storage media on device under test
+ - Play back music file using some media player (different players on different OSes)
+
+ expected:
+ - Sound of music is played back clearly from monitor or TV speakers.
+ - No hang, kernel panic and crash during the whole test process.
diff --git a/manual/generic/hdmi-input-switch.yaml b/manual/generic/hdmi-input-switch.yaml
new file mode 100644
index 0000000..61f2fd5
--- /dev/null
+++ b/manual/generic/hdmi-input-switch.yaml
@@ -0,0 +1,36 @@
+metadata:
+ name: hdmi-input-switching
+ format: "Manual Test Definition 1.0"
+ description: "Test input switching from Monitor."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - ubuntu
+ - openembedded
+ - debian
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - ifc6410
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Connect the device under test HDMI output cable to Monitor/TV.
+ - Make sure Monitor/TV has display input from at least one other source too.
+ - Boot the device under test to UI.
+ - Switch input display from Monitor/TV to board and other input source.
+ - Repeat the process few times.
+
+ expected:
+ - Switching HDMI input works well and doesn't trigger kernel/driver errors on device under test
+ - Switching back to input from device under test works well and UI is displayed on the screen
diff --git a/manual/generic/kernel-version.yaml b/manual/generic/kernel-version.yaml
new file mode 100644
index 0000000..f617132
--- /dev/null
+++ b/manual/generic/kernel-version.yaml
@@ -0,0 +1,32 @@
+metadata:
+ name: linux-kernel-version
+ format: "Manual Test Definition 1.0"
+ description: "Test if the kernel version is correct"
+ maintainer:
+ - botao.sun@linaro.org
+ os:
+ - ubuntu
+ - openembedded
+ - android
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - ifc6410
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - "uname -a"
+ - "Check the output of the kernel version matches the version displayed on the build page"
+
+ expected:
+ - "Kernel version matches the version on build page"
+
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."
diff --git a/manual/generic/primary-video-out-hdmi.yaml b/manual/generic/primary-video-out-hdmi.yaml
new file mode 100644
index 0000000..949838a
--- /dev/null
+++ b/manual/generic/primary-video-out-hdmi.yaml
@@ -0,0 +1,34 @@
+metadata:
+ name: primary-video-out-hdmi
+ format: "Manual Test Definition 1.0"
+ description: "Test if HDMI video output works well"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - ubuntu
+ - openembedded
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Plug in HDMI cable between the board and HDMI Monitor or HDMI TV.
+ - Power on the HDMI Monitor or HDMI TV, switch input source to HDMI.
+ - Boot the board.
+ - If HDMI video ouput works well, Plug out HDMI cable.
+ - Plug in HDMI cable again.
+ expected:
+ - Display is displayed well on HDMI monitor or HDMI TV.
+ - After plugged out HDMI cable no kernel/driver errors are observed on board under test
+ - When plugged in HDMI cable again, display is back to work as normal
diff --git a/manual/generic/sdcard-speed-test.yaml b/manual/generic/sdcard-speed-test.yaml
new file mode 100644
index 0000000..8d80d7a
--- /dev/null
+++ b/manual/generic/sdcard-speed-test.yaml
@@ -0,0 +1,37 @@
+metadata:
+ name: sdcard-speed-test
+ format: "Manual Test Definition 1.0"
+ description: "Measure sdcard read/write speed with dd command."
+ maintainer:
+ - chase.qi@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - benchmark
+ devices:
+ - panda
+ - panda-es
+ - arndale
+ - hi6220-hikey
+ - db410c
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Enter the root directory of the sdcard under test.
+ - On android, run the following command to test write speed.
+ - "# dd if=/dev/zero of=dd.img bs=1048576 count=2000"
+ - On debian, flag conv=fsync is needed, which tells dd to write to disk.
+ - "# dd if=/dev/zero of=dd.img bs=1048576 count=2000 conv=fsync"
+ - Before read speed test, clear the memory cache to ensure that the file is actually read from drive.
+ - "# sync; echo 3 > /proc/sys/vm/drop_caches"
+ - Run dd read speed test.
+ - "# dd if=dd.img of=/dev/null bs=1048576"
+ - Remove dd.img.
+ - "# rm dd.img"
+
+ expected:
+ - dd commands finish successfully
+ - read/write speeds are printed to screen.
diff --git a/manual/generic/serial-console.yaml b/manual/generic/serial-console.yaml
new file mode 100644
index 0000000..7b1f29b
--- /dev/null
+++ b/manual/generic/serial-console.yaml
@@ -0,0 +1,41 @@
+metadata:
+ name: serial-console
+ format: "Manual Test Definition 1.0"
+ description: "Test if the serial connection to the board works"
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - ubuntu
+ - openembedded
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - juno
+ - arndale
+ - ifc6410
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ # depending on the board, the serial cable might be UART or symmetric serial
+ - Connect the serial cable to the device under test
+ - Launch minicom in terminal of host PC.
+ # correct tty should be used. /dev/ttyUSB0 is just an example
+ - "$ minicom -D /dev/ttyUSB0 -w -C minicom_log.txt"
+ - Power the device under test
+ - After boot sequence is complete run the following command in the console
+ - "$ ls -l"
+
+ expected:
+ - Boot log is displayed in minicom after powering the device under test
+ - Command line prompt is displayed after successful boot.
+ - Input by keyboard in works and characters are echoed back and displayed in minicom
+
diff --git a/manual/generic/usb-hid-device.yaml b/manual/generic/usb-hid-device.yaml
new file mode 100644
index 0000000..5836e37
--- /dev/null
+++ b/manual/generic/usb-hid-device.yaml
@@ -0,0 +1,35 @@
+metadata:
+ name: usb-hid-device
+ format: "Manual Test Definition 1.0"
+ description: "Test if USB HID device can be detected and works properly"
+ maintainer:
+ - chase.qi@linaro.org
+ os:
+ - android
+ - linux
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - vexpress-a9
+ - vexpress-tc2
+ - arndale
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Connect USB keyboard and mouse to the device.
+ - Boot the board.
+ - Open an editor and press keyboard keys to check if it works properly.
+ - Check mouse buttons by opening some applications.
+ - Reconnect USB keyboard and mouse and do the previous two steps.
+
+ expected:
+ - USB keyboard and mouse should be detected successfully.
+ - USB keyboard and mouse should work properly.
+ - USB keyboard and mouse should work properly after hotplug.
+ - No crash is observed from serial console.
diff --git a/manual/generic/usb-storage.yaml b/manual/generic/usb-storage.yaml
new file mode 100644
index 0000000..54a47b2
--- /dev/null
+++ b/manual/generic/usb-storage.yaml
@@ -0,0 +1,36 @@
+metadata:
+ name: usb-storage
+ format: "Manual Test Definition 1.0"
+ description: "Basic test for USB keyboard functionality"
+ maintainer:
+ - chase.qi@linaro.org
+ os:
+ - android
+ - linux
+ scope:
+ - functional
+ devices:
+ - panda
+ - panda-es
+ - arndale
+ - hi6220-hikey
+ - apq8016-sbc
+ - hi6220-hikey
+ - apq8016-sbc
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Login in as root and plug in your USB storage device.
+ - Run "demsg" to find the device ID. Take "sda1" for example.
+ - Run the following command to mount the disk. Modify the disk format as needed.
+ - On Linux, run "mount /dev/sda1 /mnt/"
+ - On Android, run "mount -t vfat /dev/block/sda1 /mnt/"
+ - Copy a file to /mnt and then delete the file.
+ - Execute "umount /mnt" to umount the device.
+
+ expected:
+ - Disk mount and umount tests are successful.
+ - File copying is successful and the file can be deleted.
+ - No crash is observed from serial console.
diff --git a/manual/hikey/hikey-power-button.yaml b/manual/hikey/hikey-power-button.yaml
new file mode 100644
index 0000000..08da070
--- /dev/null
+++ b/manual/hikey/hikey-power-button.yaml
@@ -0,0 +1,30 @@
+metadata:
+ name: hikey-power-button
+ format: "Manual Test Definition 1.0"
+ description: "Test if the behaviour of hikey power button follows the definition in hardware user guide."
+ maintainer:
+ - chase.qi@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Power off the board and remove Auto Power Jumper(link 1-2) if it is installed.
+ - Press power button and hold more a second to see if it can power on the board.
+ - Boot to OS, press and release power button to see if it can power off the board.
+ - Boot to OS, press and hold power buttion for >4 seconds to see if it can reset the board.
+
+ expected:
+ # Please find Hikey hardware user guide on the below page
+ # https://github.com/96boards/documentation/wiki/HiKeyGettingStarted#96boards-hikey
+ - Test result should match the following behaviours defined in hardware user guide.
+ - A press and hold will power on the board if the Auto Power Jumper is not installed.
+ - A press and release will then power off the board.
+ - A press and hold for >4 seconds will reset the board.
diff --git a/manual/hikey/hikey-user-led.yaml b/manual/hikey/hikey-user-led.yaml
new file mode 100644
index 0000000..25354ee
--- /dev/null
+++ b/manual/hikey/hikey-user-led.yaml
@@ -0,0 +1,30 @@
+metadata:
+ name: hikey-user-led
+ format: "Manual Test Definition 1.0"
+ description: "Test if user LED working on Hikey board."
+ maintainer:
+ - amit.khare@linaro.org
+ os:
+ - android
+ - debian
+ scope:
+ - functional
+ devices:
+ - hi6220-hikey
+ environment:
+ - manual-test
+
+run:
+ steps:
+ - Boot the board successfuly.
+ - There are four user LEDs on board user_led1, user_led2, user_led3 and user_led4.
+ - To turn on specific LED, run "echo 1 > /sys/class/leds/<led_dir>/brightness"
+ - To turn off specific LED, run "echo 0 > /sys/class/leds/<led_dir>/brightness"
+ - Run "cat /sys/class/leds/<led_dir>/trigger" to show all the triggers available for a particular LED.
+ - To assign a trigger to any LED, run "echo trigger_name > /sys/class/leds/<led_dir>/trigger"
+ - example: to assign "heartbeat" trigger to user_led3, run "echo heartbeat > /sys/class/leds/user_led3/trigger"
+ - To remove trigger for any LED, run "echo none > /sys/class/leds/<led_dir>/trigger"
+
+ expected:
+ - LEDs can be turned on and off.
+ - Triggers can be assigned/removed to/from any LEDs.