From Fedora Project Wiki
March 17, 2009 From 12:00 to 0:00 UTC (8am -> 8pm EDT) #fedora-qa)

What to test?

This Fedora Test Day will focus on DeviceKit.

Who's available

The following cast of characters will be available to help with testing, workarounds, bug fixes, and general discussion ...

Prerequisities for the test day

  • Fully updated Rawhide
  • Free space for more partitions on a HD
  • FAS Account - you can create an account in 3 minutes if you don't have one
  • Your hardware profile uploaded to Smolt according to these instructions
Backup Your Data
We're going to do dangerous things to partition tables and partitions. Don't perform your testing on a disk with data you'd like to keep.

Optional accessories

  • USB flash disk / MP3 player / memory card reader with a card or two
  • External HD (connected via USB or FireWire)
  • DVD-RAM writer & media, internal or external
  • PCMCIA memory card reader with a card
  • RAID array
  • Encrypted partitions
  • Any other exotic storage device you have

How to test?

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.

Live Image

Optionally, you may download a non-destructive rawhide live image for your architecture:

Tips on using a live image are available at FedoraLiveCD.

Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can
# yum --enablerepo=rawhide update syslinux

Filing Bugs

All bugs will be tracked in Bugzilla. To file a bug against DeviceKit, click here

Please include the following information when filing a bug:

  • devkit-disks --dump
  • devkit-power --dump


Perform each of the following test cases that you are able to with the resources available to you.

  1. DeviceKit nautilus-gdu
  2. DeviceKit gvfs
  3. DeviceKit palimpsest
  4. DeviceKit power

Test Results

Once you have completed the tests, add your results to the Results table below, following the example results from Sample User as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt).

For each test case, if your system worked correctly, simply enter the word PASS. If you had any failures, enter the word FAIL, as a link to the bug report for the failure. If you could not meaningfully run the test due to limitations of your system or because of failures in more basic functionality, enter the word N/A. In the comments column, you can enter the any additional information worth noting during your testing (work-arounds, observations etc...).

User Smolt Profile 1. nautilus-gdu 2. gvfs 3. palimpsest 4. power Comments
Sample user HW PASS PASS PASS PASS Filed sample bug rhbug:1
James Laska HW INPROGRESS FAT formatting never finishes ... and chews up memory (using nautilus or gnome-disk-utility-format)