From Fedora Project Wiki

Line 1: Line 1:
Place holder for Fedora 17 Power Management Test Day. [TBD]
+
{{Infobox_group
 +
| name = Fedora Test Days
 +
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_17_test_days]]
 +
| caption = Power Management
 +
| date = 2012-04-04
 +
| time = all day
 +
| website = [[QA/Fedora_17_test_days]]
 +
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 +
| fedora_mailing_list = test
 +
}}
  
 +
{{admon/warn | Under construction | This site is under construction, please do not upload any results before the offical test day (2012-04-04). The instruction could be change.}}
 +
{{admon/note | Older events | Fedora 16 Power Management Test Day: [[Test_Day:2011-09-29_PowerManagement]]}}
  
'''Older events:'''
+
{{admon/note | Can't make the date? | If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
  
Fedora 16 Power Management Test Day: [[Test_Day:2011-09-29_PowerManagement]]
+
{{admon/note | On site event | You can attend this event online or personally: http://fedora.cz/udalosti/den-otevrenych-dveri-v-red-hatu/}}
 +
 
 +
== What to test? ==
 +
 
 +
Today's instalment of Fedora Test Day will focus on [[SIGs/PowerManagement|'''Power Management''']]
 +
 
 +
== Who's available ==
 +
 
 +
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
 +
* Development - [[User:jskarvad|Jaroslav Škarvada]] (jskarvad) / [[SIGs/PowerManagement|PowerManagement SIG]]
 +
* Quality Assurance - [[User:jscotka|Jan Ščotka]] (jscotka)
 +
 
 +
Note: jskarvad will be available at least during 10:00 - 22:00 (UTC+2) on #fedora-test-day, #fedora-power, #fedora-devel, otherwise he will be on e-mail with non guaranteed response time. He will be also available on site in Red Hat Brno Office at least during 13:00 - 19:00.
 +
 
 +
== Prerequisite for Test Day ==
 +
 
 +
* PM Test Day LiveCD [TBD] (md5sum: TBD) or an updated [http://fedoraproject.org/get-prerelease Fedora 17 pre-release] or you may get nightly composed [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ LiveCD].
 +
** It is possible to convert the LiveCD into LiveUSB by following the [[How_to_create_and_use_Live_USB]] instructions.
 +
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
 +
* Optional: account on fedoraproject.org if you plan to upload the pm-utils bugreport file. If you do not have one and you do not plan to get it, you can still attend the test day - there are instructions in the appropriate test case(s) bellow how to handle such situation.
 +
 
 +
== Typing convetions ==
 +
In the following text commands that needs to be run as root are prefixed by #, e.g.:
 +
# id
 +
means to run ''id'' command under the root account. Commands prefixed by $ do not need to be run under the root account.
 +
 
 +
== How to test? ==
 +
 
 +
It is focused especially on suspend, hibernate, power-consumption, LCD brightness control and our new tuned. Some test cases are only for laptop users and it is signalled in test case description field. If you do not have laptop just skip them. You can also skip other test cases (e.g. if you do not have enough time). In this case just leave the columns for skipped test cases blank. Please note that your report will be still valuable even if you do not finish all test cases. The procedure:
 +
 
 +
* Run test cases bellow.
 +
* Report results to the result table.
 +
 
 +
=== '''Prepare your system''' ===
 +
{{admon/note|If you are using our PM Test Day LiveCD, please skip the following steps, because everything is already prepared for you.}}
 +
# Install the public key (in case you would like to verify the PM Test Day support package, otherwise you can skip this step because the public key will be installed automatically with the PM Test Day support package in the next step):
 +
#:<pre># rpm --import http://jskarvad.fedorapeople.org/RPM-GPG-KEY-pm-test-day</pre>
 +
# Install the PM Test Day support package by:
 +
#:<pre># yum install TBD</pre>
 +
#* This procedure will also install the public key which will be then used for verification of packages from the PM Test Day repo.
 +
 
 +
Finally make sure you have all current updates (and temporal fixes) installed by:
 +
<pre># yum update</pre>
 +
 
 +
== Test Cases ==
 +
 
 +
{| class="wikitable sortable"  style="width:100%" border="1"
 +
!style="width:20%"|Testcase
 +
!style="width:60%"|Description
 +
!style="width:10%"|Target
 +
!style="width:10%"|Approx. time required
 +
|- 
 +
| [[QA:Testcase_Power_Management_pm_suspend|pm-suspend]]
 +
| Tests suspend / resume via pm-utils.
 +
| All
 +
| 2 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_pm_hibernate|pm-hibernate]] 
 +
| Tests hibernate / resume via pm-utils.
 +
| All
 +
| 5 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_pm_bugreport|pm-bugreport]] 
 +
| Tests pm-utils bug-reporting functionality.
 +
| All
 +
| 2 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_pm_powersave|pm-powersave]] 
 +
| Tests detection of AC / battery (upower functionality) and pm-powersave reactions to power source changes (pm-utils).
 +
| Laptops only
 +
| 2 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_Lid_Close|Lid close]] 
 +
| Tests system reaction to lid close.
 +
| Laptops only
 +
| 2 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_Backlight_Control|Backlight control]] 
 +
| Tests LCD backlight control.
 +
| Laptops only
 +
| 1 minute
 +
|-
 +
| [[QA:Testcase_Power_Management_tuned_basic|Tuned basic]] 
 +
| Tests tuned-adm (tuned) basic functionality.
 +
| All
 +
| 5 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_tuned_off_idle|Tuned disabled idle]] 
 +
| Measures power consumption of machine in active idle with tuned disabled.
 +
| Laptops only
 +
| 15 minutes
 +
|-
 +
| [[QA:Testcase_Power_Management_tuned_powersave_idle|Tuned powersave idle]] 
 +
| Measures power consumption of machine in active idle with tuned laptop-battery-powersave profile.
 +
| Laptops only
 +
| 15 minutes
 +
|}
 +
 
 +
== Known Bugs / Workarounds ==
 +
None at the moment.
 +
== Test Results ==
 +
 
 +
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=16&component=pm-utils pm-utils], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=16&component=tuned tuned]. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line 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 the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line. bugreport.txt will be generated by test case [[QA:Testcase_Power_Management_pm_bugreport|pm-bugreport]], instructions for uploading are included in this test case. The bugreport.txt gives us valuable information about your HW / SW configuration and debug log of your last suspend / hibernate process.
 +
 
 +
{| style="font-size:80%;"
 +
! User
 +
! Smolt<br/>Profile
 +
! [[QA:Testcase_Power_Management_pm_suspend|pm-suspend]]
 +
! [[QA:Testcase_Power_Management_pm_hibernate|pm-hibernate]]
 +
! [[QA:Testcase_Power_Management_pm_bugreport|pm-bugreport]]
 +
! [[QA:Testcase_Power_Management_pm_powersave|pm-powersave]]
 +
! [[QA:Testcase_Power_Management_Lid_Close|Lid close]]
 +
! [[QA:Testcase_Power_Management_Backlight_Control|Backlight control]]
 +
! [[QA:Testcase_Power_Management_tuned_basic|Tuned basic]]
 +
! [[QA:Testcase_Power_Management_tuned_off_idle|Tuned disabled idle]]
 +
! [[QA:Testcase_Power_Management_tuned_powersave_idle|Tuned powersave idle]]
 +
! References
 +
|-
 +
| [[User:SampleUser|Sample User]]
 +
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 Sample Machine]
 +
| {{result|fail}} <ref>{{bz|54321}}</ref>
 +
| {{result|pass}}
 +
| {{result|warn}} <ref>Got report but also encountered {{bz|54320}}</ref> [http://fedoraproject.org/w/uploads/2/2f/pm-test-day-20110324-pub_84465125-1350-4f83-87b9-5f16f7430eb8 bugreport]
 +
| {{result|pass}}
 +
| {{result|warn}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| E:4800 mWh
 +
| E:4710 mWh
 +
| <references/>
 +
|-
 +
! User
 +
! Smolt<br/>Profile
 +
! [[QA:Testcase_Power_Management_pm_suspend|pm-suspend]]
 +
! [[QA:Testcase_Power_Management_pm_hibernate|pm-hibernate]]
 +
! [[QA:Testcase_Power_Management_pm_bugreport|pm-bugreport]]
 +
! [[QA:Testcase_Power_Management_pm_powersave|pm-powersave]]
 +
! [[QA:Testcase_Power_Management_Lid_Close|Lid close]]
 +
! [[QA:Testcase_Power_Management_Backlight_Control|Backlight control]]
 +
! [[QA:Testcase_Power_Management_tuned_basic|Tuned basic]]
 +
! [[QA:Testcase_Power_Management_tuned_off_idle|Tuned disabled idle]]
 +
! [[QA:Testcase_Power_Management_tuned_powersave_idle|Tuned powersave idle]]
 +
! References
 +
|}
 +
 
 +
[[Category:Fedora 17 Test Days]]

Revision as of 14:37, 20 March 2012

Fedora Test Days
Echo-testing-48px.png
Power Management

Date 2012-04-04
Time all day

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Template:Admon/warn

Note.png
Older events
Fedora 16 Power Management Test Day: Test_Day:2011-09-29_PowerManagement
Note.png
Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
Note.png
On site event
You can attend this event online or personally: http://fedora.cz/udalosti/den-otevrenych-dveri-v-red-hatu/

What to test?

Today's instalment of Fedora Test Day will focus on Power Management

Who's available

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

Note: jskarvad will be available at least during 10:00 - 22:00 (UTC+2) on #fedora-test-day, #fedora-power, #fedora-devel, otherwise he will be on e-mail with non guaranteed response time. He will be also available on site in Red Hat Brno Office at least during 13:00 - 19:00.

Prerequisite for Test Day

  • PM Test Day LiveCD [TBD] (md5sum: TBD) or an updated Fedora 17 pre-release or you may get nightly composed LiveCD.
  • Your hardware profile uploaded to Smolt according to these instructions
  • Optional: account on fedoraproject.org if you plan to upload the pm-utils bugreport file. If you do not have one and you do not plan to get it, you can still attend the test day - there are instructions in the appropriate test case(s) bellow how to handle such situation.

Typing convetions

In the following text commands that needs to be run as root are prefixed by #, e.g.:

# id

means to run id command under the root account. Commands prefixed by $ do not need to be run under the root account.

How to test?

It is focused especially on suspend, hibernate, power-consumption, LCD brightness control and our new tuned. Some test cases are only for laptop users and it is signalled in test case description field. If you do not have laptop just skip them. You can also skip other test cases (e.g. if you do not have enough time). In this case just leave the columns for skipped test cases blank. Please note that your report will be still valuable even if you do not finish all test cases. The procedure:

  • Run test cases bellow.
  • Report results to the result table.

Prepare your system

Note.png
If you are using our PM Test Day LiveCD, please skip the following steps, because everything is already prepared for you.
  1. Install the public key (in case you would like to verify the PM Test Day support package, otherwise you can skip this step because the public key will be installed automatically with the PM Test Day support package in the next step):
    # rpm --import http://jskarvad.fedorapeople.org/RPM-GPG-KEY-pm-test-day
  2. Install the PM Test Day support package by:
    # yum install TBD
    • This procedure will also install the public key which will be then used for verification of packages from the PM Test Day repo.

Finally make sure you have all current updates (and temporal fixes) installed by:

# yum update

Test Cases

Testcase Description Target Approx. time required
pm-suspend Tests suspend / resume via pm-utils. All 2 minutes
pm-hibernate Tests hibernate / resume via pm-utils. All 5 minutes
pm-bugreport Tests pm-utils bug-reporting functionality. All 2 minutes
pm-powersave Tests detection of AC / battery (upower functionality) and pm-powersave reactions to power source changes (pm-utils). Laptops only 2 minutes
Lid close Tests system reaction to lid close. Laptops only 2 minutes
Backlight control Tests LCD backlight control. Laptops only 1 minute
Tuned basic Tests tuned-adm (tuned) basic functionality. All 5 minutes
Tuned disabled idle Measures power consumption of machine in active idle with tuned disabled. Laptops only 15 minutes
Tuned powersave idle Measures power consumption of machine in active idle with tuned laptop-battery-powersave profile. Laptops only 15 minutes

Known Bugs / Workarounds

None at the moment.

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component pm-utils, or tuned. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line 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 the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line. bugreport.txt will be generated by test case pm-bugreport, instructions for uploading are included in this test case. The bugreport.txt gives us valuable information about your HW / SW configuration and debug log of your last suspend / hibernate process.

User Smolt
Profile
pm-suspend pm-hibernate pm-bugreport pm-powersave Lid close Backlight control Tuned basic Tuned disabled idle Tuned powersave idle References
Sample User Sample Machine
Fail fail
[1]
Pass pass
Warning warn
[2] bugreport
Pass pass
Warning warn
Pass pass
Pass pass
E:4800 mWh E:4710 mWh
  1. RHBZ #54321
  2. Got report but also encountered RHBZ #54320
User Smolt
Profile
pm-suspend pm-hibernate pm-bugreport pm-powersave Lid close Backlight control Tuned basic Tuned disabled idle Tuned powersave idle References