No edit summary |
No edit summary |
||
Line 60: | Line 60: | ||
== Test Cases == | == Test Cases == | ||
{| style="width:100%" | |||
!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]] | |||
| pm-utils suspend | |||
| All | |||
| 2 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_pm_hibernate|pm-hibernate]] | |||
| pm-utils hibernate | |||
| All | |||
| 5 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_pm_bugreport|pm-bugreport]] | |||
| pm-utils bug-reporting tool | |||
| All | |||
| 2 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_pm_powersave|pm-powersave]] | |||
| pm-utils powersave | |||
| All | |||
| 2 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_Lid_Close|Lid close]] | |||
| Lid close | |||
| Laptops only | |||
| 2 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_powertop2_basic|PowerTOP 2.x basic]] | |||
| PowerTOP 2.x basic functionality | |||
| All | |||
| 5 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_powertop2_power_estimation_engine|PowerTOP 2.x PE engine]] | |||
| PowerTOP 2.x power estimation engine | |||
| Laptops only | |||
| 1 hour | |||
|- | |||
| [[QA:Testcase_Power_Management_powertop2_suggestions|PowerTOP 2.x suggestions]] | |||
| PowerTOP 2.x suggestions | |||
| All | |||
| 5 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_tuned_basic|Tuned basic]] | |||
| Tuned basic functionality | |||
| All | |||
| 5 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_tuned_powersave_idle|Tuned psave idle]] | |||
| Tuned laptop-battery-powersave profile, active idle | |||
| Laptops only | |||
| 15 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_tuned_powersave_load|Tuned psave load]] | |||
| Tuned laptop-battery-powersave profile, load | |||
| All, laptops preferred | |||
| 15 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_tuned_performance_idle|Tuned perf idle]] | |||
| Tuned throughput-performance profile, active idle | |||
| Laptops only | |||
| 15 minutes | |||
|- | |||
| [[QA:Testcase_Power_Management_tuned_performance_load|Tuned perf load]] | |||
| Tuned throughput-performance profile, load | |||
| All, laptops preferred | |||
| 15 minutes | |||
|} | |||
== Test Results == | == Test Results == | ||
Line 101: | Line 159: | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | ||
| | | [http://fedoraproject.org/w/uploads/2/2f/pm-test-day-20110324-pub_84465125-1350-4f83-87b9-5f16f7430eb8 bugreport.txt] | ||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|fail}} <ref>{{bz|12345}}</ref> | | {{result|fail}} <ref>{{bz|12345}}</ref> | ||
Line 110: | Line 168: | ||
| 1234 | | 1234 | ||
| 1234 | | 1234 | ||
| 1234 | | 1234 {{result|warn}} <ref>Encountered {{bz|54322}}</ref> | ||
| <references/> | | <references/> | ||
|- | |- |
Revision as of 10:44, 20 March 2011
Fedora Test Days | |
---|---|
Power Management | |
Date | 2011-03-24 |
Time | all day |
Website | QA/Fedora_15_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
Instructions bellow are incomplete, this page will be finalized: 2011-03-20
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 ...
- Development - Jaroslav Škarvada (jskarvad)
- Quality Assurance - Jan Ščotka (jscotka)
Note: jskarvad will be available during CET business hours (UTC+1) on #fedora-test-day, #fedora-power, #fedora-devel, otherwise he will be on e-mail with non guaranteed response time.
Prerequisite for Test Day
- An updated Fedora 15 pre-release or you may get LiveCD, (special PM test day live image will be prepared later).
- Your hardware profile uploaded to Smolt according to these instructions
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?
Focus on pm-utils, powertop, 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. Procedure:
- Run test cases bellow
- Report results to the result table
Prepare your system
Install the PM Test Day support package that will setup your system for this test day. It will install all required dependencies, packages and utilities. It will also setup your system to use the PM Test Day repo. This repo contains temporal fixes for bugs discovered and resolved shortly before test day (these fixes will get into F15 soon).
- Install the public key by:
# rpm --import http://jskarvad.fedorapeople.org/RPM-GPG-KEY-pm-test-day
- Install the PM Test Day support package by:
# yum install http://jskarvad.fedorapeople.org/pm-test-day-1-1.fc15.x86_64.rpm
Or you can skip the public key installation step and directly install the PM Test Day support package by:
# yum install --nogpgcheck http://jskarvad.fedorapeople.org/pm-test-day-1-1.fc15.x86_64.rpm
- 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 | pm-utils suspend | All | 2 minutes |
pm-hibernate | pm-utils hibernate | All | 5 minutes |
pm-bugreport | pm-utils bug-reporting tool | All | 2 minutes |
pm-powersave | pm-utils powersave | All | 2 minutes |
Lid close | Lid close | Laptops only | 2 minutes |
PowerTOP 2.x basic | PowerTOP 2.x basic functionality | All | 5 minutes |
PowerTOP 2.x PE engine | PowerTOP 2.x power estimation engine | Laptops only | 1 hour |
PowerTOP 2.x suggestions | PowerTOP 2.x suggestions | All | 5 minutes |
Tuned basic | Tuned basic functionality | All | 5 minutes |
Tuned psave idle | Tuned laptop-battery-powersave profile, active idle | Laptops only | 15 minutes |
Tuned psave load | Tuned laptop-battery-powersave profile, load | All, laptops preferred | 15 minutes |
Tuned perf idle | Tuned throughput-performance profile, active idle | Laptops only | 15 minutes |
Tuned perf load | Tuned throughput-performance profile, load | All, laptops preferred | 15 minutes |
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component pm-utils, or powertop, 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.
User | Smolt Profile | pm-suspend | pm-hibernate | pm-bugreport | bugreport.txt | pm-powersave | PowerTOP 2.x basic | PowerTOP 2.x PE engine | PowerTOP 2.x suggestions | Tuned basic | Tuned psave idle | Tuned psave load | Tuned perf idle | Tuned perf load | References |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sample User | HW | bugreport.txt | 1234 | 1234 | 1234 | 1234 |