Merge ~gavin.lin/plainbox-provider-snappy:after-suspend into plainbox-provider-snappy:master

[Gavin Lin]

Add tests for after suspend, basically they are same as the tests before suspend but removed unnecessary ones.

[Sylvain Pineau (sylvain-pineau)]

The preferred way to create "after suspend" jobs is as of plainbox 0.33 to use the flag 'also-after-suspend'

(See http://checkbox.readthedocs.io/projects/plainbox/en/latest/manpages/plainbox-job-units.html?highlight=also-after-suspend)

I'm closing this MR

review: Disapprove

Unmerged commits

644edc5... by Gavin Lin on 2017-01-06

Add some tests for after suspend

diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/bluetooth.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/bluetooth.pxu
new file mode 100644
index 0000000..889c1dc
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/bluetooth.pxu
@@ -0,0 +1,41 @@
+id: after-suspend/bluetooth/hid
+_summary: Bluetooth input device works after suspend
+_purpose:
+ Check bluetooth input device work after suspend
+ Since there's only CLI with ubuntu-core, test keyboard only
+_steps:
+ 1. Run following command to start bluetoothctl console:
+  For Desktop:
+    bluetoothctl -a
+  For UC16:
+    sudo bluez.bluetoothctl -a
+ ***Following steps are run in bluetoothctl console***
+ 2. Power on the device:
+  power on
+ 3. Register agent for keyboard:
+  agent KeyboardOnly
+  default-agent
+ 4. Put controller in pairable mode:
+  pairable on
+ 5. Scan nearby bluetooth device:
+  scan on
+ 6. Stop Scanning after bluetooth keyboard is found:
+  scan off
+ 7. Pair bluetooth
+  pair [MAC address of bluetooth keyboard]
+ 8. Enter PIN Code on bluetooth keyboard if needed
+ 9. Trust the bluetooth keyboard
+  trust [MAC address of bluetooth keyboard]
+ 10. Connect to bluetooth keyboard:
+  connect [MAC address of bluetooth keyboard]
+ 11. Quit bluetoothctl console
+  quit
+ 12. Use bluetooth keyboard to input
+_verification:
+ Can input from bluetooth input device
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+requires: device.category == 'BLUETOOTH'
+depends: suspend/suspend-manual
+estimated_duration: 5m
+
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/ethernet.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/ethernet.pxu
new file mode 100644
index 0000000..c9d65b2
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/ethernet.pxu
@@ -0,0 +1,29 @@
+id: after-suspend/ethernet/detect
+_summary:
+ Report info about available network devices after suspend
+_description:
+ Test to detect and return information about available network controllers on
+ the system under test after suspend.
+plugin: shell
+category_id: 2013.com.canonical.plainbox::suspend
+requires:
+ device.category == 'NETWORK' or device.category == 'WIRELESS'
+# package.name == 'kmod' or package.name == 'module-init-tools'
+# package.name == 'pciutils'
+depends: suspend/suspend-manual
+command: network_device_info
+estimated_duration: 2s
+
+unit: template
+template-resource: device
+template-filter: device.category == 'NETWORK'
+id: after-suspend/ethernet/ping_{interface}
+_summary: Can ping another machine over Ethernet port {interface} after suspend
+_description: Check Ethernet works by pinging another machine after suspend
+plugin: shell
+command:
+  gateway_ping_test -v --interface {interface}
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 4.0
+flags: preserve-locale
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/i2c.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/i2c.pxu
new file mode 100644
index 0000000..4579863
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/i2c.pxu
@@ -0,0 +1,46 @@
+# Copyright 2016 Canonical Ltd.
+# All rights reserved.
+#
+# Written by:
+#   Gavin Lin <[e-mail]>
+
+unit: job
+id: after-suspend/i2c/i2c-bus-detect
+_summary: Check number of detected I2C bus after suspend
+_purpose:
+ Verify if number of detected I2C bus is as expected after suspend
+_steps:
+ 1. This task is fully automatic, when expected i2c bus number($I2C_BUS_NUMBER)
+    is set, this job will verify if detected number of i2c bus is as expected.
+ 2. If expected i2c bus number is not set, this job will pass if system
+    detected there's at least one i2c bus.
+command:
+ if [ -z ${I2C_BUS_NUMBER+x} ]; then
+     i2c_driver_test bus
+ else
+     i2c_driver_test bus -b $I2C_BUS_NUMBER
+ fi
+user: root
+plugin: shell
+category_id: 2013.com.canonical.plainbox::suspend
+environ: I2C_BUS_NUMBER
+estimated_duration: 20s
+requires: manifest.has_i2c == 'True'
+depends: suspend/suspend-manual
+imports: from 2013.com.canonical.plainbox import manifest
+
+unit: job
+id: after-suspend/i2c/i2c-device-detect
+_summary: Check if any I2C device detected after suspend
+_purpose:
+ Verify if there's any I2C device after suspend
+_steps:
+ 1. This task is fully automatic, test will pass if there's at least one
+    i2c device detected on any I2C bus.
+command:
+ i2c_driver_test device
+user: root
+plugin: shell
+category_id: 2013.com.canonical.plainbox::suspend
+estimated_duration: 3m
+depends: after-suspend/i2c/i2c-bus-detect
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/led.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/led.pxu
new file mode 100644
index 0000000..ce7961f
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/led.pxu
@@ -0,0 +1,48 @@
+id: after-suspend/led/power
+_summary: Power LED behavior when powered after suspend
+_purpose:
+ Check power led is on when system is powered on after suspend
+_steps:
+ 1. Check power led when system is powered on
+_verification:
+ Power led is on when system is powered on
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 30
+
+id: after-suspend/led/bluetooth
+_summary: Bluetooth LED behavior after suspend
+_purpose:
+ Check bluetooth LED behavior is correct after suspend
+_steps:
+ 1. Run following command to start bluetoothctl console:
+  sudo bluez.bluetoothctl -a
+ ***Following steps are run in bluetoothctl console***
+ 2. Power on the device:
+  power on
+ 3. Power off the device:
+  power off
+ 4. Quit bluetoothctl console
+  quit
+_verification:
+ Bluetooth LED is turned on in step 2, and turned off in step 3.
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 3m
+
+id: after-suspend/led/serial
+_summary: Serial ports LED behavior after suspend
+_purpose:
+ Check serial ports LED behavior is correct after suspend
+_steps:
+ 1. Start the test to send data to all serial ports (/dev/ttyS*)
+_verification:
+ All serial ports LED are on for a few seconds (3-4s)
+plugin: user-interact-verify
+command: echo {0..1024} | tee /dev/ttyS{0..100} &> /dev/null
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 15
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/location.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/location.pxu
new file mode 100644
index 0000000..51bb2a0
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/location.pxu
@@ -0,0 +1,8 @@
+id: after-suspend/location/monitor
+_summary: Connects to a location service instance, monitoring its activity after suspend
+command: timeout 15m bash -c 'locationd.monitor | grep -m1 --line-buffered ".*"'
+category_id: 2013.com.canonical.plainbox::suspend
+requires: snap.name == 'locationd'
+depends: suspend/suspend-manual
+estimated_duration: 900
+flags: simple preserve-cwd
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/mediacard.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/mediacard.pxu
new file mode 100644
index 0000000..800eee9
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/mediacard.pxu
@@ -0,0 +1,451 @@
+plugin: user-interact
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/mmc-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the systems media card reader can
+     detect the insertion of a Multimedia Card (MMC) media after suspend.
+ STEPS:
+     1. Commence the test and then insert an MMC card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/mmc-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/mmc-insert
+user: root
+command: removable_storage_test -s 67120000 --memorycard sdio usb scsi --auto-reduce-size
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/mmc-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/mmc-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of the MMC card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sd-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the systems media card reader can
+     detect the insertion of an UNLOCKED Secure Digital (SD) media card after
+     suspend.
+ STEPS:
+     1. Commence the test and then insert an UNLOCKED SD card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sd-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/sd-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sd-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/sd-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects
+     the removal of an SD card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sd-preinserted
+estimated_duration: 30.0
+user: root
+command: removable_storage_test -s 268400000 --memorycard -l sdio usb scsi && removable_storage_test --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sdhc-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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 after suspend.
+ STEPS:
+     1. Commence the test and then insert an UNLOCKED SDHC card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sdhc-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/sdhc-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sdhc-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/sdhc-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of an SDHC card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/cf-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the systems media card reader can
+     detect the insertion of a Compact Flash (CF) media card after suspend.
+ STEPS:
+     1. Commence the test and then insert a CF card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/cf-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/cf-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/cf-remove
+depends: after-suspend/mediacard/cf-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of a CF card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sdxc-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+     after suspend.
+ STEPS:
+     1. Commence the test and then insert an UNLOCKED SDXC card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sdxc-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/sdxc-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/sdxc-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/sdxc-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of a SDXC card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/ms-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the systems media card reader can
+     detect the insertion of a Memory Stick (MS) media card after suspend.
+ STEPS:
+     1. Commence the test and then insert a MS card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/ms-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/ms-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/ms-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/ms-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of a MS card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/msp-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+_description:
+ PURPOSE:
+     This test will check that the systems media card reader can
+     detect the insertion of a Memory Stick Pro (MSP) media card after suspend.
+ STEPS:
+     1. Commence the test and then insert a MSP card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/msp-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/msp-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/msp-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/msp-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of a MSP card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the 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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/xd-insert
+estimated_duration: 30.0
+command: removable_storage_watcher --unmounted --memorycard insert sdio usb scsi
+requires:
+ snap.name == 'udisks2'
+ device.category == 'CARDREADER'
+depends: suspend/suspend-manual
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the systems media card reader can
+     detect the insertion of a Extreme Digital (xD) media card after suspend.
+ STEPS:
+     1. Commence the test and then insert a xD card into the reader.
+        (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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/xd-storage
+estimated_duration: 30.0
+depends: after-suspend/mediacard/xd-insert
+user: root
+command: removable_storage_test -s 268400000 --memorycard sdio usb scsi
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_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
+category_id: 2013.com.canonical.plainbox::suspend
+id: after-suspend/mediacard/xd-remove
+estimated_duration: 30.0
+depends: after-suspend/mediacard/xd-insert
+command: removable_storage_watcher --unmounted --memorycard remove sdio usb scsi
+user: root
+environ: LD_LIBRARY_PATH GI_TYPELIB_PATH
+_description:
+ PURPOSE:
+     This test will check that the system correctly detects 
+     the removal of a xD card from the systems card reader after suspend.
+ STEPS:
+     1. Commence the test and then 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.
+
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/monitor.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/monitor.pxu
new file mode 100644
index 0000000..8bf5387
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/monitor.pxu
@@ -0,0 +1,55 @@
+id: after-suspend/monitor/dvi
+_summary: Monitor works (DVI) after suspend
+_purpose:
+ Check output to display through DVI port after suspend
+_steps:
+ 1. Connect display to DVI port
+ 2. Check the display
+_verification:
+ Output to display works
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 300
+
+id: after-suspend/monitor/hdmi
+_summary: Monitor works (HDMI) after suspend
+_purpose:
+ Check output to display through HDMI port after suspend
+_steps:
+ 1. Connect display to HDMI port
+ 2. Check the display
+_verification:
+ Output to display works
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 300
+
+id: after-suspend/monitor/dvi-to-vga
+_summary: Monitor works (DVI-to-VGA) after suspend
+_purpose:
+ Check output to display through VGA adaptor on DVI port after suspend
+_steps:
+ 1. Connect display to VGA adaptor on DVI port
+ 2. Check the display
+_verification:
+ Output to display works
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 300
+
+id: after-suspend/monitor/displayport_hotplug
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+_purpose:
+     This test will check the DisplayPort port and the ability to do hotplugging
+     after suspend.
+_steps:
+     Skip this test if your system does not have a DisplayPort port.
+     1. If a display is already connected, unplug it.
+     2. (Re-)Connect a display to the DisplayPort port on your system
+_verification:
+     Was the interface displayed correctly on the screen?
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/usb-c.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/usb-c.pxu
new file mode 100644
index 0000000..23c0e1d
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/usb-c.pxu
@@ -0,0 +1,153 @@
+id: after-suspend/usb-c/c-to-a-adapter/hid
+_summary: USB HID work on USB Type-C port using a "USB Type-C to Type-A" adapter after suspend
+_purpose:
+     This test will check that you can use a USB HID device plugged in a USB
+     Type-C port using a "USB Type-C to Type-A" adapter after suspend
+_steps:
+     1. Enable either a USB mouse or keyboard by plugging it in the USB Type-C port using a "USB Type-C to Type-A" adapter
+     2. For mice, perform actions such as moving the pointer, right and left button clicks and double clicks
+     3. For keyboards, switch to another tty and type some text
+_verification:
+     Did the device work as expected?
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+imports: from 2013.com.canonical.plainbox import manifest
+requires: manifest.has_usb_type_c == 'True'
+depends: suspend/suspend-manual
+estimated_duration: 60
+
+id: after-suspend/usb-c/c-to-a-adapter/insert
+_purpose:
+     This test will check that the system correctly detects the insertion of
+     a USB 3 storage device in a USB Type-C connector using a "Type-C to Type-A"
+     adapter after suspend
+_steps:
+     1. Commence the test
+     2. Connect a USB 3 storage device to a USB Type-C port using a 
+        "Type-C to Type-A" adapter
+     3. Do not unplug the device after the test.
+_verification:
+     The verification of this test is automated. Do not change the
+     automatically selected result.
+plugin: user-interact
+user: root
+command: checkbox-support-run_watcher insertion usb3
+category_id: 2013.com.canonical.plainbox::suspend
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+ manifest.has_usb_type_c == 'True'
+depends: suspend/suspend-manual
+estimated_duration: 30
+
+id: after-suspend/usb-c/c-to-a-adapter/storage-automated
+_description:
+ This test is automated and executes after the after-suspend/usb-c/c-to-a-adapter/insert test
+ is run.
+plugin: shell
+user: root
+command: usb_read_write
+category_id: 2013.com.canonical.plainbox::suspend
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+ manifest.has_usb_type_c == 'True'
+depends: after-suspend/usb-c/c-to-a-adapter/insert
+estimated_duration: 60 
+
+id: after-suspend/usb-c/c-to-a-adapter/remove
+_purpose:
+     This test will check that the system correctly detects the removal of
+     a USB 3 storage device connected to a USB Type-C port using a "USB Type-C
+     to Type-A" adapter after suspend.
+_steps:
+     1. Commence the test
+     2. Disconnect a USB 3 storage device to a USB Type-C port using a
+        "Type-C to Type-A" adapter
+_verification:
+     The verification of this test is automated. Do not change the
+     automatically selected result.
+plugin: user-interact
+user: root
+command: checkbox-support-run_watcher removal usb3
+category_id: 2013.com.canonical.plainbox::suspend
+depends: after-suspend/usb-c/c-to-a-adapter/insert
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+ manifest.has_usb_type_c == 'True'
+estimated_duration: 30
+
+id: after-suspend/usb-c/hid
+_summary: USB HID work on USB Type-C port after suspend
+_purpose:
+     This test will check that you can use a USB HID device plugged in a USB
+     Type-C port after suspend
+_steps:
+     1. Enable either a USB mouse or keyboard by plugging it in the USB Type-C port
+     2. For mice, perform actions such as moving the pointer, right and left button clicks and double clicks
+     3. For keyboards, switch to another tty and type some text
+_verification:
+     Did the device work as expected?
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+imports: from 2013.com.canonical.plainbox import manifest
+requires: manifest.has_usb_type_c == 'True'
+depends: suspend/suspend-manual
+estimated_duration: 60
+
+id: after-suspend/usb-c/insert
+_summary: USB 3.0 storage device insertion detected on USB Type-C port after suspend
+_purpose:
+     This test will check that the system correctly detects the insertion of
+     a USB 3 storage device in a USB Type-C connector after suspend.
+_steps:
+     1. Commence the test
+     2. Connect a USB 3 storage device to a USB Type-C port
+     3. Do not unplug the device after the test.
+_verification:
+     The verification of this test is automated. Do not change the
+     automatically selected result.
+plugin: user-interact
+user: root
+command: checkbox-support-run_watcher insertion usb3
+category_id: 2013.com.canonical.plainbox::suspend
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+ manifest.has_usb_type_c == 'True'
+depends: suspend/suspend-manual
+estimated_duration: 30
+
+id: after-suspend/usb-c/storage-automated
+_summary: USB 3.0 storage device read & write works on USB Type-C port after suspend
+_description:
+ This test is automated and executes after the after-suspend/usb-c/insert test
+ is run.
+plugin: shell
+user: root
+command: usb_read_write
+category_id: 2013.com.canonical.plainbox::suspend
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+ manifest.has_usb_type_c == 'True'
+depends: after-suspend/usb-c/insert
+estimated_duration: 60
+
+id: after-suspend/usb-c/remove
+_summary: USB 3.0 storage device removal detected on USB Type-C port after suspend
+_purpose:
+     This test will check that the system correctly detects the removal of
+     a USB 3 storage device connected to a USB Type-C port after suspend.
+_steps:
+     1. Commence the test
+     2. Disconnect a USB 3 storage device to a USB Type-C port
+_verification:
+     The verification of this test is automated. Do not change the
+     automatically selected result.
+plugin: user-interact
+user: root
+command: checkbox-support-run_watcher removal usb3
+category_id: 2013.com.canonical.plainbox::suspend
+depends: after-suspend/usb-c/insert
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+ manifest.has_usb_type_c == 'True'
+estimated_duration: 30
+
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/usb.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/usb.pxu
new file mode 100644
index 0000000..8264ca8
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/usb.pxu
@@ -0,0 +1,124 @@
+id: after-suspend/usb/hid
+_summary: USB keyboard works after suspend
+_purpose:
+ Check USB input device works after suspend
+_steps:
+ 1. Connect USB keyboard
+ 2. Input somethings with USB keyboard
+_verification:
+ What just input is displayed correctly
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 60
+
+id: after-suspend/usb/insert
+_summary: USB 2.0 storage device insertion detected after suspend
+_purpose:
+ Check system can detect USB 2.0 storage when inserted after suspend
+_steps:
+ 1. Press continue
+ 2. Connect USB 2.0 storage device
+_verification:
+ Can find new USB 2.0 storage device messages in /var/log/syslog
+plugin: user-interact
+user: root
+command: checkbox-support-run_watcher insertion usb2
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 120
+
+id: after-suspend/usb/storage-automated
+_summary: USB 2.0 storage device read & write works after suspend
+_purpose:
+ Check system can read/write to USB 2.0 storage correctly
+_steps:
+ 1. This task is fully automatic and need USB 2.0 insertion test was applied
+    first.
+_verification:
+ This task is fully automatic and will verify the result for you.
+plugin: shell
+depends: after-suspend/usb/insert
+user: root
+command: usb_read_write
+category_id: 2013.com.canonical.plainbox::suspend
+estimated_duration: 300
+
+id: after-suspend/usb/remove
+_summary: USB 2.0 storage device removal detected after suspend
+_purpose:
+ Check system can detect removal of a USB 2.0 storage device after suspend
+_steps:
+ 1. Press continue
+ 2. Disconnect USB 2.0 storage device
+_verification:
+ Can find USB 2.0 storage device removed messages in /var/log/syslog
+plugin: user-interact
+depends: after-suspend/usb/insert
+user: root
+command: checkbox-support-run_watcher removal usb2
+category_id: 2013.com.canonical.plainbox::suspend
+estimated_duration: 120
+
+id: after-suspend/usb3/hid
+_summary: USB keyboard works on USB 3.0 port after suspend
+_purpose:
+ Check USB input device works on USB 3.0 port after suspend
+_steps:
+ 1. Connect USB keyboard to USB 3.0 port
+ 2. Input somethings with USB keyboard
+_verification:
+ What just input is displayed correctly
+plugin: manual
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 60
+
+id: after-suspend/usb3/insert
+_summary: USB 3.0 storage device insertion detected after suspend
+_purpose:
+ Check system can detect insertion of a USB 3.0 storage device after suspend
+_steps:
+ 1. Press continue
+ 2. Connect USB 3.0 storage device
+_verification:
+ Can find new USB 3.0 storage device messages in /var/log/syslog
+plugin: user-interact
+user: root
+command: checkbox-support-run_watcher insertion usb3
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 120
+
+id: after-suspend/usb3/storage-automated
+_summary: USB 3.0 storage device read & write works after suspend
+_purpose:
+ Check system can read/write to USB 3.0 storage devices correctly after suspend
+_steps:
+ 1. This task is fully automatic and need USB 3.0 insertion test was applied
+    first.
+_verification:
+ This task is fully automatic and will verify the result for you.
+plugin: shell
+depends: after-suspend/usb3/insert
+user: root
+command: usb_read_write
+category_id: 2013.com.canonical.plainbox::suspend
+estimated_duration: 300
+
+id: after-suspend/usb3/remove
+_summary: USB 3.0 storage device removal detected after suspend
+_purpose:
+ Check system can detect removal of a USB 3.0 storage device after suspend
+_steps:
+ 1. Press continue
+ 2. Disconnect USB 3.0 storage device
+_verification:
+ Can find USB 3.0 storage device removed messages in /var/log/syslog
+plugin: user-interact
+depends: after-suspend/usb3/insert
+user: root
+command: checkbox-support-run_watcher removal usb3
+category_id: 2013.com.canonical.plainbox::suspend
+estimated_duration: 120
+
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/watchdog.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/watchdog.pxu
new file mode 100644
index 0000000..8a5c4ec
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/watchdog.pxu
@@ -0,0 +1,28 @@
+id: after-suspend/watchdog/systemd-config
+_summary: Check if the hardware watchdog is properly configured after suspend
+command: journalctl | grep -i 'hardware watchdog'
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+flags: simple
+
+id: after-suspend/watchdog/trigger-system-reset
+depends: after-suspend/watchdog/systemd-config
+_summary: Test that the watchdog module can trigger a system reset after suspend
+_purpose:
+ The watchdog module should be capable of issuing a hard reset of the SUT after
+ suspend.
+_steps:
+ 1. Commence the test to trigger a SysRq.
+ 2. Once the watchdog timeout has expired (10s) the SUT should reset itself.
+ 3. The board will reboot and the user should resume the test session.
+_verification:
+ Did the board reset itself?
+command:
+  echo 0 > /proc/sys/kernel/panic
+  echo c > /proc/sysrq-trigger
+flags: noreturn preserve-locale
+user: root
+plugin: user-interact-verify
+category_id: 2013.com.canonical.plainbox::suspend
+estimated_duration: 60
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/wireless.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/wireless.pxu
new file mode 100644
index 0000000..3be4b0b
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/wireless.pxu
@@ -0,0 +1,814 @@
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_scanning_{interface}
+_summary: System can discover Wi-Fi networks on {interface} after suspend
+command:
+ nmcli dev wifi rescan
+ AP_COUNT=$(nmcli dev wifi list ifname {interface} | wc -l)
+ if [ $AP_COUNT -gt 1 ]; then
+   echo "Wireless access points discovered: $AP_COUNT"
+   exit 0
+ fi
+ echo "No wireless access points discovered."
+ exit 1
+user: root
+environ: LD_LIBRARY_PATH
+plugin: shell
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 6
+_description:
+ Check system can find a wireless network AP nearby after suspend
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_open_ac_{interface}
+_summary: Connect to unencrypted 802.11ac Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to insecure 802.11ac AP after suspend
+_steps:
+ 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
+ 2. Commence the test
+_verification:
+ If there's "Connection test passed" message in result, mark the test as passed.
+plugin: user-interact
+command: wifi_client_test -i {interface} -s $OPEN_AC_SSID
+environ: OPEN_AC_SSID
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 90
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_open_bg_{interface}
+_summary: Connect to unencrypted 802.11b/g Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to insecure 802.11b/g AP after suspend
+_steps:
+ 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
+ 2. Commence the test
+_verification:
+ If there's "Connection test passed" message in result, mark the test as passed.
+plugin: user-interact
+command: wifi_client_test -i {interface} -s $OPEN_BG_SSID
+environ: OPEN_BG_SSID
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 90
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_open_n_{interface}
+_summary: Connect to unencrypted 802.11n Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to insecure 802.11n AP after suspend
+_steps:
+ 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
+ 2. Commence the test
+_verification:
+ If there's "Connection test passed" message in result, mark the test as passed.
+plugin: user-interact
+command: wifi_client_test -i {interface} -s $OPEN_N_SSID
+environ: OPEN_N_SSID
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 90
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_wpa_ac_{interface}
+_summary: Connect to WPA-encrypted 802.11ac Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to 802.11ac AP with wpa security after suspend
+_steps:
+ 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
+ 2. Commence the test
+_verification:
+ If there's "Connection test passed" message in result, mark the test as passed.
+plugin: user-interact
+command: wifi_client_test -i {interface} -s $WPA_AC_SSID -k $WPA_AC_PSK
+environ: WPA_AC_SSID WPA_AC_PSK
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 90
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_wpa_bg_{interface}
+_summary: Connect to WPA-encrypted 802.11b/g Wi-Fi network {interface} after suspend
+_purpose:
+ Check system can connect to 802.11b/g AP with wpa security after suspend
+_steps:
+ 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
+ 2. Commence the test
+_verification:
+ If there's "Connection test passed" message in result, mark the test as passed.
+plugin: user-interact
+command: wifi_client_test -i {interface} -s $WPA_BG_SSID -k $WPA_BG_PSK
+environ: WPA_BG_SSID WPA_BG_PSK
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 90
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_wpa_n_{interface}
+_summary: Connect to WPA-encrypted 802.11n Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to 802.11n AP with wpa security after suspend
+_steps:
+ 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
+ 2. Commence the test
+_verification:
+ If there's "Connection test passed" message in result, mark the test as passed.
+plugin: user-interact
+command: wifi_client_test -i {interface} -s $WPA_N_SSID -k $WPA_N_PSK
+environ: WPA_N_SSID WPA_N_PSK
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 90
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_open_ac_nm_{interface}
+_summary: Connect to unencrypted 802.11ac Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to insecure 802.11ac AP after suspend
+plugin: shell
+command:
+    nmcli g > /dev/null
+    if [ $? -ne 0 ]; then
+        exit 1
+    fi
+    trap "nmcli dev disconnect {interface}; nmcli con delete id WIFI_TEST_CREATED_BY_CHECKBOX" EXIT
+    nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs nmcli c delete
+    nmcli dev wifi rescan
+    nmcli dev wifi connect $OPEN_AC_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+    iw dev {interface} link
+    COUNT=$(iw dev {interface} link | wc -l)
+    if [ $COUNT -gt 1 ]; then
+        exit 0
+    fi
+    exit 1
+environ: LD_LIBRARY_PATH OPEN_AC_SSID
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 5.0
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_open_bg_nm_{interface}
+_summary: Connect to unencrypted 802.11b/g Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to insecure 802.11b/g AP after suspend
+plugin: shell
+command:
+    nmcli g > /dev/null
+    if [ $? -ne 0 ]; then
+        exit 1
+    fi
+    trap "nmcli dev disconnect {interface}; nmcli con delete id WIFI_TEST_CREATED_BY_CHECKBOX" EXIT
+    nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs nmcli c delete
+    nmcli dev wifi rescan
+    nmcli dev wifi connect $OPEN_BG_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+    iw dev {interface} link
+    COUNT=$(iw dev {interface} link | wc -l)
+    if [ $COUNT -gt 1 ]; then
+        exit 0
+    fi
+    exit 1
+environ: LD_LIBRARY_PATH OPEN_BG_SSID
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 5.0
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_open_n_nm_{interface}
+_summary: Connect to unencrypted 802.11n Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to insecure 802.11n AP after suspend
+plugin: shell
+command:
+    nmcli g > /dev/null
+    if [ $? -ne 0 ]; then
+        exit 1
+    fi
+    trap "nmcli dev disconnect {interface}; nmcli con delete id WIFI_TEST_CREATED_BY_CHECKBOX" EXIT
+    nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs nmcli c delete
+    nmcli dev wifi rescan
+    nmcli dev wifi connect $OPEN_N_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+    iw dev {interface} link
+    COUNT=$(iw dev {interface} link | wc -l)
+    if [ $COUNT -gt 1 ]; then
+        exit 0
+    fi
+    exit 1
+environ: LD_LIBRARY_PATH OPEN_N_SSID
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 5.0
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_wpa_ac_nm_{interface}
+_summary: Connect to WPA-encrypted 802.11ac Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to 802.11ac AP with wpa security after suspend
+plugin: shell
+command:
+    nmcli g > /dev/null
+    if [ $? -ne 0 ]; then
+        exit 1
+    fi
+    trap "nmcli dev disconnect {interface}; nmcli con delete id WIFI_TEST_CREATED_BY_CHECKBOX" EXIT
+    nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs nmcli c delete
+    nmcli dev wifi rescan
+    nmcli dev wifi connect $WPA_AC_SSID password $WPA_AC_PSK ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+    iw dev {interface} link
+    COUNT=$(iw dev {interface} link | wc -l)
+    if [ $COUNT -gt 1 ]; then
+        exit 0
+    fi
+    exit 1
+environ: LD_LIBRARY_PATH WPA_AC_SSID WPA_AC_PSK
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 5.0
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_wpa_bg_nm_{interface}
+_summary: Connect to WPA-encrypted 802.11b/g Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to 802.11b/g AP with wpa security after suspend
+plugin: shell
+command:
+    nmcli g > /dev/null
+    if [ $? -ne 0 ]; then
+        exit 1
+    fi
+    trap "nmcli dev disconnect {interface}; nmcli con delete id WIFI_TEST_CREATED_BY_CHECKBOX" EXIT
+    nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs nmcli c delete
+    nmcli dev wifi rescan
+    nmcli dev wifi connect $WPA_BG_SSID password $WPA_BG_PSK ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+    iw dev {interface} link
+    COUNT=$(iw dev {interface} link | wc -l)
+    if [ $COUNT -gt 1 ]; then
+        exit 0
+    fi
+    exit 1
+environ: LD_LIBRARY_PATH WPA_BG_SSID WPA_BG_PSK
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 5.0
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wireless_connection_wpa_n_nm_{interface}
+_summary: Connect to WPA-encrypted 802.11n Wi-Fi network on {interface} after suspend
+_purpose:
+ Check system can connect to 802.11n AP with wpa security after suspend
+plugin: shell
+command:
+    nmcli g > /dev/null
+    if [ $? -ne 0 ]; then
+        exit 1
+    fi
+    trap "nmcli dev disconnect {interface}; nmcli con delete id WIFI_TEST_CREATED_BY_CHECKBOX" EXIT
+    nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs nmcli c delete
+    nmcli dev wifi rescan
+    nmcli dev wifi connect $WPA_N_SSID password $WPA_N_PSK ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+    iw dev {interface} link
+    COUNT=$(iw dev {interface} link | wc -l)
+    if [ $COUNT -gt 1 ]; then
+        exit 0
+    fi
+    exit 1
+environ: LD_LIBRARY_PATH WPA_N_SSID WPA_N_PSK
+user: root
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+estimated_duration: 5.0
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_open_a_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create open 802.11a Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: suspend/suspend-manual
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create an open 802.11a Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode a
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security open
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_open_b_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create open 802.11b Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: suspend/suspend-manual
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create an open 802.11b Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode b
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security open
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_open_g_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+_summary: Create open 802.11g Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create an open 802.11g Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode g
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security open
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_open_ad_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create open 802.11ad Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: suspend/suspend-manual
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create an open 802.11ad Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode ad
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security open
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_a_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+_summary: Create WPA2 802.11a Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create a WPA2 802.11a Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode a
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP using password "Test1234"
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_b_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+depends: suspend/suspend-manual
+_summary: Create WPA2 802.11b Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create a WPA2 802.11b Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode b
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP using password "Test1234"
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_g_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create WPA2 802.11g Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: suspend/suspend-manual
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create a WPA2 802.11g Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode g
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP using password "Test1234"
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_ad_no_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create WPA2 802.11ad Wi-Fi Access Point on {interface} with no STA after suspend
+plugin: manual
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: suspend/suspend-manual
+estimated_duration: 120.0
+_purpose:
+  Check that the system can create a WPA2 802.11ad Access Point without any STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode ad
+    $ wifi-ap.config set wifi.interface-mode direct
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+  4. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  5. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  6. Attempt to connect to the AP using password "Test1234"
+  7. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_a_with_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create WPA2 802.11a Wi-Fi Access Point on {interface} with active STA after suspend
+plugin: user-interact-verify
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: after-suspend/wireless/wireless_connection_wpa_bg_nm_{interface}
+estimated_duration: 120.0
+environ: LD_LIBRARY_PATH WPA_BG_SSID WPA_BG_PSK
+command:
+ nmcli dev wifi rescan
+ nmcli dev wifi connect $OPEN_BG_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+user: root
+_purpose:
+  Check that the system can create a WPA2 802.11a Access Point with an already active STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Connect to an 802.11b/g AP with wpa security:
+    Press Enter to continue
+  4. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode a
+    $ wifi-ap.config set wifi.interface-mode virtual
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+    $ wifi-ap.config set wifi.channel $(iw dev {interface} info | grep -oP 'channel\s+\K\d+')
+  5. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  6. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  7. Attempt to connect to the AP using password "Test1234"
+  8. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_b_with_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create WPA2 802.11b Wi-Fi Access Point on {interface} with active STA after suspend
+plugin: user-interact-verify
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: after-suspend/wireless/wireless_connection_wpa_bg_nm_{interface}
+estimated_duration: 120.0
+environ: LD_LIBRARY_PATH WPA_BG_SSID WPA_BG_PSK
+command:
+ nmcli dev wifi rescan
+ nmcli dev wifi connect $OPEN_BG_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+user: root
+_purpose:
+  Check that the system can create a WPA2 802.11b Access Point with an already active STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Connect to an 802.11b/g AP with wpa security:
+    Press Enter to continue
+  4. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode b
+    $ wifi-ap.config set wifi.interface-mode virtual
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+    $ wifi-ap.config set wifi.channel $(iw dev {interface} info | grep -oP 'channel\s+\K\d+')
+  5. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  6. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  7. Attempt to connect to the AP using password "Test1234"
+  8. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_g_with_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create WPA2 802.11g Wi-Fi Access Point on {interface} with active STA after suspend
+plugin: user-interact-verify
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: after-suspend/wireless/wireless_connection_wpa_bg_nm_{interface}
+estimated_duration: 120.0
+environ: LD_LIBRARY_PATH WPA_BG_SSID WPA_BG_PSK
+command:
+ nmcli dev wifi rescan
+ nmcli dev wifi connect $OPEN_BG_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+user: root
+_purpose:
+  Check that the system can create a WPA2 802.11g Access Point with an already active STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Connect to an 802.11b/g AP with wpa security:
+    Press Enter to continue
+  4. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode g
+    $ wifi-ap.config set wifi.interface-mode virtual
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+    $ wifi-ap.config set wifi.channel $(iw dev {interface} info | grep -oP 'channel\s+\K\d+')
+  5. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  6. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  7. Attempt to connect to the AP using password "Test1234"
+  8. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
+
+unit: template
+template-resource: device
+template-filter: device.category == 'WIRELESS'
+template-unit: job
+id: after-suspend/wireless/wifi_ap_wpa_ad_with_sta_{interface}
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Create WPA2 802.11ad Wi-Fi Access Point on {interface} with active STA after suspend
+plugin: user-interact-verify
+requires:
+ wifi_interface_mode.AP == 'supported'
+ snap.name == 'wifi-ap'
+depends: after-suspend/wireless/wireless_connection_wpa_bg_nm_{interface}
+estimated_duration: 120.0
+environ: LD_LIBRARY_PATH WPA_BG_SSID WPA_BG_PSK
+command:
+ nmcli dev wifi rescan
+ nmcli dev wifi connect $OPEN_BG_SSID ifname {interface} name WIFI_TEST_CREATED_BY_CHECKBOX
+user: root
+_purpose:
+  Check that the system can create a WPA2 802.11ad Access Point with an already active STA connection after suspend
+_steps:
+  1. Ensure no Soft AP is running prior running this test:
+    $ sudo systemctl stop snap.wifi-ap.backend
+  2. Delete existing wireless connections known to Network Manager:
+    $ network-manager.nmcli -t -f TYPE,UUID c | grep -oP "(?<=^802-11-wireless:).*" | xargs network-manager.nmcli c delete
+  3. Connect to an 802.11b/g AP with wpa security:
+    Press Enter to continue
+  4. Configure the wifi-ap snap:
+    $ wifi-ap.config set wifi.interface {interface}
+    $ wifi-ap.config set wifi.operation-mode ad
+    $ wifi-ap.config set wifi.interface-mode virtual
+    $ wifi-ap.config set disabled 0
+    $ wifi-ap.config set wifi.security wpa2
+    $ wifi-ap.config set wifi.security-passphrase Test1234
+    $ wifi-ap.config set wifi.channel $(iw dev {interface} info | grep -oP 'channel\s+\K\d+')
+  5. Start the wifi-ap service:
+    $ sudo systemctl start snap.wifi-ap.backend
+  6. Using a suitable Wi-Fi client try to detect the presence of the AP called "Ubuntu"
+  7. Attempt to connect to the AP using password "Test1234"
+  8. Stop the wifi-ap service:
+    $ sudo systemctl stop snap.wifi-ap.backend
+_verification:
+  Did the client connect?
+flags: preserve-locale
diff --git a/plainbox-provider-snappy/units/suspend/after-suspend/wwan.pxu b/plainbox-provider-snappy/units/suspend/after-suspend/wwan.pxu
new file mode 100644
index 0000000..a4b5fe7
--- /dev/null
+++ b/plainbox-provider-snappy/units/suspend/after-suspend/wwan.pxu
@@ -0,0 +1,48 @@
+# Copyright 2015 Canonical Ltd.
+# All rights reserved.
+#
+# Written by:
+#   Jonathan Cave <[e-mail]>
+#   Po-Hsu Lin <[e-mail]>
+
+unit: job
+id: after-suspend/wwan/detect
+category_id: 2013.com.canonical.plainbox::suspend
+_summary: Identify if WWAN module is missing after suspend
+_purpose:
+ Tests that there is a WWAN module present and indicates that testing of it
+ should follow after suspend.
+plugin: shell
+command:
+  COUNT=$(wwan_tests count)
+  if [ $COUNT -eq 0 ]; then
+    exit 1
+  fi
+estimated_duration: 2.0
+flags: preserve-locale
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+  manifest.has_wwan_module == 'True'
+depends: suspend/suspend-manual
+
+unit: template
+template-resource: wwan_resource
+template-unit: job
+id: after-suspend/wwan/gsm-connection-{manufacturer}-{model}-{hw_id}
+_summary:  Verify a GSM broadband modem can create a data connection after
+           suspend
+_description:
+ Any modems discovered by the resource job that list GSM support
+ will be tested to ensure a data connection can be made after suspend.
+plugin: shell
+command: wwan_tests 3gpp-connection $WWAN_CONTROL_IF $WWAN_NET_IF $WWAN_APN
+environ: LD_LIBRARY_PATH WWAN_CONTROL_IF WWAN_NET_IF WWAN_APN
+user: root
+estimated_duration: 10.0
+category_id: 2013.com.canonical.plainbox::suspend
+flags: preserve-locale
+imports: from 2013.com.canonical.plainbox import manifest
+requires:
+  manifest.has_wwan_module == 'True'
+  wwan_resource.gsm_umts == 'supported'
+depends: suspend/suspend-manual
diff --git a/plainbox-provider-snappy/units/suspend/jobs.pxu b/plainbox-provider-snappy/units/suspend/jobs.pxu
index 4352bae..515623d 100644
--- a/plainbox-provider-snappy/units/suspend/jobs.pxu
+++ b/plainbox-provider-snappy/units/suspend/jobs.pxu
@@ -8,418 +8,5 @@ _steps:
 _verification:
  System suspends successfully
 plugin: manual
-category_id: power
+category_id: 2013.com.canonical.plainbox::suspend
 estimated_duration: 300
-
-id: suspend/audio-after-suspend/headphone
-_summary: Headphones work (after suspend)
-_purpose:
- Check that headphones work after suspend
-_steps:
- 1. Plug in headset to headset port
- 2. Execute the following command:
-  alsamixer
- 3. Use arrow key to adjust volume, m key to mute/unmute
- 4. Make sure all channels are not muted and have an appropriate volume
- 5. Press q to exit alsamixer
- 6. Suspend the device
- 7. Resume the device
- 6. Execute following command:
-  arecord | aplay
- 7. Speak in to microphone on headset
-_verification:
- Verify that your voice is reproduced through the headphones clearly
-plugin: manual
-category_id: audio
-estimated_duration: 10
-
-id: suspend/audio-after-suspend/microphone
-_summary: External microphone works (after suspend)
-_purpose:
- Check that an external microphone works after suspend
-_steps:
- 1. Plug headset to headset port
- 2. Execute following command:
-  alsamixer
- 3. Use arrow key to adjust volume, m key to mute/unmute
- 4. Make sure all channels are not muted and have an appropriate volume
- 5. Press q to exit alsamixer
- 6. Suspend the device
- 7. Resume the device
- 8. Execute following command:
-  arecord | aplay
- 9. Speak in to microphone on headset
-_verification:
- Verify that your voice is reproduced through the headphones clearly
-plugin: manual
-category_id: audio
-estimated_duration: 10
-
-id: suspend/bluetooth-after-suspend/hid
-_summary: After suspend, bluetooth keyboard works
-_purpose:
- Check a bluetooth input device works after suspending the system. Given Ubuntu
- is CLI only, this implies a keyboard test.
-_steps:
- 1. Scan nearby devices:
-     hcitool scan
- 2. Pair a bluetooth input device
-     bluez-simple-agent hci0 [MAC address of bluetooth input device]
- 3. Set paired input device workable
-     sudo bluez-test-input connect [MAC address of bluetooth input device]
- 4. Suspend the device
- 5. Resume the device
-_verification:
- Can input from input device
-plugin: manual
-category_id: bluetooth
-estimated_duration: 10
-
-id: suspend/ethernet/eth0/after-suspend/ping
-_summary: After suspend, can ping another machine over first Ethernet port
-_purpose:
- Check Ethernet works after suspend by pinging another machine
-_steps:
- 1. Make sure Ethernet cable is connected and can access internet
- 2. Suspend the device
- 3. Resume the device
- 4. ping -I eth0 google.com
-_verification:
- Can successfully get ping responses from google.com
-plugin: manual
-category_id: ethernet
-estimated_duration: 10
-
-id: suspend/ethernet/eth1/after-suspend/ping
-_summary: After suspend, can ping another machine over second Ethernet port
-_purpose:
- Check Ethernet works after suspend by pinging another machine
-_steps:
- 1. Make sure Ethernet cable is connected and can access internet
- 2. Suspend the device
- 3. Resume the device
- 4. ping -I eth1 google.com
-_verification:
- Can successfully get ping responses from google.com
-plugin: manual
-category_id: ethernet
-estimated_duration: 10
-
-id: suspend/led-after-suspend/power
-_summary: After suspend, Power LED behaves correctly
-_purpose:
- Check power LED is on when system is powered on after suspend
-_steps:
- 1. Suspend the device
- 2. Resume the device
- 3. Check power led when system is powered on
-_verification:
- Power led is on when system is powered on
-plugin: manual
-category_id: led
-estimated_duration: 10
-
-id: suspend/monitor-after-suspend/dvi
-_summary: After suspend, a Monitor works when connected by DVI
-_purpose:
- Check output to display through DVI port after suspend
-_steps:
- 1. Connect display to DVI port
- 2. Check the display
- 3. Suspend the device
- 4. Resume the device
-_verification:
- Output to display works
-plugin: manual
-category_id: display
-estimated_duration: 10
-
-id: suspend/monitor-after-suspend/hdmi
-_summary: After suspend , a Monitor works when connected by HDMI
-_purpose:
- Check output to display through HDMI port after suspend
-_steps:
- 1. Connect display to HDMI port
- 2. Check the display
- 3. Suspend the device
- 4. Resume the device
-_verification:
- Output to display works
-plugin: manual
-category_id: display
-estimated_duration: 10
-
-id: suspend/monitor-after-suspend/dvi-to-vga
-_summary: After suspend, a Monitor works when connected by DVI-to-VGA
-_purpose:
- Check output to display through VGA adaptor on DVI port after suspend
-_steps:
- 1. Connect display to VGA adaptor on DVI port
- 2. Check the display
- 3. Suspend the device
- 4. Resume the device
-_verification:
- Output to display works
-plugin: manual
-category_id: display
-estimated_duration: 10
-
-id: suspend/monitor-after-suspend/hdmi-to-vga
-_summary: After suspend, a Monitor works when connected by HDMI-to-VGA
-_purpose:
- Check output to display through VGA adaptor on HDMI port after suspend
-_steps:
- 1. Connect display to VGA adaptor on HDMI port
- 2. Check the display
- 3. Suspend the device
- 4. Resume the device
-_verification:
- Output to display works
-plugin: manual
-category_id: display
-estimated_duration: 10
-
-id: suspend/serial-after-suspend/rs232-console
-_summary: After suspend, the serial debugging console is enabled and operational
-_purpose:
- Check user can still access the test machine through serial port from another
- machine
-_steps:
- 1. Connect USB to db9 null modem adapter cable to serial port of test machine
- 2. Connect the cable to USB port of another ubuntu machine (client)
- 3. Install screen on client (if not done in Prerequisite)
- 4. Execute following command on client:
-  sudo screen /dev/ttyUSB0
- 5. Start getty service on test machine:
-  sudo systemctl start getty@[rs232 device, ex. /dev/ttyS0].service
- 6. Log into the test machine from terminal on client
- 7. Execute following command in screen on client:
-  sudo systemctl suspend
- 8. Resume the test machine
- 9. Try to run some commands in terminal on client
-_verification:
- Can still run commands in terminal on client after suspend
-plugin: manual
-category_id: serial
-estimated_duration: 600
-
-id: suspend/usb-after-suspend/hid
-_summary: After suspend, USB keyboard works
-_purpose:
- Check USB input device works after suspend
-_steps:
- 1. Connect USB keyboard
- 2. Input some characters with the USB keyboard
- 3. Suspend the device
- 4. Wake the device
- 5. Input some characters with the USB keyboard
-_verification:
- Confirm the characters are displayed correctly
-plugin: manual
-category_id: usb2
-estimated_duration: 10
-
-id: suspend/usb-after-suspend/insert
-_summary: After suspend, USB storage device insertion detected
-_purpose:
- Check system can detect USB storage when inserted after suspend
-_steps:
- 1. Press continue
- 2. Connect USB storage device
-_verification:
- Can find new USB storage device messages in /var/log/syslog
-plugin: user-interact
-user: root
-command: checkbox-support-run_watcher insertion usb2
-category_id: usb2
-estimated_duration: 10
-
-id: suspend/usb-after-suspend/storage-automated
-_summary: After suspend, USB storage device read & write works
-_purpose:
- Check system can read/write to USB storage correctly after suspend
-_steps:
- 1. This task is fully automatic and need USB insertion test was applied first.
-_verification:
- This task is fully automatic and will verify the result for you.
-plugin: shell
-user: root
-command: usb_read_write
-category_id: usb2
-estimated_duration: 10
-
-id: suspend/usb-after-suspend/remove
-_summary: After suspend, USB storage removal works
-_purpose:
- Check system can detect removal of a USB storage device after suspend
-_steps:
- 1. Press continue
- 2. Disconnect USB storage device
-_verification:
- Can find USB storage device removed messages in /var/log/syslog
-plugin: user-interact
-user: root
-command: checkbox-support-run_watcher removal usb2
-category_id: usb2
-estimated_duration: 10
-
-id: suspend/usb3-after-suspend/insert
-_summary: After suspend, USB3 storage device insertion detected
-_purpose:
- Check system can detect insertion of a USB3 storage device after suspend
-_steps:
- 1. Press continue
- 2. Connect USB3 storage device
-_verification:
- Can find new USB3 storage device messages in /var/log/syslog
-plugin: user-interact
-user: root
-command: checkbox-support-run_watcher insertion usb3
-category_id: usb3
-estimated_duration: 10
-
-id: suspend/usb3-after-suspend/storage-automated
-_summary: After suspend, USB3 storage device read & write works
-_purpose:
- Check system can read/write to USB3 storage devices correctly after suspend
-_steps:
- 1. This task is fully automatic and need USB3 insertion test was applied first.
-_verification:
- This task is fully automatic and will verify the result for you.
-plugin: shell
-user: root
-command: usb_read_write
-category_id: usb3
-estimated_duration: 10
-
-id: suspend/usb3-after-suspend/remove
-_summary: After suspend, USB3 storage removal works
-_purpose:
- Check system can detect USB3 storage removal after suspend
-_steps:
- 1. Press continue
- 2. Disconnect USB3 storage device
-_verification:
- Can find USB3 storage device removed messages in /var/log/syslog
-plugin: user-interact
-user: root
-command: checkbox-support-run_watcher removal usb3
-category_id: usb3
-estimated_duration: 10
-
-id: suspend/wireless-after-suspend/wireless_scanning
-_summary: After suspend, System can discover Wi-Fi networks
-_purpose:
- Check system can find a wireless network AP nearby after suspend
-_steps:
- 1. sudo iw dev mlan0 scan
- 2. Suspend the device
- 3. Resume the device
- 4. sudo iw dev mlan0 scan
-_verification:
- In step 4, can see nearby wireless network AP
-plugin: manual
-category_id: wifi
-estimated_duration: 10
-
-id: suspend/wireless-after-suspend/wireless_connection_open_ac
-_summary: After suspend, system can connect to unencrypted 802.11ac Wi-Fi network
-_purpose:
- Check system can connect to insecure 802.11ac AP after suspend
-_steps:
- 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
- 2. Commence the test
-_verification:
- If there's "Connection test passed" message in result, mark the test as passed.
-plugin: user-interact
-command: wifi_client_test -i $WIFI_INTERFACE -s $OPEN_AC_SSID
-environ: WIFI_INTERFACE OPEN_AC_SSID
-user: root
-category_id: wifi
-estimated_duration: 90
-flags: preserve-locale
-
-id: suspend/wireless-after-suspend/wireless_connection_open_bg
-_summary: After suspend, system can connect to unencrypted 802.11b/g Wi-Fi network
-_purpose:
- Check system can connect to insecure 802.11b/g AP after suspend
-_steps:
- 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
- 2. Commence the test
-_verification:
- If there's "Connection test passed" message in result, mark the test as passed.
-plugin: user-interact
-command: wifi_client_test -i $WIFI_INTERFACE -s $OPEN_BG_SSID
-environ: WIFI_INTERFACE OPEN_BG_SSID
-user: root
-category_id: wifi
-estimated_duration: 90
-flags: preserve-locale
-
-id: suspend/wireless-after-suspend/wireless_connection_open_n
-_summary: After suspend, system can connect to unencrypted 802.11n Wi-Fi network
-_purpose:
- Check system can connect to insecure 802.11n AP after suspend
-_steps:
- 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
- 2. Commence the test
-_verification:
- If there's "Connection test passed" message in result, mark the test as passed.
-plugin: user-interact
-command: wifi_client_test -i $WIFI_INTERFACE -s $OPEN_N_SSID
-environ: WIFI_INTERFACE OPEN_N_SSID
-user: root
-category_id: wifi
-estimated_duration: 90
-flags: preserve-locale
-
-id: suspend/wireless-after-suspend/wireless_connection_wpa_ac
-_summary: After suspend, system can connect to WPA-encrypted 802.11ac Wi-Fi network
-_purpose:
- Check system can connect to 802.11ac AP with wpa security after suspend
-_steps:
- 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
- 2. Commence the test
-_verification:
- If there's "Connection test passed" message in result, mark the test as passed.
-plugin: user-interact
-command: wifi_client_test -i $WIFI_INTERFACE -s $WPA_AC_SSID -k $WPA_AC_PSK
-environ: WIFI_INTERFACE WPA_AC_SSID WPA_AC_PASK
-user: root
-category_id: wifi
-estimated_duration: 90
-flags: preserve-locale
-
-id: suspend/wireless-after-suspend/wireless_connection_wpa_bg
-_summary: After suspend, system can connect to WPA-encrypted 802.11b/g Wi-Fi network
-_purpose:
- Check system can connect to 802.11b/g AP with wpa security after suspend
-_steps:
- 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
- 2. Commence the test
-_verification:
- If there's "Connection test passed" message in result, mark the test as passed.
-plugin: user-interact
-command: wifi_client_test -i $WIFI_INTERFACE -s $WPA_BG_SSID -k $WPA_BG_PSK
-environ: WIFI_INTERFACE WPA_BG_SSID WPA_BG_PASK
-user: root
-category_id: wifi
-estimated_duration: 90
-flags: preserve-locale
-
-id: suspend/wireless-after-suspend/wireless_connection_wpa_n
-_summary: After suspend, system can connect to WPA-encrypted 802.11n Wi-Fi network
-_purpose:
- Check system can connect to 802.11n AP with wpa security after suspend
-_steps:
- 1. Remove all wireless configuration in /etc/network/interfaces and /etc/network/interfaces.d
- 2. Commence the test
-_verification:
- If there's "Connection test passed" message in result, mark the test as passed.
-plugin: user-interact
-command: wifi_client_test -i $WIFI_INTERFACE -s $WPA_N_SSID -k $WPA_N_PSK
-environ: WIFI_INTERFACE WPA_N_SSID WPA_N_PASK
-user: root
-category_id: wifi
-estimated_duration: 90
-flags: preserve-locale
diff --git a/plainbox-provider-snappy/units/suspend/test-plan.pxu b/plainbox-provider-snappy/units/suspend/test-plan.pxu
index 7920de9..3a0f43d 100644
--- a/plainbox-provider-snappy/units/suspend/test-plan.pxu
+++ b/plainbox-provider-snappy/units/suspend/test-plan.pxu
@@ -13,35 +13,32 @@ _name: Manual suspend tests
 _description: Manual suspend tests for Snappy Ubuntu Core devices
 include:
     suspend/suspend-manual
-    suspend/audio-after-suspend/headphone
-    suspend/audio-after-suspend/microphone
-    suspend/bluetooth-after-suspend/hid
-    suspend/ethernet/eth0/after-suspend/ping
-    suspend/ethernet/eth1/after-suspend/ping
-    suspend/ethernet/eth1/after-suspend/ping
-    suspend/led-after-suspend/power
-    suspend/monitor-after-suspend/dvi
-    suspend/monitor-after-suspend/hdmi
-    suspend/monitor-after-suspend/dvi-to-vga
-    suspend/monitor-after-suspend/hdmi-to-vga
-    suspend/serial-after-suspend/rs232-console
-    suspend/usb-after-suspend/hid
-    suspend/usb-after-suspend/insert
-    suspend/usb-after-suspend/remove
-    suspend/usb3-after-suspend/insert
-    suspend/usb3-after-suspend/remove
-    suspend/wireless-after-suspend/wireless_scanning
-    suspend/wireless-after-suspend/wireless_connection_open_ac
-    suspend/wireless-after-suspend/wireless_connection_open_bg
-    suspend/wireless-after-suspend/wireless_connection_open_n
-    suspend/wireless-after-suspend/wireless_connection_wpa_ac
-    suspend/wireless-after-suspend/wireless_connection_wpa_bg
-    suspend/wireless-after-suspend/wireless_connection_wpa_n
+    after-suspend/bluetooth/.*
+    after-suspend/led/.*
+    after-suspend/mediacard/.*-insert
+    after-suspend/mediacard/.*-storage
+    after-suspend/mediacard/.*-remove
+    after-suspend/monitor/.*
+    after-suspend/usb/.*
+    after-suspend/usb3/.*
+    after-suspend/usb-c/.*
+    after-suspend/watchdog/.*
 
 id: suspend-automated
 unit: test plan
 _name: Automated suspend tests
 _description: Automated suspend tests for Snappy Ubuntu Core devices
 include:
-    suspend/usb-after-suspend/storage-automated
-    suspend/usb3-after-suspend/storage-automated
+    after-suspend/ethernet/.*
+    after-suspend/i2c/.*
+    after-suspend/location/.*
+    after-suspend/mediacard/.*-preinserted
+    after-suspend/wireless/wireless_scanning_.*
+    after-suspend/wireless/wireless_connection_open_ac_nm_.*
+    after-suspend/wireless/wireless_connection_open_bg_nm_.*
+    after-suspend/wireless/wireless_connection_open_n_nm_.*
+    after-suspend/wireless/wireless_connection_wpa_ac_nm_.*
+    after-suspend/wireless/wireless_connection_wpa_bg_nm_.*
+    after-suspend/wireless/wireless_connection_wpa_n_nm_.*
+    after-suspend/wwan/.*
+    after-suspend/watchdog/systemd-config
diff --git a/plainbox-provider-snappy/units/test-plan.pxu b/plainbox-provider-snappy/units/test-plan.pxu
index 5a0da47..82a838d 100644
--- a/plainbox-provider-snappy/units/test-plan.pxu
+++ b/plainbox-provider-snappy/units/test-plan.pxu
@@ -55,6 +55,7 @@ nested_part:
     watchdog-full
     wireless-full
     wwan-full
+    suspend-full
     stress-full
 
 id: snappy-generic-automated