Architectures/ARM/Quality Assurance/2012-12-03-VFAD-Fedora 18 Test Day-Pandaboard-SD2

From FedoraProject

< Architectures | ARM | Quality Assurance(Difference between revisions)
Jump to: navigation, search
m (Results)
m (Results)
 
(5 intermediate revisions by one user not shown)
Line 7: Line 7:
 
|| 1 || {{result|pass}} ||   
 
|| 1 || {{result|pass}} ||   
 
|-
 
|-
|| 2 || ||     
+
|| 2 || {{result|pass}} ||     
 
|-
 
|-
|| 3 || ||  
+
|| 3 || {{result|pass}} ||  
 
|-
 
|-
|| 4 || ||   
+
|| 4 || {{result|pass}} ||   
 
|-
 
|-
|| 5 || ||  
+
|| 5 || {{result|fail|jbastian|883163}} || 1. lm_sensors failed, but this is expected <br /> 2. NetworkManager does not bring up eth0 consistently; <tt>nmcli con up id 'System eth0'</tt> usually fixes it <br /> 3. Cannot ssh into the server; <tt>systemctl stop firewalld.service; iptables -F</tt> "fixes" it
 
|-
 
|-
|| 6 || ||   
+
|| 6 || {{result|pass}} ||   
 
|-
 
|-
|| 7 || ||   
+
|| 7 || {{result|pass}} ||   
 
|-
 
|-
|| 8 || ||   
+
|| 8 || {{result|pass}} ||   
 
|-
 
|-
|| 9 || ||     
+
|| 9 || {{result|pass}} ||     
 
|-
 
|-
|| 10 || ||     
+
|| 10 || n/a ||     
 
|-
 
|-
|| 11 || ||
+
|| 11 || {{result|pass}} ||
 
|-
 
|-
|| 12 || ||
+
|| 12 || n/a ||
 
|-
 
|-
|| 13 || ||
+
|| 13 || n/a ||
 
|-
 
|-
|| 14 || ||
+
|| 14 || n/a ||
 
|-
 
|-
|| 15 || ||
+
|| 15 || n/a ||
 
|-
 
|-
|| 16 || ||
+
|| 16 || n/a ||
 
|-
 
|-
|| 17 || ||
+
|| 17 || n/a ||
 
|-
 
|-
|| 18 || ||
+
|| 18 || n/a ||
 
|-
 
|-
|| 19 || ||
+
|| 19 || n/a ||
 
|}
 
|}
 +
<references/>
  
 
===Tests===
 
===Tests===

Latest revision as of 14:46, 4 December 2012

2012-12-03 VFAD Fedora 18 Beta Test Day Results for Jeff Bastian on Pandaboard with SD card

[edit] Results

Test Result Notes
1
Pass pass
2
Pass pass
3
Pass pass
4
Pass pass
5
Fail fail jbastian [1]
1. lm_sensors failed, but this is expected
2. NetworkManager does not bring up eth0 consistently; nmcli con up id 'System eth0' usually fixes it
3. Cannot ssh into the server; systemctl stop firewalld.service; iptables -F "fixes" it
6
Pass pass
7
Pass pass
8
Pass pass
9
Pass pass
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
  1. RHBZ #883163

[edit] Tests

  1. Does your downloaded image have the correct checksum?
    • Run the command: sha256sum --check *CHECKSUM
  2. Check the image size:
    • xzcat NameOfImage.xz|wc -c - Is the uncompressed image no larger than 4GB?
  3. 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?
  4. Do all default services start properly?
    • Watch for service-start failure messages during boot.
  5. 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)
  6. 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
  7. 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
  8. Are you able to shutdown the system using standard console commands?
    • Test poweroff or halt or reboot or shutdown -h now
  9. If audio device support is present, does it work?
    • Test with: play /usr/share/sounds/alsa/*wav
  10. 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.
  11. Graphical user interfaces only: Is it possible to run Midori and a terminal application?
  12. Graphical user interfaces only is the default Fedora artwork used (currently not decided)?
  13. Graphical user interfaces only: Are the desktop's panels working and fully functional?
  14. 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?
  15. 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.
  16. 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?
  17. 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
  18. 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.