| 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 |
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.
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
How to test?
Focus on pm-utils, powertop, tuned. There are manual tests and one automated Tuned test, steps:
- Run test cases bellow
- Report results to the result table
- Laptop users can upload their score from automated Tuned test (optional, but highly appreciated)
Update your machine
If you're running Fedora 15, make sure you have all the current updates for it installed, using the update manager.
Test Cases
- QA:Testcase_Power_Management_pm_suspend - pm-utils suspend
- QA:Testcase_Power_Management_pm_hibernate - pm-utils hibernate
- QA:Testcase_Power_Management_pm_bugreport - pm-utils bug-reporting tool
- QA:Testcase_Power_Management_Lid_Close - Lid close
- QA:Testcase_Power_Management_powertop2_basic - PowerTOP 2.x basic
- QA:Testcase_Power_Management_powertop2_power_estimation_engine - PowerTOP 2.x power estimation engine
- QA:Testcase_Power_Management_powertop2_suggestions - PowerTOP 2.x suggestions
- QA:Testcase_Power_Management_tuned_basic - Tuned basic
- QA:Testcase_Power_Management_tuned_powersave_idle - Tuned laptop-battery-powersave profile, active idle
- QA:Testcase_Power_Management_tuned_powersave_load - Tuned laptop-battery-powersave profile, load
- QA:Testcase_Power_Management_tuned_performance_idle - Tuned throughput-performance profile, active idle
- QA:Testcase_Power_Management_tuned_performance_load - Tuned throughput-performance profile, load
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 | powertop | tuned | tuned score 1 | tuned score 2 | References |
|---|---|---|---|---|---|---|---|---|---|
| Sample User | HW |  |
|
 |
 |
|
1234 | 1234 |