UbuntuPowerManagementTesting

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2009-12-10 16:59:07 →
Size: 1428
Editor: a91-154-124-12
Comment:
← Revision 2 as of 2009-12-10 17:01:22 → ⇥
Size: 1434
Editor: a91-154-124-12
Comment:
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:

* Additional INFO required: AP model

* Display tests
  * Test idle with
    * full screen brightness
    * half brightness		    * Additional INFO required: AP model
  * Display tests
   * Test idle with
   * full screen brightness
      * half brightness

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
  • 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

AmitKucheria/UbuntuPowerManagementTesting (last edited 2010-09-24 09:41:47 by a91-154-124-12)