Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day

Fedora ARM VFAD - Fedora 17 - RC2

• When: Monday June 18th at 12PM EDT
• Where: #fedora-arm on Freednode

Please join on Monday June 18th as we test all available images to be used in the Fedora 17 ARM RC2. All can participate - even if you lack hardware you can greatly assist us by testing the functionality of our QEMU images, as well as in updating our wiki where appropriate. Our aim is to remove outdated material, and add areas that include answers to frequently asked questions, installation and usage instructions for specific hardware and anything else that may help Fedora ARM users.

Participants

Please add your name, followed by your IRC nick:

• Paul Whalen - pwhalen
• M A - maxam
• D. Marlin - dmarlin

Test Instructions

Please add your name to the wiki beside the hardware you will be testing as well as the media you will be using (eg SATA, SD). See this link for examples on how to report test results.

Overall Test Results and Board Assignment

Hardware	Who's Testing	Result	Link to Results Page	Final Notes
Versatile Express (Qemu)
Versatile Express+XFCE (Qemu)
Pandaboard	pwhalen - SD	inprogress pwhalen
Pandaboard+XFCE	pwhalen - SD
Trimslice Bare/Value Pro/H/H250	dmarlin - HFP SD	inprogress dmarlin
Trimslice Pro/H/H250
Highbank
Beagleboard XM
Kirkwood (sheevaplug, dreamplug, guruplug, etc)
Raspberry Pi+XFCE
Raspberry Pi
Efika SmartTop iMX	maxam - HFP SD	inprogress maxam	iMX HFP SD results

Testing Template

Copy the wiki source of the below tests and results chart to a page you will create, using the hardware you are testing as the end of the url. For example if you are testing a Pandaboard with SD card, use a link similar to "Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day-Pandaboard-SD" to record your results. Once completed add the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

1. Copy the below tests and results chart to a page that you create .
   • Download the image for your system from http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/ as well as the corresponding checksum file http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM or http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/armhfp/Fedora-17-armhfp-Images-CHECKSUM
2. Does your downloaded image have the correct checksum?
   • Run the command: sha256sum --check *CHECKSUM
3. Check the image size:
   • xzcat NameOfImage.xz|wc -c - Is the uncompressed image less then 4GB?
4. Copy the image to your SD card:
   • xzcat (name-of-image) > /dev/SD_Card_Device and then insert it into your system and power on. Does the system boot?
5. Do all default services start properly?
   • Watch for service-start failure messages during boot.
6. Check the boot result:
   • If graphics hardware is present and the image is configured for a graphical user interface, does the system successfully boot to the GUI?
   • If no graphical hardware is present, does the system successfully boot to a login prompt? (Note: depending on the image, the login prompt may appear on a connected monitor or on a serial console)
7. Are you able to download and install updates with yum, and if available the default graphical package manager?
   • Test this using the command: yum install sl and yum update - then use the graphical package manager for your desktop (if applicable) to install zsh
8. Is logging functional? It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages.
   • Test using the command: tail -f /var/log/message
9. Are you able to shutdown the system using standard console commands?
   • Test poweroff or halt or reboot or shutdown -h now
10. If audio device support is present, does it work?
    • Test with: play /usr/share/sounds/alsa/*wav
11. Are the final branded release notes from the Documentation team present on the installed media?
    • Check /usr/share/doc/HTML/fedora-release-notes. In a graphical user interface, look for a "Release Notes" menu entry.
12. Graphical user interfaces only: Is it possible to run Firefox and a terminal application?
    • Use the browser to download a small file - http://scotland.proximity.on.ca/arm-nightlies/vault/to-mirrors/RC2/arm/Fedora-17-arm-Images-CHECKSUM
    • Load extensions (Firefox -> Tools -> Get Add-ons _> <choose an extension>)
    • Log into FAS.
13. Graphical user interfaces only is the default Fedora artwork used?
    • Default wallpaper - http://fedoraproject.org/wiki/File:F17-final-wallpaper-standard.png
14. Graphical user interfaces only: Are the desktop's panels working and fully functional?
15. Graphical user interfaces only: Is media automatically detected when inserted?
    • Plug in a USB device or other removable media. Does the system automatically mount the device?
16. Graphical user interfaces only: On graphical hardware - do offered mechanisms (if any) for shutting down, logging out and rebooting work?
    • Use the GUI to logout, reboot and shutdown the system.
17. Graphical user interfaces only: Do all elements of the default panel (or equivalent) configuration in all release-blocking desktops function correctly in common use?
    • Does every button do what it is supposed to do?
    • Do GUI actions align correctly with the pointer position?
18. Graphical user interfaces only: Menu sanity:
    • All Applications listed in the system menus (or equivalent) must have icons which have a consistent appearance and sufficiently high resolution to avoid appearing blurry
    • Do all applications listed under the Applications menu or category start successfully?
    • Do all applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items
    • Ensure no application appears more then once in the menus. In particular, items under System must not appear under Applications
19. Graphical user interfaces only: Does Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring work?
    • Create an ssh key: ssh-keygen # Use a passphrase
    • Copy the ssh key to a remote system: ssh-copy-id YourUserId@RemoteSystem # Enter password when prompted
    • Connect to the remote system: ssh YourUserId@RemoteSystem # You should be prompted for the passphrase. Select the checkbox marked "Unlock this key when I log in" (or similar wording)
    • Log out.
    • Log back in to the system.
    • Connect to the remote system again: ssh YourUserId@RemoteSystem # You should not be prompted for your passphrase.

Results

Test	Result	Notes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19