UbuntuPowerManagementTesting
Revision 2 as of 2009-12-10 17:01:22
Clear message
Typical tests should last 30-60s to encapsulate most low-level periodic wakeups[1].
* Idle tests
- Idle after boot
- Boot up default install, wait a minute or so to let all applet to settle down (network connection WLAN) and then measure
- Idle after resume from suspend
- Same as idle after boot
- Idle after resume from hibernate
- Same as idle after boot
- Separate testing for server, desktop and UNR install
- server is expected to consume the least and will supply the baseline for a specific HW device
* HW-specific testing
- Radio tests
- WLAN idle
- Connect to AP, do network activity for a while and then idle
- Does the WLAN device switch to low-power mode?
- 3G modem
- Same as WLAN
- Bluetooth
- Same as WLAN
- Additional INFO required: AP model
- WLAN idle
- Display tests
- Test idle with
- full screen brightness
- half brightness
- Test idle with
* Figure out usecase for backlight measurements
* Usecase testing
- Browsing
- Preconfigured with flash plugin
- 5-10 tabs loading a pre-cached set of webpages
- Loading live sites changes the numbers (due to flash)
- separate tests over WLAN and 3G?
[1] Longer tests can be considered if we have certain applications that have much longer cycles of periodic activity