Merge ~teknoraver/snappy-hwe-snaps/+git/engineering-tests:bluez into ~snappy-hwe-team/snappy-hwe-snaps/+git/engineering-tests:master

[Matteo Croce]

Add bluez tests

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:ebf91453d9e78da1d658f64e96f2cd79d536b26c
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/878/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/786/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/878/rebuild

review: Needs Fixing (continuous-integration)

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:8766f34a2c6dad8a21b1df5f17b22e1cad74d816
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/884/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/792/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/884/rebuild

review: Needs Fixing (continuous-integration)

[Konrad Zapałowicz (kzapalowicz)]

It would be nice to have test category from .xls document map to a unit in plainbox - a separate pxu file. Also to keep it away from snap-related tests as these in the .xls have much more wider scope. Basically how the system with bluez installed behaves.

Im thinking of sth like:

general.pxu
  |
  +-- id: bluez/general/xxx1
  +-- id: bluez/general/xxx2

hid.pxu
  |
  +-- id: bluez/hid/xxx1

review: Needs Fixing (code)

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:d0b7575c0b425f9c2b89a767351fe35a5cb7d3e0
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/891/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/799/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/891/rebuild

review: Needs Fixing (continuous-integration)

[Jim Hodapp (jhodapp)]

> It would be nice to have test category from .xls document map to a unit in
> plainbox - a separate pxu file. Also to keep it away from snap-related tests
> as these in the .xls have much more wider scope. Basically how the system with
> bluez installed behaves.
>
> Im thinking of sth like:
>
> general.pxu
> |
> +-- id: bluez/general/xxx1
> +-- id: bluez/general/xxx2
>
> hid.pxu
> |
> +-- id: bluez/hid/xxx1

I agree with this Konrad, I think it's a very good idea to structure it this way.

[Jim Hodapp (jhodapp)]

Looks good overall. Some changes inline below. Also, please make sure your use of a period at the end of a sentence is consistent for every sentence. Either use periods or don't use periods.

review: Needs Fixing

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:2df9d2b27e7a9d8f383dff41bae3d84539ff16f7
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/892/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/800/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/892/rebuild

review: Needs Fixing (continuous-integration)

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:ac8c9f55ff5fb967338b0e446579110d5247ed28
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/893/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/801/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/893/rebuild

review: Needs Fixing (continuous-integration)

[Simon Fels (morphis)]

review: Needs Fixing

[Konrad Zapałowicz (kzapalowicz)]

Looks good overall, better than previously however still needs some improvements. Comments inline below but in general

- Please focus on not mixing this tests sets/units with the previous, snap-related tests. The reason is that the test plan has a much wider scope and serves a different purpose. The snap-related tests are here for making sure that the snap itself works; The test plan is to make sure that the system with BT installed (either as a snap or as a .deb) behaves in a correct way. This is done on multiple layers, from the kernel through bluetoothctl to the UI.

- Make sure that the test id reflects the intent of the test case as well as uses the BT vocabulary so that it is easy to understand what the test is doing. we will be publishing the tests results therefore we would like the readers of such report be able to have the basic understanding without the need of reading the .pxu files.

- Please do not put multiple verification criteria in a single tests (like for HID). This is to provide a good granularity so that a test report can provide a meaningful results what exactly is and is not working.

- Please make the test id include the category name (from .xls) like bluez/general/test_name. This is because later using the plainbox/chackbox features for creating tests plans we will be able to include these and form some sort of aggregation. It is possible to build test plans in plainbox/checkbox by writing for example: include REGEXP where the REGEXP is used to match the test id. So later we will be able to leverage a well defined id's into creating a tests plans out of our tests.

review: Needs Fixing (code)

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:dbfadf59b7cafcb5482dbc0204e5a01d4a456e82
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/925/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/833/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/925/rebuild

review: Needs Fixing (continuous-integration)

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:8c6db3585221dac508e498ee25e40d47e71b6c67
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/927/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/835/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/927/rebuild

review: Needs Fixing (continuous-integration)

[Konrad Zapałowicz (kzapalowicz)]

This is much better now, approving. That said I'm still a little bit concerned with the audio tests being present here [general] but this does not prevent this MR from being approved. I believe this is something we can solve later with when the investigation of how we structure tests story is completed, perhaps by introducing test plans and suits.

review: Approve (code)

[Simon Fels (morphis)]

Added a few comments. Generally there are instructions missing how certain things can be verified. We need to write these tests with the guideline that people not used to bluetooth/bluetoothctl (QA) will run them and then don't know what they have to do.

review: Needs Fixing

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:5ccb8fef2437c4730a74a9abe7eefba171dcaf93
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/942/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/850/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/942/rebuild

review: Needs Fixing (continuous-integration)

[Simon Fels (morphis)]

review: Needs Fixing

[System Enablement Bot (system-enablement-ci-bot)]

FAILED: Continuous integration, rev:bb7c92960b5e2ea60dd2c0cca23485b5e59e033e
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/946/
Executed test runs:
    None: https://jenkins.canonical.com/system-enablement/job/generic-update-snap-mp/854/console

Click here to trigger a rebuild:
https://jenkins.canonical.com/system-enablement/job/generic-build-snap/946/rebuild

review: Needs Fixing (continuous-integration)

[Simon Fels (morphis)]

LGTM

review: Approve

[Simon Fels (morphis)]

Approving for CI

review: Approve (continuous-integration)

diff --git a/bluez/units/bluez.pxu b/bluez/units/bluez.pxu
deleted file mode 100644
index 682bb31..0000000
--- a/bluez/units/bluez.pxu
+++ /dev/null
@@ -1,155 +0,0 @@
-# Copyright 2016 Canonical Ltd.
-# All rights reserved.
-#
-# Written by:
-#   Jim Hodapp <[e-mail]>
-
-unit: category
-id: bluez
-_name: Bluez
-
-id: bluez/setup/ensure_interface_connection_setup
-category_id: bluez
-_description: Ensure that the bluez interface is connected
-plugin: manual
-_steps:
-  1. Connect required bluez slot/plug
-  .
-    $ sudo snap connect bluez:client bluez:service
-  .
-_verification:
-  Verify that you see the following when running snap interfaces bluez:
-  bluez:service  bluez:client
-
-id: bluez/scan/get_all
-category_id: bluez
-plugin: manual
-depends: bluez/setup/ensure_interface_connection_setup
-_summary: All Bluetooth devices in range are listed
-_purpose:
- Check if all powered on devices that are within range as listed.
-_steps:
-  1. Execute the following command to retrieve the list of all Bluetooth devices:
-  .
-    $ /snap/bin/bluez.bluetoothctl
-    [bluetooth]# scan on
-  .
-_verification:
-  Your expected Bluetooth device(s) is/are shown in the output list such as:
-    [NEW] Device 04:52:C7:0D:0C:03 QC 35s
-
-id: bluez/connection/pair_and_connect
-category_id: bluez
-plugin: manual
-depends: bluez/setup/ensure_interface_connection_setup
-_summary: A Bluetooth device of choice is paired and connected
-_purpose:
- Check if your Bluetooth device of choice can be paired to the host system.
-_steps:
-  1. Execute the following command to pair and connect your device to the host
-     system using the address listed in the previous scan test:
-  .
-    [bluetooth]# pair <device_address>
-    [bluetooth]# connect <device_address>
-  .
-_verification:
-  You should see output similar to the following:
-  Attempting to pair with 04:52:C7:0D:0C:03
-    [CHG] Device 04:52:C7:0D:0C:03 Connected: yes
-    [CHG] Device 04:52:C7:0D:0C:03 Modalias: bluetooth:v009Ep400Cd0106
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00000000-deca-fade-deca-deafdecacaff
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: yes
-    [CHG] Device 04:52:C7:0D:0C:03 Paired: yes
-    Pairing successful
-    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: no
-    [CHG] Device 04:52:C7:0D:0C:03 Connected: no
-    Attempting to connect to 04:52:C7:0D:0C:03
-    [CHG] Device 04:52:C7:0D:0C:03 Connected: yes
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00000000-deca-fade-deca-deafdecacaff
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
-    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
-    Connection successful
-    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: yes
-
-id: bluez/audio/a2dp_ubuntu_classic
-category_id: bluez
-plugin: manual
-depends: bluez/connection/pair_and_connect
-_summary: Stream audio to Bluetooth headset
-_purpose:
- Verify that you can stream music to a Bluetooth headset via A2DP on Ubuntu
- Classic. Note: Skip this test if not running Ubuntu Classic.
-_steps:
-  1. Follow the previous tests to list, pair and connect your headset.
-     Navigate to the Sound panel in System Settings, select your headset device
-     in the Output tab, and make sure that Mode is set to A2DP. Then press the
-     Test Sound button and test each speaker.
-_verification:
-  Verify that you can hear the test sound "Front left", "Front right" in each
-  speaker respectively.
-
-id: bluez/audio/a2dp_disconnect
-category_id: bluez
-plugin: manual
-depends: bluez/audio/a2dp_ubuntu_classic
-_summary: Disconnect Bluetooth headset
-_purpose:
- Verify that you can disconnect Bluetooth headset while streaming and audio
- playback switches back to the device's primary speaker.
-_steps:
-  1. Follow the previous tests to start streaming audio to the headset via
-     A2DP. Then execute the following command to disconnect the headset from
-     active A2DP streaming:
-  .
-    [<device_name>]# disconnect <device_address>
-_verification:
-  Verify that you see output similar to the following:
-    Attempting to disconnect from 04:52:C7:0D:0C:03
-    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: no
-    Successful disconnected
-    [CHG] Device 04:52:C7:0D:0C:03 Connected: no
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Key: 0x0110
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x40
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x0c
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x02
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x41
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x00
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x61
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x71
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0xcd
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x92
-    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x6c
-
-id: bluez/connection/pair_and_connect_hid
-category_id: bluez
-plugin: manual
-depends: bluez/setup/ensure_interface_connection_setup
-_summary: A Bluetooth HID device (e.g. keyboard, mouse) is connected and paired
-_purpose:
- Check if your Bluetooth HID device of choice (e.g. keyboard, mouse) can be
- paired to the host system.
-_steps:
-  1. Execute the following command to pair and connect your HID device to the
-     host system:
-  .
-    [bluetooth]# scan on
-    [bluetooth]# pair <device_address>
-    [bluetooth]# connect <device_address>
-  .
-_verification:
-  Open a text editor and make sure you can type text from the HID keyboard
-  into the text box. If testing a mouse, ensure that the cursor moves when
-  moving your HID mouse.
diff --git a/bluez/units/general.pxu b/bluez/units/general.pxu
new file mode 100644
index 0000000..0bc60d3
--- /dev/null
+++ b/bluez/units/general.pxu
@@ -0,0 +1,237 @@
+# Copyright 2017 Canonical Ltd.
+# All rights reserved.
+#
+# Written by:
+#   Jim Hodapp <[e-mail]>
+#   Matteo Croce <[e-mail]>
+
+unit: category
+id: bluez
+_name: Bluez
+
+id: bluez/setup/enabled_on_boot
+category_id: bluez
+_description: Ensure that Bluetooth is enabled on boot
+plugin: manual
+_steps:
+  1. Power on the DUT
+  2. If Bluetooth isn't enabled on first boot, enable it and reboot
+  3. Use "bluetoothctl" to check if there is an active adapter
+  .
+    $ bluetoothctl 
+_verification:
+  1. Check that there is a Controller in the output, eg.
+    [NEW] Controller 00:10:20:30:40:50 pi [default]
+
+id: bluez/setup/discoverable_by_default
+category_id: bluez
+_description: Ensure that DUT is discoverable by default
+plugin: manual
+_steps:
+  1. Type:
+  .
+    $ bluetoothctl
+    [bluetooth]# show
+  2. Scan for devices from a smartphone
+_verification:
+  1. Verify that the DUT is discoverable by default, eg.
+  .
+    $ bluetoothctl
+    [bluetooth]# show
+  .
+  contains the "Discoverable: yes" line
+  2. Check that the DUT can be discovered on the smartphone
+
+id: bluez/setup/bt_name_correct
+category_id: bluez
+_description: Ensure that the Bluetooth DUT name is correct
+plugin: manual
+_steps:
+  1. Type:
+  .
+    $ bluetoothctl
+    [bluetooth]# show
+_verification:
+  1. Verify that the Bluetooth DUT name is correct: equals to the Ubuntu Touch
+  device name, eg. could be BQ Aquaris E4.5 on Ubuntu Touch,
+  or to the hostname for desktop
+  .
+    Name: Ubuntu
+
+id: bluez/setup/bt_name_correct_from_gadget
+category_id: bluez
+_description: Ensure that the Bluetooth DUT name advertise correctly
+plugin: manual
+_steps:
+  1. Scan for devices from a smartphone
+_verification:
+  1. Verify that the Bluetooth DUT name is correct as seen from an external device
+
+id: bluez/connection/gadget_reconnect_after_power_cycle
+category_id: bluez
+_description: Verify that gadgets will reconnect after power cycle
+plugin: manual
+_steps:
+  1. Connect a gadget with the DUT:
+  .
+    $ bluetoothctl
+    bluetooth]# scan on
+    Discovery started
+    [NEW] Device 01:02:03:04:05:06 device
+    [bluetooth]# pair 01:02:03:04:05:06
+    Pairing successful
+    [bluetooth]# trust 01:02:03:04:05:06
+    Trusted
+    [bluetooth]# connect 01:02:03:04:05:06
+  .
+  2. Power off the gadget
+  3. Power on the gadget
+_verification:
+  1. Verify that the paired gadget will reconnect automatically
+  .
+    $ bluetoothctl
+    bluetooth]# info 01:02:03:04:05:06
+  .
+    and check for "Connected: Yes"
+
+id: bluez/connection/reconnect_after_dut_reboot
+category_id: bluez
+_description: Verify that gadgets will reconnect after reboot
+plugin: manual
+depends: bluez/connection/gadget_reconnect_after_power_cycle
+_steps:
+  1. Pair a gadget with the DUT
+  2. Reboot the DUT
+_verification:
+  1. Verify that the paired gadget will reconnect after reboot
+
+id: bluez/connection/gadget_disconnect
+category_id: bluez
+_description: Verify that the connected gadget can be disconnected
+plugin: manual
+depends: bluez/connection/gadget_reconnect_after_power_cycle
+_steps:
+  1. Connect a gadget with the DUT
+  2. Disconnect it with:
+  .
+    $ bluetoothctl
+    [bluetooth]# disconnect 01:02:03:04:05:06
+  .
+_verification:
+  1. Verify that the gadget is disconnected
+  .
+    $ bluetoothctl
+    bluetooth]# info 01:02:03:04:05:06
+  .
+    and check for "Connected: no"
+
+id: bluez/connection/gadget_can_be_forgotten
+category_id: bluez
+_description: Verify that the paired gadget can be forgotten
+plugin: manual
+depends: bluez/connection/gadget_reconnect_after_power_cycle
+_steps:
+  1. Pair a gadget with the DUT
+  2. Remove the pairing
+  .
+    $ bluetoothctl
+    [bluetooth]# remove 01:02:03:04:05:06
+_verification:
+  1. Verify that the paired gadget no longer appears in the gadgets list
+  .
+    $ bluetoothctl
+    bluetooth]# info 01:02:03:04:05:06
+  .
+    and check for "Paired: no"
+
+id: bluez/connection/gadget_paired_again
+category_id: bluez
+_description: Verify that forgotten gadgets can be paired again
+plugin: manual
+depends: bluez/connection/gadget_can_be_forgotten
+_steps:
+  1. Pair a gadget with the DUT
+  2. Remove the pairing
+  4. Pair the gadget a second time
+_verification:
+  1. Ensure that the gadget be paired again:
+  .
+    $ bluetoothctl
+    bluetooth]# info 01:02:03:04:05:06
+  .
+    and check for "Paired: yes"
+
+id: bluez/discoverable/dut_not_discoverable
+category_id: bluez
+_description: Verify that the DUT can disable discovery
+plugin: manual
+_steps:
+  1. Toggle the DUT Bluetooth visibility off:
+  .
+    $ bluetoothctl
+    bluetooth]# discoverable off
+  .
+_verification:
+  1. Ensure that the DUT can't be discovered from any other gadget
+
+id: bluez/discoverable/dut_discoverable
+category_id: bluez
+_description: Verify that the DUT can enable discovery
+plugin: manual
+_steps:
+  1. Toggle the DUT Bluetooth visibility on
+  .
+    $ bluetoothctl
+    bluetooth]# discoverable on
+  .
+_verification:
+  1. Ensure that the DUT can be discovered from other gadgets
+
+id: bluez/audio/a2dp_ubuntu_classic
+category_id: bluez
+plugin: manual
+depends: bluez/connection/pair_and_connect
+_summary: Stream audio to Bluetooth headset
+_purpose:
+ Verify that you can stream music to a Bluetooth headset via A2DP on Ubuntu
+ Classic. Note: Skip this test if not running Ubuntu Classic
+_steps:
+  1. Follow the previous tests to list, pair and connect your headset
+     Navigate to the Sound panel in System Settings, select your headset device
+     in the Output tab, and make sure that Mode is set to A2DP
+     Then press the Test Sound button and test each speaker
+_verification:
+  Verify that you can hear the test sound "Front left", "Front right" in each
+  speaker respectively.
+
+id: bluez/audio/a2dp_disconnect
+category_id: bluez
+plugin: manual
+depends: bluez/audio/a2dp_ubuntu_classic
+_summary: Disconnect Bluetooth headset
+_purpose:
+ Verify that you can disconnect Bluetooth headset while streaming and audio
+ playback switches back to the DUT's primary speaker
+_steps:
+  1. Follow the previous tests to start streaming audio to the headset via
+     A2DP. Then execute the following command to disconnect the headset from
+     active A2DP streaming:
+  .
+    [<dut_name>]# disconnect <gadget_address>
+_verification:
+  Verify that you see output similar to the following:
+    Attempting to disconnect from 04:52:C7:0D:0C:03
+    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: no
+    Successful disconnected
+    [CHG] Device 04:52:C7:0D:0C:03 Connected: no
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Key: 0x0110
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x40
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x0c
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x02
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x41
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x00
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x61
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x71
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0xcd
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x92
+    [CHG] Device 04:52:C7:0D:0C:03 ManufacturerData Value: 0x6c
diff --git a/bluez/units/hid.pxu b/bluez/units/hid.pxu
new file mode 100644
index 0000000..fda46e3
--- /dev/null
+++ b/bluez/units/hid.pxu
@@ -0,0 +1,87 @@
+# Copyright 2017 Canonical Ltd.
+# All rights reserved.
+#
+# Written by:
+#   Matteo Croce <[e-mail]>
+
+unit: category
+id: bluez
+_name: Bluez
+
+id: bluez/hid/pair_and_connect_hid
+category_id: bluez
+plugin: manual
+depends: bluez/setup/ensure_interface_connection_setup
+_summary: A Bluetooth HID gadget (e.g. keyboard, mouse) is connected and paired
+_purpose:
+ Check if your Bluetooth HID gadget of choice (e.g. keyboard, mouse) can be
+ paired to the host system.
+_steps:
+  1. Execute the following command to pair and connect your HID gadget to the
+     host system:
+  .
+    [bluetooth]# scan on
+    [bluetooth]# scan off
+    [bluetooth]# pair 01:02:03:04:05:06
+    [bluetooth]# connect 01:02:03:04:05:06
+  .
+_verification:
+  Open a text editor and make sure you can type text from the HID keyboard
+  into the text box. If testing a mouse, ensure that the cursor moves when
+  moving your HID mouse
+
+id: bluez/hid/bt_mouse_works
+category_id: bluez
+_description: Verify that Bluetooth mice do work
+plugin: manual
+depends: bluez/setup/pair_and_connect_hid
+_steps:
+  1. Scan for a BT mouse and connect it to the DUT
+_verification:
+  1. Verify that the paired mouse can move the pointer
+  2. Verify that the device is automatically connected at boot
+  3. Verify that the device is automatically connected after resume from sleep
+
+id: bluez/hid/bt_keyboard_works
+category_id: bluez
+_description: Verify that Bluetooth keyboards do work
+plugin: manual
+_steps:
+  1. Scan for a BT keyboard and connect it to the DUT, eg.
+  .
+    $ bluetoothctl
+    [bluetooth]# scan on
+    [bluetooth]# scan off
+    [bluetooth]# pair 01:02:03:04:05:06
+    Pairing successful
+    [bluetooth]# trust 01:02:03:04:05:06
+    [bluetooth]# connect 01:02:03:04:05:06
+    Trusted
+_verification:
+  1. Verify that the paired keyboard can write in a text editor
+  2. Verify that the device is automatically connected at boot
+  3. Verify that the device is automatically connected after resume from sleep
+  4. Press a key on the keyboard and power it off. Verify that the keystrokes are not transferred endlessly
+
+id: bluez/hid/ble_mouse_works
+category_id: bluez
+_description: Verify that BLE mices do work
+plugin: manual
+_steps:
+  1. Pair a BLE mouse with the DUT.
+_verification:
+  1. Verify that the paired mouse can move the pointer
+  2. Verify that the device is automatically connected at boot
+  3. Verify that the device is automatically connected after resume from sleep
+
+id: bluez/hid/ble_keyboard_works
+category_id: bluez
+_description: Verify that BLE keyboards do work
+plugin: manual
+_steps:
+  1. Pair a BLE keyboard with the DUT.
+_verification:
+  1. Verify that the paired keyboard can write in a text editor
+  2. Verify that the device is automatically connected at boot
+  3. Verify that the device is automatically connected after resume from sleep
+  4. Press a key on the keyboard and power it off. Verify that the keystrokes are not transferred endlessly
diff --git a/bluez/units/setup.pxu b/bluez/units/setup.pxu
new file mode 100644
index 0000000..ff42f94
--- /dev/null
+++ b/bluez/units/setup.pxu
@@ -0,0 +1,82 @@
+# Copyright 2017 Canonical Ltd.
+# All rights reserved.
+#
+# Written by:
+#   Matteo Croce <[e-mail]>
+
+id: bluez/setup/ensure_interface_connection_setup
+category_id: bluez
+_description: Ensure that the bluez interface is connected
+plugin: manual
+_steps:
+  1. Connect required bluez slot/plug
+  .
+    $ sudo snap connect bluez:client bluez:service
+  .
+_verification:
+  Verify that you see the following when running snap interfaces bluez:
+  bluez:service  bluez:client
+
+id: bluez/scan/get_all
+category_id: bluez
+plugin: manual
+depends: bluez/setup/ensure_interface_connection_setup
+_summary: All Bluetooth gadgets in range are listed
+_purpose:
+ Check if all powered on gadgets that are within range as listed.
+_steps:
+  1. Execute the following command to retrieve the list of all Bluetooth gadgets:
+  .
+    $ /snap/bin/bluez.bluetoothctl
+    [bluetooth]# scan on
+  .
+_verification:
+  Your expected Bluetooth gadget(s) is/are shown in the output list such as:
+    [NEW] Device 04:52:C7:0D:0C:03 QC 35s
+
+id: bluez/connection/pair_and_connect
+category_id: bluez
+plugin: manual
+depends: bluez/setup/ensure_interface_connection_setup
+_summary: A Bluetooth gadget of choice is paired and connected
+_purpose:
+ Check if your Bluetooth gadget of choice can be paired to the host system.
+_steps:
+  1. Execute the following command to pair and connect your gadget to the host
+     system using the address listed in the previous scan test:
+  .
+    [bluetooth]# pair <gadget_address>
+    [bluetooth]# connect <gadget_address>
+  .
+_verification:
+  You should see output similar to the following:
+  Attempting to pair with 04:52:C7:0D:0C:03
+    [CHG] Device 04:52:C7:0D:0C:03 Connected: yes
+    [CHG] Device 04:52:C7:0D:0C:03 Modalias: bluetooth:v009Ep400Cd0106
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00000000-deca-fade-deca-deafdecacaff
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: yes
+    [CHG] Device 04:52:C7:0D:0C:03 Paired: yes
+    Pairing successful
+    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: no
+    [CHG] Device 04:52:C7:0D:0C:03 Connected: no
+    Attempting to connect to 04:52:C7:0D:0C:03
+    [CHG] Device 04:52:C7:0D:0C:03 Connected: yes
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00000000-deca-fade-deca-deafdecacaff
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
+    [CHG] Device 04:52:C7:0D:0C:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
+    Connection successful
+    [CHG] Device 04:52:C7:0D:0C:03 ServicesResolved: yes
+