UbuntuPowerManagementTesting

Revision 3 as of 2010-01-12 12:04:33

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 applets to settle down (e.g. 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 platform

* 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?
      • Disconnected
        • Disconnected from AP using applet and make sure we go back to base consumption (radio being turned off correctly)
        • Use rfkill switch and make sure radio is being turned off correctly
      • Active
        • Measure peak consumption and average consumption with activity over WLAN
    • 3G modem
      • Idle
      • Disconnected
      • Active
        • Similar to WLAN tests
    • Bluetooth
      • Idle
      • Disconnected
      • Active
        • Similar to WLAN tests
    • Additional INFO required: AP model
  • Display tests
    • Test idle with
      • full screen brightness
      • half brightness

* 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

CategoryHomepage