Test Day:2009-03-17 DeviceKit

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add data for DKP-power)
Line 3: Line 3:
 
| DATE || TIME || WHERE
 
| DATE || TIME || WHERE
 
|-
 
|-
| TBD || From ''TBD'' to ''TBD'' UTC (? -> ? EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa])
+
| March 17, 2009 || From ''12:00'' to ''0:00'' UTC (7am -> 7pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa])
 
|-
 
|-
 
|}
 
|}
Line 15: Line 15:
  
 
The following cast of characters will be available to help with testing, workarounds, bug fixes, and general discussion ...
 
The following cast of characters will be available to help with testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:tbzatek|Tomas Bzatek]], [[User:mclasen|Matthias Clasen]] (TBD)
+
* Development - [[User:davidz|David Zeuthen]], [[User:tbzatek|Tomas Bzatek]], [[User:rhughes|Richard Hughes]], [[User:mclasen|Matthias Clasen]]
* Quality Assurance - [[User:rbiba|Radek Biba]], [[User:QE2]], [[User:QE3]] (TBD)
+
* Quality Assurance - [[User:rbiba|Radek Biba]], [[User:Hondra|Ondrej Hudlicky]], [[User:QE3]] (TBD)
  
 
=== Prerequisities for the test day ===  
 
=== Prerequisities for the test day ===  
Line 34: Line 34:
 
* Any other exotic storage device you have
 
* Any other exotic storage device you have
  
=== How to test? ===
+
== How to test? ==
  
See the Features page / TBD
+
=== '''Update your machine''' ===
  
-----------------------
+
See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide.
Brain dump for DeviceKit-power:
+
  
DeviceKit-power is a little service that takes data from the kernel, and processes it so that it's easy to consume. Known consumers are gnome-power-manager and the XFCE battery widget.
+
=== Testing ===
  
DeviceKit-power gets all the data from the kernel over the dbus service DeviceKit.
+
Perform each of the following test cases that you are able to with the resources available to you.
  
You should get changed events from "devkit --monitor" when you do things like remove or insert the AC adaptor. Similarly, DeviceKit-power should emit signals when this happens.
+
* 1. [[QA:Testcase_DeviceKit_nautilus_gdu| DeviceKit nautilus-gdu ]]
 +
* 2. [[QA:Testcase_DeviceKit_gvfs| DeviceKit gvfs ]]
 +
* 3. [[QA:Testcase_DeviceKit_palimpsest| DeviceKit palimpsest ]]
 +
* 4. [[QA:Testcase_DeviceKit_power| DeviceKit power]]
  
This can be observed doing "devkit-power --monitor".
+
== Test Case Results ==
 
+
If you don't get changed signals in DeviceKit or DeviceKit-power then it's probably a kernel bug. This is known for some Sony laptops, and needs to be fixed in the kernel.
+
 
+
You should check you get the changed signals, and that the output of "devkit-power -d" changes to the correct values. The status of the battery typically goes from charging->unknown->discharging as the embedded controller takes a while to settle down and give valid readings.
+
 
+
Using gnome-power-statistics you can obserbe the values in more detail. Make sure the percentages are all 0..100 and the value look sensible (for instance, Voltage is 0..20V, not 340034V). If this is the case please open a bug and dump the output of /sys/class/power_supply/*/*. If the values in /sys are wrong, then it's not a DeviceKit-power bug, it's a kernel bug or hardware fault.
+
 
+
For the wakeups, ensure "devkit-power --wakeups" produces userspace and kernel wakeups, and that these are sensible. The first time you run this command, you'll probably get no data, but just try again in a few seconds, and you should have some values. We don't poll by default all the time, as this itself would use power.
+
 
+
For the tools, try and crash the devkit-power tool. Give it invalid input, and see how it copes. Try also crashing the daemon using d-feet to execute methods, or using dbus-send on the command line. If it crashes it's an important bug, so be sure to file it in bugzilla.
+
 
+
If you need to run the daemon in verbose mode, do (as root):
+
 
+
killall devkit-power-daemon
+
/usr/libexec/devkit-power-daemon --verbose
+
 
+
and then you can open another terminal and start to see the daemon output.
+
------------------------------------
+
  
 +
{|
 +
! User
 +
! Smolt Profile
 +
! 1. nautilus-gdu
 +
! 2. gvfs
 +
! 3. palimpsest
 +
! 4. power
 +
! Comments
 +
|-
 +
| Sample user
 +
| [http://www.smolts.org/client/show/UUID_HERE HW]
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| bugs: ..
 +
|-
 +
|}
  
=== Test Cases and Results ===
 
  
See the Features page / TBD
 
  
 
[[Category:Test Days]]
 
[[Category:Test Days]]

Revision as of 01:41, 14 March 2009

DATE TIME WHERE
March 17, 2009 From 12:00 to 0:00 UTC (7am -> 7pm 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
Warning (medium size).png
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.

Testing

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

Test Case Results

User Smolt Profile 1. nautilus-gdu 2. gvfs 3. palimpsest 4. power Comments
Sample user HW PASS PASS PASS PASS bugs: ..