44
44
Did the screen turn back on when the lid was opened?
47
name: power-management/network_before_suspend
49
_description: Test the network before suspending.
50
command: network_check -a
53
name: power-management/resolution_before_suspend
54
_description: Record the current resolution before suspending.
55
command: xrandr -q |grep '*'| awk '{print $1}' > $CHECKBOX_DATA/resolution_before_suspend.txt
58
name: power-management/audio_before_suspend
60
device.category == 'AUDIO'
61
package.name == 'alsa-base'
62
_description: Test the audio before suspending.
63
command: amixer > $CHECKBOX_DATA/audio_before_suspend.txt
66
name: power-management/cpu_before_suspend
68
package.name == 'linux'
69
_description: Check all the CPUs are online before suspending
70
command: cpuinfo_resource > $CHECKBOX_DATA/cpuinfo_before_suspend
73
name: power-management/memory_before_suspend
75
package.name == 'linux'
77
Dumps memory info to a file for comparison after suspend test has been run
78
command: meminfo_resource > $CHECKBOX_DATA/meminfo_before_suspend
81
name: power-management/wireless_before_suspend
82
depends: networking/wireless_connection
83
command: nmcli -t -f DEVICES con status >> $CHECKBOX_DATA/iface && connect_wireless && internet_test --interface=`nmcli dev list | grep -B 1 wireless | grep GENERAL.DEVICE | awk '{print $2}'` && reconnect `cat $CHECKBOX_DATA/iface`
85
This test disconnects all connections and then connects to the wireless
86
interface. It then checks the connection to confirm it's working as expected.
89
name: power-management/bluetooth_detect_before_suspend
90
requires: package.name == 'bluez'
91
command: hcitool dev | tail -n+2 | awk '{print $2}' > $CHECKBOX_DATA/bluetooth_address
93
This test just grabs the hardware address of the bluetooth controller
96
name: power-management/bluetooth_obex_before_suspend
97
requires: package.name == 'bluez' and package.name == 'obexd-client'
98
command: obex_send $BTDEVADDR $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
100
This test sends an image to the device specified by the BTDEVADDR environment variable.
103
name: power-management/bluetooth_obex_before_suspend_manual
104
requires: package.name == 'bluez' and package.name == 'obexd-client'
105
command: obex_send `bluetooth_scan` $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
107
This test will send the image 'JPEG_Color_Image_Ubuntu.jpg' to a specified device.
109
Select Test and you will be prompted to enter the Bluetooth device name of a device that can accept file transfers. It may take a few moments after entering the name for the file to begin sending. Accept any prompts that appear on both devices.
112
47
name: power-management/rtc
113
48
requires: package.name == 'linux'
117
52
Make sure that the RTC (Real-Time Clock) device exists.
120
name: power-management/suspend_advanced
121
depends: power-management/rtc power-management/network_before_suspend power-management/resolution_before_suspend power-management/wireless_before_suspend power-management/bluetooth_detect_before_suspend power-management/bluetooth_mouse_before_suspend power-management/cpu_before_suspend power-management/memory_before_suspend
122
requires: package.name == 'pm-utils'
124
Power management Suspend and Resume test
126
Select Test and your system will suspend for about 30 - 60 seconds. If your system does not wake itself up after 60 seconds, please press the power button momentarily to wake the system manually. If your system fails to wake at all and must be rebooted, restart System Testing after reboot and mark this test as Failed.
128
command: sleep_test -d
131
name: power-management/network_after_suspend
132
depends: power-management/suspend_advanced power-management/network_before_suspend
133
_description: Test the network after resuming.
134
command: internet_test
137
name: power-management/resolution_after_suspend
138
depends: power-management/suspend_advanced power-management/resolution_before_suspend
139
_description: Test to see that we have the same resolution after resuming as before.
140
command: xrandr -q |grep '*'| awk '{print $1}' | diff $CHECKBOX_DATA/resolution_before_suspend.txt -
143
name: power-management/audio_after_suspend
145
device.category == 'AUDIO'
146
package.name == 'alsa-base'
147
depends: power-management/suspend_advanced power-management/audio_before_suspend
148
_description: Test the audio after resuming.
149
command: amixer | diff $CHECKBOX_DATA/audio_before_suspend.txt -
152
name: power-management/cpu_after_suspend
154
package.name == 'linux'
155
depends: power-management/suspend_advanced power-management/cpu_before_suspend
156
_description: Check all CPUs are online after resuming.
157
command: cpuinfo_resource | diff $CHECKBOX_DATA/cpuinfo_before_suspend -
160
name: power-management/memory_after_suspend
162
package.name == 'linux'
163
depends: power-management/suspend_advanced power-management/memory_before_suspend
165
Check that all memory is available after resuming from suspend.
166
command: meminfo_resource | diff $CHECKBOX_DATA/meminfo_before_suspend -
169
name: power-management/display_after_suspend
171
package.name == 'linux'
172
depends: power-management/suspend_advanced
174
Does the display work normally after resuming from suspend?
177
name: power-management/wireless_after_suspend
178
depends: power-management/suspend_advanced power-management/wireless_before_suspend
179
command: nmcli -t -f DEVICES con status >> $CHECKBOX_DATA/iface && connect_wireless && internet_test --interface=`nmcli dev list | grep -B 1 wireless | grep GENERAL.DEVICE | awk '{print $2}'` && reconnect `cat $CHECKBOX_DATA/iface`
181
This test checks that the wireless interface is working after suspending the system. It
182
disconnects all interfaces and then connects to the wireless interface and checks that the
183
connection is working as expected.
186
name: power-management/bluetooth_detect_after_suspend
187
depends: power-management/suspend_advanced power-management/bluetooth_detect_before_suspend
188
requires: package.name == 'bluez'
189
command: grep -q `hcitool dev | tail -n+2 | awk '{print $2}'` $CHECKBOX_DATA/bluetooth_address
191
This test grabs the hardware address of the bluetooth adapter after suspend and compares it to the address grabbed before suspend.
194
name: power-management/bluetooth_obex_after_suspend
195
depends: power-management/suspend_advanced power-management/bluetooth_obex_before_suspend
196
requires: package.name == 'bluez' and package.name == 'obexd-client'
197
command: obex_send $BTDEVADDR $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
199
This test sends an image to the device specified by the BTDEVADDR environment variable.
202
name: power-management/bluetooth_obex_after_suspend_manual
203
depends: power-management/suspend_advanced power-management/bluetooth_obex_before_suspend_manual
204
requires: package.name == 'bluez' and package.name == 'obexd-client'
205
command: obex_send `bluetooth_scan` $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
207
This test will send the image 'JPEG_Color_Image_Ubuntu.jpg' to a specified device.
209
Select Test and you will be prompted to enter the Bluetooth device name of a device that can accept file transfers. It may take a few moments after entering the name for the file to begin sending. Accept any prompts that appear on both devices.
212
name: power-management/cycle_resolutions_after_suspend
213
requires: package.name == 'xorg'
214
depends: power-management/suspend_advanced graphics/xrandr_cycle
216
This test will check to make sure that supported video modes work after a suspend and resume. Select Test to begin.
217
command: xrandr_cycle --keyword=after_suspend
220
name: power-management/cycle_resolutions_after_suspend_auto
221
requires: package.name == 'xorg'
222
depends: power-management/suspend_advanced graphics/xrandr_cycle
224
This test will check to make sure supported video modes work after a suspend and resume.
225
This is done automatically by taking screenshots and uploading them as an attachment.
226
command: xrandr_cycle --keyword=after_suspend
229
name: power-management/xrandr_screens_after_suspend.tar.gz
230
depends: power-management/cycle_resolutions_after_suspend_auto
231
command: [ -e $CHECKBOX_DATA/xrandr_screens_after_suspend.tgz ] && cat $CHECKBOX_DATA/xrandr_screens_after_suspend.tgz
234
name: power-management/usb_storage_after_suspend
235
depends: power-management/suspend_advanced
238
This will test that USB functionality is restored after a suspend and resume cycle.
239
1. Plug in at least one USB storage device if one is not already connected.
240
2. Click Test to begin.
242
If the test is successful, you'll notice that Yes is now selected. Otherwise, No shoud be selected.
245
name: power-management/record_playback_after_suspend
246
depends: power-management/suspend_advanced
248
device.category == 'AUDIO'
249
package.name == 'alsa-base'
250
command: alsa_record_playback
252
This will check to make sure that your audio device works properly after a suspend and resume. You can use either internal or external microphone and speakers.
254
To execute this test, make sure your speaker and microphone are NOT muted and the volume is set sufficiently loud to record and play audio. Select Test and then speak into your microphone. After a few seconds, your speech will be played back to you.
256
Did you hear your speech played back?
259
name: power-management/hibernate_advanced
260
depends: power-management/rtc
261
requires: package.name == 'pm-utils'
263
command: sleep_test -s disk -w 120 --debug
265
This will check to make sure your system can successfully hibernate (if supported).
267
Select Test to begin. The system will hibernate and should wake itself within 5 minutes. If your system does not wake itself after 5 minutes, please press the power button to wake the system manually. If the system fails to resume from hibernate, please restart System Testing and mark this test as Failed.
269
Did the system successfully hibernate and did it work properly after waking up?
272
55
name: power-management/fwts_wakealarm
273
56
_description: Run Colin Kings FWTS wakealarm test