Ubuntu Certified Docking Stations Coverage for 22.04 LTS

Introduction

Although docking stations are currently out of scope of the general Ubuntu Desktop Certified Hardware programme at Canonical, we have an extension to the programme to enable and certify a particular docking station with an already Ubuntu certified system. This programme does not certify a particular docking station to work with all Ubuntu certified systems, nor will a docking station be tested and/or certified in isolation, but always as part of the certification of a full system.

This document lists the coverage for certification of docking stations for Ubuntu Desktop 22.04 LTS. This coverage will remain as it is for Ubuntu Desktop 22.04 LTS through the life cycle of Ubuntu Desktop 22.04 LTS.

For each test job, one of the following certification statuses is specified:

Blocking

Features that are required for certification. If any of the blocking tests fails, the certification will fail.

Non-blocking

Features that are tested but not mandatory for certification. Failure in non-blocking tests will not prevent certification. However, a note will be added to the certificate to inform potential customers or users.

Note

Only categories of hardware are tested and not specific types of hardware. For example, tests are run to verify USB controllers work, but the type of peripheral(s) used during those tests are not specified.

Coverage is flexible based on customer requirements (for example, if a device’s use cases don’t require LEDs, then LEDs can be non-blocking)

Certain test jobs are designed to validate specific hardware capabilities, such as camera and audio playback functionality. To ensure that the required hardware capabilities are present and properly recognised on the machine under test, these features are explicitly defined in manifest entries and linked to the relevant test jobs. This prevents test jobs from being skipped due to system deficiencies in automated detection.

Full test descriptions can be found in Canonical certification site for partners:

https://certification.canonical.com

Note

At the time of this writing, only wired docks are supported. Wireless docking requires functionality that is not known to be supported by IHVs.

Note

This also does not cover “smart” docks, i.e. docks that contain additional components (like graphics adapters, etc.).

Main testing flow

Once the connected components like DP monitors, HDMI monitors, and ethernet cables have been plugged, they will remain plugged in throughout testing. However, for user-removable components such as USB drives or Thunderbolt storage devices, hotplugging functionality will be tested. The testing process will follow a flow similar to:

1. Plug all the components into the docking station

2. Unplug the storage when meet the storage test

3. Start storage testing(Insert, auto, remove)

4. Plug it back when finish the storage test

dock-cert-full

Note

The certification tests presented in this document are validated by Checkbox version 7.0.0.dev58.

Blocking

Docking station audio tests

Output sound needs to be undistorted between 0%-100%. Output lines tested:

• 3.5mm headphones

• HDMI audio output

• DisplayPort audio output

Input needs to be recorded undistorted between 0%-100%. Input lines tested:

• 3.5mm microphone

The following test units are covered in this category:

dock/all-hotplug-audio-alsa-record-playback-external

External microphone plugged to the dock to record sound test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that recording sound using an external microphone works correctly. (Skip this test if the dock does not have a microphone connector)
Steps:	Connect a microphone to the dock’s microphone port. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click “Test”, then speak into the external microphone. 4. After a few seconds, your speech will be played back to you.
Verification:	Did you hear your speech played back?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_audio_capture == ‘True’ package.name == ‘alsa-base’ package.name == ‘gstreamer1.0-plugins-good’ or package.name == ‘gstreamer0.10-plugins-good’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_audio_capture.

dock/all-hotplug-audio-microphone-plug-detection

Microphone recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects a microphone being plugged in. (Skip this test if the dock does not have a microphone connector)
Steps:	Prepare a microphone with a standard 3.5mm jack. 2. Locate the microphone jack on the dock under test. Keep in mind that it may be shared with the headphone jack. 3. Run the test (you have 30 seconds from now on) 4. Plug the microphone into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-hotplug-audio-playback-headphones

Headphones output test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that headphones connector works correctly. (Skip this test if there is no headphone connector on the dock)
Steps:	Connect a pair of headphones to the dock. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click the Test button to play a sound to your audio device.
Verification:	Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name == ‘alsa-base’ package.name == ‘gir1.2-gst-plugins-base-0.10’ or package.name == ‘gir1.2-gst-plugins-base-1.0’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-hotplug-audio-speaker-headphone-plug-detection

Headphones recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects speakers or headphones being plugged in. (Skip this test if the dock does not have headphones connector)
Steps:	Prepare a pair of headphones or speakers with a standard 3.5mm jack. 2. Locate the speaker / headphone jack on the dock under test. 3. Run the test (you have 30 seconds from now on). 4. Plug headphones or speakers into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-hotplug-monitor-multi-head-audio-playback

Multiple monitor audio test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test is to check if every external monitor on the dock can play sound.
Steps:	Launch the test to play sound on every monitor.
Verification:	Can every external monitor play sound? If no sound output, try: 1. Go to Settings > Sound > Output > Test > Try Front Left and Front Right. 2. Repeat Step 1 for each monitor.
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-init-audio-alsa-record-playback-external

External microphone plugged to the dock to record sound test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that recording sound using an external microphone works correctly. (Skip this test if the dock does not have a microphone connector)
Steps:	Connect a microphone to the dock’s microphone port. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click “Test”, then speak into the external microphone. 4. After a few seconds, your speech will be played back to you.
Verification:	Did you hear your speech played back?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_audio_capture == ‘True’ package.name == ‘alsa-base’ package.name == ‘gstreamer1.0-plugins-good’ or package.name == ‘gstreamer0.10-plugins-good’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_audio_capture.

dock/all-init-audio-microphone-plug-detection

Microphone recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects a microphone being plugged in. (Skip this test if the dock does not have a microphone connector)
Steps:	Prepare a microphone with a standard 3.5mm jack. 2. Locate the microphone jack on the dock under test. Keep in mind that it may be shared with the headphone jack. 3. Run the test (you have 30 seconds from now on) 4. Plug the microphone into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-init-audio-playback-headphones

Headphones output test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that headphones connector works correctly. (Skip this test if there is no headphone connector on the dock)
Steps:	Connect a pair of headphones to the dock. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click the Test button to play a sound to your audio device.
Verification:	Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name == ‘alsa-base’ package.name == ‘gir1.2-gst-plugins-base-0.10’ or package.name == ‘gir1.2-gst-plugins-base-1.0’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-init-audio-speaker-headphone-plug-detection

Headphones recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects speakers or headphones being plugged in. (Skip this test if the dock does not have headphones connector)
Steps:	Prepare a pair of headphones or speakers with a standard 3.5mm jack. 2. Locate the speaker / headphone jack on the dock under test. 3. Run the test (you have 30 seconds from now on). 4. Plug headphones or speakers into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-init-monitor-multi-head-audio-playback

Multiple monitor audio test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test is to check if every external monitor on the dock can play sound.
Steps:	Launch the test to play sound on every monitor.
Verification:	Can every external monitor play sound? If no sound output, try: 1. Go to Settings > Sound > Output > Test > Try Front Left and Front Right. 2. Repeat Step 1 for each monitor.
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-poweroff-audio-alsa-record-playback-external

External microphone plugged to the dock to record sound test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that recording sound using an external microphone works correctly. (Skip this test if the dock does not have a microphone connector)
Steps:	Connect a microphone to the dock’s microphone port. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click “Test”, then speak into the external microphone. 4. After a few seconds, your speech will be played back to you.
Verification:	Did you hear your speech played back?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_audio_capture == ‘True’ package.name == ‘alsa-base’ package.name == ‘gstreamer1.0-plugins-good’ or package.name == ‘gstreamer0.10-plugins-good’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_audio_capture.

dock/all-poweroff-audio-microphone-plug-detection

Microphone recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects a microphone being plugged in. (Skip this test if the dock does not have a microphone connector)
Steps:	Prepare a microphone with a standard 3.5mm jack. 2. Locate the microphone jack on the dock under test. Keep in mind that it may be shared with the headphone jack. 3. Run the test (you have 30 seconds from now on) 4. Plug the microphone into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-poweroff-audio-playback-headphones

Headphones output test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that headphones connector works correctly. (Skip this test if there is no headphone connector on the dock)
Steps:	Connect a pair of headphones to the dock. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click the Test button to play a sound to your audio device.
Verification:	Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name == ‘alsa-base’ package.name == ‘gir1.2-gst-plugins-base-0.10’ or package.name == ‘gir1.2-gst-plugins-base-1.0’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-poweroff-audio-speaker-headphone-plug-detection

Headphones recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects speakers or headphones being plugged in. (Skip this test if the dock does not have headphones connector)
Steps:	Prepare a pair of headphones or speakers with a standard 3.5mm jack. 2. Locate the speaker / headphone jack on the dock under test. 3. Run the test (you have 30 seconds from now on). 4. Plug headphones or speakers into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-poweroff-monitor-multi-head-audio-playback

Multiple monitor audio test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test is to check if every external monitor on the dock can play sound.
Steps:	Launch the test to play sound on every monitor.
Verification:	Can every external monitor play sound? If no sound output, try: 1. Go to Settings > Sound > Output > Test > Try Front Left and Front Right. 2. Repeat Step 1 for each monitor.
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-reboot-audio-alsa-record-playback-external

External microphone plugged to the dock to record sound test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that recording sound using an external microphone works correctly. (Skip this test if the dock does not have a microphone connector)
Steps:	Connect a microphone to the dock’s microphone port. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click “Test”, then speak into the external microphone. 4. After a few seconds, your speech will be played back to you.
Verification:	Did you hear your speech played back?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_audio_capture == ‘True’ package.name == ‘alsa-base’ package.name == ‘gstreamer1.0-plugins-good’ or package.name == ‘gstreamer0.10-plugins-good’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_audio_capture.

dock/all-reboot-audio-microphone-plug-detection

Microphone recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects a microphone being plugged in. (Skip this test if the dock does not have a microphone connector)
Steps:	Prepare a microphone with a standard 3.5mm jack. 2. Locate the microphone jack on the dock under test. Keep in mind that it may be shared with the headphone jack. 3. Run the test (you have 30 seconds from now on) 4. Plug the microphone into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-reboot-audio-playback-headphones

Headphones output test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that headphones connector works correctly. (Skip this test if there is no headphone connector on the dock)
Steps:	Connect a pair of headphones to the dock. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click the Test button to play a sound to your audio device.
Verification:	Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name == ‘alsa-base’ package.name == ‘gir1.2-gst-plugins-base-0.10’ or package.name == ‘gir1.2-gst-plugins-base-1.0’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-reboot-audio-speaker-headphone-plug-detection

Headphones recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects speakers or headphones being plugged in. (Skip this test if the dock does not have headphones connector)
Steps:	Prepare a pair of headphones or speakers with a standard 3.5mm jack. 2. Locate the speaker / headphone jack on the dock under test. 3. Run the test (you have 30 seconds from now on). 4. Plug headphones or speakers into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-reboot-monitor-multi-head-audio-playback

Multiple monitor audio test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test is to check if every external monitor on the dock can play sound.
Steps:	Launch the test to play sound on every monitor.
Verification:	Can every external monitor play sound? If no sound output, try: 1. Go to Settings > Sound > Output > Test > Try Front Left and Front Right. 2. Repeat Step 1 for each monitor.
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-suspend-audio-alsa-record-playback-external

External microphone plugged to the dock to record sound test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that recording sound using an external microphone works correctly. (Skip this test if the dock does not have a microphone connector)
Steps:	Connect a microphone to the dock’s microphone port. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click “Test”, then speak into the external microphone. 4. After a few seconds, your speech will be played back to you.
Verification:	Did you hear your speech played back?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_audio_capture == ‘True’ package.name == ‘alsa-base’ package.name == ‘gstreamer1.0-plugins-good’ or package.name == ‘gstreamer0.10-plugins-good’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_audio_capture.

dock/all-suspend-audio-microphone-plug-detection

Microphone recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects a microphone being plugged in. (Skip this test if the dock does not have a microphone connector)
Steps:	Prepare a microphone with a standard 3.5mm jack. 2. Locate the microphone jack on the dock under test. Keep in mind that it may be shared with the headphone jack. 3. Run the test (you have 30 seconds from now on) 4. Plug the microphone into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-suspend-audio-playback-headphones

Headphones output test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that headphones connector works correctly. (Skip this test if there is no headphone connector on the dock)
Steps:	Connect a pair of headphones to the dock. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click the Test button to play a sound to your audio device.
Verification:	Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name == ‘alsa-base’ package.name == ‘gir1.2-gst-plugins-base-0.10’ or package.name == ‘gir1.2-gst-plugins-base-1.0’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-suspend-audio-speaker-headphone-plug-detection

Headphones recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects speakers or headphones being plugged in. (Skip this test if the dock does not have headphones connector)
Steps:	Prepare a pair of headphones or speakers with a standard 3.5mm jack. 2. Locate the speaker / headphone jack on the dock under test. 3. Run the test (you have 30 seconds from now on). 4. Plug headphones or speakers into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-suspend-hotplug-audio-alsa-record-playback-external

External microphone plugged to the dock to record sound test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that recording sound using an external microphone works correctly. (Skip this test if the dock does not have a microphone connector)
Steps:	Connect a microphone to the dock’s microphone port. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click “Test”, then speak into the external microphone. 4. After a few seconds, your speech will be played back to you.
Verification:	Did you hear your speech played back?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_audio_capture == ‘True’ package.name == ‘alsa-base’ package.name == ‘gstreamer1.0-plugins-good’ or package.name == ‘gstreamer0.10-plugins-good’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_audio_capture.

dock/all-suspend-hotplug-audio-microphone-plug-detection

Microphone recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects a microphone being plugged in. (Skip this test if the dock does not have a microphone connector)
Steps:	Prepare a microphone with a standard 3.5mm jack. 2. Locate the microphone jack on the dock under test. Keep in mind that it may be shared with the headphone jack. 3. Run the test (you have 30 seconds from now on) 4. Plug the microphone into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-suspend-hotplug-audio-playback-headphones

Headphones output test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test will check that headphones connector works correctly. (Skip this test if there is no headphone connector on the dock)
Steps:	Connect a pair of headphones to the dock. 2. Go to the Sound settings and make sure the correct Output is selected. 3. Click the Test button to play a sound to your audio device.
Verification:	Did you hear a sound through the headphones and did the sound play without any distortion, clicks or other strange noises from your headphones?
After-suspend:	True
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name == ‘alsa-base’ package.name == ‘gir1.2-gst-plugins-base-0.10’ or package.name == ‘gir1.2-gst-plugins-base-1.0’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-suspend-hotplug-audio-speaker-headphone-plug-detection

Headphones recognized when plugged to the dock test

Category ID:	dock-audio
Status:	Blocking
Purpose:	Check that system detects speakers or headphones being plugged in. (Skip this test if the dock does not have headphones connector)
Steps:	Prepare a pair of headphones or speakers with a standard 3.5mm jack. 2. Locate the speaker / headphone jack on the dock under test. 3. Run the test (you have 30 seconds from now on). 4. Plug headphones or speakers into the appropriate jack. 5. Unplug the device for subsequent tests.
Verification:	Verification is automatic, no action is required. The test times out after 30 seconds (and fails in that case).
Plugin:	user-interact
Requires:	manifest.has_audio_playback == ‘True’ manifest.has_dock_headset == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback, has_dock_headset.

dock/all-suspend-hotplug-monitor-multi-head-audio-playback

Multiple monitor audio test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test is to check if every external monitor on the dock can play sound.
Steps:	Launch the test to play sound on every monitor.
Verification:	Can every external monitor play sound? If no sound output, try: 1. Go to Settings > Sound > Output > Test > Try Front Left and Front Right. 2. Repeat Step 1 for each monitor.
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

dock/all-suspend-monitor-multi-head-audio-playback

Multiple monitor audio test

Category ID:	dock-audio
Status:	Blocking
Purpose:	This test is to check if every external monitor on the dock can play sound.
Steps:	Launch the test to play sound on every monitor.
Verification:	Can every external monitor play sound? If no sound output, try: 1. Go to Settings > Sound > Output > Test > Try Front Left and Front Right. 2. Repeat Step 1 for each monitor.
Plugin:	user-interact-verify
Requires:	manifest.has_audio_playback == ‘True’ package.name in [‘pulseaudio-utils’, ‘pipewire’]

For details about the required manifest entry, see has_audio_playback.

Docking station display tests

Multi-monitors should be supported following the specifications of the docking station and DUT. The amount of monitors and which ports are going to be used is not specified, it depends on the hardware limitation of the docking station and DUT.

The following test units are covered in this category:

dock/all-hotplug-monitor-multi-head

Dual monitors test while docked

Category ID:	dock-display
Status:	Blocking
Purpose:	This test is to verify that multi-monitor output works using the dock. You will need multiple external monitors to perform this test. Depends on the specification of the device to use 4K monitor or FHD monitor.
Steps:	Skip this test if your video card or the dock do not support multiple monitors. 1. If your dock provides more than one monitor outputs, connect multiple monitors. 2. Open the “Displays” tool (open the dash and search for “Displays”). 3. Configure your output to provide one desktop across all the monitors. 4. Open any application and drag its window from one monitor to the next.
Verification:	Was the stretched desktop displayed correctly across all the screens?
Plugin:	manual

dock/all-init-monitor-multi-head

Dual monitors test while docked

Category ID:	dock-display
Status:	Blocking
Purpose:	This test is to verify that multi-monitor output works using the dock. You will need multiple external monitors to perform this test. Depends on the specification of the device to use 4K monitor or FHD monitor.
Steps:	Skip this test if your video card or the dock do not support multiple monitors. 1. If your dock provides more than one monitor outputs, connect multiple monitors. 2. Open the “Displays” tool (open the dash and search for “Displays”). 3. Configure your output to provide one desktop across all the monitors. 4. Open any application and drag its window from one monitor to the next.
Verification:	Was the stretched desktop displayed correctly across all the screens?
Plugin:	manual

dock/all-poweroff-monitor-multi-head

Dual monitors test while docked

Category ID:	dock-display
Status:	Blocking
Purpose:	This test is to verify that multi-monitor output works using the dock. You will need multiple external monitors to perform this test. Depends on the specification of the device to use 4K monitor or FHD monitor.
Steps:	Skip this test if your video card or the dock do not support multiple monitors. 1. If your dock provides more than one monitor outputs, connect multiple monitors. 2. Open the “Displays” tool (open the dash and search for “Displays”). 3. Configure your output to provide one desktop across all the monitors. 4. Open any application and drag its window from one monitor to the next.
Verification:	Was the stretched desktop displayed correctly across all the screens?
Plugin:	manual

dock/all-reboot-monitor-multi-head

Dual monitors test while docked

Category ID:	dock-display
Status:	Blocking
Purpose:	This test is to verify that multi-monitor output works using the dock. You will need multiple external monitors to perform this test. Depends on the specification of the device to use 4K monitor or FHD monitor.
Steps:	Skip this test if your video card or the dock do not support multiple monitors. 1. If your dock provides more than one monitor outputs, connect multiple monitors. 2. Open the “Displays” tool (open the dash and search for “Displays”). 3. Configure your output to provide one desktop across all the monitors. 4. Open any application and drag its window from one monitor to the next.
Verification:	Was the stretched desktop displayed correctly across all the screens?
Plugin:	manual

dock/all-suspend-hotplug-monitor-multi-head

Dual monitors test while docked

Category ID:	dock-display
Status:	Blocking
Purpose:	This test is to verify that multi-monitor output works using the dock. You will need multiple external monitors to perform this test. Depends on the specification of the device to use 4K monitor or FHD monitor.
Steps:	Skip this test if your video card or the dock do not support multiple monitors. 1. If your dock provides more than one monitor outputs, connect multiple monitors. 2. Open the “Displays” tool (open the dash and search for “Displays”). 3. Configure your output to provide one desktop across all the monitors. 4. Open any application and drag its window from one monitor to the next.
Verification:	Was the stretched desktop displayed correctly across all the screens?
Plugin:	manual

dock/all-suspend-monitor-multi-head

Dual monitors test while docked

Category ID:	dock-display
Status:	Blocking
Purpose:	This test is to verify that multi-monitor output works using the dock. You will need multiple external monitors to perform this test. Depends on the specification of the device to use 4K monitor or FHD monitor.
Steps:	Skip this test if your video card or the dock do not support multiple monitors. 1. If your dock provides more than one monitor outputs, connect multiple monitors. 2. Open the “Displays” tool (open the dash and search for “Displays”). 3. Configure your output to provide one desktop across all the monitors. 4. Open any application and drag its window from one monitor to the next.
Verification:	Was the stretched desktop displayed correctly across all the screens?
Plugin:	manual

Docking station network tests

• Ethernet (RJ-45 Network Jack). Connections are tested for functionality, but not for performance.

The following test units are covered in this category:

dock/all-hotplug-ethernet-detect

Detect if at least one ethernet device is detected

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to detect and return information about available network controllers on the system under test.
Plugin:	shell
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-hotplug-networking-gateway-ping

Ping test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Tests whether the system has a working Internet connection.
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to ping the network using the Ethernet connection?
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-hotplug-networking-ntp

NTP sync test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to see if we can sync local clock to an NTP server
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to synchronize system time using the Ethernet connection?
User:	root
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’ (package.name == ‘ntpdate’ or package.name == ‘ntpsec-ntpdate’)

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-init-ethernet-detect

Detect if at least one ethernet device is detected

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to detect and return information about available network controllers on the system under test.
Plugin:	shell
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-init-networking-gateway-ping

Ping test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Tests whether the system has a working Internet connection.
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to ping the network using the Ethernet connection?
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-init-networking-ntp

NTP sync test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to see if we can sync local clock to an NTP server
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to synchronize system time using the Ethernet connection?
User:	root
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’ (package.name == ‘ntpdate’ or package.name == ‘ntpsec-ntpdate’)

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-poweroff-ethernet-detect

Detect if at least one ethernet device is detected

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to detect and return information about available network controllers on the system under test.
Plugin:	shell
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-poweroff-networking-gateway-ping

Ping test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Tests whether the system has a working Internet connection.
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to ping the network using the Ethernet connection?
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-poweroff-networking-ntp

NTP sync test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to see if we can sync local clock to an NTP server
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to synchronize system time using the Ethernet connection?
User:	root
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’ (package.name == ‘ntpdate’ or package.name == ‘ntpsec-ntpdate’)

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-reboot-ethernet-detect

Detect if at least one ethernet device is detected

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to detect and return information about available network controllers on the system under test.
Plugin:	shell
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-reboot-networking-gateway-ping

Ping test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Tests whether the system has a working Internet connection.
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to ping the network using the Ethernet connection?
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-reboot-networking-ntp

NTP sync test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to see if we can sync local clock to an NTP server
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to synchronize system time using the Ethernet connection?
User:	root
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’ (package.name == ‘ntpdate’ or package.name == ‘ntpsec-ntpdate’)

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-suspend-ethernet-detect

Detect if at least one ethernet device is detected

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to detect and return information about available network controllers on the system under test.
Plugin:	shell
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-suspend-hotplug-ethernet-detect

Detect if at least one ethernet device is detected

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to detect and return information about available network controllers on the system under test.
Plugin:	shell
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-suspend-hotplug-networking-gateway-ping

Ping test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Tests whether the system has a working Internet connection.
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to ping the network using the Ethernet connection?
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-suspend-hotplug-networking-ntp

NTP sync test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to see if we can sync local clock to an NTP server
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to synchronize system time using the Ethernet connection?
User:	root
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’ (package.name == ‘ntpdate’ or package.name == ‘ntpsec-ntpdate’)

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-suspend-networking-gateway-ping

Ping test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Tests whether the system has a working Internet connection.
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to ping the network using the Ethernet connection?
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’

For details about the required manifest entry, see has_dock_ethernet_adapter.

dock/all-suspend-networking-ntp

NTP sync test using dock’s Ethernet connectivity

Category ID:	dock-network
Status:	Blocking
Purpose:	Test to see if we can sync local clock to an NTP server
Steps:	Make sure the dock is connected to network using an Ethernet cable. 2. Make sure the laptop itself is not connected to any network. 3. Launch the test.
Verification:	Was the test able to synchronize system time using the Ethernet connection?
User:	root
Plugin:	user-interact-verify
Requires:	manifest.has_dock_ethernet_adapter == ‘True’ (package.name == ‘ntpdate’ or package.name == ‘ntpsec-ntpdate’)

For details about the required manifest entry, see has_dock_ethernet_adapter.

Docking station tests

The following test units are covered in this category:

dock/all-hotplug

Verify the device functionality after hotplug actions with the docking station.

Category ID:	dock
Status:	Blocking
Purpose:	This test checks if the device is still working after hotplug.
Steps:	Unplug the docking station. 2. Wait for 30 seconds. 3. Plug in the docking station.
Verification:	Mark it Pass if you have hotplugged the docking station. The functionality will be verified through the following test cases.
Plugin:	manual

dock/all-hotplug-thunderbolt3-storage-manual

Thunderbolt3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a Thunderbolt3 HDD to the dock could be detected, then performs read/write operations on the attached Thunderbolt3 storage and checks if the removal of the Thunderbolt3 HDD can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a Thunderbolt3 HDD into an available Thunderbolt3 port on the dock. If it’s not mounted automatically, please click the HDD icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached Thunderbolt3 HDD from the Thunderbolt3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	manifest.has_dock_thunderbolt3 == ‘True’

For details about the required manifest entry, see has_dock_thunderbolt3.

dock/all-hotplug-usb-c-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a usb-c storage to the dock could be detected, then performs read/write operations on the attached usb-c storage and checks if the removal of the usb-c storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available usb-c port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached usb-c storage from the usb-c port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’ manifest.has_dock_usbc_data == ‘True’

For details about the required manifest entry, see has_dock_usbc_data.

dock/all-hotplug-usb3-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a USB3 storage to the dock could be detected, then performs read/write operations on the attached USB3 storage and checks if the removal of the USB3 storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available USB3 port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached USB3 storage from the USB3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’

dock/all-init

Prepare all I/O ports on the dock by connecting all devices it supports.

Category ID:	dock
Status:	Blocking
Purpose:	This test is to set up the initial status for all I/O ports on the docking station. Note: Try to meet the limitations in the spec of the dock. If there’s no port as described below, you can just skip it.
Steps:	Connect an Ethernet cable to the docking station. 2. Connect a DP monitor to the docking station. 3. Connect an HDMI monitor to the docking station. 4. Connect a Thunderbolt monitor to the docking station. 5. Connect a Thunderbolt3 storage to the docking station. 6. Connect a USB Type-C storage to the docking station. 7. Connect a USB3.0 storage to the docking station. 8. Connect a headset to the docking station. 9. If the laptop is currently undocked, dock it now.
Verification:	Mark it Pass if you have connected all I/O ports as mentioned above. The functionality will be verified through the following test cases.
Plugin:	manual

dock/all-init-thunderbolt3-storage-manual

Thunderbolt3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a Thunderbolt3 HDD to the dock could be detected, then performs read/write operations on the attached Thunderbolt3 storage and checks if the removal of the Thunderbolt3 HDD can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a Thunderbolt3 HDD into an available Thunderbolt3 port on the dock. If it’s not mounted automatically, please click the HDD icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached Thunderbolt3 HDD from the Thunderbolt3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	manifest.has_dock_thunderbolt3 == ‘True’

For details about the required manifest entry, see has_dock_thunderbolt3.

dock/all-init-usb-c-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a usb-c storage to the dock could be detected, then performs read/write operations on the attached usb-c storage and checks if the removal of the usb-c storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available usb-c port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached usb-c storage from the usb-c port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’ manifest.has_dock_usbc_data == ‘True’

For details about the required manifest entry, see has_dock_usbc_data.

dock/all-init-usb3-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a USB3 storage to the dock could be detected, then performs read/write operations on the attached USB3 storage and checks if the removal of the USB3 storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available USB3 port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached USB3 storage from the USB3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’

dock/all-poweroff

Test device functionality after powering off and on.

Category ID:	dock
Status:	Blocking
Purpose:	This test is to check if the device is still working after power-off.
Steps:	Power off the system. 2. Wait for 30 seconds. 3. Power on the system.
Verification:	Mark it Pass if you have powered off and powered on the system. The functionality will be verified through the following test cases.
Plugin:	manual

dock/all-poweroff-thunderbolt3-storage-manual

Thunderbolt3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a Thunderbolt3 HDD to the dock could be detected, then performs read/write operations on the attached Thunderbolt3 storage and checks if the removal of the Thunderbolt3 HDD can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a Thunderbolt3 HDD into an available Thunderbolt3 port on the dock. If it’s not mounted automatically, please click the HDD icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached Thunderbolt3 HDD from the Thunderbolt3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	manifest.has_dock_thunderbolt3 == ‘True’

For details about the required manifest entry, see has_dock_thunderbolt3.

dock/all-poweroff-usb-c-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a usb-c storage to the dock could be detected, then performs read/write operations on the attached usb-c storage and checks if the removal of the usb-c storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available usb-c port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached usb-c storage from the usb-c port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’ manifest.has_dock_usbc_data == ‘True’

For details about the required manifest entry, see has_dock_usbc_data.

dock/all-poweroff-usb3-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a USB3 storage to the dock could be detected, then performs read/write operations on the attached USB3 storage and checks if the removal of the USB3 storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available USB3 port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached USB3 storage from the USB3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’

dock/all-reboot

<missing summary>

Category ID:	dock
Status:	Blocking
Purpose:	This test is to check if the device is still working after reboot.
Steps:	Reboot the system.
Verification:	Mark it Pass if you have rebooted the system. The functionality will be verified through the following test cases.
Plugin:	manual

dock/all-reboot-thunderbolt3-storage-manual

Thunderbolt3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a Thunderbolt3 HDD to the dock could be detected, then performs read/write operations on the attached Thunderbolt3 storage and checks if the removal of the Thunderbolt3 HDD can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a Thunderbolt3 HDD into an available Thunderbolt3 port on the dock. If it’s not mounted automatically, please click the HDD icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached Thunderbolt3 HDD from the Thunderbolt3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	manifest.has_dock_thunderbolt3 == ‘True’

For details about the required manifest entry, see has_dock_thunderbolt3.

dock/all-reboot-usb-c-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a usb-c storage to the dock could be detected, then performs read/write operations on the attached usb-c storage and checks if the removal of the usb-c storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available usb-c port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached usb-c storage from the usb-c port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’ manifest.has_dock_usbc_data == ‘True’

For details about the required manifest entry, see has_dock_usbc_data.

dock/all-reboot-usb3-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a USB3 storage to the dock could be detected, then performs read/write operations on the attached USB3 storage and checks if the removal of the USB3 storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available USB3 port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached USB3 storage from the USB3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’

dock/all-suspend

Test the system’s functionality after suspend and resume.

Category ID:	dock
Status:	Blocking
Purpose:	This test is to check if the device is still functional after suspend.
Steps:	Suspend the system. 2. Wait for 30 seconds. 3. Resume the system.
Verification:	Mark it as Pass if you have successfully suspended and resumed the system. The functionality will be verified through the following test cases.
Plugin:	manual

dock/all-suspend-hotplug

Test the system’s functionality after suspend and resume.

Category ID:	dock
Status:	Blocking
Purpose:	This test is to check if the device can resume automatically and remain functional after a hotplug event during suspend.
Steps:	Ensure the dock is connected. 2. Suspend the system. 3. Wait for 30 seconds. 4. Hotplug dock. 5. Resume the system.
Verification:	Mark it as Pass if the system can resume automatically when the dock is hotplugged during suspend. The functionality will be verified through the following test cases.
Plugin:	manual

dock/all-suspend-hotplug-thunderbolt3-storage-manual

Thunderbolt3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a Thunderbolt3 HDD to the dock could be detected, then performs read/write operations on the attached Thunderbolt3 storage and checks if the removal of the Thunderbolt3 HDD can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a Thunderbolt3 HDD into an available Thunderbolt3 port on the dock. If it’s not mounted automatically, please click the HDD icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached Thunderbolt3 HDD from the Thunderbolt3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	manifest.has_dock_thunderbolt3 == ‘True’

For details about the required manifest entry, see has_dock_thunderbolt3.

dock/all-suspend-hotplug-usb-c-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a usb-c storage to the dock could be detected, then performs read/write operations on the attached usb-c storage and checks if the removal of the usb-c storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available usb-c port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached usb-c storage from the usb-c port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’ manifest.has_dock_usbc_data == ‘True’

For details about the required manifest entry, see has_dock_usbc_data.

dock/all-suspend-hotplug-usb3-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a USB3 storage to the dock could be detected, then performs read/write operations on the attached USB3 storage and checks if the removal of the USB3 storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available USB3 port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached USB3 storage from the USB3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’

dock/all-suspend-thunderbolt3-storage-manual

Thunderbolt3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a Thunderbolt3 HDD to the dock could be detected, then performs read/write operations on the attached Thunderbolt3 storage and checks if the removal of the Thunderbolt3 HDD can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a Thunderbolt3 HDD into an available Thunderbolt3 port on the dock. If it’s not mounted automatically, please click the HDD icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached Thunderbolt3 HDD from the Thunderbolt3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	manifest.has_dock_thunderbolt3 == ‘True’

For details about the required manifest entry, see has_dock_thunderbolt3.

dock/all-suspend-usb-c-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a usb-c storage to the dock could be detected, then performs read/write operations on the attached usb-c storage and checks if the removal of the usb-c storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available usb-c port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached usb-c storage from the usb-c port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’ manifest.has_dock_usbc_data == ‘True’

For details about the required manifest entry, see has_dock_usbc_data.

dock/all-suspend-usb3-storage-manual

USB3 storage insertion + read/write + removal

Category ID:	dock
Status:	Blocking
Purpose:	This test will check if the connection of a USB3 storage to the dock could be detected, then performs read/write operations on the attached USB3 storage and checks if the removal of the USB3 storage can be detected.
Steps:	Click ‘Test’ to begin the test. This test will timeout and fail if the insertion has not been detected within 30 seconds. 2. Plug a USB3 storage into an available USB3 port on the dock. If it’s not mounted automatically, please click the storage icon to mount it. 3. Wait for the read/write operations to complete. 4. Press Enter to start the removal test. 5. Remove the previously attached USB3 storage from the USB3 port.
Verification:	The verification of this test is automated. Do not change the automatically selected result.
After-suspend:	True
User:	root
Plugin:	user-interact
Requires:	usb.usb3 == ‘supported’

dock/init-connection

Ensure the dock can be detected and set up correctly the first time.

Category ID:	dock
Status:	Blocking
Purpose:	This test is to ensure the system can detect and set up the dock correctly the first time. Please reset the OS before testing this test case again.
Steps:	Boot into OS. 2. Connect the dock to the system.
Verification:	Mark it as Pass if the system can detect and set up the dock correctly. The functionality will be verified through the following test cases.
Plugin:	manual

Manifest Entries

The following manifest entries are required for certification:

has_audio_capture

Audio capture: Machine can record sound. (For example, a desktop PC probably requires a microphone connected to it)

Value type:	bool
Prompt:	Does this machine have the following audio features?

has_audio_playback

Audio playback: Machine can emit sound. (For example, a desktop PC probably requires speakers connected to it)

Value type:	bool
Prompt:	Does this machine have the following audio features?

has_dock_ethernet_adapter

An Ethernet Port on dock

Value type:	bool
Prompt:	Does this dock has the following features?

has_dock_headset

Headset (Headphones + Microphone) port on dock

Value type:	bool
Prompt:	Does this dock has the following features?

has_dock_thunderbolt3

Thunderbolt 3 Support on dock

Value type:	bool
Prompt:	Does this dock has the following features?

has_dock_usbc_data

USB Type-C Data (e.g. HID, Drives, Ethernet) on dock

Value type:	bool
Prompt:	Does this dock has the following features?