diff options
Diffstat (limited to 'manual/generic/android')
53 files changed, 1874 insertions, 0 deletions
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" |