Draft laptop testing spec

Carl Karsten carl at personnelware.com
Sat Jun 4 14:42:20 CDT 2005


I seem to remember seeing a bios setting for what my button does: power, sleep, 
hibernate, shutdown.  I am guessing these are all posible things that could be 
triggered by various events: buttons, lid open/close, AC power on/off, inactivity 
timeout, etc.

I have a feeling that it will make more sense to split the tests into 2 groups:

1. ability to detect events (can we tell when X has happend? button, switch, AC, 
docked)

2. ability to transision between various states: (sleep, hibernate, on) 
(docked/undoced)  (removable hardware in out)

I think there should be a status app that shows when the #1 events happen.  That 
way we can have a better idea why the box didn't hibernate when we pushed the button.


> POWER MANAGEMENT TEST
> 
> Does pressing the sleep button cause the machine to sleep?
>   After a few seconds, the machine's screen should go blank and the 
>   sleep light come on
> 
> Does the machine then wake up correctly?
>   After a few seconds, the machine should wake up. Moving the mouse 
>   should result in a screen unlock box appearing.
>   Does the keyboard still work after resume?
>   Does the network still work after resume?

What should lan and wifi do?  espicaly when the box wakes up in a different state 
(different wifi AP, network cable unplugged)

Also, box put to sleep, pcmica cards changed, box wakes up.

Carl Karsten



More information about the ubuntu-devel mailing list