From Fedora Project Wiki

(add data for DKP-power)
(Drop direct Test Days category membership)
 
(52 intermediate revisions by 10 users not shown)
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 (8am -> 8pm EDT) || [irc://irc.freenode.net/fedora-qa #fedora-qa])
|-
|-
|}
|}
__NOTOC__


=== What to test? ===
=== What to test? ===


This Fedora Test Day will focus on [[Features/DeviceKit | DeviceKit]].
This Fedora Test Day will focus on [[Features/DeviceKit | DeviceKit]].
* [[QA/Test_Days/2009-03-17/DeviceKit_power | DeviceKit power - testing braindump ]]


=== Who's available ===  
=== Who's available ===  


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:jlaska|James Laska]]


=== Prerequisities for the test day ===  
=== Prerequisities for the test day ===  


* Fully updated rawhide
* Fully updated [[Releases/Rawhide|Rawhide]]
* Free space for more partitions on a HD
* Free space for more partitions on a HD
* FAS Account - you can [https://admin.fedoraproject.org/accounts/ create] an account in 3 minutes if you don't have one
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
{{admon/warning|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.}}


{{admon/warning|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 ====
 
=== Optional accessories ===
* USB flash disk / MP3 player / memory card reader with a card or two
* USB flash disk / MP3 player / memory card reader with a card or two
* External HD (connected via USB or FireWire)
* External HD (connected via USB or FireWire)
Line 34: Line 35:
* 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.
=== Live Image ===


DeviceKit-power gets all the data from the kernel over the dbus service DeviceKit.
Optionally, you may download a non-destructive rawhide live image for your architecture:
* [http://katzj.fedorapeople.org/testday/livecd-fedora-livecd-desktop-200903161319-i386.iso i386]
* [http://katzj.fedorapeople.org/testday/livecd-fedora-livecd-desktop-200903161250-x86_64.iso x86_64]


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.
Tips on using a live image are available at [[FedoraLiveCD]].


This can be observed doing "devkit-power --monitor".
{{admon/note|Note|Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows [http://fedorahosted.org/liveusb-creator liveusb-creator].  Users of F10 and below can <pre># yum --enablerepo=rawhide update syslinux</pre>}}


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.
=== Filing Bugs ===


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.
All bugs will be tracked in [[Bugzilla]].  To file a bug against DeviceKit, [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=DeviceKit&version=rawhide&short_desc=%5BUEFI%20Test%20Day%5D&cf_qa_whiteboard=UEFITestDay click here]


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.
=== Testing ===


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.
Perform each of the following test cases that you are able to with the resources available to you.


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.
# [[QA:Testcase_DeviceKit_nautilus_gdu]]
# [[QA:Testcase_DeviceKit_gvfs]]
# [[QA:Testcase_DeviceKit_palimpsest]]
# [[QA:Testcase_DeviceKit_power]]


If you need to run the daemon in verbose mode, do (as root):
== Test Results ==


killall devkit-power-daemon
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).
/usr/libexec/devkit-power-daemon --verbose


and then you can open another terminal and start to see the daemon output.
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
! [[QA:Testcase_DeviceKit_nautilus_gdu|nautilus-gdu]]
! [[QA:Testcase_DeviceKit_gvfs|gvfs]]
! [[QA:Testcase_DeviceKit_palimpsest|palimpsest]]
! [[QA:Testcase_DeviceKit_power|power]]
! Comments
|-
| Sample user
| [http://www.smolts.org/client/show/UUID_HERE HW]
| PASS
| PASS
| PASS
| PASS
| Filed sample bug [[rhbug:1]]
|-
| [[User:JamesLaska|James Laska]]
| [http://www.smolts.org/client/show/pub_606a8b52-d28b-41c7-aee2-f4994df2911e HW]
| FAIL (see comments)
| <!-- PASS || [[rhbug:123456|FAIL]] || INPROGRESS -->
| PASS (see comments)
| <!-- PASS || [[rhbug:123456|FAIL]] || INPROGRESS -->
|
* ''nautilus-gdu'' - FAT formatting occasionally '''never''' finishes ... and chews up memory (using nautilus or gnome-disk-utility-format). 
* ''nautilus-gdu'' - gnome-disk-utility dialogs include dbus strings (filed enhancement gnomebug#[http://bugzilla.gnome.org/show_bug.cgi?id=575710 575710])
* ''nautilus-gdu'' - Failure while creating an ext3+LUKS partition gnomebug#[http://bugzilla.gnome.org/show_bug.cgi?id=575725 575725]
* ''nautilus-gdu'' - Failure while trying to mount an encrypted ext3+LUKS partitions gnomebug#[http://bugzilla.gnome.org/show_bug.cgi?id=575728 575728]
* ''palimpsest'' - Gets [http://jlaska.fedorapeople.org/palimpsest.png confused] with too many partitions (See [[rhbug:488554]])
|-
| [[User:Mnowak|Michal Nowak]]
| [http://www.smolts.org/client/show/pub_2179dd43-43bb-4fba-88cf-dc453f10632e HW]
| 2/5 PASS ratio
| 1/2 PASS ratio
| PASS
| N/A
| When playing with USB key, the g-d-u-f seemed to me fragile, a lot of problems I had to temporary "solve" via (un)plugging the USB key. Palimpsest needs some polishing like: SMART self-test happened (and probably passed) but now window reported this success back to me.
|-
| [[User:zmraz|Zbysek MRAZ]]
| [http://www.smolts.org/client/show/pub_8aed6655-c835-4916-9a34-4134eeaf77a4 HW]
| PASS
| [https://bugzilla.redhat.com/show_bug.cgi?id=490692 FAIL]
| FAIL - not able to handle any USB device. All edit options are inactive even running as root
| N/A
| 1. Find some FAT & cryptsetup issues alltogether with tbzatek
|-
| [[User:Adamwill|Adam Williamson]]
| [http://www.smolts.org/client/show/pub_83c50393-af40-48b6-ac0b-6affb7801aca HW]
| FAIL(*)
| PASS
| FAIL(+)
| FAIL(o)
|
* *: [[gnomebug:575745|crashes]] on USB stick with partition but no filesystem or USB stick with no partition
* +: 'Device is busy' trying to delete an existing unmounted LUKS-encrypted partition on a USB stick
* o: Battery / AC switch [[rhbug:490764|isn't done right]]
|-
| [[User:Hondra|Ondrej Hudlicky]]
| [http://www.smolts.org/client/show/pub_6e039116-4e28-4cd0-a62a-7807ccc0c56a HW]
| FAIL
| FAIL
| FAIL
| N/A
|
* [[rhbug:490870| 490870 ]] No support for root actions in nautilus
* [[rhbug:490873| 490873 ]] palimpsest: no option to mount unmounted volumes
* [[rhbug:490881| 490881 ]] palimpsest: limited function for root user
|-
| <!-- [[User:FasName]] -->
| <!-- [http://www.smolts.org/client/show/UUID_HERE HW] -->
| <!-- PASS || [[rhbug:123456|FAIL]] || INPROGRESS -->
| <!-- PASS || [[rhbug:123456|FAIL]] || INPROGRESS -->
| <!-- PASS || [[rhbug:123456|FAIL]] || INPROGRESS -->
| <!-- PASS || [[rhbug:123456|FAIL]] || INPROGRESS -->
| <!-- Comments, concerns or issues -->
|}


=== Test Cases and Results ===
[[Category:Fedora 11 Test Days]]
 
See the Features page / TBD
 
[[Category:Test Days]]

Latest revision as of 19:33, 26 June 2015

DATE TIME WHERE
March 17, 2009 From 12:00 to 0:00 UTC (8am -> 8pm EDT) #fedora-qa)

What to test?[edit]

This Fedora Test Day will focus on DeviceKit.

Who's available[edit]

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

Prerequisities for the test day[edit]

  • 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[edit]

  • 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?[edit]

Update your machine[edit]

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

Live Image[edit]

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

Tips on using a live image are available at FedoraLiveCD.

Note
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[edit]

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

Testing[edit]

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

  1. QA:Testcase_DeviceKit_nautilus_gdu
  2. QA:Testcase_DeviceKit_gvfs
  3. QA:Testcase_DeviceKit_palimpsest
  4. QA:Testcase_DeviceKit_power

Test Results[edit]

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 nautilus-gdu gvfs palimpsest power Comments
Sample user HW PASS PASS PASS PASS Filed sample bug rhbug:1
James Laska HW FAIL (see comments) PASS (see comments)
  • nautilus-gdu - FAT formatting occasionally never finishes ... and chews up memory (using nautilus or gnome-disk-utility-format).
  • nautilus-gdu - gnome-disk-utility dialogs include dbus strings (filed enhancement gnomebug#575710)
  • nautilus-gdu - Failure while creating an ext3+LUKS partition gnomebug#575725
  • nautilus-gdu - Failure while trying to mount an encrypted ext3+LUKS partitions gnomebug#575728
  • palimpsest - Gets confused with too many partitions (See rhbug:488554)
Michal Nowak HW 2/5 PASS ratio 1/2 PASS ratio PASS N/A When playing with USB key, the g-d-u-f seemed to me fragile, a lot of problems I had to temporary "solve" via (un)plugging the USB key. Palimpsest needs some polishing like: SMART self-test happened (and probably passed) but now window reported this success back to me.
Zbysek MRAZ HW PASS FAIL FAIL - not able to handle any USB device. All edit options are inactive even running as root N/A 1. Find some FAT & cryptsetup issues alltogether with tbzatek
Adam Williamson HW FAIL(*) PASS FAIL(+) FAIL(o)
  • *: crashes on USB stick with partition but no filesystem or USB stick with no partition
  • +: 'Device is busy' trying to delete an existing unmounted LUKS-encrypted partition on a USB stick
  • o: Battery / AC switch isn't done right
Ondrej Hudlicky HW FAIL FAIL FAIL N/A
  • 490870 No support for root actions in nautilus
  • 490873 palimpsest: no option to mount unmounted volumes
  • 490881 palimpsest: limited function for root user