Merge lp:~bladernr/opencompute/ocp-cleanup into lp:opencompute/checkbox

[Jeff Lane ]

Merged Jeff Lane's OCP-Checkbox cleanup branch

[Jeff Lane  (bladernr)]

jobs: removed unnecessary jobs files
scripts: removed unnecessary scripts
po/POTFILES.in: removed refs to deleted job files

[Jeff Marcom (jeffmarcom)]

Some of the files removed from the scripts directory seem to be still in po/POTFILES.in,

like this one:
scripts/keyboard_test

Also, please make sure that whatever jobs are removed here, the corresponding unittest for them are removed as well.

Sorry :/

review: Needs Fixing

[Jeff Lane  (bladernr)]

Oh... snap. Good points, I didn't think that there would be actual
scripts in the POTILEs list...

Nor did I think about unit tests for them... good call.

On Sat, Aug 17, 2013 at 3:28 PM, Jeff Marcom <email address hidden> wrote:
> Review: Needs Fixing
>
> Some of the files removed from the scripts directory seem to be still in po/POTFILES.in,
>
> like this one:
> scripts/keyboard_test
>
>
> Also, please make sure that whatever jobs are removed here, the corresponding unittest for them are removed as well.
>
> Sorry :/
> --
> https://code.launchpad.net/~bladernr/opencompute/ocp-cleanup/+merge/179783
> You are the owner of lp:~bladernr/opencompute/ocp-cleanup.

--
Jeff Lane - Server and Cloud Certification and Tools Development
Ubuntu Ham: W4KDH
Freenode IRC: bladernr or bladernr_
gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417 C466 4ABD 3635 3A14 B2DD

[lp:~bladernr/opencompute/ocp-cleanup]

2145. By Jeff Lane  on 2013-08-19

po/POTFILES.in - Removed refs to deleted scripts.

2146. By Jeff Lane  on 2013-08-19

Removed refs to deleted job files in setup.cfg. Verified unit tests don't error because of missing job files.

[Jeff Lane  (bladernr)]

fixed

[Jeff Lane  (bladernr)]

whoops resumit... heh

review: Needs Resubmitting

[Jeff Marcom (jeffmarcom)]

Awesome, thanks

review: Approve

=== modified file 'debian/changelog'
--- debian/changelog	2013-08-06 16:43:05 +0000
+++ debian/changelog	2013-08-19 20:47:35 +0000
@@ -12,5 +12,9 @@
   * data/ - Cleanup, removed unnecessary data files, dirs and whitelists
     bin/ - all checkbox launchers now default to 
     opencompute-ready-local.whitelist
+  * jobs/, po/, scripts/ - Cleanup, removed unnecessary job and scritp files
+    and their references in po/POTFILES.in
+    checkbox/tests/ - Cleaned up unit tests that were looking for things
+    removed in this merge.
 
  -- Jeff Marcom <[e-mail]>  Wed, 31 Jul 2013 19:36:52 -0400

=== removed file 'jobs/audio.txt.in'
--- jobs/audio.txt.in	2013-07-05 16:43:48 +0000
+++ jobs/audio.txt.in	1970-01-01 00:00:00 +0000
@@ -1,222 +0,0 @@
-plugin: shell 
-name: audio/list_devices
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
-command: cat /proc/asound/cards
-_description: Test to detect audio devices
-
-plugin: manual
-name: audio/playback_auto
-depends: audio/list_devices
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- package.name == 'pulseaudio-utils'
-command: audio_settings store --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --device=pci --volume=50; gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! autoaudiosink'; EXIT_CODE=$?; audio_settings restore --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     This test will check that internal speakers work correctly
- STEPS:
-     1. Make sure that no external speakers or headphones are connected
-        If testing a desktop, external speakers are allowed
-     2. Click the Test button to play a brief tone on your audio device
- VERIFICATION:
-     Did you hear a tone?
-
-plugin: manual
-name: audio/playback_hdmi
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- package.name == 'pulseaudio-utils'
-command:
- audio_settings store --verbose --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --verbose --device=hdmi --volume=50; gst_pipeline_test -t 2 --device hdmi 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! autoaudiosink'; EXIT_CODE=$?; audio_settings restore --verbose --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     HDMI audio interface verification
- STEPS:
-     1. Plug an external HDMI device with sound (Use only one HDMI/DisplayPort interface at a time for this test)
-     2. Click the Test button
- VERIFICATION:
-     Did you hear the sound from the HDMI device?
-
-plugin: manual
-name: audio/playback_displayport
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- package.name == 'pulseaudio-utils'
-command:
- audio_settings store --verbose --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --verbose --device=hdmi --volume=50; gst_pipeline_test -t 2 --device hdmi 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! autoaudiosink'; EXIT_CODE=$?; audio_settings restore --verbose --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     DisplayPort audio interface verification
- STEPS:
-     1. Plug an external DisplayPort device with sound (Use only one HDMI/DisplayPort interface at a time for this test)
-     2. Click the Test button
- VERIFICATION:
-     Did you hear the sound from the DisplayPort device?
-
-plugin: manual
-name: audio/playback_headphones
-depends: audio/list_devices
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- package.name == 'pulseaudio-utils'
-command: audio_settings store --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --device=pci --volume=50; gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! autoaudiosink'; EXIT_CODE=$?; audio_settings restore --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     This test will check that headphones connector works correctly
- STEPS:
-     1. Connect a pair of headphones to your audio device
-     2. Click the Test button to play a sound to your audio device
- VERIFICATION:
-     Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
-
-plugin: manual
-name: audio/alsa_record_playback_internal
-depends: audio/playback_auto
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'pulseaudio-utils'
- package.name == 'gstreamer1.0-plugins-good' or package.name == 'gstreamer0.10-plugins-good'
-command: audio_settings store --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --device=pci --volume=50; alsa_record_playback; EXIT_CODE=$?; audio_settings restore --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     This test will check that recording sound using the onboard microphone works correctly
- STEPS:
-     1. Disconnect any external microphones that you have plugged in
-     2. Click "Test", then speak into your internal microphone
-     3. After a few seconds, your speech will be played back to you.
- VERIFICATION:
-     Did you hear your speech played back?
-
-plugin: manual
-name: audio/alsa_record_playback_external
-depends: audio/playback_headphones
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'pulseaudio-utils'
- package.name == 'gstreamer1.0-plugins-good' or package.name == 'gstreamer0.10-plugins-good'
-command: audio_settings store --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --device=pci --volume=50; alsa_record_playback; EXIT_CODE=$?; audio_settings restore --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     This test will check that recording sound using an external microphone works correctly
- STEPS:
-     1. Connect a microphone to your microphone port
-     2. Click "Test", then speak into the external microphone
-     3. After a few seconds, your speech will be played back to you
- VERIFICATION:
-     Did you hear your speech played back?
-
-plugin: manual
-name: audio/alsa_record_playback_usb
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'pulseaudio-utils'
- package.name == 'gstreamer1.0-plugins-good' or package.name == 'gstreamer0.10-plugins-good'
-command: audio_settings store --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --device=usb --volume=50; alsa_record_playback; EXIT_CODE=$?; audio_settings restore --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     This test will check that a USB audio device works correctly
- STEPS:
-     1. Connect a USB audio device to your system
-     2. Click "Test", then speak into the microphone
-     3. After a few seconds, your speech will be played back to you
- VERIFICATION:
-     Did you hear your speech played back through the USB headphones?
-
-plugin: shell
-name: audio/alsa_record_playback_automated
-requires:
- package.name == 'python3-gi'
- package.name == 'gir1.2-gstreamer-1.0'
- package.name == 'libgstreamer1.0-0'
- package.name == 'gstreamer1.0-plugins-good'
- package.name == 'gstreamer1.0-pulseaudio'
- package.name == 'alsa-base'
- device.category == 'AUDIO'
-command: audio_test
-_description:
- Play back a sound on the default output and listen for it on the 
- default input.
-
-plugin: shell
-name: audio/alsa_info_collect
-command: alsa_info --no-dialog --no-upload --output ${CHECKBOX_DATA}/alsa_info.log
-_description:
- Collect audio-related system information. This data can be used to
- simulate this computer's audio subsystem and perform more detailed tests
- under a controlled environment.
-
-plugin: attachment
-name: audio/alsa_info_attachment
-depends: audio/alsa_info_collect
-command: [ -e ${CHECKBOX_DATA}/alsa_info.log ] && cat ${CHECKBOX_DATA}/alsa_info.log
-_description:
- Attaches the audio hardware data collection log to the results.
-
-plugin: manual
-name: audio/channels
-command: speaker-test -c 2 -l 1 -t wav
-_description:
- PURPOSE:
-     Check that the various audio channels are working properly
- STEPS:
-     1. Click the Test button
- VERIFICATION:
-     You should clearly hear a voice from the different audio channels
-
-plugin: shell
-name: audio/check_volume
-requires:
- package.name == 'pulseaudio-utils'
- device.category == 'AUDIO'
-command: volume_test --minvol 1 --maxvol 100
-_description:
- This test will verify that the volume levels are at an acceptable level on
- your local system.  The test will validate that the volume is greater than
- or equal to minvol and less than or equal to maxvol for all sources (inputs)
- and sinks (outputs) recognized by PulseAudio.  It will also validate that the
- active source and sink are not muted.  You should not manually adjust the 
- volume or mute before running this test.
-
-plugin: manual
-name: audio/external-lineout
-_description:
- PURPOSE:
-      Check that external line out connection works correctly
- STEPS:
-      1. Insert cable to speakers (with built-in amplifiers) on the line out port
-      2. Open system sound preferences, 'Output' tab, select 'Line-out' on the connector list. Click the Test button
-      3. On the system sound preferences, select 'Internal Audio' on the device list and click 'Test Speakers' to check left and right channel
- VERIFICATION:
-      1. Do you hear a sound in the speakers? The internal speakers should *not* be muted automatically
-      2. Do you hear the sound coming out on the corresponding channel?
-
-plugin: manual
-name: audio/external-linein
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
- package.name == 'pulseaudio-utils'
- package.name == 'gstreamer1.0-plugins-good' or package.name == 'gstreamer0.10-plugins-good'
-command: audio_settings store --file=$CHECKBOX_DATA/pulseaudio_settings; audio_settings set --device=pci --volume=50; alsa_record_playback; EXIT_CODE=$?; audio_settings restore --file=$CHECKBOX_DATA/pulseaudio_settings; exit $EXIT_CODE
-_description:
- PURPOSE:
-     Check that external line in connection works correctly
- STEPS:
-     1. Use a cable to connect the line in port to an external line out source.
-     2. Open system sound preferences, 'Input' tab, select 'Line-in' on the connector list. Click the Test button
-     3. After a few seconds, your recording will be played back to you.
- VERIFICATION:
-     Did you hear your recording?

=== removed file 'jobs/bluetooth.txt.in'
--- jobs/bluetooth.txt.in	2013-01-11 08:49:44 +0000
+++ jobs/bluetooth.txt.in	1970-01-01 00:00:00 +0000
@@ -1,90 +0,0 @@
-
-plugin: shell
-name: bluetooth/detect-output
-requires:
- package.name == 'bluez'
- device.category == 'BLUETOOTH'
-command:
- if rfkill list bluetooth | grep -q 'Hard blocked: yes'; then
-   echo "rfkill shows BT is hard blocked"
- fi
- if rfkill list bluetooth | grep -q 'Soft blocked: yes'; then
-   echo "rfkill shows BT is soft blocked, removing before testing"
-   rfkill unblock bluetooth
-   sleep 3
- fi
- output=$(hcitool dev | tail -n+2 | awk '{print $2}' | tee $CHECKBOX_DATA/bluetooth_address)
- echo "$output"
- if [ -z "$output" ]; then
-     "BT hardware not available"
-     exit 1
- fi
-_description:
- Automated test to store bluetooth device information in checkbox report
-
-plugin: manual
-name: bluetooth/browse-files
-depends: bluetooth/detect-output
-_description:
- PURPOSE:
-     This test will check that bluetooth connection works correctly
- STEPS:
-     1. Enable bluetooth on any mobile device (PDA, smartphone, etc.)
-     2. Click on the bluetooth icon in the menu bar
-     3. Select 'Setup new device'
-     4. Look for the device in the list and select it
-     5. In the device write the PIN code automatically chosen by the wizard
-     6. The device should pair with the computer
-     7. Right-click on the bluetooth icon and select browse files
-     8. Authorize the computer to browse the files in the device if needed
-     9. You should be able to browse the files
- VERIFICATION:
-     Did all the steps work?
-
-plugin: manual
-name: bluetooth/file-transfer
-depends: bluetooth/browse-files bluetooth/detect-output
-_description:
- PURPOSE:
-     This test will check that you can transfer information through a bluetooth connection
- STEPS:
-     1. Make sure that you're able to browse the files in your mobile device
-     2. Copy a file from the computer to the mobile device
-     3. Copy a file from the mobile device to the computer
- VERIFICATION:
-     Were all files copied correctly?
-
-plugin: manual
-name: bluetooth/audio
-depends: bluetooth/detect-output
-command: arecord -d 5 -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE
-_description:
- PURPOSE:
-     This test will check that you can record and hear audio using a bluetooth audio device
- STEPS:
-     1. Enable the bluetooth headset
-     2. Click on the bluetooth icon in the menu bar
-     3. Select 'Setup new device'
-     4. Look for the device in the list and select it
-     5. In the device write the PIN code automatically chosen by the wizard
-     6. The device should pair with the computer
-     7. Click "Test" to record for five seconds and reproduce in the bluetooth device
- VERIFICATION:
-     Did you hear the sound you recorded in the bluetooth
-
-plugin: manual
-name: bluetooth/HID
-depends: bluetooth/detect-output
-command: keyboard_test
-_description:
- PURPOSE:
-     This test will check that you can use a BlueTooth HID device
- STEPS:
-     1. Enable either a BT mouse or keyboard
-     2. Click on the bluetooth icon in the menu bar
-     3. Select 'Setup new device'
-     4. Look for the device in the list and select it
-     5. For mice, perform actions such as moving the pointer, right and left button clicks and double clicks
-     6. For keyboards, click the Test button to lauch a small tool. Enter some text into the tool and close it.
- VERIFICATION:
-     Did the device work as expected?

=== removed file 'jobs/camera.txt.in'
--- jobs/camera.txt.in	2013-05-03 14:31:50 +0000
+++ jobs/camera.txt.in	1970-01-01 00:00:00 +0000
@@ -1,48 +0,0 @@
-plugin: shell
-name: camera/detect
-requires:
- device.category == 'CAPTURE'
-command: camera_test detect
-_description: This Automated test attempts to detect a camera.
-
-plugin: user-verify
-name: camera/display
-depends: camera/detect
-requires:
- device.category == 'CAPTURE'
-command: camera_test display
-_description:
- PURPOSE:
-     This test will check that the built-in camera works
- STEPS:
-     1. Click on Test to display a video capture from the camera for ten seconds.
- VERIFICATION:
-     Did you see the video capture?
-
-plugin: user-verify
-name: camera/still
-depends: camera/detect
-requires:
- package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- package.name == 'eog'
- package.name == 'fswebcam' or package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- device.category == 'CAPTURE'
-command: camera_test still
-_description:
- PURPOSE:
-     This test will check that the built-in camera works
- STEPS:
-     1. Click on Test to display a still image from the camera for ten seconds.
- VERIFICATION:
-     Did you see the image?
-
-plugin: shell
-name: camera/multiple-resolution-images
-depends: camera/detect
-requires:
- package.name == 'fswebcam' or package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
- device.category == 'CAPTURE'
-command: camera_test resolutions
-_description:
-  Takes multiple pictures based on the resolutions supported by the camera and
-  validates their size and that they are of a valid format.

=== removed file 'jobs/codecs.txt.in'
--- jobs/codecs.txt.in	2012-06-07 12:26:26 +0000
+++ jobs/codecs.txt.in	1970-01-01 00:00:00 +0000
@@ -1,29 +0,0 @@
-plugin: manual
-name: codecs/ogg-vorbis
-requires:
- package.name == 'gstreamer0.10-plugins-base' or package.name == 'gstreamer1.0-plugins-base'
- package.name == 'totem' and package.name == 'ubuntu-sounds'
-command: totem /usr/share/sounds/ubuntu/stereo/system-ready.ogg
-_description:
- PURPOSE:
-    This test will verify your system's ability to play Ogg Vorbis audio files.
- STEPS:
-    1. Click Test to play an Ogg Vorbis file (.ogg)
-    2. Please close the player to proceed.
- VERIFICATION:
-    Did the sample play correctly?
-
-plugin: manual
-name: codecs/wav
-requires:
- package.name == 'gstreamer0.10-plugins-good' or package.name == 'gstreamer1.0-plugins-good'
- package.name == 'totem' and package.name == 'alsa-utils'
-command: totem /usr/share/sounds/alsa/Noise.wav
-_description:
- PURPOSE:
-    This test will verify your system's ability to play Wave Audio files.
- STEPS:
-    1. Select Test to play a Wave Audio format file (.wav)
-    2. Please close the player to proceed.
- VERIFICATION:
-    Did the sample play correctly?

=== removed file 'jobs/daemons.txt.in'
--- jobs/daemons.txt.in	2012-10-09 15:21:35 +0000
+++ jobs/daemons.txt.in	1970-01-01 00:00:00 +0000
@@ -1,66 +0,0 @@
-plugin: shell
-name: daemons/atd
-requires: package.name == 'at'
-command: pgrep -f '/usr/sbin/atd' >/dev/null
-_description: Test if the atd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/cron
-requires: package.name == 'cron'
-command: pgrep -f '/usr/sbin/cron' >/dev/null
-_description: Test if the cron daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/cupsd
-requires: package.name == 'cupsys'
-command: pgrep -f '/usr/sbin/cupsd' >/dev/null
-_description: Test if the cupsd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/getty
-requires: package.name == 'util-linux'
-command: pgrep -f '/sbin/getty' >/dev/null
-_description: Test if the getty daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/init
-requires: package.name == 'upstart'
-command: pgrep -f '/sbin/init' >/dev/null
-_description: Test if the init daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/klogd
-requires: package.name == 'klogd'
-command: pgrep -f '/sbin/klogd' >/dev/null
-_description: Test if the klogd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/nmbd
-requires: package.name == 'samba'
-command: pgrep -f '/usr/sbin/nmbd' >/dev/null
-_description: Test if the nmbd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/smbd
-requires: package.name == 'samba'
-command: pgrep -f '/usr/sbin/smbd' >/dev/null
-_description: Test if the smbd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/syslogd
-requires: package.name == 'syslogd'
-command: pgrep -f '/sbin/syslogd' >/dev/null
-_description: Test if the syslogd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/udevd
-requires:
- package.name == 'udevd'
-command: pgrep -f '/sbin/udevd' >/dev/null
-_description: Test if the udevd daemon is running when the package is installed.
-
-plugin: shell
-name: daemons/winbindd
-requires: package.name == 'winbind'
-command: pgrep -f '/usr/sbin/winbindd' >/dev/null
-_description: Test if the winbindd daemon is running when the package is installed.

=== removed file 'jobs/esata.txt.in'
--- jobs/esata.txt.in	2013-03-07 07:46:10 +0000
+++ jobs/esata.txt.in	1970-01-01 00:00:00 +0000
@@ -1,37 +0,0 @@
-plugin: user-interact
-name: esata/insert
-command: removable_storage_watcher insert ata_serial_esata
-_description:
- PURPOSE:
-     This test will check the system can detect the insertion of an eSATA HDD
- STEPS:
-     1. Click 'Test' to begin the test. This test will
-        timeout and fail if the insertion has not been detected within 20 seconds.
-     2. Plug an eSATA HDD into an available eSATA port.
- VERIFICATION:
-     The verification of this test is automated. Do not change the automatically
-     selected result
-
-plugin: shell
-name: esata/storage-test
-user: root
-depends: esata/insert
-command: removable_storage_test -s 268400000 ata_serial_esata
-_description:
- This is an automated test which performs read/write operations on an attached
- eSATA HDD
-
-plugin: user-interact
-name: esata/remove
-depends: esata/storage-test
-command: removable_storage_watcher remove ata_serial_esata
-_description:
- PURPOSE:
-     This test will check the system can detect the removal of an eSATA HDD
- STEPS:
-     1. Click 'Test' to begin the test. This test will timeout and fail if
-        the removal has not been detected within 20 seconds.
-     2. Remove the previously attached eSATA HDD from the eSATA port.
- VERIFICATION:
-     The verification of this test is automated. Do not change the automatically
-     selected result

=== removed file 'jobs/expresscard.txt.in'
--- jobs/expresscard.txt.in	2012-10-23 21:52:31 +0000
+++ jobs/expresscard.txt.in	1970-01-01 00:00:00 +0000
@@ -1,10 +0,0 @@
-plugin: manual
-name: expresscard/verification
-_description:
- PURPOSE:
-     This will verify that an ExpressCard slot can detect inserted devices.
-     If you do not have an ExpressCard slot, please skip test.
- STEPS:
-     1. Plug an ExpressCard device into the ExpressCard slot
- VERIFICATION:
-     Was the device correctly detected?

=== removed file 'jobs/fingerprint.txt.in'
--- jobs/fingerprint.txt.in	2013-07-05 16:43:48 +0000
+++ jobs/fingerprint.txt.in	1970-01-01 00:00:00 +0000
@@ -1,29 +0,0 @@
-plugin: manual
-name: fingerprint/login
-_description:
- PURPOSE:
-    This test will verify that a fingerprint reader will work properly for logging into your system. This test case assumes that there's a testing account from which test cases are run and a personal account that the tester uses to verify the fingerprint reader
- STEPS:
-    1. Click on the User indicator on the left side of the panel (your user name).
-    2. Select "Switch User Account"
-    3. On the LightDM screen select your username.
-    4. Use the fingerprint reader to login.
-    5. Click on the user switcher applet.
-    6. Select the testing account to continue running tests.
- VERIFICATION:
-    Did the authentication procedure work correctly?
-
-plugin: manual
-name: fingerprint/unlock
-_description:
- PURPOSE:
-    This test will verify that a fingerprint reader can be used to unlock a locked system.
- STEPS:
-    1. Click on the Session indicator (Cog icon on the Left side of the panel) .
-    2. Select 'Lock screen'.
-    3. Press any key or move the mouse.
-    4. A window should appear that provides the ability to unlock either typing your password or using fingerprint authentication.
-    5. Use the fingerprint reader to unlock.
-    6. Your screen should be unlocked.
- VERIFICATION:
-    Did the authentication procedure work correctly?

=== removed file 'jobs/firewire.txt.in'
--- jobs/firewire.txt.in	2013-03-07 07:46:10 +0000
+++ jobs/firewire.txt.in	1970-01-01 00:00:00 +0000
@@ -1,38 +0,0 @@
-plugin: user-interact
-name: firewire/insert
-command: removable_storage_watcher insert firewire
-_description:
- PURPOSE:
-     This test will check the system can detect the insertion of a FireWire HDD
- STEPS:
-     1. Click 'Test' to begin the test. This test will
-        timeout and fail if the insertion has not been detected within 20 seconds.
-     2. Plug a FireWire HDD into an available FireWire port.
- VERIFICATION:
-     The verification of this test is automated. Do not change the automatically
-     selected result
-
-plugin: shell
-name: firewire/storage-test
-user: root
-depends: firewire/insert
-command: removable_storage_test -s 268400000 firewire
-_description:
- This is an automated test which performs read/write operations on an attached
- FireWire HDD
-
-plugin: user-interact
-name: firewire/remove
-depends: firewire/storage-test
-command: removable_storage_watcher remove firewire
-_description:
- PURPOSE:
-     This test will check the system can detect the removal of a FireWire HDD
- STEPS:
-     1. Click 'Test' to begin the test. This test will timeout and fail if
-        the removal has not been detected within 20 seconds.
-     2. Remove the previously attached FireWire HDD from the FireWire port.
- VERIFICATION:
-     The verification of this test is automated. Do not change the automatically
-     selected result
-

=== removed file 'jobs/floppy.txt.in'
--- jobs/floppy.txt.in	2011-07-07 10:00:04 +0000
+++ jobs/floppy.txt.in	1970-01-01 00:00:00 +0000
@@ -1,13 +0,0 @@
-plugin: local
-name: floppy/check
-requires: device.driver == 'floppy'
-_description: Floppy test
-command:
- cat <<'EOF' | run_templates -t -s 'udev_resource | filter_templates -w "driver=floppy"'
- plugin: shell
- name: floppy/check_`ls /sys$path/driver/*/*/*/block`
- requires: device.path == "$path"
- description: Floppy test for $product
- user: root
- command: floppy_test /dev/`ls /sys$path/driver/*/*/*/block`
- EOF

=== removed file 'jobs/graphics.txt.in'
--- jobs/graphics.txt.in	2013-05-10 13:03:39 +0000
+++ jobs/graphics.txt.in	1970-01-01 00:00:00 +0000
@@ -1,223 +0,0 @@
-plugin: shell
-name: graphics/driver_version
-command: graphics_driver
-_description: Parses Xorg.0.Log and discovers the running X driver and version
-
-plugin: shell
-name: graphics/xorg-version
-requires: package.name == "x11-utils"
-command: xdpyinfo | grep "^X.Org version" | cut -d ':' -f 2 | tr -d ' '
-_description: Test to output the Xorg version
-
-plugin: manual
-name: graphics/resolution-change
-depends: graphics/xorg-version
-_description:
- PURPOSE:
-     This test will verify that the GUI is usable after manually changing resolution
- STEPS:
-     1. Open the Displays application
-     2. Select a new resolution from the dropdown list
-     3. Click on Apply
-     4. Select the original resolution from the dropdown list
-     5. Click on Apply
- VERIFICATION:
-     Did the resolution change as expected?
-
-plugin: shell
-name: graphics/xorg-process
-requires:
- package.name == 'xorg'
- package.name == 'procps'
-command: pgrep -f '/usr/bin/X' >/dev/null
-_description: Test that the X process is running.
-
-plugin: shell
-name: graphics/xorg-failsafe
-requires: package.name == 'xorg'
-command: ! test -e /var/log/Xorg.failsafe.log
-_description: Test that the X is not running in failsafe mode.
-
-plugin: user-verify
-name: graphics/resolution
-requires:
- device.category == 'VIDEO'
-command: resolution_test
-_description:
- PURPOSE:
-     This test will verify the default display resolution
- STEPS:
-     1. This display is using the following resolution:
- INFO:
-     $output
- VERIFICATION:
-     Is this acceptable for your display?
-
-plugin: shell
-name: graphics/minimum_resolution
-requires:
- device.category == 'VIDEO'
-command: resolution_test --horizontal 800 --vertical 600
-_description:
- Ensure the current resolution meets or exceeds the recommended minimum
- resolution (800x600). See here for details:
- .
- https://help.ubuntu.com/community/Installation/SystemRequirements
-
-name: graphics/modes
-plugin: shell
-command: graphics_modes_info
-_description: Collect info on graphics modes (screen resolution and refresh rate)
-
-name: graphics/color_depth
-plugin: shell
-command: color_depth_info
-_description: Collect info on color depth and pixel format.
-
-name: graphics/fresh_rate
-plugin: shell
-command: fresh_rate_info
-_description: Collect info on fresh rate.
-
-name: graphics/graphic_memory
-plugin: shell
-command: graphic_memory_info
-_description: Collect info on graphic memory.
-
-plugin: user-verify
-name: graphics/display
-requires: 
- package.name == 'xorg'
- package.name == 'gir1.2-gst-plugins-base-0.10' or package.name == 'gir1.2-gst-plugins-base-1.0'
-command: gst_pipeline_test -t 2 'videotestsrc ! ffmpegcolorspace ! autovideosink'
-_description:
- PURPOSE:
-     This test will test the default display
- STEPS:
-     1. Click "Test" to display a video test.
- VERIFICATION:
-     Do you see color bars and static?
-
-plugin: shell
-name: graphics/VESA_drivers_not_in_use
-command: cat /var/log/Xorg.0.log | perl -e '$a=0;while(<>){$a++ if /Loading.*vesa_drv\.so/;$a-- if /Unloading.*vesa/&&$a}exit 1 if $a'
-_description: Check that VESA drivers are not in use
-
-plugin: user-verify
-name: graphics/cycle_resolution
-requires: package.name == 'xorg'
-depends: graphics/VESA_drivers_not_in_use
-command: xrandr_cycle --screenshot-dir $CHECKBOX_DATA
-_description:
- PURPOSE:
-     This test cycles through the detected video modes
- STEPS:
-     1. Click "Test" to start cycling through the video modes
- VERIFICATION:
-     Did the screen appear to be working for each mode?
-
-plugin: user-verify
-name: graphics/rotation
-depends: graphics/xorg-version
-command: rotation_test
-_description:
- PURPOSE:
-     This test will test display rotation
- STEPS:
-     1. Click "Test" to test display rotation. The display will be rotated every 4 seconds.
-     2. Check if all rotations (normal right inverted left) took place without permanent screen corruption
- VERIFICATION:
-     Did the display rotation take place without without permanent screen corruption?
-
-plugin: shell
-name: graphics/compiz_check
-requires: package.name == 'nux-tools'
-command: set -o pipefail; /usr/lib/nux/unity_support_test -c -p | ansi_parser
-_description: Check that hardware is able to run compiz
-
-plugin: shell
-name: graphics/unity-support
-requires: package.name == 'nux-tools'
-command: set -o pipefail; /usr/lib/nux/unity_support_test -p | ansi_parser
-_description: Check that hardware is able to run Unity 3D
-
-plugin: user-verify
-name: graphics/glxgears
-requires: package.name == 'mesa-utils'
-command: glxgears; true
-_description:
- PURPOSE:
-     This test tests the basic 3D capabilities of your video card
- STEPS:
-     1. Click "Test" to execute an OpenGL demo. Press ESC at any time to close.
-     2. Verify that the animation is not jerky or slow.
- VERIFICATION:
-     1. Did the 3d animation appear?
-     2. Was the animation free from slowness/jerkiness?
-
-plugin: shell
-name: graphics/3d_window_open_close
-requires: package.name == 'mesa-utils'
-command: window_test -t open-close -i 10
-_description: Open and close a 3D window multiple times
-
-plugin: shell
-name: graphics/3d_window_suspend_resume
-requires: package.name == 'mesa-utils'
-command: window_test -t suspend-resume -i 10
-_description: Open, suspend resume and close a 3D window multiple times
-
-plugin: shell
-name: graphics/multi_3d_windows_open_close
-requires: package.name == 'mesa-utils'
-command: window_test -t open-close-multi -i 10 -w 4
-_description: Open and close 4 3D windows multiple times
-
-plugin: shell
-name: graphics/3d_window_move
-requires: package.name == 'mesa-utils'
-command: window_test -t move
-_description: Move a 3D window around the screen
-
-plugin: shell
-name: graphics/screenshot
-requires: package.name == 'fswebcam'
-command: set -o pipefail; camera_test still --device=/dev/external_webcam -f ${CHECKBOX_DATA}/screenshot.jpg -q 2>&1 | ansi_parser
-_description:
- PURPOSE:
-     Take a screengrab of the current screen (logged on Unity desktop)
- STEPS:
-     1. Take picture using USB webcam
- VERIFICATION:
-     Review attachment manually later
-
-plugin: attachment
-name: screenshot.jpg
-depends: graphics/screenshot
-command: base64 ${CHECKBOX_DATA}/screenshot.jpg
-_description: Attaches the screenshot captured in graphics/screenshot.
-
-plugin: shell
-name: graphics/screenshot_fullscreen_video
-requires: package.name == 'fswebcam'
-command:
- dbus-launch gsettings set org.gnome.totem repeat true
- totem --fullscreen ${CHECKBOX_SHARE}/data/video/Ogg_Theora_Video.ogv 2>/dev/null &
- set -o pipefail
- sleep 15 && camera_test still --device=/dev/external_webcam -f ${CHECKBOX_DATA}/screenshot_fullscreen_video.jpg -q 2>&1 | ansi_parser
- sleep 5 && totem --quit 2>/dev/null
- dbus-launch gsettings set org.gnome.totem repeat false
-_description:
- PURPOSE:
-     Take a screengrab of the current screen during fullscreen video playback
- STEPS:
-     1. Start a fullscreen video playback
-     2. Take picture using USB webcam after a few seconds
- VERIFICATION:
-     Review attachment manually later
-
-plugin: attachment
-name: screenshot_fullscreen_video.jpg
-depends: graphics/screenshot_fullscreen_video
-command: base64 ${CHECKBOX_DATA}/screenshot_fullscreen_video.jpg
-_description: Attaches the screenshot captured in graphics/screenshot_fullscreen_video.

=== removed file 'jobs/hibernate.txt.in'
--- jobs/hibernate.txt.in	2013-04-24 13:11:53 +0000
+++ jobs/hibernate.txt.in	1970-01-01 00:00:00 +0000
@@ -1,34 +0,0 @@
-plugin: manual
-name: power-management/hibernate_advanced
-depends: power-management/rtc
-environ: CHECKBOX_DATA
-user: root
-command:
- if type -P fwts >/dev/null; then
-  echo "Calling fwts"
-  fwts_test -l $CHECKBOX_DATA/hibernate-single -f none -s s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120
- else
-  echo "Calling sleep_test"
-  sleep_test -s disk -w 120
- fi
-_description:
- PURPOSE:
-     This test will check to make sure your system can successfully hibernate (if supported)
- STEPS:
-     1. Click on Test
-     2. The system will hibernate and should wake itself within 5 minutes
-     3. If your system does not wake itself after 5 minutes, please press the power button to wake the system manually
-     4. If the system fails to resume from hibernate, please restart System Testing and mark this test as Failed
- VERIFICATION:
-     Did the system successfully hibernate and did it work properly after waking up?
-
-plugin: shell
-name: power-management/hibernate-single-log-check
-command: [ -e $CHECKBOX_DATA/hibernate-single.log ] && sleep_test_log_check -v s4 $CHECKBOX_DATA/hibernate-single.log
-_description:
- Automated check of the hibernate log for errors discovered by fwts
-
-plugin: attachment
-name: power-management/hibernate-single-log-attach
-command: [ -e $CHECKBOX_DATA/hibernate-single.log ] && cat $CHECKBOX_DATA/hibernate-single.log
-description: attaches log from single hibernate/resume test to results

=== removed file 'jobs/input.txt.in'
--- jobs/input.txt.in	2013-03-15 20:31:24 +0000
+++ jobs/input.txt.in	1970-01-01 00:00:00 +0000
@@ -1,67 +0,0 @@
-plugin: local
-name: input/pointing
-requires:
- device.category == 'MOUSE' or device.category == 'TOUCH'
-_description: Pointing device tests.
-command:
- cat <<'EOF' | run_templates -t -s 'udev_resource | filter_templates -w "category=MOUSE" -w "category=TOUCH"'
- plugin: manual
- name: input/pointing_`basename $path`
- requires: device.path == "$path"
- description:
-  PURPOSE:
-      This will test your $product device
-  STEPS:
-      1. Move the cursor with your $product.
-  VERIFICATION:
-      Did the cursor move?
- EOF
-
-plugin: manual
-name: input/mouse
-_description:
- PURPOSE:
-     This test will test your pointing device
- STEPS:
-     1. Move the cursor using the pointing device or touch the screen.
-     2. Perform some single/double/right click operations.
- VERIFICATION:
-     Did the pointing device work as expected?
-
-plugin: manual
-name: input/keyboard
-command: keyboard_test
-requires: device.category == 'KEYBOARD'
-_description:
- PURPOSE:
-     This test will test your keyboard
- STEPS:
-     1. Click on Test
-     2. On the open text area, use your keyboard to type something
- VERIFICATION:
-     Is your keyboard working properly?
-
-plugin: manual
-name: input/accelerometer_verify
-_description:
- PURPOSE:
-     Manual detection of accelerometer.
- STEPS:
-     1. Look at the specifications for your system.
- VERIFICATION:
-     Is this system supposed to have an accelerometer?
-
-plugin: user-interact
-name: input/accelerometer
-user: root
-depends: input/accelerometer_verify
-command: accelerometer_test -m
-_description:
- PURPOSE:
-     This test will test your accelerometer to see if it is detected
-     and operational as a joystiq device. 
- STEPS:
-     1. Click on Test
-     2. Tilt your hardware in the directions onscreen until the axis threshold is met. 
- VERIFICATION:
-     Is your accelerometer properly detected? Can you use the device?

=== removed file 'jobs/install.txt.in'
--- jobs/install.txt.in	2012-08-27 20:04:37 +0000
+++ jobs/install.txt.in	1970-01-01 00:00:00 +0000
@@ -1,19 +0,0 @@
-plugin: shell
-name: install/apt-get-gets-updates
-requires: package.name == 'apt'
-user: root
-command: apt-get -d -y --force-yes dist-upgrade
-_description: 
- Tests to see that apt can access repositories and get updates (does
- not install updates). This is done to confirm that you could recover
- from an incomplete or broken update.
-
-plugin: shell
-name: install/oem-config
-requires: package.name == 'oem-config-gtk' and package.name == 'python-xpresser'
-user: root
-environ: CHECKBOX_SHARE
-command: oem_config_test -u 'testaccount1' -p 'testaccount1' -d $CHECKBOX_SHARE/data/images/oem-config/
-_description: 
- Tests oem-config using Xpresser, and then checks that the user has been created successfully.
- Cleans up the newly created user after the test has passed.

=== removed file 'jobs/keys.txt.in'
--- jobs/keys.txt.in	2013-04-19 13:40:29 +0000
+++ jobs/keys.txt.in	1970-01-01 00:00:00 +0000
@@ -1,145 +0,0 @@
-plugin: manual
-name: keys/brightness
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     This test will test the brightness key
- STEPS:
-     1. Press the brightness buttons on the keyboard
- VERIFICATION:
-     Did the brightness change following to your key presses?
-
-plugin: manual
-name: keys/volume
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s '0xe02e,0xe0ae:Volume Down' '0xe030,0xe0b0:Volume Up'
-_description:
- PURPOSE:
-     This test will test the volume keys of your keyboard
- STEPS:
-     1. Click test to open a window on which to test the volume keys.
-     2. If all the keys work, the test will be marked as passed.
-     3. If your computer has no volume keys, Skip this test.
- VERIFICATION:
-     Do the keys work as expected?
-
-plugin: manual
-name: keys/mute
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s '0xe020,0xe0a0:Mute'
-_description:
- PURPOSE:
-     This test will test the mute key of your keyboard
- STEPS:
-     1. Click test to open a window on which to test the mute key.
-     2. If the key works, the test will pass and the window will close.
- VERIFICATION:
-     Does the mute key work as expected?
-
-plugin: manual
-name: keys/sleep
-requires:
- device.category == 'KEYBOARD'
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     This test will test the sleep key
- STEPS:
-     1. Press the sleep key on the keyboard
-     2. Wake your system up by pressing the power button
- VERIFICATION:
-     Did the system go to sleep after pressing the sleep key?
-
-plugin: manual
-name: keys/battery-info
-requires: dmi.product in ['Notebook','Laptop','Portable']
-user: root
-command: key_test -s '0xe071,0xef1:Battery Info'
-_description:
- PURPOSE:
-     This test will test the battery information key
- STEPS:
-     If you do not have a Battery Button, skip this test
-     1. Click Test to begin
-     2. Press the Battery Info button (or combo like Fn+F3)
-     3: Close the Power Statistics tool if it opens
- VERIFICATION:
-     Did the Battery Info key work as expected?
-
-plugin: manual
-name: keys/wireless
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     This test will test the wireless key
- STEPS:
-     1. Press the wireless key on the keyboard
-     2. Check that the wifi LED turns off or changes color
-     3. Check that wireless is disabled
-     4. Press the same key again
-     5. Check that the wifi LED turns on or changes color
-     6. Check that wireless is enabled
- VERIFICATION:
-     Did the wireless turn off on the first press and on again on the second?
-     (NOTE: the LED functionality will be reviewed in a following test. Please
-     only consider the functionality of the wifi itself here.)
-
-plugin: user-interact
-name: keys/media-control
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s 0xe010,0xe090:Previous 0xe024,0xe0a4:Stop 0xe019,0xe099:Next 0xe022,0xe0a2:Play
-_description:
- PURPOSE:
-     This test will test the media keys of your keyboard
- STEPS:
-     1. Click test to open a window on which to test the media keys.
-     2. If all the keys work, the test will be marked as passed.
-     3. If your computer has no media keys, Skip this test.
- VERIFICATION:
-     Do the keys work as expected?
-
-plugin: user-interact
-name: keys/super
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s '0xe05b,0xe0db:Left Super Key'
-_description:
- PURPOSE:
-     This test will test the super key of your keyboard
- STEPS:
-     1. Click test to open a window on which to test the super key.
-     2. If the key works, the test will pass and the window will close.
- VERIFICATION:
-     Does the super key work as expected?
-
-plugin: manual
-name: keys/video-out
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     Validate that the External Video hot key is working as expected
- STEPS:
-     1. Plug in an external monitor
-     2. Press the display hot key to change the monitors configuration
- VERIFICATION:
-     Check that the video signal can be mirrored, extended, displayed on external or onboard only.
-
-plugin: manual
-name: keys/touchpad
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     Verify touchpad hotkey toggles touchpad functionality on and off
- STEPS:
-     1. Verify the touchpad is functional
-     2. Tap the touchpad toggle hotkey
-     3. Tap the touchpad toggle hotkey again
- VERIFICATION:
-     Verify the touchpad has been disabled and re-enabled.

=== removed file 'jobs/led.txt.in'
--- jobs/led.txt.in	2013-04-24 03:40:17 +0000
+++ jobs/led.txt.in	1970-01-01 00:00:00 +0000
@@ -1,197 +0,0 @@
-plugin: manual
-name: led/power
-_description:
- PURPOSE:
-     Power LED verification
- STEPS:
-     1. Power LED should be on while device is switched on
- VERIFICATION:
-     Does the power LED light as expected?
-
-plugin: manual
-name: led/power-blink-suspend
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Power LED verification
- STEPS:
-     1. The Power LED should blink or change color while the system is suspended
- VERIFICATION:
-     Did the Power LED blink or change color while the system was suspended for the previous suspend test?
-
-plugin: manual
-name: led/suspend
-_description:
- PURPOSE:
-     Suspend LED verification. If your system does not have a dedicated Suspend
-     LED, skip this test.
- STEPS:
-     1. The Suspend LED should blink or change color while the system is
-     supended
- VERIFICATION
-     Did the Suspend LED blink or change color while the system was suspended?
-
-plugin: manual
-name: led/battery-charging
-_description:
- PURPOSE:
-     Validate that the battery light shows charging status
- STEPS:
-     1. Let system run on battery for a while
-     2. Plug in AC plug
- VERIFICATION:
-     Did the battery indicator LED turn orange?
-
-plugin: manual
-name: led/battery-charged
-_description:
- PURPOSE:
-     Validate that the battery LED properly displays charged status
- STEPS:
-     1. Let system run on battery for a short time
-     2. Plug in AC
-     3. Let system run on AC
- VERIFICATION:
-     Does the orange battery LED shut off when system is fully charged?
-
-plugin: manual
-name: led/battery-low
-_description:
- PURPOSE:
-     Validate that the battery LED indicated low power
- STEPS:
-     1. Let system run on battery for several hours
-     2. Monitor battery LED carefully
- VERIFICATION:
-     Does the LED light orange when battery is low?
-
-plugin: manual
-name: led/hdd
-command: led_hdd_test
-_description:
- PURPOSE:
-     HDD LED verification
- STEPS:
-     1. Select "Test" to write and read a temporary file for a few seconds
-     2. HDD LED should light when writing to/reading from HDD
- VERIFICATION:
-     Did the HDD LED light?
-
-plugin: manual
-name: led/numeric-keypad
-command: keyboard_test
-_description:
- PURPOSE:
-     Numeric keypad LED verification
- STEPS:
-     1. Press "Block Num" key to toggle numeric keypad LED
-     2. Click on the "Test" button to open a window to verify your typing
-     3. Type using the numeric keypad both when the LED is on and off
- VERIFICATION:
-     1. Numeric keypad LED status should toggle everytime the "Block Num" key is pressed
-     2. Numbers should only be entered in the keyboard verification window when the LED is on
-
-plugin: manual
-name: led/caps-lock
-_description:
- PURPOSE:
-     Block cap keys LED verification
- STEPS:
-     1. Press "Block Cap Keys" to activate/deactivate cap keys blocking
-     2. Cap Keys LED should be switched on/off every time the key is pressed
- VERIFICATION:
-     Did the Cap Keys LED light as expected?
-
-plugin: manual
-name: led/wlan
-depends: keys/wireless
-_description:
- PURPOSE:
-     WLAN LED verification
- STEPS:
-     1. During the keys/wireless test you should have observed the
-     wireless LED while turning wireless back on.
-     2. WLAN LED should light or change color when wireless is turned on
- VERIFICATION:
-     Did the WLAN LED turn on or change color as expected?
-
-plugin: manual
-name: led/wlan-disabled
-depends: keys/wireless
-_description:
- PURPOSE:
-     Validate that WLAN LED shuts off when disabled
- STEPS:
-     1. During the keys/wireless test you should have observed the WLAN LED
-     while performing that test after turning wireless off.
-     2. WLAN LED should turn off or change color when wireless is turned off
- VERIFICATION:
-     Did the WLAN LED turn off or change color as expected?
-
-plugin: manual
-name: led/bluetooth
-depends: bluetooth/detect-output
-_description:
- PURPOSE:
-     Validate that the Bluetooth LED turns on and off when BT is enabled/disabled
- STEPS:
-     1. Switch bluetooth off from a hardware switch (if present)
-     2. Switch bluetooth back on
-     3. Switch bluetooth off from the panel applet
-     4. Switch bluetooth back on
- VERIFICATION:
-     Did the bluetooth LED turn off and on twice?
-
-plugin: manual
-name: led/camera
-depends: camera/detect
-command: camera_test led
-_description:
- PURPOSE:
-     Camera LED verification
- STEPS:
-     1. Select Test to activate camera
-     2. Camera LED should light for a few seconds
- VERIFICATION:
-     Did the camera LED light?
-
-plugin: manual
-name: led/touchpad
-_description:
- PURPOSE:
-     Touchpad LED verification
- STEPS:
-     1. Click on the touchpad button or press key combination to enable/disable touchpad button
-     2. Slide your finger on the touchpad
- VERIFICATION:
-     1. Touchpad LED status should toggle everytime the button is clicked or the key combination is pressed
-     2. When the LED is on, the mouse pointer should move on touchpad usage
-     3. When the LED is off, the mouse pointer should not move on touchpad usage
-
-plugin: manual
-name: led/wireless
-_description:
- PURPOSE:
-     Wireless (WLAN + Bluetooth) LED verification
- STEPS:
-     1. Make sure WLAN connection is established and Bluetooth is enabled.
-     2. WLAN/Bluetooth LED should light
-     3. Switch WLAN and Bluetooth off from a hardware switch (if present)
-     4. Switch them back on
-     5. Switch WLAN and Bluetooth off from the panel applet
-     6. Switch them back on
- VERIFICATION:
-     Did the WLAN/Bluetooth LED light as expected?
-
-plugin: manual
-name: led/mute
-depends: keys/mute
-_description:
- PURPOSE:
-     Audio Mute LED verification. Skip this test if your system does not have
-     a special Audio Mute LED
- STEPS:
-     1. Press the Mute key twice and observe the Audio LED to determine if it
-     either turned off and on or changed colors.
- VERIFICATION:
-     Did the Audio LED turn on and off change color as expected?

=== modified file 'jobs/local.txt.in'
--- jobs/local.txt.in	2013-08-06 16:40:36 +0000
+++ jobs/local.txt.in	2013-08-19 20:47:35 +0000
@@ -1,10 +1,3 @@
-name: __audio__
-plugin: local
-_description: Audio tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/audio.txt?(.in)
-
 name: __benchmarks__
 plugin: local
 _description: Benchmarks tests
@@ -12,27 +5,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/benchmarks.txt?(.in)
 
-name: __bluetooth__
-plugin: local
-_description: Bluetooth tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/bluetooth.txt?(.in)
-
-name: __camera__
-plugin: local
-_description: Camera tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/camera.txt?(.in)
-
-name: __codecs__
-plugin: local
-_description: Codec tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/codecs.txt?(.in)
-
 name: __cpu__
 plugin: local
 _description: CPU tests
@@ -40,13 +12,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/cpu.txt?(.in)
 
-name: __daemons__
-plugin: local
-_description: System Daemon tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/daemons.txt?(.in)
-
 name: __disk__
 plugin: local
 _description: Disk tests
@@ -61,48 +26,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/dcmi_in_band.txt?(.in)
 
-name: __esata__
-plugin: local
-_description: eSATA disk tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/esata.txt?(.in)
-
-name: __fingerprint__
-plugin: local
-_description: Fingerprint reader tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/fingerprint.txt?(.in)
-
-name: __firewire__
-plugin: local
-_description: Firewire disk tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/firewire.txt?(.in)
-
-name: __floppy__
-plugin: local
-_description: Floppy disk tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/floppy.txt?(.in)
-
-name: __graphics__
-plugin: local
-_description: Graphics tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/graphics.txt?(.in)
-
-name: __hibernate__
-plugin: local
-_description: Hibernation tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/hibernate.txt?(.in)
-
 name: __info__
 plugin: local
 _description: Informational tests
@@ -110,20 +33,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/info.txt?(.in)
 
-name: __input__
-plugin: local
-_description: Input Devices tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/input.txt?(.in)
-
-name: __install__
-plugin: local
-_description: Software Installation tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/install.txt?(.in)
-
 name: __ipmi_out_of_band__
 plugin: local
 _description: IPMI out of band tests
@@ -131,27 +40,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/ipmi_out_of_band.txt?(.in)
 
-name: __keys__
-plugin: local
-_description: Hotkey tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/keys.txt?(.in)
-
-name: __led__
-plugin: local
-_description: LED tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/led.txt?(.in)
-
-name: __mediacard__
-plugin: local
-_description: Media Card tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/mediacard.txt?(.in)
-
 name: __memory__
 plugin: local
 _description: Memory tests
@@ -159,13 +47,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/memory.txt?(.in)
 
-name: __rendercheck__
-plugin: local
-_description: Rendercheck tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/rendercheck.txt?(.in)
-
 name: __miscellanea__
 plugin: local
 _description: Miscellaneous tests
@@ -173,13 +54,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/miscellanea.txt?(.in)
 
-name: __monitor__
-plugin: local
-_description: Monitor tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/monitor.txt?(.in)
-
 name: __networking__
 plugin: local
 _description: Networking tests
@@ -194,41 +68,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/optical.txt?(.in)
 
-name: __panel_clock__
-plugin: local
-_description: Panel Clock Verification tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/panel_clock_test.txt?(.in)
-
-name: __panel_reboot__
-plugin: local
-_description: Panel Reboot Verification tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/panel_reboot.txt?(.in)
-
-name: __expresscard__
-plugin: local
-_description: ExpressCard tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/expresscard.txt?(.in)
-
-name: __peripheral__
-plugin: local
-_description: Peripheral tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/peripheral.txt?(.in)
-
-name: __piglit__
-plugin: local
-_description: Piglit tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/piglit.txt?(.in)
-
 name: __power-management__
 plugin: local
 _description: Power Management tests
@@ -236,34 +75,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/power-management.txt?(.in)
 
-name: __server-services__
-plugin: local
-_description: Server Services checks
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/server-services.txt?(.in)
-
-name: __suspend__
-plugin: local
-_description: Suspend tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/suspend.txt?(.in)
-
-name: __touchpad__
-plugin: local
-_description: Touchpad tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/touchpad.txt?(.in)
-
-name: __touchscreen__
-plugin: local
-_description: Touchscreen tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/touchscreen.txt?(.in)
-
 name: __usb__
 plugin: local
 _description: USB tests
@@ -271,13 +82,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/usb.txt?(.in)
 
-name: __user_apps__
-plugin: local
-_description: User Applications
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/user_apps.txt?(.in)
-
 name: __virtualization__
 plugin: local
 _description: Virtualization tests
@@ -285,20 +89,6 @@
   shopt -s extglob
   cat $CHECKBOX_SHARE/jobs/virtualization.txt?(.in)
 
-name: __wireless__
-plugin: local
-_description: Wireless networking tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/wireless.txt?(.in)
-
-name: __mobilebroadband__
-plugin: local
-_description: Mobile broadband tests
-command:
-  shopt -s extglob
-  cat $CHECKBOX_SHARE/jobs/mobilebroadband.txt?(.in)
-
 name: __stress__
 plugin: local
 _description: Stress tests

=== removed file 'jobs/mediacard.txt.in'
--- jobs/mediacard.txt.in	2013-05-06 21:44:33 +0000
+++ jobs/mediacard.txt.in	1970-01-01 00:00:00 +0000
@@ -1,662 +0,0 @@
-plugin: user-interact
-name: mediacard/mmc-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a Multimedia Card (MMC) media
- STEPS:
-     1. Click "Test" and insert an MMC card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/mmc-storage
-depends: mediacard/mmc-insert
-user: root
-command: removable_storage_test -s 67120000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/mmc-insert
- test is run. It tests reading and writing to the MMC card.
-
-plugin: user-interact
-name: mediacard/mmc-remove
-depends: mediacard/mmc-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of the MMC card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the MMC card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/mmc-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of an MMC card after the system has been suspended
- STEPS:
-     1. Click "Test" and insert an MMC card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/mmc-storage-after-suspend
-depends: mediacard/mmc-insert-after-suspend
-user: root
-command: removable_storage_test -s 67120000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/mmc-insert-after-suspend test
- is run. It tests reading and writing to the MMC card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/mmc-remove-after-suspend
-depends: mediacard/mmc-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of an MMC card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the MMC card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/sd-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of an UNLOCKED Secure Digital (SD) media card
- STEPS:
-     1. Click "Test" and insert an UNLOCKED SD card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sd-storage
-depends: mediacard/sd-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/sd-insert
- test is run. It tests reading and writing to the SD card.
-
-plugin: user-interact
-name: mediacard/sd-remove
-depends: mediacard/sd-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of an SD card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the SD card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/sd-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of an UNLOCKED SD card after the system
-     has been suspended
- STEPS:
-     1. Click "Test" and insert an UNLOCKED SD card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sd-storage-after-suspend
-depends: mediacard/sd-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/sd-insert-after-suspend test
- is run. It tests reading and writing to the SD card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/sd-remove-after-suspend
-depends: mediacard/sd-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of an SD card from the systems card reader 
-     after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the SD card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sd-preinserted
-user: root
-requires: device.category == 'CARDREADER'
-command: removable_storage_test -s 268400000 --memorycard -l sdio usb scsi && removable_storage_test --memorycard sdio usb scsi
-_description:
- This is a fully automated version of mediacard/sd-automated and assumes that the
- system under test has a memory card device plugged in prior to checkbox execution.
- It is intended for SRU automated testing.
-
-plugin: user-interact
-name: mediacard/sdhc-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a UNLOCKED Secure Digital High-Capacity 
-     (SDHC) media card
- STEPS:
-     1. Click "Test" and insert an UNLOCKED SDHC card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sdhc-storage
-depends: mediacard/sdhc-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/sdhc-insert
- test is run. It tests reading and writing to the SDHC card.
-
-plugin: user-interact
-name: mediacard/sdhc-remove
-depends: mediacard/sdhc-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of an SDHC card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the SDHC card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/sdhc-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of an UNLOCKED SDHC media card after the 
-     system has been suspended
- STEPS:
-     1. Click "Test" and insert an UNLOCKED SDHC card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sdhc-storage-after-suspend
-depends: mediacard/sdhc-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/sdhc-insert-after-suspend test
- is run. It tests reading and writing to the SDHC card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/sdhc-remove-after-suspend
-depends: mediacard/sdhc-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of an SDHC card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the SDHC card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/cf-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a Compact Flash (CF) media card
- STEPS:
-     1. Click "Test" and insert a CF card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/cf-storage
-depends: mediacard/cf-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/cf-insert
- test is run. It tests reading and writing to the CF card.
-
-plugin: user-interact
-name: mediacard/cf-remove
-depends: mediacard/cf-storage
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of a CF card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the CF card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/cf-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a CF card after the system has been suspended
- STEPS:
-     1. Click "Test" and insert a CF card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/cf-storage-after-suspend
-depends: mediacard/cf-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/cf-insert-after-suspend test
- is run. It tests reading and writing to the CF card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/cf-remove-after-suspend
-depends: mediacard/cf-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of a CF card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the CF card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/sdxc-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a Secure Digital Extended Capacity (SDXC) media card
- STEPS:
-     1. Click "Test" and insert a SDXC card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sdxc-storage
-depends: mediacard/sdxc-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/sdxc-insert
- test is run. It tests reading and writing to the SDXC card.
-
-plugin: user-interact
-name: mediacard/sdxc-remove
-depends: mediacard/sdxc-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of a SDXC card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the SDXC card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/sdxc-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a SDXC card after the system has been suspended
- STEPS:
-     1. Click "Test" and insert a SDXC card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/sdxc-storage-after-suspend
-depends: mediacard/sdxc-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/sdxc-insert-after-suspend test
- is run. It tests reading and writing to the SDXC card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/sdxc-remove-after-suspend
-depends: mediacard/sdxc-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of a SDXC card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the SDXC card from the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/ms-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a Memory Stick (MS) media card
- STEPS:
-     1. Click "Test" and insert a MS card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/ms-storage
-depends: mediacard/ms-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/ms-insert
- test is run. It tests reading and writing to the MS card.
-
-plugin: user-interact
-name: mediacard/ms-remove
-depends: mediacard/ms-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of a MS card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the MS card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/ms-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a MS card after the system has been suspended
- STEPS:
-     1. Click "Test" and insert a MS card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/ms-storage-after-suspend
-depends: mediacard/ms-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/ms-insert-after-suspend test
- is run. It tests reading and writing to the MS card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/ms-remove-after-suspend
-depends: mediacard/ms-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of a MS card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the MS card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/msp-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a Memory Stick Pro (MSP) media card
- STEPS:
-     1. Click "Test" and insert a MSP card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/msp-storage
-depends: mediacard/msp-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/msp-insert
- test is run. It tests reading and writing to the MSP card.
-
-plugin: user-interact
-name: mediacard/msp-remove
-depends: mediacard/msp-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of a MSP card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the MSP card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/msp-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a MSP card after the system has been suspended
- STEPS:
-     1. Click "Test" and insert a MSP card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/msp-storage-after-suspend
-depends: mediacard/msp-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/msp-insert-after-suspend test
- is run. It tests reading and writing to the MSP card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/msp-remove-after-suspend
-depends: mediacard/msp-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of a MSP card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the MSP card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/xd-insert
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a Extreme Digital (xD) media card
- STEPS:
-     1. Click "Test" and insert a xD card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/xd-storage
-depends: mediacard/xd-insert
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/xd-insert
- test is run. It tests reading and writing to the xD card.
-
-plugin: user-interact
-name: mediacard/xd-remove
-depends: mediacard/xd-insert
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects 
-     the removal of a xD card from the systems card reader.
- STEPS:
-     1. Click "Test" and remove the xD card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: user-interact
-name: mediacard/xd-insert-after-suspend
-depends: suspend/suspend_advanced
-command: removable_storage_watcher --memorycard insert sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the systems media card reader can
-     detect the insertion of a xD card after the system has been suspended
- STEPS:
-     1. Click "Test" and insert a xD card into the reader.
-        If a file browser opens up, you can safely close it.
-        (Note: this test will time-out after 20 seconds.)
-     2. Do not remove the device after this test.
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.
-
-plugin: shell
-name: mediacard/xd-storage-after-suspend
-depends: mediacard/xd-insert-after-suspend
-user: root
-command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
-_description:
- This test is automated and executes after the mediacard/xd-insert-after-suspend test
- is run. It tests reading and writing to the xD card after the system has been suspended.
-
-plugin: user-interact
-name: mediacard/xd-remove-after-suspend
-depends: mediacard/xd-insert-after-suspend
-command: removable_storage_watcher --memorycard remove sdio usb scsi
-_description:
- PURPOSE:
-     This test will check that the system correctly detects the removal
-     of a xD card from the systems card reader after the system has been suspended.
- STEPS:
-     1. Click "Test" and remove the xD card from the reader.
-        (Note: this test will time-out after 20 seconds.)
- VERIFICATION:
-     The verification of this test is automated. Do not change the
-     automatically selected result.

=== removed file 'jobs/mobilebroadband.txt.in'
--- jobs/mobilebroadband.txt.in	2013-04-17 20:18:21 +0000
+++ jobs/mobilebroadband.txt.in	1970-01-01 00:00:00 +0000
@@ -1,21 +0,0 @@
-plugin: shell
-name: mobilebroadband/gsm_connection
-requires:
-    package.name == 'network-manager'
-    package.name == 'modemmanager'
-    mobilebroadband.gsm == 'supported'
-user: root
-environ: GSM_CONN_NAME GSM_APN GSM_USERNAME GSM_PASSWORD
-command: trap "nmcli con delete id $GSM_CONN_NAME" EXIT; create_connection mobilebroadband gsm `if [ ${GSM_APN} ]; then echo "--apn=$GSM_APN"; fi` `if [ ${GSM_CONN_NAME} ]; then echo "--name=$GSM_CONN_NAME"; fi` `if [ ${GSM_USERNAME} ]; then echo "--username=$GSM_USERNAME"; fi` `if [ ${GSM_PASSWORD} ]; then echo "--password=$GSM_PASSWORD"; fi` && curl http://start.ubuntu.com/connectivity-check.html --interface `nmcli dev status | awk '/gsm/ {print $1}'`
-_description: Creates a mobile broadband connection for a GSM based modem and checks the connection to ensure it's working.
-
-plugin: shell
-name: mobilebroadband/cdma_connection
-requires:
-    package.name == 'network-manager'
-    package.name == 'modemmanager'
-    mobilebroadband.cdma == 'supported'
-user: root
-environ: CDMA_CONN_NAME CDMA_USERNAME CDMA_PASSWORD
-command: trap "nmcli con delete id $CDMA_CONN_NAME" EXIT; create_connection mobilebroadband cdma `if [ ${CDMA_CONN_NAME} ]; then echo "--name=$CDMA_CONN_NAME"; fi` `if [ ${CDMA_USERNAME} ]; then echo "--username=$CDMA_USERNAME"; fi` `if [ ${CDMA_PASSWORD} ]; then echo "--password=$CDMA_PASSWORD"; fi` && curl http://start.ubuntu.com/connectivity-check.html --interface `nmcli dev status | awk '/gsm/ {print $1}'`
-_description: Creates a mobile broadband connection for a CDMA based modem and checks the connection to ensure it's working.

=== removed file 'jobs/monitor.txt.in'
--- jobs/monitor.txt.in	2013-05-03 20:18:33 +0000
+++ jobs/monitor.txt.in	1970-01-01 00:00:00 +0000
@@ -1,105 +0,0 @@
-plugin: manual
-name: monitor/vga
-requires: display.vga == 'supported'
-_description:
- PURPOSE:
-     This test will check your VGA port. Skip if your system does not have a VGA port.
- STEPS:
-     1. Connect a display (if not already connected) to the VGA port on your system
- VERIFICATION:
-     Was the desktop displayed correctly on both screens?
-
-plugin: manual
-name: monitor/dvi
-requires: display.dvi == 'supported'
-_description:
- PURPOSE:
-     This test will check your DVI port. Skip if your system does not have a DVI port
- STEPS:
-     1. Connect a display (if not already connected) to the DVI port on your system
- VERIFICATION:
-     Was the desktop displayed correctly on both screens?
-
-plugin: manual
-name: monitor/displayport
-requires: display.dp == 'supported'
-_description:
- PURPOSE:
-     This test will check your DisplayPort port. Skip if your system does not have a DisplayPort port
- STEPS:
-     1. Connect a display (if not already connected) to the DisplayPort port on your system
- VERIFICATION:
-     Was the desktop displayed correctly on both screens?
-
-plugin: manual
-name: monitor/hdmi
-requires: display.hdmi == 'supported'
-_description:
- PURPOSE:
-     This test will check your HDMI port. Skip if your system does not have a HDMI port
- STEPS:
-     1. Connect a display (if not already connected) to the HDMI port on your system
- VERIFICATION:
-     Was the desktop displayed correctly on both screens?
-
-plugin: manual
-name: monitor/svideo
-requires: display.svideo == 'supported'
-_description:
- PURPOSE:
-     This test will check your S-VIDEO port. Skip if your system does not have a S-VIDEO port
- STEPS:
-     1. Connect a display (if not already connected) to the S-VIDEO port on your system
- VERIFICATION:
-     Was the desktop displayed correctly on both screens?
-
-plugin: manual
-name: monitor/rca
-requires: display.rca == 'supported'
-_description:
- PURPOSE:
-     This test will check your RCA port. Skip if your system does not have a RCA port
- STEPS:
-     1. Connect a display (if not already connected) to the RCA port on your system
- VERIFICATION:
-     Was the desktop displayed correctly on both screens?
-
-plugin: manual
-name: monitor/multi-head
-requires: dmi.product in ['Desktop','Low Profile Desktop','Tower','Mini Tower']
-_description:
- PURPOSE:
-     This test verifies that multi-monitor output works on your desktop system. This is NOT the same test as the external monitor tests you would run on your laptop. If your video card does not support multiple monitors, please skip this test. You will need two monitors to perform this test.
- STEPS:
-     1. If your second monitor is not already connected, connect it now
-     2. Open the "Displays" tool (open the dash and search for "Displays")
-     3. Configure your output to provide one desktop across both monitors
-     4. Open any application and drag it from one monitor to the next.
- VERIFICATION:
-     Was the stretched desktop displayed correctly across both screens?
-
-plugin: manual
-name: monitor/powersaving
-command: xset dpms force off
-_description:
- PURPOSE:
-     This test will check your monitor power saving capabilities
- STEPS:
-     1. Click "Test" to try the power saving capabilities of your monitor
-     2. Press any key or move the mouse to recover
- VERIFICATION:
-     Did the monitor go blank and turn on again?
-
-plugin: manual
-name: monitor/dim_brightness
-user: root
-command: brightness_test
-_description:
- PURPOSE:
-     This test will test changes to screen brightness
- STEPS:
-     1. Click "Test" to try to dim the screen.
-     2. Check if the screen was dimmed approximately to half of the maximum brightness.
-     3. The screen will go back to the original brightness in 2 seconds.
- VERIFICATION:
-     Was your screen dimmed approximately to half of the maximum brightness?

=== removed file 'jobs/panel_clock_test.txt.in'
--- jobs/panel_clock_test.txt.in	2012-05-10 13:12:45 +0000
+++ jobs/panel_clock_test.txt.in	1970-01-01 00:00:00 +0000
@@ -1,29 +0,0 @@
-name: panel_clock/verify
-plugin: manual
-requires: package.name == 'gnome-system-tools'
-_description:
- PURPOSE:
-    This test will verify that the desktop clock displays the correct date and time
- STEPS:
-    1. Check the clock in the upper right corner of your desktop.
- VERIFICATION:
-    Is the clock displaying the correct date and time for your timezone?
-
-name: panel_clock/test
-plugin: manual
-depends: panel_clock/verify
-requires: package.name == 'gnome-system-tools'
-user: root
-command: date -s "`date -d '1 hour'`"
-_description:
- PURPOSE:
-    This test will verify that the desktop clock synchronizes with the system clock.
- STEPS:
-    1. Click the "Test" button and verify the clock moves ahead by 1 hour.
-    Note: It may take a minute or so for the clock to refresh
-    2. Right click on the clock, then click on "Time & Date Settings..."
-    3. Ensure that your clock application is set to manual.
-    4. Change the time 1 hour back
-    5. Close the window and reboot
- VERIFICATION:
-    Is your system clock displaying the correct date and time for your timezone?

=== removed file 'jobs/panel_reboot.txt.in'
--- jobs/panel_reboot.txt.in	2012-10-09 15:21:35 +0000
+++ jobs/panel_reboot.txt.in	1970-01-01 00:00:00 +0000
@@ -1,11 +0,0 @@
-plugin: manual
-name: panel_reboot_test
-_description:
- PURPOSE:
-    This test will verify that you can reboot your system from the desktop menu
- STEPS:
-    1. Click the Gear icon in the upper right corner of the desktop and click on "Shut Down"
-    2. Click the "Restart" button on the left side of the Shut Down dialog
-    3. After logging back in, restart System Testing and it should resume here
- VERIFICATION:
-    Did your system restart and bring up the GUI login cleanly?

=== removed file 'jobs/peripheral.txt.in'
--- jobs/peripheral.txt.in	2013-01-21 22:21:29 +0000
+++ jobs/peripheral.txt.in	1970-01-01 00:00:00 +0000
@@ -1,38 +0,0 @@
-plugin: manual
-name: peripheral/printer
-_description:
- PURPOSE:
-    This test will verify that a network printer is usable
- STEPS:
-    1. Make sure that a printer is available in your network
-    2. Click on the Gear icon in the upper right corner and then click on Printers
-    3. If the printer isn't already listed, click on Add
-    4. The printer should be detected and proper configuration values  should be displayed
-    5. Print a test page
- VERIFICATION:
-    Were you able to print a test page to the network printer?
-
-plugin: manual
-name: peripheral/external-usb-modem
-command: network_check
-_description:
- PURPOSE:
-    This test will verify that a USB DSL or Mobile Broadband modem works
- STEPS:
-    1. Connect the USB cable to the computer
-    2. Right click on the Network icon in the panel
-    3. Select 'Edit Connections'
-    4. Select the 'DSL' (for ADSL modem) or 'Mobile Broadband' (for 3G modem) tab
-    5. Click on 'Add' button
-    6. Configure the connection parameters properly
-    7. Notify OSD should confirm that the connection has been established
-    8. Select Test to verify that it's possible to establish an HTTP connection
- VERIFICATION:
-    Was the connection correctly established?
-
-plugin: shell
-name: peripheral/external-usb-modem-http
-depends: peripheral/external-usb-modem
-command: wget -SO /dev/null http://$TRANSFER_SERVER
-_description:
- Automated test case to make sure that it's possible to download files through HTTP

=== removed file 'jobs/piglit.txt.in'
--- jobs/piglit.txt.in	2012-12-11 12:09:53 +0000
+++ jobs/piglit.txt.in	1970-01-01 00:00:00 +0000
@@ -1,72 +0,0 @@
-plugin: shell
-name: piglit/fbo
-requires:
- package.name == 'piglit'
-command: piglit_test -t ^spec/EXT_framebuffer_object -n fbo
-_description:
- Runs piglit tests for checking support for framebuffer object operations, depth buffer and stencil buffer
-
-plugin: shell
-name: piglit/gl-2.1
-requires:
- package.name == 'piglit'
-command: piglit_test -t spec/'!OpenGL 2.1'/ -n gl-2.1
-_description:
- Runs piglit tests for checking OpenGL 2.1 support
-
-plugin: shell
-name: piglit/vbo
-requires:
- package.name == 'piglit'
-command: piglit_test -t spec/ARB_vertex_buffer_object/ -n vbo
-_description:
- Runs piglit tests for checking support for vertex buffer object operations
-
-plugin: shell
-name: piglit/glsl-fragment-shader
-requires:
- package.name == 'piglit'
-command: piglit_test -t ^shaders/glsl-arb-fragment -n glsl-fragment-shader
-_description:
- Runs piglit tests for checking support for GLSL fragment shader operations
-
-plugin: shell
-name: piglit/glsl-vertex-shader
-requires:
- package.name == 'piglit'
-command: piglit_test -t ^shaders/glsl-clamp-vertex-color -t ^shaders/glsl-max-vertex-attrib -t ^shaders/glsl-novertexdata -n glsl-vertex-shader
-_description:
- Runs piglit tests for checking support for GLSL vertex shader operations
-
-plugin: shell
-name: piglit/glx-tfp
-requires:
- package.name == 'piglit'
-command: piglit_test -t glx-tfp -n glx-tfp
-_description:
- Runs piglit tests for checking support for texture from pixmap
-
-plugin: shell
-name: piglit/stencil_buffer
-requires:
- package.name == 'piglit'
-command: piglit_test -t glx-visuals-stencil -t readpixels-24_8 -n stencil_buffer
-_description:
- Runs piglit_tests for checking support for stencil buffer operations
-
-plugin: shell
-name: piglit/summarize_results
-requires:
- package.name == 'piglit'
-command: [ -e $CHECKBOX_DATA/piglit-results ] && piglit-summary-html.py $CHECKBOX_DATA/piglit-summary/ `find $CHECKBOX_DATA/piglit-results/ -name main` && echo "Successfully summarized piglit results. They are available in $CHECKBOX_DATA/piglit-sumary/"
-_description:
- Runs the piglit results summarizing tool
-
-plugin: shell
-name: piglit/tarball
-requires:
- package.name == 'piglit'
-depends: piglit/summarize_results
-command: [ -e $CHECKBOX_DATA/piglit-summary ] && tar cvfz $CHECKBOX_DATA/piglit-results.tar.gz $CHECKBOX_DATA/piglit-summary/
-_description:
- Archives the piglit-summary directory into the piglit-results.tar.gz.

=== removed file 'jobs/rendercheck.txt.in'
--- jobs/rendercheck.txt.in	2013-05-03 10:46:46 +0000
+++ jobs/rendercheck.txt.in	1970-01-01 00:00:00 +0000
@@ -1,13 +0,0 @@
-plugin: shell
-name: rendercheck/tests
-requires:
- package.name == 'x11-apps'
-command: ( rendercheck_test -b repeat -b gradients -d -o $CHECKBOX_DATA/rendercheck-results && echo "Rendercheck tests completed successfully" ) || ( echo "Error running rendercheck. Please see the log $CHECKBOX_DATA/rendercheck-results for details" >&2 && false )
-_description:
- Runs all of the rendercheck test suites. This test can take a few minutes.
-
-plugin: attachment
-name: rendercheck/tarball
-depends: rendercheck/tests
-command: [ -e $CHECKBOX_DATA/rendercheck-results ] && tar cvfz $CHECKBOX_DATA/rendercheck-results.tar.gz $CHECKBOX_DATA/rendercheck-results && cat $CHECKBOX_DATA/rendercheck-results.tar.gz
-_description: Attach log from rendercheck tests

=== removed file 'jobs/server-services.txt.in'
--- jobs/server-services.txt.in	2011-10-05 21:01:59 +0000
+++ jobs/server-services.txt.in	1970-01-01 00:00:00 +0000
@@ -1,39 +0,0 @@
-plugin: shell
-name: services/open_ssh_test
-requires: package.name == 'ssh'
-command: pgrep sshd >/dev/null || (echo 'FAIL: sshd is not running.' 2>&1 && false)
-_description: Verifies that sshd is running.
-
-plugin: shell
-name: services/print_server_test
-requires: package.name == 'cups'
-command: pgrep cupsd >/dev/null || (echo 'FAIL: cupsd is not running.' 2>&1 && false)
-_description: Verifies that Print/CUPs server is running.
-
-plugin: shell
-name: services/dns_server_test
-requires: package.name == 'bind9' and package.name == 'dnsutils'
-user: root
-command: dns_server_test
-_description: Verifies that DNS server is running and working.
-
-plugin: shell
-name: services/samba_test
-requires: package.name == 'samba' and package.name == 'winbind'
-user: root
-command: samba_test
-_description: Verifies that Samba server is running.
-
-plugin: shell
-name: services/lamp_test
-requires: package.name == 'apache2' and package.name == 'php5-mysql' and package.name == 'libapache2-mod-php5' and package.name == 'mysql-server'
-user: root
-command: lamp_test
-_description: Verifies that the LAMP stack is running (Apache, MySQL and PHP).
-
-plugin: shell
-name: services/tomcat_test
-requires: package.name == 'tomcat6'
-user: root
-command: tomcat_test
-_description: Verifies that Tomcat server is running and working.

=== removed file 'jobs/suspend.txt.in'
--- jobs/suspend.txt.in	2013-07-05 16:43:48 +0000
+++ jobs/suspend.txt.in	1970-01-01 00:00:00 +0000
@@ -1,1237 +0,0 @@
-plugin: shell
-name: suspend/network_before_suspend
-depends: networking/detect
-_description: Record the current network before suspending.
-command: set -o pipefail; internet_test | tee $CHECKBOX_DATA/network_before_suspend.txt
-
-plugin: shell
-name: suspend/resolution_before_suspend
-_description: Record the current resolution before suspending.
-command: xrandr -q |grep '*'| awk '{print $1}' > $CHECKBOX_DATA/resolution_before_suspend.txt
-
-plugin: shell
-name: suspend/audio_before_suspend
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
-_description: Record mixer settings before suspending.
-command: audio_settings store --file=$CHECKBOX_DATA/audio_settings_before_suspend
-
-plugin: shell
-name: suspend/cpu_before_suspend
-_description: Verify that all the CPUs are online before suspending
-command: cpuinfo_resource > $CHECKBOX_DATA/cpuinfo_before_suspend
-
-plugin: shell
-name: suspend/memory_before_suspend
-_description:
- Dumps memory info to a file for comparison after suspend test has been run
-command: meminfo_resource > $CHECKBOX_DATA/meminfo_before_suspend
-
-plugin: shell
-name: suspend/wireless_before_suspend
-depends: wireless/wireless_connection
-requires: device.category == 'WIRELESS'
-command: nmcli -t -f UUID con status > $CHECKBOX_DATA/connections && connect_wireless && internet_test --interface=`nmcli dev list | grep -B 1 wireless | grep GENERAL.DEVICE | awk '{print $2}'` && for con in `cat $CHECKBOX_DATA/connections`; do nmcli con up uuid "$con"; done
-_description:
- This test disconnects all connections and then connects to the wireless
- interface. It then checks the connection to confirm it's working as expected.
-
-plugin: shell
-name: suspend/bluetooth_obex_before_suspend
-requires:
- package.name == 'bluez'
- package.name == 'obexd-client'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill shows BT is soft blocked, removing before testing."
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  obex_send $BTDEVADDR $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
-_description:
- This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_send_before_suspend
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR send 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_browse_before_suspend
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR browse 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth test. It emulates browsing on a remote device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_get_before_suspend
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR get 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth test. It receives the given file from a remote host specified by the BTDEVADDR environment variable
-
-plugin: manual
-name: suspend/bluetooth_obex_before_suspend_manual
-requires:
- package.name == 'bluez'
- package.name == 'obexd-client'
- device.category == 'BLUETOOTH'
-command: rfkill unblock bluetooth; obex_send `bluetooth_scan` $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
-_description:
- PURPOSE:
-     This test will send the image 'JPEG_Color_Image_Ubuntu.jpg' to a specified device
- STEPS:
-     1. Make sure Bluetooth is enabled by checking the Bluetooth indicator applet
-     2. Click "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)
-     3. Accept any prompts that appear on both devices
- VERIFICATION:
-     Was the data correctly transferred?
-
-plugin: user-verify
-name: suspend/suspend_advanced
-depends: power-management/rtc
-requires:
- sleep.mem == 'supported'
-user: root
-environ: CHECKBOX_DATA
-command:
- if type -P fwts >/dev/null; then
-  echo "Calling fwts"
-  set -o pipefail; fwts_test -f none -l $CHECKBOX_DATA/suspend_single -s s3 --s3-sleep-delay=30 --s3-device-check --s3-device-check-delay=45 | tee $CHECKBOX_DATA/suspend_single_times.log
- else
-  echo "Calling sleep_test"
-  set -o pipefail; sleep_test -p | tee $CHECKBOX_DATA/suspend_single_times.log
- fi
-_description:
- PURPOSE:
-     This test will check suspend and resume
- STEPS:
-     1. Click "Test" and your system will suspend for about 30 - 60 seconds
-     2. Observe the Power LED to see if it blinks or changes color during suspend
-     3. If your system does not wake itself up after 60 seconds, please press the power button momentarily to wake the system manually
-     4. If your system fails to wake at all and must be rebooted, restart System Testing after reboot and mark this test as Failed
- VERIFICATION:
-     Did your system suspend and resume correctly?
-     (NOTE: Please only consider whether the system successfully suspended and resumed. Power/Suspend LED verification will occur after this test is completed.)
-
-plugin: shell
-name: suspend/suspend_advanced_auto
-depends: power-management/rtc
-requires:
-    sleep.mem == 'supported'
-_description:
- This is the automated version of suspend/suspend_advanced.
-user: root
-environ: CHECKBOX_DATA
-command: set -o pipefail; fwts_test -f none -l $CHECKBOX_DATA/suspend_single -s s3 --s3-sleep-delay=30 --s3-device-check --s3-device-check-delay=45 | tee $CHECKBOX_DATA/suspend_single_times.log
-
-plugin: shell
-name: suspend/suspend-single-log-check
-command: [ -e $CHECKBOX_DATA/suspend_single.log ] && sleep_test_log_check -v s3 $CHECKBOX_DATA/suspend_single.log
-_description:
- Automated check of the suspend log to look for errors reported by fwts
-
-plugin: attachment
-name: suspend/suspend-single-log-attach
-command: [ -e $CHECKBOX_DATA/suspend_single.log ] && cat $CHECKBOX_DATA/suspend_single.log
-_description:
- Attaches the log from the single suspend/resume test to the results
-
-plugin: shell
-name: suspend/suspend-time-check
-command: [ -e $CHECKBOX_DATA/suspend_single_times.log ] && sleep_time_check $CHECKBOX_DATA/suspend_single_times.log
-_description:
- Checks the sleep times to ensure that a machine suspends and resumes within a given threshold
-
-plugin: manual
-name: power-management/usb_wakeup_keyboard
-user: root
-depends: suspend/suspend_advanced
-command: pm-suspend
-_description:
- PURPOSE:
-     Wake up by USB keyboard
- STEPS:
-     1. Enable "Wake by USB KB/Mouse" item in BIOS
-     2. Press "Test" to enter suspend (S3) mode
-     3. Press any key of USB keyboard to wake system up
- VERIFICATION:
-     Did the system wake up from suspend mode when you pressed a keyboard key?
-
-plugin: manual
-name: power-management/usb_wakeup_mouse
-user: root
-depends: suspend/suspend_advanced
-command: pm-suspend
-_description:
- PURPOSE:
-     Wake up by USB mouse
- STEPS:
-     1. Enable "Wake by USB KB/Mouse" item in BIOS
-     2. Press "Test" to enter suspend (S3) mode
-     3. Press any button of USB mouse to wake system up
- VERIFICATION:
-     Did the system wake up from suspend mode when you pressed the mouse button?
-
-plugin: shell
-name: suspend/network_after_suspend
-depends: suspend/suspend_advanced suspend/network_before_suspend
-_description: Test the network after resuming.
-command: network_wait; internet_test | diff $CHECKBOX_DATA/network_before_suspend.txt -
-
-plugin: shell
-name: suspend/resolution_after_suspend
-depends: suspend/suspend_advanced suspend/resolution_before_suspend
-_description: Test to see that we have the same resolution after resuming as before.
-command: xrandr -q |grep '*'| awk '{print $1}' | diff $CHECKBOX_DATA/resolution_before_suspend.txt -
-
-plugin: shell
-name: suspend/audio_after_suspend
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
-depends: suspend/suspend_advanced suspend/audio_before_suspend
-_description: Verify that mixer settings after suspend are the same as before suspend.
-command: 
- audio_settings store --file=$CHECKBOX_DATA/audio_settings_after_suspend; diff $CHECKBOX_DATA/audio_settings_before_suspend $CHECKBOX_DATA/audio_settings_after_suspend
-
-plugin: shell
-name: suspend/audio_after_suspend_auto
-requires:
- device.category == 'AUDIO'
- package.name == 'alsa-base'
-depends: suspend/suspend_advanced_auto suspend/audio_before_suspend
-_description: Verify that mixer settings after suspend are the same as before suspend.
-command:
- audio_settings store --file=$CHECKBOX_DATA/audio_settings_after_suspend; diff $CHECKBOX_DATA/audio_settings_before_suspend $CHECKBOX_DATA/audio_settings_after_suspend
-
-plugin: shell
-name: suspend/cpu_after_suspend
-depends: suspend/suspend_advanced suspend/cpu_before_suspend
-_description: Verify that all CPUs are online after resuming.
-command: cpuinfo_resource | diff $CHECKBOX_DATA/cpuinfo_before_suspend -
-
-plugin: shell
-name: suspend/cpu_after_suspend_auto
-depends: suspend/suspend_advanced_auto suspend/cpu_before_suspend
-_description: Verify that all CPUs are online after resuming.
-command: cpuinfo_resource | diff $CHECKBOX_DATA/cpuinfo_before_suspend -
-
-plugin: shell
-name: suspend/memory_after_suspend
-depends: suspend/suspend_advanced suspend/memory_before_suspend
-_description:
- Verify that all memory is available after resuming from suspend.
-command: meminfo_resource | diff $CHECKBOX_DATA/meminfo_before_suspend -
-
-plugin: shell
-name: suspend/memory_after_suspend_auto
-depends: suspend/suspend_advanced_auto suspend/memory_before_suspend
-_description:
- Verify that all memory is available after resuming from suspend.
-command: meminfo_resource | diff $CHECKBOX_DATA/meminfo_before_suspend -
-
-plugin: manual
-name: suspend/display_after_suspend
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     This test will check that the display is correct after suspend and resume
- STEPS:
-     1. Check that your display does not show up visual artifacts after resuming.
- VERIFICATION:
-     Does the display work normally after resuming from suspend?
-
-plugin: shell
-name: suspend/wireless_after_suspend
-depends: suspend/suspend_advanced suspend/wireless_before_suspend
-requires:
- device.category == 'WIRELESS'
-command: connect_wireless && internet_test --interface=`nmcli dev list | grep -B 1 wireless | grep GENERAL.DEVICE | awk '{print $2}'` && for con in `cat $CHECKBOX_DATA/connections`; do nmcli con up uuid "$con"; done
-_description:
- This test checks that the wireless interface is working after suspending the system. It
- disconnects all interfaces and then connects to the wireless interface and checks that the
- connection is working as expected.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_wpa_bg
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: WPA_BG_SSID WPA_BG_PSK
-command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using WPA
- security and the 802.11b/g protocols after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_open_bg
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: OPEN_BG_SSID
-command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_BG_SSID" EXIT; create_connection wifi $OPEN_BG_SSID; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using no
- security and the 802.11b/g protocols after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_wpa_n
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: WPA_N_SSID WPA_N_PSK
-command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_N_SSID" EXIT; create_connection wifi $WPA_N_SSID --security=wpa --key=$WPA_N_PSK; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using WPA
- security and the 802.11n protocol after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_open_n
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: OPEN_N_SSID
-command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_N_SSID" EXIT; create_connection wifi $OPEN_N_SSID; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using no
- security and the 802.11n protocol after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_wpa_bg_auto
-depends: suspend/suspend_advanced_auto
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: WPA_BG_SSID WPA_BG_PSK
-command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using WPA
- security and the 802.11b/g protocols after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_open_bg_auto
-depends: suspend/suspend_advanced_auto
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: OPEN_BG_SSID
-command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_BG_SSID" EXIT; create_connection wifi $OPEN_BG_SSID; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using no
- security and the 802.11b/g protocols after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_wpa_n_auto
-depends: suspend/suspend_advanced_auto
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: WPA_N_SSID WPA_N_PSK
-command: trap "rm -f /etc/NetworkManager/system-connections/$WPA_N_SSID" EXIT; create_connection wifi $WPA_N_SSID --security=wpa --key=$WPA_N_PSK; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using WPA
- security and the 802.11n protocol after the system has been suspended.
-
-plugin: shell
-name: suspend/wireless_connection_after_suspend_open_n_auto
-depends: suspend/suspend_advanced_auto
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: OPEN_N_SSID
-command: trap "rm -f /etc/NetworkManager/system-connections/$OPEN_N_SSID" EXIT; create_connection wifi $OPEN_N_SSID; internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using no
- security and the 802.11n protocol after the system has been suspended.
-
-plugin: manual
-name: suspend/wireless_connection_after_suspend_wpa_bg_manual
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID ROUTER_PSK
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using WPA
-     security and the 802.11b/g protocols.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the B and G wireless bands
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: manual
-name: suspend/wireless_connection_after_suspend_open_bg_manual
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using
-     no security and the 802.11b/g protocols.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the B and G wireless bands
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use no security
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: manual
-name: suspend/wireless_connection_after_suspend_wpa_n_manual
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID ROUTER_PSK
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using WPA
-     security and the 802.11n protocols.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the N wireless band
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: manual
-name: suspend/wireless_connection_after_suspend_open_n_manual
-depends: suspend/suspend_advanced
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using
-     no security and the 802.11n protocol.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the N wireless band
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use no security
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: shell
-name: suspend/bluetooth_detect_after_suspend
-depends: suspend/suspend_advanced bluetooth/detect-output
-requires:
- package.name == 'bluez'
- device.category == 'BLUETOOTH'
-command:
- if rfkill list bluetooth | grep -q 'Hard blocked: yes'; then
-   echo "rfkill shows BT is hard blocked"
- fi
- if rfkill list bluetooth | grep -q 'Soft blocked: yes'; then
-   echo "rfkill shows BT is soft blocked, removing before testing"
-   rfkill unblock bluetooth
-   sleep 3
- fi
- output=$(hcitool dev | tail -n+2 | awk '{print $2}')
- echo $output | diff $CHECKBOX_DATA/bluetooth_address -
- if [ -z "$output" ]; then
-     echo "BT hardware not available"
-     exit 1
- fi
-_description:
- This test grabs the hardware address of the bluetooth adapter after suspend and compares it to the address grabbed before suspend.
-
-plugin: shell
-name: suspend/bluetooth_obex_after_suspend
-depends: suspend/suspend_advanced suspend/bluetooth_obex_before_suspend
-requires:
- package.name == 'bluez'
- package.name == 'obexd-client'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill shows BT is soft blocked, removing before testing."
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  obex_send $BTDEVADDR $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
-_description:
- This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_after_suspend_auto
-depends: suspend/suspend_advanced_auto suspend/bluetooth_obex_before_suspend
-requires:
- package.name == 'bluez'
- package.name == 'obexd-client'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill shows BT is soft blocked, removing before testing."
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  obex_send $BTDEVADDR $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
-_description:
- This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_send_after_suspend
-depends: suspend/suspend_advanced
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR send 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_send_after_suspend_auto
-depends: suspend/suspend_advanced_auto
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR send 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth file transfer test. It sends an image to the device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_browse_after_suspend
-depends: suspend/suspend_advanced
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR browse 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth test. It emulates browsing on a remote device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_browse_after_suspend_auto
-depends: suspend/suspend_advanced_auto
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR browse 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth test. It emulates browsing on a remote device specified by the BTDEVADDR environment variable.
-
-plugin: shell
-name: suspend/bluetooth_obex_get_after_suspend
-depends: suspend/suspend_advanced
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR get 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth test. It receives the given file from a remote host specified by the BTDEVADDR environment variable
-
-plugin: shell
-name: suspend/bluetooth_obex_get_after_suspend_auto
-depends: suspend/suspend_advanced_auto
-requires:
- package.name == 'bluez'
- package.name == 'obexftp'
- device.category == 'BLUETOOTH'
-command:
-  if [ -z "$BTDEVADDR" ]
-  then
-    echo "btdevaddr option not set to device address of Bluetooth target in checkbox.ini"
-    exit 1
-  fi
-  if rfkill list bluetooth | grep -q 'Hard blocked: yes'
-  then
-    echo "rfkill list shows BT is hard blocked"
-  fi
-  if rfkill list bluetooth | grep -q 'Soft blocked: yes'
-  then
-    echo "rfkill list shows BT is soft blocked, removing before testing"
-    rfkill unblock bluetooth
-    sleep 3
-  fi
-  set -o pipefail; bluetooth_test $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg $BTDEVADDR get 2>&1 | ansi_parser
-_description:
- This is an automated Bluetooth test. It receives the given file from a remote host specified by the BTDEVADDR environment variable
-
-plugin: manual
-name: suspend/bluetooth_obex_after_suspend_manual
-depends: suspend/suspend_advanced suspend/bluetooth_obex_before_suspend_manual
-requires:
- package.name == 'bluez'
- package.name == 'obexd-client'
- device.category == 'BLUETOOTH'
-command: rfkill unblock bluetooth; obex_send `bluetooth_scan` $CHECKBOX_SHARE/data/images/JPEG_Color_Image_Ubuntu.jpg
-_description:
- PURPOSE:
-     This test will send the image 'JPEG_Color_Image_Ubuntu.jpg' to a specified device
- STEPS:
-     1. Click "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)
-     2. Accept any prompts that appear on both devices
- VERIFICATION:
-     Was the data correctly transferred?
-
-plugin: manual
-name: suspend/cycle_resolutions_after_suspend
-requires: package.name == 'xorg'
-depends: suspend/suspend_advanced graphics/cycle_resolution
-command: xrandr_cycle --keyword=after_suspend --screenshot-dir $CHECKBOX_DATA
-_description:
- PURPOSE:
-     This test will cycle through the detected display modes
- STEPS:
-     1. Click "Test" and the display will cycle trough the display modes
- VERIFICATION:
-     Did your display look fine in the detected mode?
-
-plugin: shell
-name: suspend/cycle_resolutions_after_suspend_auto
-requires: package.name == 'xorg'
-depends: suspend/suspend_advanced_auto graphics/cycle_resolution
-_description:
- This test will check to make sure supported video modes work after a suspend and resume.
- This is done automatically by taking screenshots and uploading them as an attachment.
-command: xrandr_cycle --keyword=after_suspend --screenshot-dir $CHECKBOX_DATA
-
-plugin: attachment
-name: suspend/xrandr_screens_after_suspend.tar.gz
-depends: suspend/cycle_resolutions_after_suspend_auto
-command: [ -e $CHECKBOX_DATA/xrandr_screens_after_suspend.tgz ] && cat $CHECKBOX_DATA/xrandr_screens_after_suspend.tgz
-_description: This attaches screenshots from the suspend/cycle_resolutions_after_suspend_auto test to the results submission.
-
-plugin: shell
-name: suspend/record_playback_after_suspend
-depends: suspend/suspend_advanced
-requires:
- package.name == 'python3-gi'
- package.name == 'gir1.2-gstreamer-1.0'
- package.name == 'libgstreamer1.0-0'
- package.name == 'gstreamer1.0-plugins-good'
- package.name == 'gstreamer1.0-pulseaudio'
- package.name == 'alsa-base'
- device.category == 'AUDIO'
-command: audio_test
-_description:
- This will check to make sure that your audio device works properly after a suspend and resume.  This may work fine with speakers and onboard microphone, however, it works best if used with a cable connecting the audio-out jack to the audio-in jack.
-
-plugin: shell
-name: suspend/record_playback_after_suspend_auto
-depends: suspend/suspend_advanced_auto
-requires:
- package.name == 'python3-gi'
- package.name == 'gir1.2-gstreamer-1.0'
- package.name == 'libgstreamer1.0-0'
- package.name == 'gstreamer1.0-plugins-good'
- package.name == 'gstreamer1.0-pulseaudio'
- package.name == 'alsa-base'
- device.category == 'AUDIO'
-command: audio_test
-_description:
- This will check to make sure that your audio device works properly after a suspend and resume.  This may work fine with speakers and onboard microphone, however, it works best if used with a cable connecting the audio-out jack to the audio-in jack.
-
-plugin: attachment
-name: suspend/suspend-auto-single-log-attach
-command: [ -e $CHECKBOX_DATA/suspend_auto_single_log ] && cat $CHECKBOX_DATA/suspend_auto_single_log
-_description:
- Attaches the log from the single suspend/resume test to the results
-
-plugin: shell
-name: suspend/screenshot_after_suspend
-depends: suspend/suspend_advanced_auto
-requires: package.name == 'fswebcam'
-command: set -o pipefail; camera_test still --device=/dev/external_webcam -f ${CHECKBOX_DATA}/screenshot_after_suspend.jpg -q 2>&1 | ansi_parser
-_description:
- PURPOSE:
-     Take a screengrab of the current screen after suspend (logged on Unity desktop)
- STEPS:
-     1. Take picture using USB webcam
- VERIFICATION:
-     Review attachment manually later
-
-plugin: attachment
-name: screenshot_after_suspend.jpg
-depends: suspend/screenshot_after_suspend
-command: base64 ${CHECKBOX_DATA}/screenshot_after_suspend.jpg
-_description: Attaches the screenshot captured in graphics/screenshot.
-
-plugin: shell
-name: suspend/gpu_lockup_after_suspend
-requires:
- package.name == 'wmctrl'
- package.name == 'mesa-utils'
- package.name == 'firefox'
-depends: suspend/suspend_advanced_auto
-command: gpu_test
-_description:
- PURPOSE:
-     Do some challenging operations then check for lockup on the GPU
- STEPS:
-     1. Create 2 glxgears windows and move them quickly
-     2. Switch workspaces with wmctrl
-     3. Launch an HTML5 video playback in firefox
- VERIFICATION:
-     After a 60s workload, check kern.log for reported GPU errors
-
-plugin: shell
-name: suspend/wifi_resume_time
-depends: suspend/suspend_advanced
-requires:
-   device.category == 'WIRELESS'
-command: network_reconnect_resume_test -t 20 -d wifi
-_description:
- Checks the length of time it takes to reconnect an existing wifi connection
- after a suspend/resume cycle.
-
-plugin: shell
-name: suspend/wifi_resume_time_auto
-depends: suspend/suspend_advanced_auto
-requires:
-   device.category == 'WIRELESS'
-command: network_reconnect_resume_test -t 20 -d wifi
-_description:
- Checks the length of time it takes to reconnect an existing wifi connection
- after a suspend/resume cycle.
-
-plugin: shell
-name: suspend/network_resume_time
-depends: suspend/suspend_advanced
-requires:
-   device.category == 'NETWORK'
-command: network_reconnect_resume_test -t 10 -d wired
-_description:
- Checks the length of time it takes to reconnect an existing wired connection
-  after a suspend/resume cycle.
-
-plugin: shell
-name: suspend/network_resume_time_auto
-depends: suspend/suspend_advanced_auto
-requires:
-   device.category == 'NETWORK'
-command: network_reconnect_resume_test -t 10 -d wired
-_description:
- Checks the length of time it takes to reconnect an existing wired connection
-  after a suspend/resume cycle.
-
-plugin: manual
-name: suspend/led_after_suspend/power
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that the power LED operated the same after resuming from suspend
- STEPS:
-     1. Power LED should be on while device is switched on
- VERIFICATION:
-     Does the power LED remain on after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/battery-charging
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that the battery light shows charging status after resuming from suspend
- STEPS:
-     1. Let system run on battery for a while
-     2. Plug in AC plug
- VERIFICATION:
-     Did the battery indicator LED still turn orange after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/battery-charged
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that the battery LED properly displays charged status after resuming from suspend
- STEPS:
-     1. Let system run on battery for a short time
-     2. Plug in AC
-     3. Let system run on AC
- VERIFICATION:
-     Does the orange battery LED still shut off when system is fully charged after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/battery-low
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that the battery LED indicated low power after resuming from suspend
- STEPS:
-     1. Let system run on battery for several hours
-     2. Monitor battery LED carefully
- VERIFICATION:
-     Does the LED light orange when battery is low after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/hdd
-depends: suspend/suspend_advanced
-command: led_hdd_test
-_description:
- PURPOSE:
-     Validate that the HDD LED still operates as expected after resuming from suspend
- STEPS:
-     1. Select "Test" to write and read a temporary file for a few seconds
-     2. HDD LED should blink when writing to/reading from HDD
- VERIFICATION:
-     Did the HDD LED still blink with HDD activity after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/numeric-keypad
-depends: suspend/suspend_advanced
-command: keyboard_test
-_description:
- PURPOSE:
-     Validate that the numeric keypad LED operates the same before and after resuming from suspend
- STEPS:
-     1. Press "Block Num" key to toggle numeric keypad LED
-     2. Click on the "Test" button to open a window to verify your typing
-     3. Type using the numeric keypad both when the LED is on and off
- VERIFICATION:
-     1. Numeric keypad LED status should toggle everytime the "Block Num" key is pressed
-     2. Numbers should only be entered in the keyboard verification window when the LED is on
-
-plugin: manual
-name: suspend/led_after_suspend/caps-lock
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that the Caps Lock key operates the same before and after resuming from suspend
- STEPS:
-     1. Press "Block Cap Keys" to activate/deactivate cap keys blocking
-     2. Cap Keys LED should be switched on/off every time the key is pressed
- VERIFICATION:
-     Did the Cap Keys LED light as expected after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/wlan
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     WLAN LED verification after resuming from suspend
- STEPS:
-     1. Make sure WLAN connection is established
-     2. WLAN LED should light
- VERIFICATION:
-     Did the WLAN LED light as expected after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/wlan-disabled
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that WLAN LED shuts off when disabled after resuming from suspend
- STEPS:
-     1. Connect to AP
-     2. Use Physical switch to disable WLAN
-     3. Re-enable
-     4. Use Network-Manager to disable WLAN
- VERIFICATION:
-     Did the LED turn off then WLAN is disabled after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/bluetooth
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate that the Bluetooth LED turns on and off when BT is enabled/disabled after resuming from suspend
- STEPS:
-     1. Switch bluetooth off from a hardware switch (if present)
-     2. Switch bluetooth back on
-     3. Switch bluetooth off from the panel applet
-     4. Switch bluetooth back on
- VERIFICATION:
-     Did the bluetooth LED turn off and on twice after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/camera
-depends:
- camera/detect
- suspend/suspend_advanced
-command: camera_test led
-_description:
- PURPOSE:
-     Validate that the camera LED still works as expected after resuming from suspend
- STEPS:
-     1. Select Test to activate camera
-     2. Camera LED should light for a few seconds
- VERIFICATION:
-     Did the camera LED still turn on and off after resuming from suspend?
-
-plugin: manual
-name: suspend/led_after_suspend/touchpad
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Touchpad LED verification after resuming from suspend
- STEPS:
-     1. Click on the touchpad button or press key combination to enable/disable touchpad button
-     2. Slide your finger on the touchpad
- VERIFICATION:
-     1. Touchpad LED status should toggle everytime the button is clicked or the key combination is pressed
-     2. When the LED is on, the mouse pointer should move on touchpad usage
-     3. When the LED is off, the mouse pointer should not move on touchpad usage
-
-plugin: manual
-name: suspend/led_after_suspend/wireless
-depends: suspend/suspend_advanced
-_description:
- PURPOSE:
-     Validate Wireless (WLAN + Bluetooth) LED operated the same after resuming from suspend
- STEPS:
-     1. Make sure WLAN connection is established and Bluetooth is enabled.
-     2. WLAN/Bluetooth LED should light
-     3. Switch WLAN and Bluetooth off from a hardware switch (if present)
-     4. Switch them back on
-     5. Switch WLAN and Bluetooth off from the panel applet
-     6. Switch them back on
- VERIFICATION:
-     Did the WLAN/Bluetooth LED light as expected after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/brightness
-depends: suspend/suspend_advanced
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     This test will test the brightness key after resuming from suspend
- STEPS:
-     1. Press the brightness buttons on the keyboard
- VERIFICATION:
-     Did the brightness change following to your key presses after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/volume
-depends: suspend/suspend_advanced
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s '0xe02e,0xe0ae:Volume Up' '0xe030,0xe0b0:Volume Down'
-_description:
- PURPOSE:
-     This test will test the volume keys of your keyboard after resuming from suspend
- STEPS:
-     1. Click test to open a window on which to test the volume keys.
-     2. If all the keys work, the test will be marked as passed.
-     3. If your computer has no volume keys, Skip this test.
- VERIFICATION:
-     Did the volume change following to your key presses?
-
-plugin: manual
-name: suspend/keys_after_suspend/mute
-depends: suspend/suspend_advanced
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s '0xe020,0xe0a0:Mute'
-_description:
- PURPOSE:
-     This test will test the mute key of your keyboard after resuming from suspend
- STEPS:
-     1. Click test to open a window on which to test the mute key.
-     2. If the key works, the test will pass and the window will close.
- VERIFICATION:
-     Did the volume mute following your key presses?
-
-plugin: manual
-name: suspend/keys_after_suspend/sleep
-depends: suspend/suspend_advanced
-requires:
- device.category == 'KEYBOARD'
-_description:
- PURPOSE:
-     This test will test the sleep key after resuming from suspend
- STEPS:
-     1. Press the sleep key on the keyboard
-     2. Wake your system up by pressing the power button
- VERIFICATION:
-     Did the system go to sleep after pressing the sleep key after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/battery-info
-depends: suspend/suspend_advanced
-requires: dmi.product in ['Notebook','Laptop','Portable']
-user: root
-command: key_test -s '0xe071,0xef1:Battery Info'
-_description:
- PURPOSE:
-     This test will test the battery information key after resuming from suspend
- STEPS:
-     If you do not have a Battery Button, skip this test
-     1. Click Test to begin
-     2. Press the Battery Info button (or combo like Fn+F3)
-     3: Close the Power Statistics tool if it opens
- VERIFICATION:
-     Did the Battery Info key work as expected after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/wireless
-depends: suspend/suspend_advanced
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     This test will test the wireless key after resuming from suspend
- STEPS:
-     1. Press the wireless key on the keyboard
-     2. Press the same key again
- VERIFICATION:
-     Did the wireless go off on the first press and on again on the second after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/media-control
-depends: suspend/suspend_advanced
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s 0xe010,0xe090:Previous 0xe024,0xe0a4:Stop 0xe019,0xe099:Next 0xe022,0xe0a2:Play
-_description:
- PURPOSE:
-     This test will test the media keys of your keyboard after resuming from suspend
- STEPS:
-     1. Click test to open a window on which to test the media keys.
-     2. If all the keys work, the test will be marked as passed.
-     3. If your computer has no media keys, Skip this test.
- VERIFICATION:
-     Do the keys work as expected after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/super
-depends: suspend/suspend_advanced
-requires:
- device.category == 'KEYBOARD'
-user: root
-command: key_test -s '0xe05b,0xe0db:Left Super Key'
-_description:
- PURPOSE:
-     This test will test the super key of your keyboard after resuming from suspend
- STEPS:
-     1. Click test to open a window on which to test the super key.
-     2. If the key works, the test will pass and the window will close.
- VERIFICATION:
-     Does the super key work as expected after resuming from suspend?
-
-plugin: manual
-name: suspend/keys_after_suspend/video-out
-depends: suspend/suspend_advanced
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     Validate that the External Video hot key is working as expected after resuming from suspend
- STEPS:
-     1. Plug in an external monitor
-     2. Press the display hot key to change the monitors configuration
- VERIFICATION:
-     Check that the video signal can be mirrored, extended, displayed on external or onboard only, after resuming from suspend.
-
-plugin: manual
-name: suspend/keys_after_suspend/touchpad
-depends: suspend/suspend_advanced
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     Verify touchpad hotkey toggles touchpad functionality on and off after resuming from suspend
- STEPS:
-     1. Verify the touchpad is functional
-     2. Tap the touchpad toggle hotkey
-     3. Tap the touchpad toggle hotkey again
- VERIFICATION:
-     Verify the touchpad has been disabled and re-enabled.

=== removed file 'jobs/touchpad.txt.in'
--- jobs/touchpad.txt.in	2013-07-05 16:43:48 +0000
+++ jobs/touchpad.txt.in	1970-01-01 00:00:00 +0000
@@ -1,68 +0,0 @@
-plugin: manual
-name: touchpad/basic
-requires: dmi.product in ['Notebook','Laptop','Portable']
-_description:
- PURPOSE:
-     Touchpad user-verify
- STEPS:
-     1. Make sure that touchpad is enabled.
-     2. Move cursor using the touchpad.
- VERIFICATION:
-     Did the cursor move?
-
-plugin: user-interact
-name: touchpad/horizontal
-requires:
-  'Button Horiz Wheel Left' in xinput.button_labels and 'Button Horiz Wheel Right' in xinput.button_labels
-command: touchpad_test right left
-_description:
- PURPOSE:
-     Touchpad horizontal scroll verification
- STEPS:
-     1. Select "Test" when ready and place your cursor within the borders of the displayed test window.
-     2. Verify that you can move the horizontal slider by moving your finger right and left in the lower part of the touchpad.
- VERIFICATION:
-     Could you scroll right and left?
-
-plugin: user-interact
-name: touchpad/vertical
-requires:
-  'Button Wheel Up' in xinput.button_labels and 'Button Wheel Down' in xinput.button_labels
-command: touchpad_test up down
-_description:
- PURPOSE:
-     Touchpad vertical scroll verification
- STEPS:
-     1. Select "Test" when ready and place your cursor within the borders of the displayed test window.
-     2. Verify that you can move the vertical slider by moving your finger up and down in the right part of the touchpad.
- VERIFICATION:
-     Could you scroll up and down?
-
-plugin: shell
-name: touchpad/singletouch-automated
-requires:
-  dmi.product in ['Notebook','Laptop','Portable']
-  xinput.device_class == 'XITouchClass' and xinput.touch_mode != 'dependent'
-command: true
-_description:
- Determine whether the touchpad is detected as a singletouch device automatically.
-
-plugin: shell
-name: touchpad/multitouch-automated
-requires:
-  dmi.product in ['Notebook','Laptop','Portable']
-  xinput.device_class == 'XITouchClass' and xinput.touch_mode == 'dependent'
-command: true
-_description:
- Determine whether the touchpad is detected as a multitouch device automatically.
-
-plugin: manual
-name: touchpad/multitouch-manual
-depends: touchpad/singletouch-automated
-_description:
- PURPOSE:
-     Touchpad manual detection of multitouch.
- STEPS:
-     1. Look at the specifications for your system.
- VERIFICATION:
-     Is the touchpad supposed to be multitouch?

=== removed file 'jobs/touchscreen.txt.in'
--- jobs/touchscreen.txt.in	2012-10-22 19:43:53 +0000
+++ jobs/touchscreen.txt.in	1970-01-01 00:00:00 +0000
@@ -1,58 +0,0 @@
-plugin: manual
-name: touchscreen/tap-detect
-_description:
- PURPOSE:
-     Check touchscreen tap recognition
- STEPS:
-     1. Tap an object on the screen with finger. The cursor should jump to location tapped and object should highlight
- VERIFICATION:
-     Does tap recognition work?
-
-plugin: manual
-name: touchscreen/drag-n-drop
-_description:
- PURPOSE:
-     Check touchscreen drag & drop
- STEPS:
-     1. Double tap, hold, and drag an object on the desktop
-     2. Drop the object in a different location
- VERIFICATION:
-     Does the object select and drag and drop?
-
-plugin: manual
-name: touchscreen/multitouch-zoom
-_description:
- PURPOSE:
-     Check touchscreen pinch gesture for zoom
- STEPS:
-     1. Place two fingers on the screen and pinch them together
-     2. Place two fingers on the screen and move then apart
- VERIFICATION:
-     Does the screen zoom in and out?
-
-plugin: shell
-name: touchscreen/nontouch-automated
-requires:
-  xinput.device_class == 'XITouchClass' and xinput.touch_mode != 'direct'
-command: true
-_description:
- Determine whether the screen is detected as a non-touch device automatically.
-
-plugin: shell
-name: touchscreen/multitouch-automated
-requires:
-  xinput.device_class == 'XITouchClass' and xinput.touch_mode == 'direct'
-command: true
-_description:
- Determine whether the screen is detected as a multitouch device automatically.
-
-plugin: manual
-name: touchscreen/multitouch-manual
-depends: touchscreen/nontouch-automated
-_description:
- PURPOSE:
-     Touchscreen manual detection of multitouch.
- STEPS:
-     1. Look at the specifications for your system.
- VERIFICATION:
-     Is the screen supposed to be multitouch?

=== removed file 'jobs/user_apps.txt.in'
--- jobs/user_apps.txt.in	2012-07-25 19:08:46 +0000
+++ jobs/user_apps.txt.in	1970-01-01 00:00:00 +0000
@@ -1,505 +0,0 @@
-plugin: manual
-name: software/update_manager_finds_updates
-depends: networking/detect
-user: root
-requires: package.name == 'update-manager'
-_description:
- PURPOSE:
-  This test will check that the update manager can find updates.
- STEPS:
-  1. Click Test to launch update-manager.
-  2. Follow the prompts and if updates are found, install them. 
-  3. When Update Manager has finished, please close the app by clicking the Close button in the lower right corner.
- VERIFICATION:
-  Did Update manager find and install updates (Pass if no updates are found,
-  but Fail if updates are found but not installed)
-command: update-manager --check-dist-upgrades
-
-plugin: manual
-name: software/nautilus_folder_create
-requires: package.name == 'nautilus'
-command: nautilus
-_description:
- PURPOSE:
-  This test will check that the file browser can create a new folder.
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. On the menu bar, click File -> Create Folder. 
-  3. In the name box for the new folder, enter the name Test Folder and hit Enter.
-  4. Close the File browser.
- VERIFICATION:
-  Do you now have a new folder called Test Folder?
-
-plugin: manual
-name: software/nautilus_folder_copy
-depends: software/nautilus_folder_create
-command: nautilus
-_description:
- PURPOSE:
-  This test will check that the file browser can copy a folder
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. Right click on the folder called Test Folder and click on Copy.
-  3. Right Click on any white area in the window and click on Paste.
-  4. Right click on the folder called Test Folder(copy) and click Rename.
-  5. Enter the name Test Data in the name box and hit Enter.
-  6. Close the File browser.
- VERIFICATION:
-  Do you now have a folder called Test Data?
-
-plugin: manual
-name: software/nautilus_folder_move
-depends: software/nautilus_folder_copy
-command: nautilus
-_description:
- PURPOSE:
-  This test will verify that the file browser can move a folder.
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. Click and drag the folder called Test Data onto the icon called Test Folder. 
-  3. Release the button.
-  4. Double click the folder called Test Folder to open it up.
-  5. Close the File Browser.
- VERIFICATION:
-  Was the folder called Test Data successfully moved into the folder called Test Folder?
-
-plugin: manual
-name: software/nautilus_file_create
-depends: software/nautilus_folder_create
-command: nautilus $HOME/"Test Folder"
-_description:
- PURPOSE:
-  This test will check that the file browser can create a new file.
- STEPS:
-  1. Click Select Test to open the File Browser. 
-  2. Right click in the white space and click Create Document -> Empty Document. 
-  3. Enter the name Test File 1 in the name box and hit Enter.
-  4. Close the File browser.
- VERIFICATION:
-  Do you now have a file called Test File 1?
-
-plugin: manual
-name: software/nautilus_file_copy
-depends: software/nautilus_file_create
-command: nautilus $HOME/"Test Folder"
-_description:
- PURPOSE:
-  This test will check that the file browser can copy a file.
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. Right click on the file called Test File 1 and click Copy. 
-  3. Right click in the white space and click Paste.
-  4. Right click on the file called Test File 1(copy) and click Rename. 
-  5. Enter the name Test File 2 in the name box and hit Enter.
-  6. Close the File Browser.
- VERIFICATION:
-  Do you now have a file called Test File 2?
-
-plugin: manual
-name: software/nautilus_file_move
-depends: software/nautilus_file_copy
-command: nautilus $HOME/"Test Folder"
-_description:
- PURPOSE:
-  This test will check that the file browser can move a file.
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. Click and drag the file called Test File 2 onto the icon for the folder called Test Data. 
-  3. Release the button.
-  4. Double click the icon for Test Data to open that folder up.
-  5. Close the File Browser.
- VERIFICATION:
-  Was the file Test File 2 successfully moved into the Test Data folder?
-
-plugin: manual
-name: software/nautilus_file_delete
-depends: software/nautilus_file_create
-command: nautilus $HOME/"Test Folder"
-_description:
- PURPOSE:
-  This test will check that the file browser can delete a file.
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. Right click on the file called Test File 1 and click on Move To Trash.
-  3. Verify that Test File 1 has been removed.
-  4. Close the File Browser.
- VERIFICATION:
-   Is Test File 1 now gone?
-
-plugin: manual
-name: software/nautilus_folder_delete
-depends: software/nautilus_folder_create
-command: nautilus
-_description:
- PURPOSE:
-  This test will check that the file browser can delete a folder.
- STEPS:
-  1. Click Test to open the File Browser. 
-  2. Right click on the folder called Test Folder and click on Move To Trash.
-  3. Verify that the folder was deleted.
-  4. Close the file browser.
- VERIFICATION:
-  Has Test Folder been successfully deleted?
-
-plugin: local
-name: software/view_office_document
-requires: package.name == "ubuntu-desktop"
-_description: Common Document Types Test
-command:
- cat <<'EOF' | run_templates -s "find $CHECKBOX_SHARE/data/documents -type f"
- name: `basename $0`_test
- plugin: manual
- description:
-  PURPOSE:
-   This test will check that common office document types can be opened in the default application.
-  STEPS:
-   1. Click Test to open the file '$0' with its default viewer. 
-   2. After the viewer opens, check out the file that was opened.
-   3. Close the application (LibreOffice, Doc Viewer, etc.)
-  VERIFICATION:
-   Did the application open the document properly? (e.g was it displayed and did it function properly?)
- command: xdg-open $0
- EOF
-
-plugin: local
-name: software/audio_file_play
-requires: package.name == "ubuntu-desktop"
-_description: Common Document Types Test
-command:
- cat <<'EOF' | run_templates -s "find $CHECKBOX_SHARE/data/audio -type f"
- name: `basename $0`_test
- plugin: manual
- description:
-  PURPOSE:
-   This test will check that common audio files can be opened in the default player.
-  STEPS:
-   1. Click Test to open the audio file '$0' with its default player. 
-   2. After the player opens listen to the sound.
-   3. Close the application.
-  VERIFICATION:
-   Did the application play the audio file properly? (no skips, crackles, etc)
- command: xdg-open $0
- EOF
-
-plugin: local
-name: software/video_file_play
-requires: package.name == "ubuntu-desktop"
-_description: Common Document Types Test
-command:
- cat <<'EOF' | run_templates -s "find $CHECKBOX_SHARE/data/video -type f"
- name: `basename $0`_test
- plugin: manual
- description:
-  PURPOSE:
-   This test will check that common video files can be played in the default player.
-  STEPS:
-   1. Click Test to play the video '$0' with its default player. 
-   2. Watch the video.
-   3. Close the application.
-  VERIFICATION:
-   Did the application play '$0' proplerly (no video or audio issues with playback?)
- command: xdg-open $0
- EOF
-
-plugin: local
-name: software/view_image_file
-requires: package.name == "ubuntu-desktop"
-_description: Common Document Types Test
-command:
- cat <<'EOF' | run_templates -s "find $CHECKBOX_SHARE/data/images -type f"
- name: `basename $0`_test
- plugin: manual
- description:
-  PURPOSE:
-   This test will check that common image formats can be opened in the default viewer.
-  STEPS:
-   1. Click Test to attempt to open the image '$0' with its default viewer.
-   2. Check out the file that was opened.
-   3. Close the application.
-  VERIFICATION:
-   Did the image display properly?
- command: xdg-open $0
- EOF
-
-plugin: manual
-name: software/firefox
-requires: package.name == 'firefox'
-command: firefox $CHECKBOX_SHARE/data/websites/testindex.html
-_description:
- PURPOSE:
-  This test will check that Firefox can render a basic web page.
- STEPS:
-  1. Select Test to launch Firefox and view the test web page.
- VERIFICATION:
-  Did the Ubuntu Test page load correctly?
-
-plugin: manual
-name: software/firefox-java
-depends: software/firefox
-requires: package.name == 'firefox'
-command: firefox $CHECKBOX_SHARE/data/websites/javatest.html
-_description:
- PURPOSE:
-  This test will check that Firefox can run a java applet in a web page. Note:
-  this may require installing additional software to complete successfully.
- STEPS:
-  1. Select Test to open Firefox with the Java test page, and follow the instructions there.
- VERIFICATION:
-  Did the applet display?
-
-plugin: manual
-name: software/firefox-flash
-depends: software/firefox
-requires: package.name == 'firefox'
-command: firefox $CHECKBOX_SHARE/data/websites/flashtest.html
-_description:
- PURPOSE:
-  This test will check that Firefox can run flash applications. Note: this may
-  require installing additional software to successfully complete.
- STEPS:
-  1. Select Test to launch Firefox and view a sample Flash test.
- VERIFICATION:
-  Did you see the text?
-
-plugin: manual
-name: software/firefox-flash-video
-depends: software/firefox-flash
-requires: package.name == 'firefox'
-command: firefox $CHECKBOX_SHARE/data/websites/flashvideo.html
-_description:
- PURPOSE:
-  This test will check that Firefox can play a Flash video. Note: this may
-  require installing additional software to successfully complete.
- STEPS:
-  1. Select Test to launch Firefox and view a short flash video.
- VERIFICATION:
-  Did the video play correctly?
-
-plugin: manual
-name: software/firefox-totem
-depends: software/firefox
-requires: 
-    package.name == 'firefox'
-    package.name == 'gstreamer0.10-ffmpeg'
-command: firefox $CHECKBOX_SHARE/data/video/Quicktime_Video.mov
-_description:
- PURPOSE:
-  This test will check that Firefox can play a Quicktime (.mov) video file.
-  Note: this may require installing additional software to successfully
-  complete.
- STEPS:
-  1. Select Test to launch Firefox with a sample video.
- VERIFICATION:
-  Did the video play using a plugin?
-
-plugin: manual
-name: software/empathy-facebook_chat
-requires: package.name == "empathy"
-command: empathy
-_description:
- PURPOSE:
-  This test will check that Empathy messaging client works.
- STEPS:
-  1. Select Test to launch Empathy.
-  2. Configure it to connect to the Facebook Chat service. 
-  3. Once you have completed the test, please quit Empathy to continue here.
- VERIFICATION:
-  Were you able to connect correctly and send/receive messages?
-
-plugin: manual
-name: software/empathy-google_talk
-requires: package.name == "empathy"
-command: empathy
-_description:
- PURPOSE:
-  This test will check that Empathy messaging client works.
- STEPS:
-  1. Select Test to launch Empathy.
-  2. Configure it to connect to the Google Talk (gtalk) service. 
-  3. Once you have completed the test, please quit Empathy to continue here.
- VERIFICATION:
-  Were you able to connect correctly and send/receive messages?
-
-plugin: manual
-name: software/empathy-jabber
-requires: package.name == "empathy"
-command: empathy
-_description:
- PURPOSE:
-  This test will check that Empathy messaging client works.
- STEPS:
-  1. Select Test to launch Empathy.
-  2. Configure it to connect to the Jabber service. 
-  3. Once you have completed the test, please quit Empathy to continue here.
- VERIFICATION:
-  Were you able to connect correctly and send/receive messages?
-
-plugin: manual
-name: software/empathy-aim
-requires: package.name == "empathy"
-command: empathy
-_description:
- PURPOSE:
-  This test will check that Empathy messaging client works.
- STEPS:
-  1. Select Test to launch Empathy.
-  2. Configure it to connect to the AOL Instant Messaging (AIM) service. 
-  3. Once you have completed the test, please quit Empathy to continue here.
- VERIFICATION:
-  Were you able to connect correctly and send/receive messages?
-
-plugin: manual
-name: software/empathy-msn
-requires: package.name == "empathy"
-command: empathy
-_description:
- PURPOSE:
-  This test will check that Empathy messaging client works.
- STEPS:
-  1. Select Test to launch Empathy.
-  2. Configure it to connect to the Microsoft Network (MSN) service. 
-  3. Once you have completed the test, please quit Empathy to continue here.
- VERIFICATION:
-  Were you able to connect correctly and send/receive messages?
-
-plugin: manual
-name: software/evolution-pop3
-requires: package.name == "evolution"
-command: evolution
-_description:
- PURPOSE:
-  This test will check that Evolution works.
- STEPS:
-  1. Click the "Test" button to launch Evolution.
-  2. Configure it to connect to a POP3 account.
- VERIFICATION:
-  Were you able to receive and read e-mail correctly?
-
-plugin: manual
-name: software/evolution-imap
-requires: package.name == "evolution"
-command: evolution
-_description:
- PURPOSE:
-  This test will check that Evolution works.
- STEPS:
-  1. Click the "Test" button to launch Evolution.
-  2. Configure it to connect to a IMAP account.
- VERIFICATION:
-  Were you able to receive and read e-mail correctly?
-
-plugin: manual
-name: software/evolution-smtp
-requires: package.name == "evolution"
-command: evolution
-_description:
- PURPOSE:
-  This test will check that Evolution works.
- STEPS:
-  1. Click the "Test" button to launch Evolution.
-  2. Configure it to connect to a SMTP account.
- VERIFICATION:
-  Were you able to send e-mail without errors?
-
-plugin: manual
-name: software/gcalctool
-requires: package.name == "gcalctool"
-command: gcalctool
-_description:
- PURPOSE:
-  This test checks that gcalctool (Calculator) works.
- STEPS:
-  Click the "Test" button to open the calculator.
- VERIFICATION:
-  Did it launch correctly?
-
-plugin: manual
-name: software/gcalctool-functions
-depends: software/gcalctool
-requires: package.name == "gcalctool"
-command: gcalctool
-_description:
- PURPOSE:
-  This test checks that gcalctool (Calculator) works.
- STEPS:
-  Click the "Test" button to open the calculator and perform:
-  1. Simple math functions (+,-,/,*)
-  2. Nested math functions ((,))
-  3. Fractional math
-  4. Decimal math
- VERIFICATION:
-  Did the functions perform as expected?
-
-plugin: manual
-name: software/gcalctool-memory
-depends: software/gcalctool
-requires: package.name == "gcalctool"
-command: gcalctool
-_description:
- PURPOSE:
-  This test checks that gcalctool (Calculator) works.
- STEPS:
-  Click the "Test" button to open the calculator and perform:
-   1. Memory set
-   2. Memory reset
-   3. Memory last clear
-   4. Memory clear
- VERIFICATION:
-  Did the functions perform as expected?
-
-plugin: manual
-name: software/gcalctool-clipboard
-depends: software/gcalctool
-requires: package.name == "gcalctool"
-command: gcalctool
-_description:
- PURPOSE:
-  This test checks that gcalctool (Calculator) works.
- STEPS:
-  Click the "Test" button to open the calculator and perform:
-   1. Cut
-   2. Copy
-   3. Paste
- VERIFICATION:
-  Did the functions perform as expected?
-
-plugin: manual
-name: software/gedit
-requires: package.name == "gedit"
-command: gedit
-_description:
- PURPOSE:
-  This test checks that gedit works.
- STEPS:
-  1. Click the "Test" button to open gedit.
-  2. Enter some text and save the file (make a note of the file name you use), then close gedit.
- VERIFICATION:
-  Did this perform as expected?
-
-plugin: manual
-name: software/gedit-read
-depends: software/gedit
-requires: package.name == "gedit"
-command: gedit
-_description:
- PURPOSE:
-  This test checks that gedit works.
- STEPS:
-  1. Click the "Test" button to open gedit, and re-open the file you created previously.
-  2. Edit then save the file, then close gedit.
- VERIFICATION:
-  Did this perform as expected?
-
-plugin: manual
-name: software/gnome-terminal
-requires: package.name == "gnome-terminal"
-command: gnome-terminal
-_description:
- PURPOSE:
-  This test will check that Gnome Terminal works.
- STEPS:
-  1. Click the "Test" button to open Terminal.
-  2. Type 'ls' and press enter. You should see a list of files and folder in your home directory.
-  3. Close the terminal window.
- VERIFICATION:
-  Did this perform as expected?

=== removed file 'jobs/wireless.txt.in'
--- jobs/wireless.txt.in	2013-04-18 11:48:32 +0000
+++ jobs/wireless.txt.in	1970-01-01 00:00:00 +0000
@@ -1,221 +0,0 @@
-plugin: shell
-name: wireless/wireless_scanning
-requires:
-  package.name == 'network-manager'
-  device.category == 'WIRELESS'
-command:
- rfkill unblock wlan wifi
- if rfkill list wlan wifi | grep -q 'Hard blocked: yes'; then
-   echo "Hard block is applied to WiFi device. Please remove and retest."
-   exit 1
- fi
- wireless_networks=`nmcli -f SSID dev wifi list`
- if [ `echo "$wireless_networks" | wc -l` -gt 1 ]; then
-   echo "Wireless networks discovered: "
-   echo "$wireless_networks"
-   exit 0
- fi
- echo "No wireless networks discovered."
- exit 1
-_description: Wireless scanning test. It scans and reports on discovered APs.
-
-plugin: manual
-name: wireless/wireless_connection
-command: network_check
-requires: device.category == 'WIRELESS'
-_description:
- PURPOSE:
-     This test will check your wireless connection.
- STEPS:
-     1. Click on the Network icon in the panel.
-     2. Select a network below the 'Wireless networks' section.
-     3. Click "Test" to verify that it's possible to establish an HTTP connection.
- VERIFICATION:
-     Did a notification show and was the connection correctly established?
-
-plugin: shell
-name: wireless/wireless_connection_wpa_bg
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: WPA_BG_SSID WPA_BG_PSK
-command: trap "nmcli con delete id $WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using WPA
- security and the 802.11b/g protocols.
-
-plugin: shell
-name: wireless/wireless_connection_open_bg
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: OPEN_BG_SSID
-command: trap "nmcli con delete id $OPEN_BG_SSID" EXIT; create_connection wifi $OPEN_BG_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using no
- security and the 802.11b/g protocols.
-
-plugin: shell
-name: wireless/wireless_connection_wpa_n
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: WPA_N_SSID WPA_N_PSK
-command: trap "nmcli con delete id $WPA_N_SSID" EXIT; create_connection wifi $WPA_N_SSID --security=wpa --key=$WPA_N_PSK && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using WPA
- security and the 802.11n protocol.
-
-plugin: shell
-name: wireless/wireless_connection_open_n
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'multiple'
-user: root
-environ: OPEN_N_SSID
-command: trap "nmcli con delete id $OPEN_N_SSID" EXIT; create_connection wifi $OPEN_N_SSID &&  internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- Tests that the systems wireless hardware can connect to a router using no
- security and the 802.11n protocol.
-
-plugin: manual
-name: wireless/wireless_connection_wpa_bg_manual
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID ROUTER_PSK
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using WPA
-     security and the 802.11b/g protocols.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the B and G wireless bands
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: manual
-name: wireless/wireless_connection_open_bg_manual
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using
-     no security and the 802.11b/g protocols.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the B and G wireless bands
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use no security
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: manual
-name: wireless/wireless_connection_wpa_n_manual
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID ROUTER_PSK
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID --security=wpa --key=$ROUTER_PSK && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using WPA
-     security and the 802.11n protocols.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the N wireless band
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use WPA2 and ensure the PSK matches that set in ROUTER_PSK
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: manual
-name: wireless/wireless_connection_open_n_manual
-requires:
- device.category == 'WIRELESS'
- environment.ROUTERS == 'single'
-user: root
-environ: ROUTER_SSID
-command: trap "nmcli con delete id $ROUTER_SSID" EXIT; create_connection wifi $ROUTER_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
- PURPOSE:
-     Tests that the systems wireless hardware can connect to a router using
-     no security and the 802.11n protocol.
- STEPS:
-     1. Open your routers configuration tool
-     2. Change the settings to only accept connections on the N wireless band
-     3. Make sure the SSID is set to ROUTER_SSID
-     4. Change the security settings to use no security
-     5. Click the 'Test' button to create a connection to the router and test the connection
- VERIFICATION:
-     Verification is automated, do not change the automatically selected result.
-
-plugin: shell
-name: wireless/monitor_wireless_connection
-requires:
- package.name == 'iperf'
- device.category == 'WIRELESS'
-user: root
-environ: WPA_BG_SSID WPA_BG_PSK SERVER_IPERF
-command: trap "nmcli con delete id $WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK && iperf -c $SERVER_IPERF -t 300 -i 30
-_description:
- Tests the performance of a systems wireless connection through the iperf tool.
-
-plugin: shell
-name: wireless/monitor_wireless_connection_udp
-requires:
- package.name == 'iperf'
- device.category == 'WIRELESS'
-user: root
-environ: WPA_BG_SSID WPA_BG_PSK SERVER_IPERF
-command: trap "nmcli con delete id $WPA_BG_SSID" EXIT; create_connection wifi $WPA_BG_SSID --security=wpa --key=$WPA_BG_PSK && iperf -c $SERVER_IPERF -t 300 -i 30 -u -b 100m -p 5050
-_description:
- Tests the performance of a systems wireless connection through the iperf tool, using UDP packets.
-
-plugin: shell
-name: wireless/wireless_connection_open_a
-requires: device.category == 'WIRELESS'
-user: root
-environ: OPEN_A_SSID
-command: trap "nmcli con delete id $OPEN_A_SSID" EXIT; create_connection wifi $OPEN_A_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
-  Test that the system's wireless hardware can connect to a router using the
-  802.11a protocol. This requires that you have a router pre-configured to only
-  respond to requests on the 802.11a protocol.
-
-plugin: shell
-name: wireless/wireless_connection_open_b
-requires: device.category == 'WIRELESS'
-user: root
-environ: OPEN_B_SSID
-command: trap "nmcli con delete id $OPEN_B_SSID" EXIT; create_connection wifi $OPEN_B_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
-  Test that the system's wireless hardware can connect to a router using the
-  802.11b protocol. This requires that you have a router pre-configured to only
-  respond to requests on the 802.11b protocol.
-
-plugin: shell
-name: wireless/wireless_connection_open_g
-requires: device.category == 'WIRELESS'
-user: root
-environ: OPEN_G_SSID
-command: trap "nmcli con delete id $OPEN_G_SSID" EXIT; create_connection wifi $OPEN_G_SSID && internet_test --interface=`nmcli dev status | awk '/802-11-wireless/ {print $1}'`
-_description:
-  Test that the system's wireless hardware can connect to a router using the
-  802.11g protocol. This requires that you have a router pre-configured to only
-  respond to requests on the 802.11g protocol.

=== modified file 'po/POTFILES.in'
--- po/POTFILES.in	2013-08-06 16:40:53 +0000
+++ po/POTFILES.in	2013-08-19 20:47:35 +0000
@@ -1,54 +1,24 @@
 [encoding: UTF-8]
 [type: gettext/glade] gtk/checkbox-gtk.ui
 qt/checkbox-qt.desktop.in
-[type: gettext/rfc822deb] jobs/audio.txt.in
 [type: gettext/rfc822deb] jobs/benchmarks.txt.in
-[type: gettext/rfc822deb] jobs/bluetooth.txt.in
-[type: gettext/rfc822deb] jobs/camera.txt.in
-[type: gettext/rfc822deb] jobs/codecs.txt.in
 [type: gettext/rfc822deb] jobs/cpu.txt.in
-[type: gettext/rfc822deb] jobs/daemons.txt.in
 [type: gettext/rfc822deb] jobs/dcmi_in_band.txt.in
 [type: gettext/rfc822deb] jobs/disk.txt.in
-[type: gettext/rfc822deb] jobs/esata.txt.in
-[type: gettext/rfc822deb] jobs/expresscard.txt.in
-[type: gettext/rfc822deb] jobs/fingerprint.txt.in
-[type: gettext/rfc822deb] jobs/firewire.txt.in
-[type: gettext/rfc822deb] jobs/floppy.txt.in
-[type: gettext/rfc822deb] jobs/graphics.txt.in
-[type: gettext/rfc822deb] jobs/hibernate.txt.in
 [type: gettext/rfc822deb] jobs/info.txt.in
-[type: gettext/rfc822deb] jobs/input.txt.in
-[type: gettext/rfc822deb] jobs/install.txt.in
 [type: gettext/rfc822deb] jobs/ipmi_out_of_band.txt.in
-[type: gettext/rfc822deb] jobs/keys.txt.in
-[type: gettext/rfc822deb] jobs/led.txt.in
 [type: gettext/rfc822deb] jobs/local.txt.in
-[type: gettext/rfc822deb] jobs/mediacard.txt.in
 [type: gettext/rfc822deb] jobs/memory.txt.in
 [type: gettext/rfc822deb] jobs/miscellanea.txt.in
-[type: gettext/rfc822deb] jobs/mobilebroadband.txt.in
-[type: gettext/rfc822deb] jobs/monitor.txt.in
 [type: gettext/rfc822deb] jobs/networking.txt.in
 [type: gettext/rfc822deb] jobs/optical.txt.in
-[type: gettext/rfc822deb] jobs/panel_clock_test.txt.in
-[type: gettext/rfc822deb] jobs/panel_reboot.txt.in
-[type: gettext/rfc822deb] jobs/peripheral.txt.in
-[type: gettext/rfc822deb] jobs/piglit.txt.in
 [type: gettext/rfc822deb] jobs/power-management.txt.in
-[type: gettext/rfc822deb] jobs/rendercheck.txt.in
 [type: gettext/rfc822deb] jobs/resource.txt.in
-[type: gettext/rfc822deb] jobs/server-services.txt.in
 [type: gettext/rfc822deb] jobs/smoke.txt.in
 [type: gettext/rfc822deb] jobs/sniff.txt.in
 [type: gettext/rfc822deb] jobs/stress.txt.in
-[type: gettext/rfc822deb] jobs/suspend.txt.in
-[type: gettext/rfc822deb] jobs/touchpad.txt.in
-[type: gettext/rfc822deb] jobs/touchscreen.txt.in
 [type: gettext/rfc822deb] jobs/usb.txt.in
-[type: gettext/rfc822deb] jobs/user_apps.txt.in
 [type: gettext/rfc822deb] jobs/virtualization.txt.in
-[type: gettext/rfc822deb] jobs/wireless.txt.in
 checkbox/application.py
 checkbox/job.py
 checkbox/lib/signal.py
@@ -71,8 +41,6 @@
 plugins/shell_test.py
 plugins/suites_prompt.py
 plugins/user_interface.py
-scripts/keyboard_test
-scripts/key_test
 scripts/internet_test
 checkbox_qt/qt_interface.py
 qt/frontend/checkboxtr.cpp

=== removed file 'scripts/accelerometer_test'
--- scripts/accelerometer_test	2012-08-30 16:00:12 +0000
+++ scripts/accelerometer_test	1970-01-01 00:00:00 +0000
@@ -1,347 +0,0 @@
-#!/usr/bin/env python3
-'''
-script to test accerometer functionality
-
-Copyright (C) 2012 Canonical Ltd.
-
-Authors
-  Jeff Marcom <[e-mail]>
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the GNU General Public License version 3,
-as published by the Free Software Foundation.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-The purpose of this script is to simply interact with an onboard
-accelerometer, and check to be sure that the x, y, z axis respond
-to physical movement of hardware.
-'''
-from argparse import ArgumentParser
-from gi.repository import Gdk, GLib, Gtk
-import logging
-import os
-import re
-import sys
-import threading
-import time
-from subprocess import Popen, PIPE, check_output, STDOUT, CalledProcessError
-from checkbox.parsers.modinfo import ModinfoParser
-
-handler = logging.StreamHandler()
-logger = logging.getLogger()
-logger.addHandler(handler)
-logger.setLevel(logging.DEBUG)
-
-
-class AccelerometerUI(Gtk.Window):
-    """Builds UI Framework for axis threshold tests using Gtk"""
-
-    def __init__(self):
-        Gtk.Window.__init__(self, title="Accelerometer Test")
-
-        self.set_default_size(450, 100)
-        self.set_type_hint(Gdk.WindowType.TOPLEVEL)
-
-        self.enabled = False
-
-        # Create UI Grid
-        w_table = Gtk.Grid()
-        self.add(w_table)
-
-        # Create axis buttons
-        self.up_icon = Gtk.Image(stock=Gtk.STOCK_GO_UP)
-        self.up_icon.set_padding(10, 30)
-        self.down_icon = Gtk.Image(stock=Gtk.STOCK_GO_DOWN)
-        self.down_icon.set_padding(10, 30)
-        self.left_icon = Gtk.Image(stock=Gtk.STOCK_GO_BACK)
-        self.right_icon = Gtk.Image(stock=Gtk.STOCK_GO_FORWARD)
-
-        # Set debug
-        self.debug_label = Gtk.Label("Debug")
-
-        # Set Grid layout for UI
-        message = "Please tilt your hardware in the positions shown below:"
-        w_table.attach(Gtk.Label(message), 0, 0, 4, 1)
-
-        w_table.attach(self.up_icon, 2, 2, 1, 1)
-        w_table.attach_next_to(self.debug_label, self.up_icon,
-                               Gtk.PositionType.BOTTOM, 1, 1)
-        w_table.attach_next_to(self.down_icon, self.debug_label,
-                               Gtk.PositionType.BOTTOM, 1, 1)
-        w_table.attach_next_to(self.left_icon, self.debug_label,
-                               Gtk.PositionType.LEFT, 1, 1)
-        w_table.attach_next_to(self.right_icon, self.debug_label,
-                               Gtk.PositionType.RIGHT, 1, 1)
-
-    def update_axis_icon(self, direction):
-        """Change desired directional icon to checkmark"""
-        exec('self.%s_icon.set_from_stock' % (direction) \
-             + '(Gtk.STOCK_YES, size=Gtk.IconSize.BUTTON)')
-
-    def update_debug_label(self, text):
-        """Update axis information in center of UI"""
-        self.debug_label.set_text(text)
-
-    def destroy(self):
-        Gtk.main_quit()
-
-    def enable(self):
-        self.enabled = True
-        self.connect("delete-event", Gtk.main_quit)
-        self.show_all()
-
-        # Enable GLib/Gdk threading so the UI won't lock main
-        GLib.threads_init()
-        Gdk.threads_init()
-        Gdk.threads_enter()
-        Gtk.main()
-        Gdk.threads_leave()
-
-
-class PermissionException(RuntimeError):
-    def __init__(self, error):
-        message = "Please re-run with root permissions: %s" % error.strip()
-        super(PermissionException, self).__init__(message)
-
-
-class AxisData(threading.Thread):
-    """Acquire information from kernel regarding the state of the
-    accelerometer axis positions. Gathered data will be compared to
-    a preset threshold reading. The default threshold (either - or + )
-    for any direction is 600. Return values for thread are SUCCESS:0
-    FAILURE:1. FAILURE is likely to exists when thread is unable to
-    obtain a valid reading from the hardware."""
-
-    def __init__(self, device_path, ui_control=None):
-        threading.Thread.__init__(self)