From Fedora Project Wiki

Line 25: Line 25:
! Architecture !! SHA1SUM  
! Architecture !! SHA1SUM  
|-
|-
| i586 || <code></code>
| [http://mclasen.fedorapeople.org/livecd-fedora-livecd-desktop-200908101443.i686.iso i586] || <code>e9ab9f9846bea2d0d0eb4514a4048d9365a07950</code>
|-
|-
| x86_64 || <code></code>
| [http://mclasen.fedorapeople.org/livecd-fedora-livecd-desktop-200908101347.x86_64.iso x86_64] || <code>6f49f3f7b6a3fab49514c73035bdfe42a8ca1416</code>
|}
|}
* A variety of gizmos that can be plugged into a computer. See above for a representative list of devices that might be good to test
* A variety of gizmos that can be plugged into a computer. See above for a representative list of devices that might be good to test

Revision as of 20:01, 10 August 2009

DATE TIME WHERE
2009-08-11 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-fit-and-finish)


What to test?

Today's instalment of Fedora Test Day will focus on user experience issues of peripherals. We are interesting in the problems you face when plugging anything into your computer, be it a mouse, a keyboard an external hard drive, a modem, a printer, a camera, a phone, a music player, a GPS or whatever.

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion: Matthias Clasen, David Zeuthen, Bastien Nocera

Prerequisites for Test Day

  • An up-to-date rawhide installation. See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. If that feels too risky to you, we also have recent rawhide live images available that allow you to participate without risking your existing installation. Tips on using a live image are available at FedoraLiveCD.

Note that the images will be removed shortly after the test day, since they are strictly for test day usage only.

Architecture SHA1SUM
i586 e9ab9f9846bea2d0d0eb4514a4048d9365a07950
x86_64 6f49f3f7b6a3fab49514c73035bdfe42a8ca1416
  • A variety of gizmos that can be plugged into a computer. See above for a representative list of devices that might be good to test
  • A good mood. Remember; while we are poking into things that may make us angry or frustrated, we are doing it to make things better

How to test

In this test day, we want to find small and large issues that ruin the user experience of working with devices that can be (hot-)plugged into your computer.

Test cases:

Here are some things to look at:

  • Does the desktop react in the right way if you plug in your device ?
  • Is a suitable icon used to represent the device ?
  • Do the relevant applications 'see' the device, e.g. does a music player appear in rhythmbox ?
  • Do applications react appropriately to the device being unplugged ?
  • Do things work in the same way if the device is already plugged in before boot or before login ?

Issues that were identified

Tester Description Bug references

Things that work alright

Tester Description