Architectures/ARM/Quality Assurance/2012-12-20-VFAD-Fedora 18 Beta-Kirkwood-Guruplug-Server-USB

From FedoraProject

< Architectures | ARM | Quality Assurance(Difference between revisions)
Jump to: navigation, search
(Created page with "#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/f18-beta-tc3...")
 
 
Line 60: Line 60:
 
|| 3 || {{result|pass}}  ||  
 
|| 3 || {{result|pass}}  ||  
 
|-
 
|-
|| 4 || {{result|pass}}  ||
+
|| 4 || {{result|pass}}  || Had to reconfigure U-Boot, reformat the "boot" filesystem as a vfat, and change /etc/fstab to mount /boot on "LABEL=boot", and type vfat
 
|-
 
|-
 
|| 5 || {{result|pass}}  ||     
 
|| 5 || {{result|pass}}  ||     
Line 68: Line 68:
 
|| 7 || {{result|pass}}  ||   
 
|| 7 || {{result|pass}}  ||   
 
|-
 
|-
|| 8 || {{result|pass}}  || I noticed a USB reset message in the log:
+
|| 8 || {{result|pass}}  ||  
  usb 3-1: reset high-speed USB device number 2 using tegra-ehci
+
 
|-
 
|-
 
|| 9 || {{result|pass}}  || Tested reboot.
 
|| 9 || {{result|pass}}  || Tested reboot.

Latest revision as of 00:11, 21 December 2012

  1. Copy the below tests and results chart to a page that you create.
  2. Does your downloaded image have the correct checksum?
    • Run the command: sha256sum --check SHA256SUMS
  3. Check the image size:
    • xzcat NameOfImage.xz|wc -c - Is the uncompressed image no larger than 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 (you may want to limit this to one package as updates can take a while depending on your media. eg - yum update bash)
    • Graphical user interfaces only: 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/messages
  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 Midori and a terminal application?
  13. Graphical user interfaces only is the default Fedora artwork used (currently not decided)?
  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.

[edit] Results

Test Result Notes
1
Pass pass
2
Pass pass
3
Pass pass
4
Pass pass
Had to reconfigure U-Boot, reformat the "boot" filesystem as a vfat, and change /etc/fstab to mount /boot on "LABEL=boot", and type vfat
5
Pass pass
6
Pass pass
7
Pass pass
8
Pass pass
9
Pass pass
Tested reboot.
10 n/a
11
Pass pass
12 n/a
13 n/a
14 n/a
15 n/a
16 n/a
17 n/a
18 n/a
19 n/a