Launchpad automatic translations update.plainbox-provider-checkbox-v0.26c3plainbox-provider-checkbox-v0.26

1 files changed, 7865 insertions, 0 deletions

diff --git a/po/de.po b/po/de.po
new file mode 100644
index 0000000..e6c8038
--- /dev/null
+++ b/po/de.po
@@ -0,0 +1,7865 @@
+# German translation for checkbox
+# Copyright (c) 2016 Rosetta Contributors and Canonical Ltd 2016
+# This file is distributed under the same license as the checkbox package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2016.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: checkbox\n"
+"Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>\n"
+"POT-Creation-Date: 2016-03-07 14:59+0800\n"
+"PO-Revision-Date: 2016-03-12 10:07+0000\n"
+"Last-Translator: Denis Graipel <Unknown>\n"
+"Language-Team: German <de@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Launchpad-Export-Date: 2016-03-13 05:16+0000\n"
+"X-Generator: Launchpad (build 17939)\n"
+
+#. description
+#: ../jobs/audio.txt.in:9 ../units/dock.pxu:108
+msgid "Test to detect audio devices"
+msgstr "Test zur Erkennung von Audio-Geräten"
+
+#. description
+#: ../jobs/audio.txt.in:28
+msgid ""
+"PURPOSE:\n"
+" This test will check that internal speakers work correctly\n"
+"STEPS:\n"
+" 1. Make sure that no external speakers or headphones are connected\n"
+" When testing a desktop, you can skip this test if there is no\n"
+" internal speaker, we will test the external output later\n"
+" 2. Commence the test to play a brief tone on your audio device\n"
+"VERIFICATION:\n"
+" Did you hear a tone?"
+msgstr ""
+
+#. purpose
+#: ../jobs/audio.txt.in:58
+msgid " HDMI audio interface verification"
+msgstr ""
+
+#. steps
+#: ../jobs/audio.txt.in:60
+msgid ""
+" 1. Plug an external HDMI device with sound (Use only one "
+"HDMI/DisplayPort/Thunderbolt interface at a time for this test)\n"
+" 2. Commence the test"
+msgstr ""
+
+#. verification
+#: ../jobs/audio.txt.in:63 ../units/dock.pxu:133
+msgid " Did you hear the sound from the HDMI device?"
+msgstr ""
+
+#. purpose
+#: ../jobs/audio.txt.in:85
+msgid " DisplayPort audio interface verification"
+msgstr ""
+
+#. steps
+#: ../jobs/audio.txt.in:87
+msgid ""
+" 1. Plug an external DisplayPort device with sound (Use only one "
+"HDMI/DisplayPort/Thunderbolt interface at a time for this test)\n"
+" 2. Commence the test"
+msgstr ""
+
+#. verification
+#: ../jobs/audio.txt.in:90 ../units/dock.pxu:159
+msgid " Did you hear the sound from the DisplayPort device?"
+msgstr ""
+
+#. purpose
+#: ../jobs/audio.txt.in:113
+msgid " Thunderbolt audio interface verification"
+msgstr ""
+
+#. steps
+#: ../jobs/audio.txt.in:115
+msgid ""
+" 1. Plug an external Thunderbolt device with sound (Use only one "
+"HDMI/DisplayPort/Thunderbolt interface at a time for this test)\n"
+" 2. Commence the test"
+msgstr ""
+
+#. verification
+#: ../jobs/audio.txt.in:118
+msgid " Did you hear the sound from the Thunderbolt device?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:138
+msgid ""
+"PURPOSE:\n"
+" This test will check that headphones connector works correctly\n"
+"STEPS:\n"
+" 1. Connect a pair of headphones to your audio device\n"
+" 2. Commence the test to play a sound to your audio device\n"
+"VERIFICATION:\n"
+" Did you hear a sound through the headphones and did the sound play "
+"without any distortion, clicks or other strange noises from your headphones?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:164
+msgid ""
+"PURPOSE:\n"
+" This test will check that recording sound using the onboard microphone "
+"works correctly\n"
+"STEPS:\n"
+" 1. Disconnect any external microphones that you have plugged in\n"
+" 2. Click \"Test\", then speak into your internal microphone\n"
+" 3. After a few seconds, your speech will be played back to you.\n"
+"VERIFICATION:\n"
+" Did you hear your speech played back?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:191
+msgid ""
+"PURPOSE:\n"
+" This test will check that recording sound using an external microphone "
+"works correctly\n"
+"STEPS:\n"
+" 1. Connect a microphone to your microphone port\n"
+" 2. Click \"Test\", then speak into the external microphone\n"
+" 3. After a few seconds, your speech will be played back to you\n"
+"VERIFICATION:\n"
+" Did you hear your speech played back?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:217
+msgid ""
+"PURPOSE:\n"
+" This test will check that a USB audio device works correctly\n"
+"STEPS:\n"
+" 1. Connect a USB audio device to your system\n"
+" 2. Click \"Test\", then speak into the microphone\n"
+" 3. After a few seconds, your speech will be played back to you\n"
+"VERIFICATION:\n"
+" Did you hear your speech played back through the USB headphones?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:240
+msgid ""
+"Play back a sound on the default output and listen for it on the default "
+"input."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:249 ../units/dock.pxu:221
+msgid ""
+"Collect audio-related system information. This data can be used to simulate "
+"this computer's audio subsystem and perform more detailed tests under a "
+"controlled environment."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:260 ../units/dock.pxu:232
+msgid "Attaches the audio hardware data collection log to the results."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:268
+msgid ""
+"PURPOSE:\n"
+" Check that the various audio channels are working properly\n"
+"STEPS:\n"
+" 1. Commence the test\n"
+"VERIFICATION:\n"
+" You should clearly hear a voice from the different audio channels"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:296
+msgid ""
+"PURPOSE:\n"
+" Check that external line out connection works correctly\n"
+"STEPS:\n"
+" 1. Insert cable to speakers (with built-in amplifiers) on the line out "
+"port\n"
+" 2. Open system sound preferences, 'Output' tab, select 'Line-out' on "
+"the connector list. Commence the test\n"
+" 3. On the system sound preferences, select 'Internal Audio' on the "
+"device list and click 'Test Speakers' to check left and right channel\n"
+"VERIFICATION:\n"
+" 1. Do you hear a sound in the speakers? The internal speakers should "
+"*not* be muted automatically\n"
+" 2. Do you hear the sound coming out on the corresponding channel?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:323
+msgid ""
+"PURPOSE:\n"
+" Check that external line in connection works correctly\n"
+"STEPS:\n"
+" 1. Use a cable to connect the line in port to an external line out "
+"source.\n"
+" 2. Open system sound preferences, 'Input' tab, select 'Line-in' on the "
+"connector list. Commence the test\n"
+" 3. After a few seconds, your recording will be played back to you.\n"
+"VERIFICATION:\n"
+" Did you hear your recording?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:341
+msgid ""
+"PURPOSE:\n"
+" Check that system detects speakers or headphones being plugged in\n"
+"STEPS:\n"
+" 1. Prepare a pair of headphones or speakers with a standard 3.5mm jack\n"
+" 2. Locate the speaker / headphone jack on the device under test\n"
+" 3. Run the test (you have 30 seconds from now on)\n"
+" 4. Plug headphones or speakers into the appropriate jack\n"
+" 5. Unplug the device for subsequent tests.\n"
+"VERIFICATION:\n"
+" Verification is automatic, no action is required.\n"
+" The test times out after 30 seconds (and fails in that case)."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:362
+msgid ""
+"PURPOSE:\n"
+" Check that system detects a microphone being plugged in\n"
+"STEPS:\n"
+" 1. Prepare a microphone with a standard 3.5mm jack\n"
+" 2. Locate the microphone jack on the device under test.\n"
+" Keep in mind that it may be shared with the headphone jack.\n"
+" 3. Run the test (you have 30 seconds from now on)\n"
+" 4. Plug the microphone into the appropriate jack\n"
+" 5. Unplug the device for subsequent tests.\n"
+"VERIFICATION:\n"
+" Verification is automatic, no action is required.\n"
+" The test times out after 30 seconds (and fails in that case)."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:393
+msgid ""
+"PURPOSE:\n"
+" Check that balance control works correctly on internal speakers\n"
+"STEPS:\n"
+" 1. Check that moving the balance slider from left to right works "
+"smoothly\n"
+" 2. Commence the test to play an audio tone for 10 seconds.\n"
+" 3. Move the balance slider from left to right and back.\n"
+" 4. Check that actual speaker audio balance follows your setting.\n"
+"VERIFICATION:\n"
+" Does the slider move smoothly, as well as being followed by the setting "
+"by the actual audio output?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:421
+msgid ""
+"PURPOSE:\n"
+" Check that balance control works correctly on external headphone\n"
+"STEPS:\n"
+" 1. Check that moving the balance slider from left to right works "
+"smoothly\n"
+" 2. Commence the test to play an audio tone for 10 seconds.\n"
+" 3. Move the balance slider from left to right and back.\n"
+" 4. Check that actual headphone audio balance follows your setting.\n"
+"VERIFICATION:\n"
+" Does the slider move smoothly, as well as being followed by the setting "
+"by the actual audio output?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:441
+msgid "Test to detect audio devices after suspending 30 times."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:460
+msgid ""
+"PURPOSE:\n"
+" This test will check that internal speakers work correctly after "
+"suspending 30 times.\n"
+"STEPS:\n"
+" 1. Make sure that no external speakers or headphones are connected\n"
+" When testing a desktop, you can skip this test if there is no\n"
+" internal speaker, we will test the external output later\n"
+" 2. Commence the test to play a brief tone on your audio device\n"
+"VERIFICATION:\n"
+" Did you hear a tone?"
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:485
+msgid ""
+"Play back a sound on the default output and listen for it on the default "
+"input, after suspending 30 times."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:498
+msgid ""
+"This test will verify that the volume levels are at an acceptable level on "
+"your local system. The test will validate that the volume is greater than "
+"or equal to minvol and less than or equal to maxvol for all sources (inputs) "
+"and sinks (outputs) recognized by PulseAudio. It will also validate that "
+"the active source and sink are not muted. You should not manually adjust "
+"the volume or mute before running this test."
+msgstr ""
+
+#. description
+#: ../jobs/audio.txt.in:514
+msgid "Record mixer settings after suspending 30 times."
+msgstr ""
+
+#. summary
+#: ../jobs/benchmarks.txt.in:11
+msgid "Raw read timing benchmark of {name} using hdparm"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:12
+msgid ""
+"This test runs hdparm timing of device reads as a benchmark for {name}"
+msgstr ""
+
+#. summary
+#: ../jobs/benchmarks.txt.in:24
+msgid "Cached read timing benchmark of {name} using hdparm."
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:25
+msgid "This test runs hdparm timing of cache reads as a benchmark for {name}"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:34
+msgid "Run gtkperf to make sure that GTK based test cases work"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:43
+msgid "Run Render-Bench XRender/Imlib2 benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:51
+msgid "Run Qgears2 XRender Extension gearsfancy benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:59
+msgid "Run Qgears2 XRender Extension image scaling benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:67
+msgid "Run Qgears2 OpenGL gearsfancy benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:75
+msgid "Run Qgears2 OpenGL image scaling benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:85
+msgid "Run GLmark2-ES2 benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:96
+msgid "Run GLmark2 benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:103
+msgid "Run Unigine Santuary benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:110
+msgid "Run Unigine Tropics benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:117
+msgid "Run Unigine Heaven benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:124
+msgid "Run Lightsmark benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:132
+msgid "Run Cachebench Read benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:140
+msgid "Run Cachebench Write benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:148
+msgid "Run Cachebench Read / Modify / Write benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:156
+msgid "Run Stream Copy benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:164
+msgid "Run Stream Scale benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:172
+msgid "Run Stream Add benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:180
+msgid "Run Stream Triad benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:188
+msgid "Run Network Loopback benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:195
+msgid "Check the time needed to reconnect to a WIFI access point"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:203
+msgid "Run Encode MP3 benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:211
+msgid "Run x264 H.264/AVC encoder benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:218
+msgid "Run GnuPG benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:226
+msgid "Run Compress PBZIP2 benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:234
+msgid "Run Compress 7ZIP benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:242
+msgid "Run N-Queens benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:250
+msgid "Run Himeno benchmark"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:258
+msgid "CPU utilization on an idle system."
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:266
+msgid "Disk utilization on an idle system."
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:276
+msgid ""
+"Run a stress test based on FurMark (OpenGL 2.1 or 3.2) Fullscreen 1920x1080 "
+"no antialiasing"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:288
+msgid ""
+"Run a stress test based on FurMark (OpenGL 2.1 or 3.2) Windowed 1024x640 no "
+"antialiasing"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:300
+msgid ""
+"Run GiMark, a geometry instancing test (OpenGL 3.3) Fullscreen 1920x1080 no "
+"antialiasing"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:312
+msgid ""
+"Run GiMark, a geometry instancing test (OpenGL 3.3) Windowed 1024x640 no "
+"antialiasing"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:324
+msgid ""
+"Run a tessellation test based on TessMark (OpenGL 4.0) Fullscreen 1920x1080 "
+"no antialiasing"
+msgstr ""
+
+#. description
+#: ../jobs/benchmarks.txt.in:335
+msgid ""
+"Run a tessellation test based on TessMark (OpenGL 4.0) Windowed 1024x640 no "
+"antialiasing"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:23
+msgid ""
+"Automated test to store bluetooth device information in checkbox report"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:31
+msgid ""
+"PURPOSE:\n"
+" This test will check that bluetooth connection works correctly\n"
+"STEPS:\n"
+" 1. Enable bluetooth on any mobile device (PDA, smartphone, etc.)\n"
+" 2. Click on the bluetooth icon in the menu bar\n"
+" 3. Select 'Setup new device'\n"
+" 4. Look for the device in the list and select it\n"
+" 5. In the device write the PIN code automatically chosen by the wizard\n"
+" 6. The device should pair with the computer\n"
+" 7. Right-click on the bluetooth icon and select browse files\n"
+" 8. Authorize the computer to browse the files in the device if needed\n"
+" 9. You should be able to browse the files\n"
+"VERIFICATION:\n"
+" Did all the steps work?"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:52
+msgid ""
+"PURPOSE:\n"
+" This test will check that you can transfer information through a "
+"bluetooth connection\n"
+"STEPS:\n"
+" 1. Make sure that you're able to browse the files in your mobile device\n"
+" 2. Copy a file from the computer to the mobile device\n"
+" 3. Copy a file from the mobile device to the computer\n"
+"VERIFICATION:\n"
+" Were all files copied correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:77
+msgid ""
+"PURPOSE:\n"
+" This test will check the High Fidelity Playback (A2DP) capability of "
+"your Bluetooth device,\n"
+" to see if you can hear audio from it.\n"
+"STEPS:\n"
+" 1. Enable and pair the bluetooth headset\n"
+" 2. Click \"Test\" to play a brief tone on your Bluetooth device, if it "
+"failed to set the Mode to A2DP,\n"
+" please select the device and change it manually in the \"Sound "
+"Settings\"\n"
+"VERIFICATION:\n"
+" Did you hear the tone?"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:94
+msgid ""
+"PURPOSE:\n"
+" This test will check the Telephony Duplex capability of your bluetooth "
+"device,\n"
+" to see if you can record and hear audio from it simultaneously.\n"
+"STEPS:\n"
+" 1. Enable the bluetooth headset\n"
+" 2. Click on the bluetooth icon in the menu bar\n"
+" 3. Select \"Setup new device\"\n"
+" 4. Look for the device in the list and pair it\n"
+" 5. Click the sound icon\n"
+" 6. Click \"Sound Settings\"\n"
+" 7. Select device and ensure Mode is set to \"Telephony Duplex "
+"(HSP/HFP)\"\n"
+" 8. Click \"Test\" to record and play for five seconds in the bluetooth "
+"device\n"
+"VERIFICATION:\n"
+" Did you hear the sound you recorded in the bluetooth with a slight "
+"intended delay?"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:116
+msgid ""
+"PURPOSE:\n"
+" This test will check that you can use a BlueTooth HID device\n"
+"STEPS:\n"
+" 1. Enable either a BT mouse or keyboard\n"
+" 2. Click on the bluetooth icon in the menu bar\n"
+" 3. Select 'Setup new device'\n"
+" 4. Look for the device in the list and select it\n"
+" 5. For mice, perform actions such as moving the pointer, right and left "
+"button clicks and double clicks\n"
+" 6. For keyboards, commence the test to launch a small tool. Enter some "
+"text into the tool and close it.\n"
+"VERIFICATION:\n"
+" Did the device work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/bluetooth.txt.in:154
+msgid ""
+"This is an automated Bluetooth file transfer test. It sends a large file to "
+"the device specified by the BTDEVADDR environment variable, then retrieves "
+"it again using Bluetooth and verifies the checksum to ensure the transfer "
+"didn't corrupt the file."
+msgstr ""
+
+#. description
+#: ../jobs/camera.txt.in:8
+msgid "This Automated test attempts to detect a camera."
+msgstr ""
+
+#. description
+#: ../jobs/camera.txt.in:18
+msgid ""
+"PURPOSE:\n"
+" This test will check that the built-in camera works\n"
+"STEPS:\n"
+" 1. Click on Test to display a video capture from the camera for ten "
+"seconds.\n"
+"VERIFICATION:\n"
+" Did you see the video capture?"
+msgstr ""
+
+#. description
+#: ../jobs/camera.txt.in:37
+msgid ""
+"PURPOSE:\n"
+" This test will check that the built-in camera works\n"
+"STEPS:\n"
+" 1. Click on Test to display a still image from the camera for ten "
+"seconds.\n"
+"VERIFICATION:\n"
+" Did you see the image?"
+msgstr ""
+
+#. description
+#: ../jobs/camera.txt.in:54
+msgid ""
+" Takes multiple pictures based on the resolutions supported by the camera "
+"and\n"
+" validates their size and that they are of a valid format."
+msgstr ""
+
+#. description
+#: ../jobs/codecs.txt.in:9
+msgid ""
+"PURPOSE:\n"
+" This test will verify your system's ability to play Ogg Vorbis audio "
+"files.\n"
+"STEPS:\n"
+" 1. Click Test to play an Ogg Vorbis file (.ogg)\n"
+" 2. Please close the player to proceed.\n"
+"VERIFICATION:\n"
+" Did the sample play correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/codecs.txt.in:26
+msgid ""
+"PURPOSE:\n"
+" This test will verify your system's ability to play Wave Audio files.\n"
+"STEPS:\n"
+" 1. Select Test to play a Wave Audio format file (.wav)\n"
+" 2. Please close the player to proceed.\n"
+"VERIFICATION:\n"
+" Did the sample play correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:10
+msgid ""
+"Test the CPU scaling capabilities using Firmware Test Suite (fwts cpufreq)."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:19
+msgid ""
+"Attaches the log generated by cpu/scaling_test to the results submission."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:30
+msgid ""
+"Test that the CPU can run at its max frequency using Firmware Test Suite "
+"(fwts cpufreq)."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:39
+msgid ""
+"Attaches the log generated by cpu/maxfreq_test to the results submission."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:47
+msgid "Tests the CPU for clock jitter."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:56
+msgid "Test offlining of each CPU core in a multicore system."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:65
+msgid "This test checks cpu topology for accuracy between proc and sysfs."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:74
+msgid "This test checks that CPU frequency governors are obeyed when set."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:83
+msgid "Validate that the Vector Floating Point Unit is running on ARM device"
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:92
+msgid "Run Firmware Test Suite (fwts) cstates tests."
+msgstr ""
+
+#. description
+#: ../jobs/cpu.txt.in:104 ../jobs/firmware.txt.in:57
+msgid "Attaches the FWTS desktop diagnosis results log to the submission"
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:6
+msgid "Test if the atd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:13
+msgid "Test if the cron daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:20
+msgid "Test if the cupsd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:27
+msgid "Test if the getty daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:34
+msgid "Test if the init daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:41
+msgid "Test if the klogd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:48
+msgid "Test if the nmbd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:55
+msgid "Test if the smbd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:62
+msgid "Test if the syslogd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:70
+msgid "Test if the udevd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/daemons.txt.in:77
+msgid "Test if the winbindd daemon is running when the package is installed."
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:7
+msgid ""
+"Displays information about each disk detected on the system under test."
+msgstr ""
+
+#. summary
+#: ../jobs/disk.txt.in:21
+msgid "Disk statistics for /dev/{name}"
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:22
+msgid ""
+"This test checks disk stats, generates some activity and rechecks stats to "
+"verify they've changed. It also verifies that disks appear in the various "
+"files they're supposed to."
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:22
+msgid "This test will inspect the following disk:"
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:22
+msgid ""
+" product name: {product}\n"
+" sysfs path: {path}\n"
+" device node path: /dev/{name}"
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:45
+msgid ""
+"This test checks {name} disk stats, generates some activity and rechecks "
+"stats to verify they've changed. It also verifies that disks appear in the "
+"various files they're supposed to."
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:59
+msgid ""
+"This tests the SMART capabilities for {product} (Note that this test will "
+"not work against hardware RAID)"
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:89
+msgid "Disk I/O stress test for {product}"
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:101
+msgid ""
+"Some new hard drives include a feature that parks the drive heads after a "
+"short period of inactivity. This is a power-saving feature, but it can have "
+"a bad interaction with the operating system that results in the drive "
+"constantly parked then activated. This produces excess wear on the drive, "
+"potentially leading to early failures."
+msgstr ""
+
+#. description
+#: ../jobs/disk.txt.in:114
+msgid ""
+"PURPOSE:\n"
+" This test checks that a systems drive protection mechanism works properly.\n"
+"STEPS:\n"
+" 1. Click on Test\n"
+" 2. Move the system under test around, ensuring it is raised and lowered at "
+"some point.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/esata.txt.in:5
+msgid ""
+"PURPOSE:\n"
+" This test will check the system can detect the insertion of an eSATA "
+"HDD\n"
+"STEPS:\n"
+" 1. Click 'Test' to begin the test. This test will\n"
+" timeout and fail if the insertion has not been detected within 20 "
+"seconds.\n"
+" 2. Plug an eSATA HDD into an available eSATA port.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. description
+#: ../jobs/esata.txt.in:22 ../units/dock.pxu:942
+msgid ""
+"This is an automated test which performs read/write operations on an "
+"attached eSATA HDD"
+msgstr ""
+
+#. description
+#: ../jobs/esata.txt.in:31
+msgid ""
+"PURPOSE:\n"
+" This test will check the system can detect the removal of an eSATA HDD\n"
+"STEPS:\n"
+" 1. Click 'Test' to begin the test. This test will timeout and fail if\n"
+" the removal has not been detected within 20 seconds.\n"
+" 2. Remove the previously attached eSATA HDD from the eSATA port.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:14
+msgid ""
+"Test to detect and return information about available network controllers on "
+"the system under test."
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:26
+msgid ""
+"Gathers some info on the current state of your network devices. If no "
+"devices are found, the test will exit with an error."
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:35
+msgid ""
+"PURPOSE:\n"
+" This test will check your wired connection\n"
+"STEPS:\n"
+" 1. Click on the Network icon in the top panel\n"
+" 2. Select a network below the \"Wired network\" section\n"
+" 3. Click \"Test\" to verify that it's possible to establish a HTTP "
+"connection\n"
+"VERIFICATION:\n"
+" Did a notification show and was the connection correctly established?"
+msgstr ""
+
+#. summary
+#: ../jobs/ethernet.txt.in:51
+msgid "Multi-NIC Iperf testing for NIC {interface}"
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:61
+msgid ""
+"This test uses iperf to ensure network devices pass data at an acceptable "
+"minimum percentage of advertized speed."
+msgstr ""
+
+#. summary
+#: ../jobs/ethernet.txt.in:71
+msgid "Multi-NIC Iperf3 testing for NIC {interface}"
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:81
+msgid ""
+"This test uses iperf3 to ensure network devices pass data at an acceptable "
+"minimum percentage of advertized speed."
+msgstr ""
+
+#. summary
+#: ../jobs/ethernet.txt.in:91
+msgid "ethtool check for NIC {interface}"
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:97
+msgid ""
+"This test executes ethtool requests against ethernet device {__index__} "
+"({interface})."
+msgstr ""
+
+#. summary
+#: ../jobs/ethernet.txt.in:106
+msgid "Maximum bandwidth test of device {__index__} ({interface})"
+msgstr ""
+
+#. purpose
+#: ../jobs/ethernet.txt.in:115
+msgid ""
+"User verification of whether the observed transfer throughput is acceptable "
+"for the type and maximum speed of each ethernet interface."
+msgstr ""
+
+#. steps
+#: ../jobs/ethernet.txt.in:118 ../jobs/mobilebroadband.txt.in:103
+#: ../jobs/wireless.txt.in:691
+msgid ""
+"1. Click \"Test\". 2. Read the network test summary and confirm that the "
+"throughput is acceptable. 3. If needed, click \"Test\" again to repeat the "
+"transfer test."
+msgstr ""
+
+#. verification
+#: ../jobs/ethernet.txt.in:122 ../jobs/mobilebroadband.txt.in:107
+#: ../jobs/wireless.txt.in:695
+msgid ""
+"Was the reported throughput acceptable for the type and maximum speed of "
+"this interface?"
+msgstr ""
+
+#. summary
+#: ../jobs/ethernet.txt.in:131
+msgid ""
+"Stress and performance test of ethernet device {__index__} ({interface})"
+msgstr ""
+
+#. description
+#: ../jobs/ethernet.txt.in:137
+msgid ""
+"Automated test that tests performance of ethernet device {__index__} "
+"({interface})."
+msgstr ""
+
+#. description
+#: ../jobs/expresscard.txt.in:4
+msgid ""
+"PURPOSE:\n"
+" This will verify that an ExpressCard slot can detect inserted devices.\n"
+"STEPS:\n"
+" Skip this test if you do not have an ExpressCard slot.\n"
+" 1. Plug an ExpressCard device into the ExpressCard slot\n"
+"VERIFICATION:\n"
+" Was the device correctly detected?"
+msgstr ""
+
+#. description
+#: ../jobs/fingerprint.txt.in:4
+msgid ""
+"PURPOSE:\n"
+" This test will verify that a fingerprint reader will work properly for "
+"logging into your system. This test case assumes that there's a testing "
+"account from which test cases are run and a personal account that the tester "
+"uses to verify the fingerprint reader\n"
+"STEPS:\n"
+" 1. Click on the User indicator on the left side of the panel (your user "
+"name).\n"
+" 2. Select \"Switch User Account\"\n"
+" 3. On the LightDM screen select your username.\n"
+" 4. Use the fingerprint reader to login.\n"
+" 5. Click on the user switcher applet.\n"
+" 6. Select the testing account to continue running tests.\n"
+"VERIFICATION:\n"
+" Did the authentication procedure work correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/fingerprint.txt.in:20
+msgid ""
+"PURPOSE:\n"
+" This test will verify that a fingerprint reader can be used to unlock a "
+"locked system.\n"
+"STEPS:\n"
+" 1. Click on the Session indicator (Cog icon on the Left side of the "
+"panel) .\n"
+" 2. Select 'Lock screen'.\n"
+" 3. Press any key or move the mouse.\n"
+" 4. A window should appear that provides the ability to unlock either "
+"typing your password or using fingerprint authentication.\n"
+" 5. Use the fingerprint reader to unlock.\n"
+" 6. Your screen should be unlocked.\n"
+"VERIFICATION:\n"
+" Did the authentication procedure work correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/firewire.txt.in:6
+msgid ""
+"PURPOSE:\n"
+" This test will check the system can detect the insertion of a FireWire "
+"HDD\n"
+"STEPS:\n"
+" 1. Click 'Test' to begin the test. This test will\n"
+" timeout and fail if the insertion has not been detected within 20 "
+"seconds.\n"
+" 2. Plug a FireWire HDD into an available FireWire port.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. description
+#: ../jobs/firewire.txt.in:24 ../units/dock.pxu:897
+msgid ""
+"This is an automated test which performs read/write operations on an "
+"attached FireWire HDD"
+msgstr ""
+
+#. description
+#: ../jobs/firewire.txt.in:34
+msgid ""
+"PURPOSE:\n"
+" This test will check the system can detect the removal of a FireWire "
+"HDD\n"
+"STEPS:\n"
+" 1. Click 'Test' to begin the test. This test will timeout and fail if\n"
+" the removal has not been detected within 20 seconds.\n"
+" 2. Remove the previously attached FireWire HDD from the FireWire port.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:11
+msgid "Run {name} test from Firmware Test Suite."
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:23
+msgid "Attach log for FWTS {name} test."
+msgstr ""
+
+#. description
+#: ../jobs/firmware.txt.in:31
+msgid ""
+"Run Firmware Test Suite (fwts) QA-concerned desktop-specific diagnosis tests."
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:33
+msgid "Run FWTS QA-concerned desktop-specific diagnosis tests."
+msgstr ""
+
+#. description
+#: ../jobs/firmware.txt.in:44
+msgid ""
+"Run Firmware Test Suite (fwts) HWE-concerned desktop-specific diagnosis "
+"tests."
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:46
+msgid "Run FWTS HWE-concerned desktop-specific diagnosis tests."
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:58
+msgid "Attach FWTS desktop diagnosis log to submission"
+msgstr ""
+
+#. description
+#: ../jobs/firmware.txt.in:66
+msgid ""
+"Attaches the FWTS desktop diagnosis results log to the submission (to HWE)"
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:67
+msgid "Attach FWTS desktop diagnosis log to submission (to HWE)"
+msgstr ""
+
+#. summary
+#: ../jobs/firmware.txt.in:72
+msgid "No _REV interface in ACPI [DS]SDT tables"
+msgstr ""
+
+#. description
+#: ../jobs/firmware.txt.in:76
+msgid ""
+"This Automated test checks misuse of the _REV interface in ACPI DSDT and "
+"SSDT tables"
+msgstr ""
+
+#. description
+#: ../jobs/floppy.txt.in:8
+msgid "Floppy test for {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:8
+msgid ""
+"Parses Xorg.0.Log and discovers the running X driver and version for the "
+"{vendor} {product} graphics card"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:9
+msgid "Test X driver/version for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:17
+msgid "Test to output the Xorg version"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:18
+msgid "Test Xorg version"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:26
+msgid "Test changing resolution for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:27
+msgid ""
+"PURPOSE:\n"
+" This test will verify that the GUI is usable after manually changing "
+"resolution on the {vendor} {product} graphics card.\n"
+"STEPS:\n"
+" 1. Select the {vendor} {product} graphics card (a reboot may be "
+"necessary)\n"
+" 2. Open the Displays application\n"
+" 3. Select a new resolution from the dropdown list\n"
+" 4. Click on Apply\n"
+" 5. Select the original resolution from the dropdown list\n"
+" 6. Click on Apply\n"
+"VERIFICATION:\n"
+" Did the resolution on the {vendor} {product} graphics card change as "
+"expected?"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:49
+msgid "Test that the X process is running."
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:57
+msgid "Test that the X is not running in failsafe mode."
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:58
+msgid "Test that X is not in failsafe mode."
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:71
+msgid ""
+"PURPOSE:\n"
+" This test will verify the default display resolution on the {vendor} "
+"{product} graphics card.\n"
+"STEPS:\n"
+" 1. Click \"Test\".\n"
+" 2. Confirm that the resolution shown in the text window is acceptable "
+"for your display.\n"
+"VERIFICATION:\n"
+" Is the resolution shown acceptable for your display on {vendor} "
+"{product} graphics card?"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:90
+msgid "Test default resolution for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:91
+msgid ""
+"PURPOSE:\n"
+" This test will verify the default display resolution on the {vendor} "
+"{product} graphics card\n"
+"STEPS:\n"
+" 1. Click on Test to display the screen resolution overlay for 5 "
+"seconds.\n"
+"VERIFICATION:\n"
+" Is this acceptable for your display on the {vendor} {product} graphics "
+"card?"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:108
+msgid "Test that {vendor} {product} meets minimum resolution requirement"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:109
+msgid ""
+"Ensure the current resolution meets or exceeds the recommended minimum "
+"resolution (800x600) on the {vendor} {product} graphics card. See here for "
+"details: https://help.ubuntu.com/community/Installation/SystemRequirements"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:128
+msgid "Test maximum supported resolution for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:129
+msgid ""
+"PURPOSE:\n"
+" This test will verify the maximum supported resolution on the {vendor} "
+"{product} graphics card.\n"
+"STEPS:\n"
+" 1. Select the {vendor} {product} graphics card (a reboot may be "
+"necessary)\n"
+" 2. Consult the system's specifications and locate the screen's maximum "
+"supported resolution.\n"
+" 3. Click on Test to display the maximum resolution that can be used by "
+"Ubuntu on the current display.\n"
+"VERIFICATION:\n"
+" Is this the maximum resolution for the display connected to the {vendor} "
+"{product} graphics card?"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:146
+msgid ""
+"Collect info on graphics modes (screen resolution and refresh rate) for "
+"{vendor} {product}"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:147
+msgid "Test graphic modes info for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:156
+msgid "Collect info on color depth and pixel format for {vendor} {product}"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:157
+msgid "Test color depth info for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:165
+msgid "Collect info on fresh rate for {vendor} {product}."
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:166
+msgid "Test refresh rate for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:174
+msgid "Collect info on graphic memory for {vendor} {product}."
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:175
+msgid "Test graphic memory info for {vendor} {product}."
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:186
+msgid "Test that video can be displayed with {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:187
+msgid ""
+"PURPOSE:\n"
+" This test will test the default display with a sample video\n"
+"STEPS:\n"
+" 1. Click \"Test\" to display a video test.\n"
+"VERIFICATION:\n"
+" Do you see color bars and static?"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:200
+msgid "Check that VESA drivers are not in use"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:201
+msgid "Test that VESA drivers are not in use"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:212
+msgid "Test resolution cycling for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:213
+msgid ""
+"PURPOSE:\n"
+" This test cycles through the detected video modes for the {vendor} "
+"{product} graphics card\n"
+"STEPS:\n"
+" 1. Click \"Test\" to start cycling through the video modes\n"
+"VERIFICATION:\n"
+" Did the screen appear to be working for each mode?"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:229
+msgid "Test rotation for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:230
+msgid ""
+"PURPOSE:\n"
+" This test will test display rotation on the {vendor} {product} graphics "
+"card\n"
+"STEPS:\n"
+" 1. Click \"Test\" to test display rotation. The display will be rotated "
+"every 4 seconds.\n"
+" 2. Check if all rotations (normal right inverted left) took place "
+"without permanent screen corruption\n"
+"VERIFICATION:\n"
+" Did the display rotation take place without without permanent screen "
+"corruption?"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:247
+msgid "Check that {vendor} {product} hardware is able to run compiz"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:248
+msgid "Test Compiz support for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:258
+msgid "Check that {vendor} {product} hardware is able to run Unity 3D"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:259
+msgid "Test Unity 3D support for {vendor} {product}"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:268
+msgid "Test that glxgears works for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:269
+msgid ""
+"PURPOSE:\n"
+" This test tests the basic 3D capabilities of your {vendor} {product} "
+"video card\n"
+"STEPS:\n"
+" 1. Click \"Test\" to execute an OpenGL demo. Press ESC at any time to "
+"close.\n"
+" 2. Verify that the animation is not jerky or slow.\n"
+"VERIFICATION:\n"
+" 1. Did the 3d animation appear?\n"
+" 2. Was the animation free from slowness/jerkiness?"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:287
+msgid ""
+"Open and close a 3D window multiple times on the {vendor} {product} video "
+"card"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:288
+msgid "Test 3D window open/close for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:298
+msgid ""
+"Open, suspend resume and close a 3D window multiple times on the {vendor} "
+"{product} video card"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:299
+msgid "Test a 3D window with suspend/resume for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:309
+msgid ""
+"Open and close 4 3D windows multiple times on the {vendor} {product} video "
+"card"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:310
+msgid "Test Multi 3D window open/close for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:322
+msgid ""
+"Move a 3D window around the screen on the {vendor} {product} video card"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:323
+msgid "Test 3D window movement for {vendor} {product}"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:332
+msgid "Test grabbing a screenshot for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:333
+msgid ""
+"PURPOSE:\n"
+" Take a screengrab of the current screen (logged on Unity desktop) as "
+"produced by the {vendor} {product} graphics card\n"
+"STEPS:\n"
+" 1. Take picture using USB webcam\n"
+"VERIFICATION:\n"
+" Review attachment manually later"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:348
+msgid ""
+"Attaches the screenshot captured in graphics/screenshot for the {vendor} "
+"{product} graphics card."
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:349
+msgid "Attach results of screenshot test for {vendor} {product}"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:365
+msgid "Test FSV screenshot for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:366
+msgid ""
+"PURPOSE:\n"
+" Take a screengrab of the current screen during fullscreen video playback "
+"using the {vendor} {product} graphics card\n"
+"STEPS:\n"
+" 1. Start a fullscreen video playback\n"
+" 2. Take picture using USB webcam after a few seconds\n"
+"VERIFICATION:\n"
+" Review attachment manually later"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:380
+msgid "Test GPU switching for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:381
+msgid ""
+"PURPOSE:\n"
+" Manually switch to the {vendor} {product} card.\n"
+"STEPS:\n"
+" 1. If your system is already running with the {vendor} {product} card, "
+"then please mark this test as \"passed\" and proceed.\n"
+" 2. Using the appropriate tool (either NVidia settings or AMD Control "
+"Center), switch your system to use the {vendor} {product} graphics card. "
+"This will require restarting your session.\n"
+" 3. Once the session restarts, please restart this testing program and "
+"select \"continue\" when prompted for a resume action.\n"
+" 4. Don't answer the verification question until the system has restarted "
+"with the {vendor} {product} card enabled.\n"
+"VERIFICATION:\n"
+" Is the system using the {vendor} {product} card now?"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:399
+msgid "Attach results of FSV screenshot test for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:400
+msgid ""
+"Attaches the screenshot captured in graphics/screenshot_fullscreen_video for "
+"the {vendor} {product} graphics card"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:405
+msgid "Obtains a simple screen capture"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:409
+msgid "Obtains a simple screen capture using gnome-screenshot if present"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:414
+msgid "Attaches a simple screen capture"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:418
+msgid "Attaches the simple screen capture file"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:425
+msgid "Obtains a simple screen capture of {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:429
+msgid ""
+"Obtains a simple screen capture of {vendor} {product} using gnome-screenshot "
+"if present"
+msgstr ""
+
+#. summary
+#: ../jobs/graphics.txt.in:437
+msgid "Attaches a simple screen capture of {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/graphics.txt.in:440
+msgid "Attaches the simple screen capture file of {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/hibernate.txt.in:18
+msgid ""
+"PURPOSE:\n"
+" This test will check to make sure your system can successfully hibernate "
+"(if supported)\n"
+"STEPS:\n"
+" 1. Click on Test\n"
+" 2. The system will hibernate and should wake itself within 5 minutes\n"
+" 3. If your system does not wake itself after 5 minutes, please press the "
+"power button to wake the system manually\n"
+" 4. If the system fails to resume from hibernate, please restart System "
+"Testing and mark this test as Failed\n"
+"VERIFICATION:\n"
+" Did the system successfully hibernate and did it work properly after "
+"waking up?"
+msgstr ""
+
+#. purpose
+#: ../jobs/hibernate.txt.in:48
+msgid ""
+" This test will check to make sure your system can successfully hibernate "
+"(if supported)"
+msgstr ""
+
+#. steps
+#: ../jobs/hibernate.txt.in:50
+msgid ""
+" 1. Click on Test\n"
+" 2. The system will hibernate and should wake itself within 5 minutes\n"
+" 3. If your system does not wake itself after 5 minutes, please press the "
+"power button to wake the system manually\n"
+" 4. If the system fails to resume from hibernate, please restart System "
+"Testing and mark this test as Failed"
+msgstr ""
+
+#. verification
+#: ../jobs/hibernate.txt.in:55
+msgid ""
+" Did the system successfully hibernate and did it work properly after "
+"waking up?"
+msgstr ""
+
+#. description
+#: ../jobs/hibernate.txt.in:62
+msgid "Automated check of the hibernate log for errors discovered by fwts"
+msgstr ""
+
+#. description
+#: ../jobs/hibernate.txt.in:81
+msgid "attaches log from single hibernate/resume test to results"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:22
+msgid "Attaches a report of installed codecs for Intel HDA"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:29
+msgid "Attaches a report of CPU information"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:30
+msgid "Attach a copy of /proc/cpuinfo"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:37
+msgid "Attaches a copy of /var/log/dmesg to the test results"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:38
+msgid "Attach a copy of /var/log/dmesg"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:45
+msgid "Attaches info on DMI"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:46
+msgid "Attach a copy of /sys/class/dmi/id/*"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:55
+msgid "Attaches dmidecode output"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:56
+msgid "Attach a copy of of the output of dmidecode"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:64
+msgid "Attaches lshw output"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:72
+msgid "Attaches the firmware version"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:79
+msgid "Attaches very verbose lspci output."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:80
+msgid "Attach a list of PCI devices"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:87
+msgid "Attaches very verbose lspci output (with central database Query)."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:90
+msgid "Attach PCI configuration space hex dump"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:95
+msgid ""
+" Attaches a hex dump of the standard part of the PCI configuration\n"
+" space for all PCI devices."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:106
+msgid "Attaches a list of detected USB devices."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:113
+msgid "Attaches info on system memory as seen in /proc/meminfo."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:120
+msgid "Attaches the contents of the various modprobe conf files."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:121
+msgid "Attach the contents of modprobe configuration files"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:126
+msgid "Attach modinfo information"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:135
+msgid "Attaches modinfo information for all currently loaded modules"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:142
+msgid "Attaches the contents of the /etc/modules file."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:143
+msgid "Attach the contents of /etc/modules"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:150
+msgid "Attaches the contents of various sysctl config files."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:151
+msgid "Attach sysctl configuration files."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:156
+msgid "Attaches a report of sysfs attributes."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:164
+msgid "Attach detailed sysfs property output from udev"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:171
+msgid ""
+"Attaches a dump of the udev database showing system hardware information."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:172
+msgid "Attach hardware database (udev)"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:179
+msgid "Attaches the output of udev_resource, for debugging purposes"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:186
+msgid "Attaches disk block devices mount points"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:187
+msgid "Attaches information about disk block devices and their mount points"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:195
+msgid "Attaches a tarball of gcov data if present."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:202
+msgid "Attaches a list of the currently running kernel modules."
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:203
+msgid "Attach a list of currently running kernel modules"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:210
+msgid "Attaches json dumps of installed dkms package information."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:217
+msgid "Attaches the contents of /proc/acpi/sleep if it exists."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:222
+msgid "Bootchart information."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:248
+msgid "Attaches the bootchart png file for bootchart runs"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:257
+msgid "Attaches the bootchart log for bootchart test runs."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:266
+msgid "Attach the installer bootchart tarball if it exists."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:274
+msgid "Attaches the installer debug log if it exists."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:282
+msgid ""
+"Returns the name, driver name and driver version of any touchpad discovered "
+"on the system."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:295
+msgid "Lists the device driver and version for all audio devices."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:306
+msgid "Provides information about network devices"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:313
+msgid "Provides information about wwan/mobile broadband devices"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:319
+msgid "Provides information about displays attached to the system"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:327
+msgid "Attaches information about disk partitions"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:333
+msgid "Attaches the buildstamp identifier for the preinstalled OS"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:334
+msgid "Attach /etc/buildstamp"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:344
+msgid "Check existence of recovery partition"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:355
+msgid "Check the recovery type is dell or not"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:365
+msgid "Attach the recovery partition versions"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:366
+msgid ""
+"Attach the recovery partition version image_version is the preinstalled OS "
+"image version bto_version is only for dell_recovery Example: image_version: "
+"somerville-trusty-amd64-20140620-0 bto_version: A00_dell-bto-trusty-houston-"
+"15-A11-iso-20141203-0.iso"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:382
+msgid "Attach the bto.xml in Dell recovery partition"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:383
+msgid ""
+"bto.xml is basically a Fish manifest The information include:\n"
+" - fish packages\n"
+" - dell recovery stage 2 boot log"
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:394
+msgid ""
+"Attaches the debug log from the virtualization/kvm_check_vm test to the "
+"results submission."
+msgstr ""
+
+#. description
+#: ../jobs/info.txt.in:404
+msgid "Attaches the kernel command line used to boot"
+msgstr ""
+
+#. summary
+#: ../jobs/info.txt.in:405
+msgid "Attach a copy of /proc/cmdline"
+msgstr ""
+
+#. summary
+#: ../jobs/input.txt.in:9
+msgid "Check pointing functionality for {product}"
+msgstr ""
+
+#. purpose
+#: ../jobs/input.txt.in:10
+msgid " This will test your {product} device"
+msgstr ""
+
+#. steps
+#: ../jobs/input.txt.in:12
+msgid " 1. Move the cursor with your {product}."
+msgstr ""
+
+#. verification
+#: ../jobs/input.txt.in:14
+msgid " Did the cursor move?"
+msgstr ""
+
+#. description
+#: ../jobs/input.txt.in:21
+msgid ""
+"PURPOSE:\n"
+" This test will test your pointing device\n"
+"STEPS:\n"
+" 1. Move the cursor using the pointing device or touch the screen.\n"
+" 2. Perform some single/double/right click operations.\n"
+"VERIFICATION:\n"
+" Did the pointing device work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/input.txt.in:36
+msgid ""
+"PURPOSE:\n"
+" This test will test your keyboard\n"
+"STEPS:\n"
+" 1. Click on Test\n"
+" 2. On the open text area, use your keyboard to type something\n"
+"VERIFICATION:\n"
+" Is your keyboard working properly?"
+msgstr ""
+
+#. description
+#: ../jobs/input.txt.in:49
+msgid ""
+"PURPOSE:\n"
+" Manual detection of accelerometer.\n"
+"STEPS:\n"
+" 1. Look at the specifications for your system.\n"
+"VERIFICATION:\n"
+" Is this system supposed to have an accelerometer?"
+msgstr ""
+
+#. description
+#: ../jobs/input.txt.in:64
+msgid ""
+"PURPOSE:\n"
+" This test will test your accelerometer to see if it is detected\n"
+" and operational as a joystick device.\n"
+"STEPS:\n"
+" 1. Click on Test\n"
+" 2. Tilt your hardware in the directions onscreen until the axis "
+"threshold is met.\n"
+"VERIFICATION:\n"
+" Is your accelerometer properly detected? Can you use the device?"
+msgstr ""
+
+#. summary
+#: ../jobs/input.txt.in:82
+msgid "Check button functionality for {product}"
+msgstr ""
+
+#. purpose
+#: ../jobs/input.txt.in:83
+msgid " This will test the buttons of your {product} device"
+msgstr ""
+
+#. steps
+#: ../jobs/input.txt.in:85
+msgid ""
+" 1. Click the left button with your {product}.\n"
+" 2. Click the right button with your {product}.\n"
+" 3. Click the middle button with your {product} (if available).\n"
+" 4. Double-click the left button with your {product}."
+msgstr ""
+
+#. verification
+#: ../jobs/input.txt.in:90
+msgid " Did these buttons work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/install.txt.in:6
+msgid ""
+"Tests to see that apt can access repositories and get updates (does not "
+"install updates). This is done to confirm that you could recover from an "
+"incomplete or broken update."
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:8
+msgid ""
+"PURPOSE:\n"
+" This test will test the screen lock key\n"
+"STEPS:\n"
+" 1. Commence the test. If there is no such key, please skip this test.\n"
+" 2. Press the lock screen button on the keyboard in 30 seconds.\n"
+" 3. If the screen is locked, move the mouse or press any key to activate "
+"the prompt.\n"
+" 4. Input the password to unlock the screen.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:25
+msgid ""
+"PURPOSE:\n"
+" This test will test the brightness key\n"
+"STEPS:\n"
+" 1. Press the brightness buttons on the keyboard\n"
+"VERIFICATION:\n"
+" Did the brightness change following to your key presses?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:41
+msgid ""
+"PURPOSE:\n"
+" This test will test the volume keys of your keyboard\n"
+"STEPS:\n"
+" Skip this test if your computer has no volume keys.\n"
+" 1. Click test to open a window on which to test the volume keys.\n"
+" 2. If all the keys work, the test will be marked as passed.\n"
+"VERIFICATION:\n"
+" Do the keys work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:59
+msgid ""
+"PURPOSE:\n"
+" This test will test the mute key of your keyboard\n"
+"STEPS:\n"
+" 1. Click test to open a window on which to test the mute key.\n"
+" 2. If the key works, the test will pass and the window will close.\n"
+"VERIFICATION:\n"
+" Does the mute key work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:74
+msgid ""
+"PURPOSE:\n"
+" This test will test the sleep key\n"
+"STEPS:\n"
+" 1. Press the sleep key on the keyboard\n"
+" 2. Wake your system up by pressing the power button\n"
+"VERIFICATION:\n"
+" Did the system go to sleep after pressing the sleep key?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:90
+msgid ""
+"PURPOSE:\n"
+" This test will test the battery information key\n"
+"STEPS:\n"
+" Skip this test if you do not have a Battery Button.\n"
+" 1. Click Test to begin\n"
+" 2. Press the Battery Info button (or combo like Fn+F3)\n"
+" 3: Close the Power Statistics tool if it opens\n"
+"VERIFICATION:\n"
+" Did the Battery Info key work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:106
+msgid ""
+"PURPOSE:\n"
+" This test will test the wireless key\n"
+"STEPS:\n"
+" 1. Press the wireless key on the keyboard\n"
+" 2. Check that the wifi LED turns off or changes color\n"
+" 3. Check that wireless is disabled\n"
+" 4. Press the same key again\n"
+" 5. Check that the wifi LED turns on or changes color\n"
+" 6. Check that wireless is enabled\n"
+"VERIFICATION:\n"
+" Did the wireless turn off on the first press and on again on the "
+"second?\n"
+" (NOTE: the LED functionality will be reviewed in a following test. "
+"Please\n"
+" only consider the functionality of the wifi itself here.)"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:129
+msgid ""
+"PURPOSE:\n"
+" This test will test the media keys of your keyboard\n"
+"STEPS:\n"
+" Skip this test if your computer has no media keys.\n"
+" 1. Click test to open a window on which to test the media keys.\n"
+" 2. If all the keys work, the test will be marked as passed.\n"
+"VERIFICATION:\n"
+" Do the keys work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:147
+msgid ""
+"PURPOSE:\n"
+" This test will test the super key of your keyboard\n"
+"STEPS:\n"
+" 1. Click test to open a window on which to test the super key.\n"
+" 2. If the key works, the test will pass and the window will close.\n"
+"VERIFICATION:\n"
+" Does the super key work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:161
+msgid ""
+"PURPOSE:\n"
+" Validate that the External Video hot key is working as expected\n"
+"STEPS:\n"
+" 1. Plug in an external monitor\n"
+" 2. Press the display hot key to change the monitors configuration\n"
+"VERIFICATION:\n"
+" Check that the video signal can be mirrored, extended, displayed on "
+"external or onboard only."
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:175
+msgid ""
+"PURPOSE:\n"
+" Verify touchpad hotkey toggles touchpad functionality on and off\n"
+"STEPS:\n"
+" 1. Verify the touchpad is functional\n"
+" 2. Tap the touchpad toggle hotkey\n"
+" 3. Tap the touchpad toggle hotkey again\n"
+"VERIFICATION:\n"
+" Verify the touchpad has been disabled and re-enabled."
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:190
+msgid ""
+"PURPOSE:\n"
+" Verify that the keyboard backlight toggle key works properly\n"
+"STEPS:\n"
+" 1. Tap the keyboard backlight key\n"
+" 2. Confirm that the keyboard backlight was toggled to the opposite "
+"state\n"
+" 3. Tap the keyboard backlight key again\n"
+" 4. Confirm that the keyboard backlight was toggled to the opposite "
+"state\n"
+"VERIFICATION:\n"
+" Did the keyboard backlight state change on each press?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:218
+msgid ""
+"PURPOSE:\n"
+" This test will test the mute key for your microphone\n"
+"STEPS:\n"
+" 1. Click \"Test\" then speak: \"Imagination is more important than "
+"knowledge\" (or anything else) into your microphone.\n"
+" 2. While you are speaking, please press the mute key for the microphone "
+"to mute it and press it again to unmute.\n"
+" 3. After a few seconds, your speech will be played back to you. If the "
+"key works, your speech should be interrupted for a few seconds.\n"
+"VERIFICATION:\n"
+" Does the microphone mute key work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:233
+msgid ""
+"PURPOSE:\n"
+" This test will test the hibernate key\n"
+"STEPS:\n"
+" 1. Press the hibernate key on the keyboard\n"
+" 2. Check that the system hibernated correctly\n"
+" 3. Wake your system after hibernating by pressing the power button\n"
+"VERIFICATION:\n"
+" Did the system go to hibernate after pressing the hibernate key?"
+msgstr ""
+
+#. description
+#: ../jobs/keys.txt.in:248
+msgid ""
+"PURPOSE:\n"
+" This test will test the keyboard overhead light key or switch\n"
+"STEPS:\n"
+" 1. Press the keyboard overhead light key or swtich on the light\n"
+" 2. Check the the keyboard overhead light turn on correctly\n"
+" 3. Press the key or switch again to toggle off the light\n"
+"VERIFICATION:\n"
+" Did the keyboard overhead light key or switch turns on and off the light?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:5
+msgid ""
+"PURPOSE:\n"
+" Power LED verification\n"
+"STEPS:\n"
+" 1. Power LED should be on while device is switched on\n"
+"VERIFICATION:\n"
+" Does the power LED light as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:18
+msgid ""
+"PURPOSE:\n"
+" Power LED verification\n"
+"STEPS:\n"
+" 1. The Power LED should blink or change color while the system is "
+"suspended\n"
+"VERIFICATION:\n"
+" Did the Power LED blink or change color while the system was suspended "
+"for the previous suspend test?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:31
+msgid ""
+"PURPOSE:\n"
+" Suspend LED verification.\n"
+"STEPS:\n"
+" Skip this test if your system does not have a dedicated Suspend LED.\n"
+" 1. The Suspend LED should blink or change color while the system is\n"
+" suspended\n"
+"VERIFICATION\n"
+" Did the Suspend LED blink or change color while the system was suspended?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:45
+msgid ""
+"PURPOSE:\n"
+" Validate that the battery light shows charging status\n"
+"STEPS:\n"
+" 1. Let system run on battery for a while\n"
+" 2. Plug in AC plug\n"
+"VERIFICATION:\n"
+" Did the battery indicator LED turn orange?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:58
+msgid ""
+"PURPOSE:\n"
+" Validate that the battery LED properly displays charged status\n"
+"STEPS:\n"
+" 1. Let system run on battery for a short time\n"
+" 2. Plug in AC\n"
+" 3. Let system run on AC\n"
+"VERIFICATION:\n"
+" Does the orange battery LED shut off when system is fully charged?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:72
+msgid ""
+"PURPOSE:\n"
+" Validate that the battery LED indicated low power\n"
+"STEPS:\n"
+" 1. Let system run on battery for several hours\n"
+" 2. Monitor battery LED carefully\n"
+"VERIFICATION:\n"
+" Does the LED light orange when battery is low?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:86
+msgid ""
+"PURPOSE:\n"
+" HDD LED verification\n"
+"STEPS:\n"
+" 1. Select \"Test\" to write and read a temporary file for a few seconds\n"
+" 2. HDD LED should light when writing to/reading from HDD\n"
+"VERIFICATION:\n"
+" Did the HDD LED light?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:100
+msgid ""
+"PURPOSE:\n"
+" Numeric keypad LED verification\n"
+"STEPS:\n"
+" 1. Press \"Block Num\" key to toggle numeric keypad LED\n"
+" 2. Click on the \"Test\" button to open a window to verify your typing\n"
+" 3. Type using the numeric keypad both when the LED is on and off\n"
+"VERIFICATION:\n"
+" 1. Numeric keypad LED status should toggle everytime the \"Block Num\" "
+"key is pressed\n"
+" 2. Numbers should only be entered in the keyboard verification window "
+"when the LED is on"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:115
+msgid ""
+"PURPOSE:\n"
+" Block cap keys LED verification\n"
+"STEPS:\n"
+" 1. Press \"Block Cap Keys\" to activate/deactivate cap keys blocking\n"
+" 2. Cap Keys LED should be switched on/off every time the key is pressed\n"
+"VERIFICATION:\n"
+" Did the Cap Keys LED light as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:129
+msgid ""
+"PURPOSE:\n"
+" WLAN LED verification\n"
+"STEPS:\n"
+" 1. During the keys/wireless test you should have observed the\n"
+" wireless LED while turning wireless back on.\n"
+" 2. WLAN LED should light or change color when wireless is turned on\n"
+"VERIFICATION:\n"
+" Did the WLAN LED turn on or change color as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:144
+msgid ""
+"PURPOSE:\n"
+" Validate that WLAN LED shuts off when disabled\n"
+"STEPS:\n"
+" 1. During the keys/wireless test you should have observed the WLAN LED\n"
+" while performing that test after turning wireless off.\n"
+" 2. WLAN LED should turn off or change color when wireless is turned off\n"
+"VERIFICATION:\n"
+" Did the WLAN LED turn off or change color as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:159
+msgid ""
+"PURPOSE:\n"
+" Validate that the Bluetooth LED turns on and off when BT is "
+"enabled/disabled\n"
+"STEPS:\n"
+" 1. Switch bluetooth off from a hardware switch (if present)\n"
+" 2. Switch bluetooth back on\n"
+" 3. Switch bluetooth off from the panel applet\n"
+" 4. Switch bluetooth back on\n"
+"VERIFICATION:\n"
+" Did the bluetooth LED turn off and on twice?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:176
+msgid ""
+"PURPOSE:\n"
+" Camera LED verification\n"
+"STEPS:\n"
+" 1. Select Test to activate camera\n"
+" 2. Camera LED should light for a few seconds\n"
+"VERIFICATION:\n"
+" Did the camera LED light?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:189
+msgid ""
+"PURPOSE:\n"
+" Touchpad LED verification\n"
+"STEPS:\n"
+" 1. Click on the touchpad button or press key combination to "
+"enable/disable touchpad button\n"
+" 2. Slide your finger on the touchpad\n"
+"VERIFICATION:\n"
+" 1. Touchpad LED status should toggle everytime the button is clicked or "
+"the key combination is pressed\n"
+" 2. When the LED is on, the mouse pointer should move on touchpad usage\n"
+" 3. When the LED is off, the mouse pointer should not move on touchpad "
+"usage"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:204
+msgid ""
+"PURPOSE:\n"
+" Wireless (WLAN + Bluetooth) LED verification\n"
+"STEPS:\n"
+" 1. Make sure WLAN connection is established and Bluetooth is enabled.\n"
+" 2. WLAN/Bluetooth LED should light\n"
+" 3. Switch WLAN and Bluetooth off from a hardware switch (if present)\n"
+" 4. Switch them back on\n"
+" 5. Switch WLAN and Bluetooth off from the panel applet\n"
+" 6. Switch them back on\n"
+"VERIFICATION:\n"
+" Did the WLAN/Bluetooth LED light as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:222
+msgid ""
+"PURPOSE:\n"
+" Audio Mute LED verification.\n"
+"STEPS:\n"
+" Skip this test if your system does not have a special Audio Mute LED.\n"
+" 1. Press the Mute key twice and observe the Audio LED to determine if "
+"it\n"
+" either turned off and on or changed colors.\n"
+"VERIFICATION:\n"
+" Did the Audio LED turn on and off or change color as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/led.txt.in:237
+msgid ""
+"PURPOSE:\n"
+" Microphone Mute LED verification.\n"
+"STEPS:\n"
+" Skip this test if your system does not have a special Microphone Mute "
+"LED.\n"
+" 1. Press the Microphone Mute key twice and observe the Microphone LED "
+"to\n"
+" determine if it either turned off and on or changed colors.\n"
+"VERIFICATION:\n"
+" Did the Microphone Mute LED turn on and off or change color as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:3
+msgid "Audio tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:10
+msgid "Benchmarks tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:17
+msgid "Bluetooth tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:24
+msgid "Camera tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:31
+msgid "Codec tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:38
+msgid "CPU tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:45
+msgid "System Daemon tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:52
+msgid "Disk tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:59
+msgid "Docking tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:66
+msgid "Ethernet Device tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:73
+msgid "eSATA disk tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:80
+msgid "Fingerprint reader tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:87
+msgid "Firewire disk tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:94
+msgid "Firmware tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:101
+msgid "Floppy disk tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:108
+msgid "Graphics tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:115
+msgid "Hibernation tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:122
+msgid "Informational tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:129
+msgid "Input Devices tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:136
+msgid "Software Installation tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:143
+msgid "Hotkey tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:150
+msgid "LED tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:157
+msgid "Media Card tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:164
+msgid "Memory tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:171
+msgid "Rendercheck tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:178
+msgid "MIR tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:185
+msgid "Miscellaneous tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:192
+msgid "Monitor tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:199
+msgid "Non-device specific networking tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:206
+msgid "Optical Drive tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:213
+msgid "Panel Clock Verification tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:220
+msgid "Panel Reboot Verification tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:227
+msgid "ExpressCard tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:234
+msgid "Peripheral tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:241
+msgid "Power Management tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:248
+msgid "Server Services checks"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:255
+msgid "Suspend tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:262
+msgid "Thunderbolt tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:269
+msgid "Touchpad tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:276
+msgid "Touchscreen tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:283
+msgid "USB tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:290
+msgid "User Applications"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:297
+msgid "Virtualization tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:304
+msgid "Wireless networking tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:311
+msgid "Mobile broadband tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:318
+msgid "Stress tests"
+msgstr ""
+
+#. description
+#: ../jobs/local.txt.in:325
+msgid "Smoke tests"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:6
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a Multimedia Card (MMC) media\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert an MMC card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:26
+msgid ""
+"This test is automated and executes after the mediacard/mmc-insert test is "
+"run. It tests reading and writing to the MMC card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:36
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of the MMC card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the MMC card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:52
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of an UNLOCKED Secure Digital (SD) media card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert an UNLOCKED SD card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:72
+msgid ""
+"This test is automated and executes after the mediacard/sd-insert test is "
+"run. It tests reading and writing to the SD card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:82
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of an SD card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the SD card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:100
+msgid ""
+"This is a fully automated version of mediacard/sd-automated and assumes that "
+"the system under test has a memory card device plugged in prior to checkbox "
+"execution. It is intended for SRU automated testing."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:110
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a UNLOCKED Secure Digital High-Capacity\n"
+" (SDHC) media card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert an UNLOCKED SDHC card into the "
+"reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:131
+msgid ""
+"This test is automated and executes after the mediacard/sdhc-insert test is "
+"run. It tests reading and writing to the SDHC card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:141
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of an SDHC card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the SDHC card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:157
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a Compact Flash (CF) media card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert a CF card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:177
+msgid ""
+"This test is automated and executes after the mediacard/cf-insert test is "
+"run. It tests reading and writing to the CF card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:187
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of a CF card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the CF card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:203
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a Secure Digital Extended Capacity (SDXC) media "
+"card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert an UNLOCKED SDXC card into the "
+"reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:223
+msgid ""
+"This test is automated and executes after the mediacard/sdxc-insert test is "
+"run. It tests reading and writing to the SDXC card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:233
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of a SDXC card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the SDXC card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:249
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a Memory Stick (MS) media card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert a MS card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:269
+msgid ""
+"This test is automated and executes after the mediacard/ms-insert test is "
+"run. It tests reading and writing to the MS card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:279
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of a MS card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the MS card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:295
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a Memory Stick Pro (MSP) media card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert a MSP card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:315
+msgid ""
+"This test is automated and executes after the mediacard/msp-insert test is "
+"run. It tests reading and writing to the MSP card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:325
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of a MSP card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the MSP card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:341
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a Extreme Digital (xD) media card\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then insert a xD card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:361
+msgid ""
+"This test is automated and executes after the mediacard/xd-insert test is "
+"run. It tests reading and writing to the xD card."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:371
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of a xD card from the systems card reader.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and then remove the xD card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:389
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert SD card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:405
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert SDHC card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:421
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert MMC card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:437
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert CF card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:453
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert SDXC card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:469
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert MS card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:485
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert MSP card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/mediacard.txt.in:501
+msgid ""
+"PURPOSE:\n"
+" This test will check your Media Card data transfer performance.\n"
+"STEPS:\n"
+" 1. Insert xD card into the reader slot on this computer.\n"
+" 2. Commence the test.\n"
+"VERIFICATION:\n"
+" Did the results of the test match the expected performance of the "
+"inserted device?"
+msgstr ""
+
+#. description
+#: ../jobs/memory.txt.in:7
+msgid ""
+"This test checks the amount of memory which is reporting in meminfo against "
+"the size of the memory modules detected by DMI."
+msgstr ""
+
+#. description
+#: ../jobs/memory.txt.in:19
+msgid ""
+"Test to perform some basic stress and exercise of system memory. This test "
+"also includes an over-commit function to force swapping to disk, thus SUTs "
+"should have suitably large swap files for the amount of RAM they have "
+"installed."
+msgstr ""
+
+#. description
+#: ../jobs/memory.txt.in:33
+msgid ""
+"Test to perform some basic stress and exercise of system memory via the "
+"stress_ng tool. This test also includes an over-commit function to force "
+"swapping to disk, thus SUTs should have suitably large swap files for the "
+"amount of RAM they have installed."
+msgstr ""
+
+#. summary
+#: ../jobs/mir.txt.in:10
+msgid "MIR Integration test ({name})"
+msgstr ""
+
+#. description
+#: ../jobs/mir.txt.in:11
+msgid "Run {name} test from MIR Integration tests."
+msgstr ""
+
+#. summary
+#: ../jobs/mir.txt.in:22
+msgid "MIR Acceptance test ({name})"
+msgstr ""
+
+#. description
+#: ../jobs/mir.txt.in:23
+msgid "Run {name} test from MIR Acceptance tests."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:18
+msgid ""
+"A meta-job that verifies the data necessary for a complete result submission "
+"are present. Failure indicates that the results are incomplete and may be "
+"rejected."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:26
+msgid ""
+"PURPOSE:\n"
+" Keep tester related information in the report\n"
+"STEPS:\n"
+" 1. Tester Information\n"
+" 2. Please enter the following information in the comments field:\n"
+" a. Name\n"
+" b. Email Address\n"
+" c. Reason for this test run\n"
+"VERIFICATION:\n"
+" Nothing to verify for this test"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:45
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system can switch to a virtual terminal "
+"and back to X\n"
+"STEPS:\n"
+" 1. Click \"Test\" to switch to another virtual terminal and then back to "
+"X\n"
+"VERIFICATION:\n"
+" Did your screen change temporarily to a text console and then switch "
+"back to your current session?"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:60
+msgid "Run Firmware Test Suite (fwts) automated tests."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:73
+msgid "Attaches the miscellanes/fwts_test results log to the submission."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:83
+msgid "Attaches the FWTS results log to the submission (to HWE)"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:84
+msgid "Attach FWTS log to submission (to HWE)"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:92
+msgid ""
+"This will run some basic commands in-band against a BMC, verifying that IPMI "
+"works. Use of MAAS to deploy the system implicitly tests out-of-band BMC "
+"control."
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:103
+msgid "EFI-mode boot test"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:104
+msgid ""
+"Test to verify that the system booted in EFI mode with Secure Boot active."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:115
+msgid ""
+"This will gather some info about the BMC itself for diagnostic purposes. "
+"This will not works on non-IPMI systems like AMT and blade/sled type systems."
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:118
+msgid "Gather BMC Identification info"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:128
+msgid ""
+"Sanity check of CPU information; fails if CPU is an engineering sample"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:130
+msgid "CPU sanity check"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:140
+msgid "Sanity check of DMI system identification data (for servers)"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:142
+msgid "DMI ID sanity check (servers)"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:152
+msgid ""
+"Sanity check of DMI system identification data (for desktops & laptops)"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:154
+msgid "DMI ID sanity check (desktops/laptops)"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:161
+msgid ""
+" Determine if we need to run tests specific to portable computers that may "
+"not apply to desktops."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:170
+msgid ""
+"Test that the /var/crash directory doesn't contain anything. Lists the files "
+"contained within if it does, or echoes the status of the directory (doesn't "
+"exist/is empty)"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:177
+msgid ""
+"Checks that a specified sources list file contains the requested repositories"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:185
+msgid "PXE verification test of device {__index__} ({interface})"
+msgstr ""
+
+#. purpose
+#: ../jobs/miscellanea.txt.in:187
+msgid ""
+"This test will verify that you have attempted to PXE boot this machine from "
+"the network device {__index__} ({interface})."
+msgstr ""
+
+#. steps
+#: ../jobs/miscellanea.txt.in:190
+msgid ""
+"1. Prior to running this test, you should have attempted to boot this system "
+"via PXE on every Network Port available."
+msgstr ""
+
+#. verification
+#: ../jobs/miscellanea.txt.in:192
+msgid ""
+"1. Select Yes if you successfully used PXE to boot this system using the NIC "
+"{interface} 2. Select No if you attempted to PXE boot via {interface} and it "
+"failed for some reason. 3. Select Skip if you did not attempt to PXE boot "
+"this system using the NIC {interface}"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:203
+msgid ""
+"Remote Shared IPMI verification test for device {__index__} ({interface})"
+msgstr ""
+
+#. purpose
+#: ../jobs/miscellanea.txt.in:205
+msgid ""
+"This test will verify that you have attempted IPMI control of this machine "
+"from the network device {__index__} ({interface})."
+msgstr ""
+
+#. steps
+#: ../jobs/miscellanea.txt.in:207
+msgid ""
+"1. Prior to running this test, you should have configured and used IPMI to "
+"power this machine off and on using every Network Port available."
+msgstr ""
+
+#. verification
+#: ../jobs/miscellanea.txt.in:209
+msgid ""
+"1. Select Yes if you successfully used IPMI to remotely power this system "
+"off and on using the NIC {interface} 2. Select No if you did not attempt to "
+"use IPMI to remotely power this sytem off and on via the NIC {interface} 3. "
+"Select No if you attempted to use IPMI to remotely power off/on this system "
+"via {interface} and it failed for some reason."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:217
+msgid ""
+"PURPOSE:\n"
+" Some systems do not share IPMI over all NICs but instead have a dedicated "
+"management port directly connected to the BMC. This test verifies that you "
+"have used that port for remote IPMI connections and actions.\n"
+"STEPS:\n"
+" 1. Prior to running the test, you should have configured and used the "
+"Dedicated Management Port to remotely power off/on this sytem.\n"
+"VERIFICATION:\n"
+" Skip this test if this system ONLY uses shared management/ethernet ports OR "
+"if this system does not have a Management Controller.\n"
+" 1. Select Yes if you successfully used IPMI to remotely power this system "
+"off and on using the dedicated management port.\n"
+" 2. Select No if you attempted to use the dedicated management port to "
+"remotely power this system off/on and it failed for some reason."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:233
+msgid "Run Firmware Test Suite (fwts) oops tests."
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:245
+msgid "Attaches the FWTS oops results log to the submission"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:258
+msgid ""
+"If system was installed via MAAS from a cert server, the MAAS version used "
+"should be contained in /etc/installed-by-maas"
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:259
+msgid "Gets the version of MAAS used to deploy the SUT"
+msgstr ""
+
+#. description
+#: ../jobs/miscellanea.txt.in:267
+msgid ""
+"Retrieve the computer's make and model for easier access than digging "
+"through the dmidecode output."
+msgstr ""
+
+#. summary
+#: ../jobs/miscellanea.txt.in:268
+msgid "Retrieve the computer's make and model"
+msgstr ""
+
+#. description
+#: ../jobs/mobilebroadband.txt.in:29
+msgid ""
+"Creates a mobile broadband connection for a GSM based modem and checks the "
+"connection to ensure it's working. "
+msgstr ""
+
+#. description
+#: ../jobs/mobilebroadband.txt.in:58
+msgid ""
+"Creates a mobile broadband connection for a CDMA based modem and checks the "
+"connection to ensure it's working."
+msgstr ""
+
+#. purpose
+#: ../jobs/mobilebroadband.txt.in:100
+msgid ""
+"User verification of whether the observed transfer throughput is acceptable "
+"for the type and maximum speed of device {__index__} ({interface})."
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:7
+msgid " This test will check your VGA port."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:9
+msgid ""
+" Skip this test if your system does not have a VGA port.\n"
+" 1. Connect a display (if not already connected) to the VGA port on your "
+"system"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:21
+msgid " This test will check your DVI port."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:23
+msgid ""
+" Skip this test if your system does not have a DVI port.\n"
+" 1. Connect a display (if not already connected) to the DVI port on your "
+"system"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:35
+msgid " This test will check your DisplayPort port."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:37
+msgid ""
+" Skip this test if your system does not have a DisplayPort port.\n"
+" 1. Connect a display (if not already connected) to the DisplayPort port "
+"on your system"
+msgstr ""
+
+#. verification
+#: ../jobs/monitor.txt.in:40
+msgid " Was the desktop displayed correctly on both screens?"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:49
+msgid " This test will check your HDMI port."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:51
+msgid ""
+" Skip this test if your system does not have a HDMI port.\n"
+" 1. Connect a display (if not already connected) to the HDMI port on your "
+"system"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:63
+msgid " This test will check your S-VIDEO port."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:65
+msgid ""
+" Skip this test if your system does not have a S-VIDEO port.\n"
+" 1. Connect a display (if not already connected) to the S-VIDEO port on "
+"your system"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:77
+msgid " This test will check your RCA port."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:79
+msgid ""
+" Skip this test if your system does not have a RCA port.\n"
+" 1. Connect a display (if not already connected) to the RCA port on your "
+"system"
+msgstr ""
+
+#. verification
+#: ../jobs/monitor.txt.in:82 ../units/dock.pxu:673
+msgid " Was the desktop displayed correctly on both screens?"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:91
+msgid ""
+" This test verifies that multi-monitor output works on your desktop "
+"system. This is NOT the same test as the external monitor tests you would "
+"run on your laptop. You will need two monitors to perform this test."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:93
+msgid ""
+" Skip this test if your video card does not support multiple monitors.\n"
+" 1. If your second monitor is not already connected, connect it now\n"
+" 2. Open the \"Displays\" tool (open the dash and search for "
+"\"Displays\")\n"
+" 3. Configure your output to provide one desktop across both monitors\n"
+" 4. Open any application and drag it from one monitor to the next."
+msgstr ""
+
+#. verification
+#: ../jobs/monitor.txt.in:99
+msgid " Was the stretched desktop displayed correctly across both screens?"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:108
+msgid " This test will check your monitor power saving capabilities"
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:110
+msgid ""
+" 1. Click \"Test\" to try the power saving capabilities of your monitor\n"
+" 2. Press any key or move the mouse to recover"
+msgstr ""
+
+#. verification
+#: ../jobs/monitor.txt.in:113
+msgid " Did the monitor go blank and turn on again?"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:124
+msgid " This test will test changes to screen brightness"
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:126
+msgid ""
+" 1. Click \"Test\" to try to dim the screen.\n"
+" 2. Check if the screen was dimmed approximately to half of the maximum "
+"brightness.\n"
+" 3. The screen will go back to the original brightness in 2 seconds."
+msgstr ""
+
+#. verification
+#: ../jobs/monitor.txt.in:130
+msgid ""
+" Was your screen dimmed approximately to half of the maximum brightness?"
+msgstr ""
+
+#. summary
+#: ../jobs/monitor.txt.in:141
+msgid "Display connected via Thunderbolt for {vendor} {product}"
+msgstr ""
+
+#. purpose
+#: ../jobs/monitor.txt.in:142
+msgid ""
+" This test will check your Thunderbolt port as a monitor interconnect for "
+"{vendor} {product}."
+msgstr ""
+
+#. steps
+#: ../jobs/monitor.txt.in:144
+msgid ""
+" 1. Connect a display (if not already connected) to the Thunderbolt port "
+"on\n"
+" your system\n"
+" 2. Switch display modes between in your Display Settings, check if it can "
+"be\n"
+" set to mirrored, extended, displayed on external or onboard only"
+msgstr ""
+
+#. verification
+#: ../jobs/monitor.txt.in:149
+msgid ""
+" Was the desktop displayed correctly with {vendor} {product} on the "
+"Thunderbolt-connected\n"
+" screen in every mode?"
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:7 ../units/dock.pxu:512
+msgid "Tests whether the system has a working Internet connection."
+msgstr ""
+
+#. summary
+#: ../jobs/networking.txt.in:15
+msgid "Network Information of device {__index__} ({interface})"
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:19
+msgid ""
+"PURPOSE:\n"
+" This test will check the network device {__index__} ({interface})\n"
+"STEPS:\n"
+" 1. Click \"Test\" to verify the information for this network device\n"
+"VERIFICATION:\n"
+" Is this correct?"
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:31
+msgid ""
+"PURPOSE:\n"
+" This test will check that a DSL modem can be configured and connected.\n"
+"STEPS:\n"
+" 1. Connect the telephone line to the computer\n"
+" 2. Click on the Network icon on the top panel.\n"
+" 3. Select \"Edit Connections\"\n"
+" 4. Select the \"DSL\" tab\n"
+" 5. Click on \"Add\" button\n"
+" 6. Configure the connection parameters properly\n"
+" 7. Click \"Test\" to verify that it's possible to establish an HTTP "
+"connection\n"
+"VERIFICATION:\n"
+" Did a notification show and was the connection correctly established?"
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:49
+msgid ""
+"Automated test case to verify availability of some system on the network "
+"using ICMP ECHO packets."
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:56 ../jobs/peripheral.txt.in:40
+msgid ""
+"Automated test case to make sure that it's possible to download files "
+"through HTTP"
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:65
+msgid "Test to see if we can sync local clock to an NTP server"
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:72
+msgid ""
+"Verify that an installation of checkbox-server on the network can be reached "
+"over SSH."
+msgstr ""
+
+#. description
+#: ../jobs/networking.txt.in:79
+msgid "Try to enable a remote printer on the network and print a test page."
+msgstr ""
+
+#. description
+#: ../jobs/optical.txt.in:6
+msgid "Detects optical drives (CD/DVD) attached to the system."
+msgstr ""
+
+#. description
+#: ../jobs/optical.txt.in:42
+msgid ""
+"This is an automated version of optical/read. It assumes you have already "
+"inserted a data CD into your optical drive prior to running Checkbox."
+msgstr ""
+
+#. description
+#: ../jobs/optical.txt.in:57
+msgid ""
+"PURPOSE:\n"
+" This test will check your system's {product} CD writing capabilities. "
+"This test requires a blank CD-R or CD+R.\n"
+"STEPS:\n"
+" Skip this test if you do not have a blank CD disk.\n"
+" 1. Insert a blank CD-R or CD+R into your drive\n"
+" 2. Click \"Test\" to begin.\n"
+" 3. When the CD tray ejects the media after burning, close it (DO NOT "
+"remove the disk, it is needed for the second portion of the test). Note, you "
+"must close the drive within 5 minutes or the test will time out.\n"
+"VERIFICATION:\n"
+" This test should automatically select \"Yes\" if it passes, \"No\" if it "
+"fails."
+msgstr ""
+
+#. description
+#: ../jobs/optical.txt.in:80
+msgid ""
+"This is an automated version of optical/cdrom-write. It assumes you have "
+"already inserted a data CD into your {product} optical drive prior to "
+"running Checkbox."
+msgstr ""
+
+#. description
+#: ../jobs/optical.txt.in:91
+msgid ""
+"PURPOSE:\n"
+" This test will check your {product} CD audio playback capabilities\n"
+"STEPS:\n"
+" 1. Insert an audio CD in your optical drive\n"
+" 2. When prompted, launch the Music Player\n"
+" 3. Locate the CD in the display of the Music Player\n"
+" 4. Select the CD in the Music Player\n"
+" 5. Click the Play button to listen to the music on the CD\n"
+" 6. Stop playing after some time\n"
+" 7. Right click on the CD icon and select \"Eject Disc\"\n"
+" 8. The CD should be ejected\n"
+" 9. Close the Music Player\n"
+"VERIFICATION:\n"
+" Did all the steps work?"
+msgstr ""
+
+#. description
+#: ../jobs/optical.txt.in:153
+msgid ""
+"PURPOSE:\n"
+" This test will check your DVD playback capabilities\n"
+"STEPS:\n"
+" 1. Insert a DVD that contains any movie in your optical drive\n"
+" 2. Click \"Test\" to play the DVD in Totem\n"
+"VERIFICATION:\n"
+" Did the file play?"
+msgstr ""
+
+#. description
+#: ../jobs/panel_clock_test.txt.in:4
+msgid ""
+"PURPOSE:\n"
+" This test will verify that the desktop clock displays the correct date "
+"and time\n"
+"STEPS:\n"
+" 1. Check the clock in the upper right corner of your desktop.\n"
+"VERIFICATION:\n"
+" Is the clock displaying the correct date and time for your timezone?"
+msgstr ""
+
+#. description
+#: ../jobs/panel_clock_test.txt.in:18
+msgid ""
+"PURPOSE:\n"
+" This test will verify that the desktop clock synchronizes with the system "
+"clock.\n"
+"STEPS:\n"
+" 1. Commence the test and verify the clock moves ahead by 1 hour.\n"
+" Note: It may take a minute or so for the clock to refresh\n"
+" 2. Right click on the clock, then click on \"Time & Date Settings...\"\n"
+" 3. Ensure that your clock application is set to manual.\n"
+" 4. Change the time 1 hour back\n"
+" 5. Close the window and reboot\n"
+"VERIFICATION:\n"
+" Is your system clock displaying the correct date and time for your "
+"timezone?"
+msgstr ""
+
+#. description
+#: ../jobs/panel_reboot.txt.in:3
+msgid ""
+"PURPOSE:\n"
+" This test will verify that you can reboot your system from the desktop "
+"menu\n"
+"STEPS:\n"
+" 1. Click the Gear icon in the upper right corner of the desktop and click "
+"on \"Shut Down\"\n"
+" 2. Click the \"Restart\" button on the left side of the Shut Down dialog\n"
+" 3. After logging back in, restart System Testing and it should resume "
+"here\n"
+"VERIFICATION:\n"
+" Did your system restart and bring up the GUI login cleanly?"
+msgstr ""
+
+#. description
+#: ../jobs/peripheral.txt.in:4
+msgid ""
+"PURPOSE:\n"
+" This test will verify that a network printer is usable\n"
+"STEPS:\n"
+" 1. Make sure that a printer is available in your network\n"
+" 2. Click on the Gear icon in the upper right corner and then click on "
+"Printers\n"
+" 3. If the printer isn't already listed, click on Add\n"
+" 4. The printer should be detected and proper configuration values should "
+"be displayed\n"
+" 5. Print a test page\n"
+"VERIFICATION:\n"
+" Were you able to print a test page to the network printer?"
+msgstr ""
+
+#. description
+#: ../jobs/peripheral.txt.in:20
+msgid ""
+"PURPOSE:\n"
+" This test will verify that a USB DSL or Mobile Broadband modem works\n"
+"STEPS:\n"
+" 1. Connect the USB cable to the computer\n"
+" 2. Right click on the Network icon in the panel\n"
+" 3. Select 'Edit Connections'\n"
+" 4. Select the 'DSL' (for ADSL modem) or 'Mobile Broadband' (for 3G modem) "
+"tab\n"
+" 5. Click on 'Add' button\n"
+" 6. Configure the connection parameters properly\n"
+" 7. Notify OSD should confirm that the connection has been established\n"
+" 8. Select Test to verify that it's possible to establish an HTTP "
+"connection\n"
+"VERIFICATION:\n"
+" Was the connection correctly established?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:5
+msgid ""
+"PURPOSE:\n"
+" This test will check your system shutdown/booting cycle.\n"
+"STEPS:\n"
+" 1. Shutdown your machine.\n"
+" 2. Boot your machine.\n"
+" 3. Repeat steps 1 and 2 at least 5 times.\n"
+"VERIFICATION:\n"
+" Did the system shutdown and rebooted correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:21
+msgid "Test ACPI Wakealarm (fwts wakealarm)"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:31
+msgid "Attach log from fwts wakealarm test"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:48
+msgid ""
+"PURPOSE:\n"
+" This test will check the system's ability to power-off and boot.\n"
+"STEPS:\n"
+" 1. Select \"Test\" to begin.\n"
+" 2. The machine will shut down.\n"
+" 3. Power the machine back on.\n"
+" 4. After rebooting, wait for the test prompts to inform you that the test "
+"is complete.\n"
+" 5. Once the test has completed, restart checkbox and select 'Re-run' when "
+"prompted.\n"
+"VERIFICATION:\n"
+" If the machine successfully shuts down and boots, select 'Yes', otherwise,\n"
+" select 'No'."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:68
+msgid ""
+"This will attach any logs from the power-management/poweroff test to the "
+"results."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:82
+msgid ""
+"PURPOSE:\n"
+" This test will check the system's ability to reboot cleanly.\n"
+"STEPS:\n"
+" 1. Select \"Test\" to begin.\n"
+" 2. The machine will reboot.\n"
+" 3. After rebooting, wait for the test prompts to inform you that the test "
+"is complete.\n"
+" 4. Once the test has completed, restart checkbox and select Re-Run when "
+"prompted.\n"
+"VERIFICATION:\n"
+" If the machine successfully reboots, select Yes then select Next."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:100
+msgid ""
+"This will attach any logs from the power-management/reboot test to the "
+"results."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:108
+msgid ""
+"PURPOSE:\n"
+" This test will check your lid sensors.\n"
+"STEPS:\n"
+" 1. Close your laptop lid.\n"
+"VERIFICATION:\n"
+" Does closing your laptop lid cause your system to suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:127
+msgid ""
+"PURPOSE:\n"
+" This test will check your lid sensors\n"
+"STEPS:\n"
+" 1. Click \"Test\".\n"
+" 2. Close and open the lid.\n"
+"VERIFICATION:\n"
+" Did the screen turn off while the lid was closed?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:147
+msgid ""
+"PURPOSE:\n"
+" This test will check your lid sensors.\n"
+"STEPS:\n"
+" 1. Click \"Test\".\n"
+" 2. Close the lid.\n"
+" 3. Wait 5 seconds with the lid closed.\n"
+" 4. Open the lid.\n"
+"VERIFICATION:\n"
+" Did the system resume when the lid was opened?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:168
+msgid ""
+"Verify that the Real-time clock (RTC) device functions properly, if present."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:176
+msgid ""
+"Check to see if CONFIG_NO_HZ is set in the kernel (this is just a simple "
+"regression check)"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:184
+msgid ""
+"PURPOSE:\n"
+" This test will ensure that the AC is unplugged for the battery drain "
+"tests to run.\n"
+"STEPS:\n"
+" 1. Unplug laptop from AC.\n"
+"VERIFICATION:\n"
+" Was the laptop unplugged from AC?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:198
+msgid ""
+"Checks the battery drain during idle. Reports time and capacity until empty."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:209
+msgid ""
+"Checks the battery drain while watching a movie. Reports time and capacity "
+"until empty. Requires MOVIE_VAR to be set."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:222
+msgid ""
+"Checks the battery drain during suspend. Reports time and capacity until "
+"empty."
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:231
+msgid ""
+"PURPOSE:\n"
+" This test will ensure that the AC is plugged back in after the battery.\n"
+" tests\n"
+"STEPS:\n"
+" 1. Plug laptop into AC.\n"
+"VERIFICATION:\n"
+" Was the laptop plugged into AC?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:246
+msgid ""
+"PURPOSE:\n"
+" This test will verify that your system can successfully reboot.\n"
+"STEPS:\n"
+" 1. Select 'Test' to initiate a system reboot.\n"
+" 2. When the grub boot menu is displayed, boot into Ubuntu (Or allow the\n"
+" system to automatically boot on its own).\n"
+" 3. Once the system has restarted, log in and restart checkbox-"
+"certification-server.\n"
+" 4. Select 'Re-Run' to return to this test.\n"
+" 5. Select 'Yes' to indicate the test has passed if the system rebooted\n"
+" successfully, otherwise, select 'No' to indicate there was a problem.\n"
+"VERIFICATION:\n"
+" Did the system reboot correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/power-management.txt.in:266
+msgid ""
+"PURPOSE:\n"
+" This test will check your system shutdown/booting cycle\n"
+"STEPS:\n"
+" 1. Select 'Test' to initiate a system shutdown.\n"
+" 2. Power the system back on.\n"
+" 3. From the grub menu, boot into the Xen Hypervisor.\n"
+" 4. When the system has restarted, log in and restart checkbox-"
+"certification-server.\n"
+" 5. Select 'Re-Run' to return to this test.\n"
+" 6. Select 'Yes' to indicate the test has passed if the machine shut "
+"down\n"
+" successfully otherwise, Select 'No' to indicate there was a problem.\n"
+"VERIFICATION:\n"
+" Did the system shutdown and boot correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/rendercheck.txt.in:7
+msgid ""
+"Runs all of the rendercheck test suites. This test can take a few minutes."
+msgstr ""
+
+#. description
+#: ../jobs/rendercheck.txt.in:15
+msgid "Attach log from rendercheck tests"
+msgstr ""
+
+#. description
+#: ../jobs/server-services.txt.in:5
+msgid "Verifies that sshd is running."
+msgstr ""
+
+#. description
+#: ../jobs/server-services.txt.in:11
+msgid "Verifies that Print/CUPs server is running."
+msgstr ""
+
+#. description
+#: ../jobs/server-services.txt.in:20
+msgid "Verifies that DNS server is running and working."
+msgstr ""
+
+#. description
+#: ../jobs/server-services.txt.in:29
+msgid "Verifies that Samba server is running."
+msgstr ""
+
+#. description
+#: ../jobs/server-services.txt.in:40
+msgid "Verifies that the LAMP stack is running (Apache, MySQL and PHP)."
+msgstr ""
+
+#. description
+#: ../jobs/server-services.txt.in:47
+msgid "Verifies that Tomcat server is running and working."
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:4
+msgid "Check success result from shell test case"
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:10
+msgid "Check failed result from shell test case"
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:17
+msgid "Check job is executed when dependency succeeds"
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:24
+msgid "Check job result is set to uninitiated when dependency fails"
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:31
+msgid "Check job is executed when requirements are met"
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:38
+msgid ""
+"Check job result is set to \"not required on this system\" when requirements "
+"are not met"
+msgstr ""
+
+#. description
+#: ../jobs/smoke.txt.in:43
+msgid ""
+"PURPOSE:\n"
+" This test checks that the manual plugin works fine\n"
+"STEPS:\n"
+" 1. Add a comment\n"
+" 2. Set the result as passed\n"
+"VERIFICATION:\n"
+" Check that in the report the result is passed and the comment is "
+"displayed"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:9
+msgid ""
+"Simulate high system load using the 'stress' tool to exercise the CPU for "
+"several hours. The test is considered passed if the system does not freeze "
+"or abend."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:27
+msgid ""
+"Impose a high system load using the 'stress_ng' tool to exercise the CPU for "
+"several hours. The test is considered passed if the system does not freeze "
+"and if the stress_ng tool does not report errors."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:51
+msgid ""
+"PURPOSE:\n"
+" This is an automated stress test that will force the system to "
+"hibernate/resume for 30 cycles"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:60
+msgid ""
+"Automated check of the 30 cycle hibernate log for errors detected by fwts."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:68
+msgid "Attaches the log from the 30 cycle Hibernate/Resume test if it exists"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:81
+msgid ""
+"This is an automated stress test that will run a sequence of '30 "
+"suspend/resume cycles and one reboot' 3 times."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:101
+msgid ""
+"PURPOSE:\n"
+" This is an automated stress test that will force the system to "
+"suspend/resume for 30 cycles."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:111
+msgid ""
+"Automated check of the 30 cycle suspend log for errors detected by fwts."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:120
+msgid ""
+"Automated check of the '30 cycle suspend and 1 reboot times 3' logs for "
+"errors detected by fwts."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:129
+msgid "Attaches the log from the 30 cycle Suspend/Resume test if it exists"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:138
+msgid ""
+"Attaches the log from the '30 cycle Suspend/Resume and one reboot times 3' "
+"test if it exists"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:174
+msgid ""
+"PURPOSE:\n"
+" This is an automated stress test that will force the system to "
+"hibernate/resume for 250 cycles"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:183
+msgid ""
+"Attaches the log from the 250 cycle Hibernate/Resume test if it exists"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:201
+msgid ""
+"PURPOSE:\n"
+" This is an automated stress test that will force the system to "
+"suspend/resume for 250 cycles."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:210
+msgid "Attaches the log from the 250 cycle Suspend/Resume test if it exists"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:218 ../jobs/suspend.txt.in:366
+msgid ""
+"Checks the sleep times to ensure that a machine suspends and resumes within "
+"a given threshold"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:232
+msgid "Stress reboot system (100 cycles)"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:255
+msgid "Stress reboot system (30 cycles)"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:277
+msgid "Stress poweroff system (100 cycles)"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:300
+msgid "Stress poweroff system (30 cycles)"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:317
+msgid "Check logs for the stress reboot (30 cycles) test case"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:334
+msgid "Check logs for the stress poweroff (30 cycles) test case"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:351
+msgid "Check logs for the stress reboot (100 cycles) test case"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:368
+msgid "Check logs for the stress poweroff (100 cycles) test case"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:388
+msgid "Run the graphics stress test. This test can take a few minutes."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:398
+msgid "Attaches the graphics stress results to the submission."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:406
+msgid "Runs a test that transfers 100 10MB files 3 times to usb."
+msgstr ""
+
+#. summary
+#: ../jobs/stress.txt.in:412
+msgid "Stress test for SDHC card"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:415
+msgid ""
+"PURPOSE:\n"
+" This test will transfers 100 10MB files 3 times to a SDHC card, to\n"
+" check that the systems media card reader can transfer large amounts\n"
+" of data.\n"
+"STEPS:\n"
+" 1. Insert a SDHC card into the reader and then Click \"Test\".\n"
+" If a file browser opens up, you can safely close it.\n"
+" 2. Do not remove the device during this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:435
+msgid "Ping ubuntu.com and restart network interfaces 100 times"
+msgstr ""
+
+#. description
+#: ../jobs/stress.txt.in:449
+msgid ""
+"PURPOSE:\n"
+" To make sure that stressing the wifi hotkey does not cause applets to "
+"disappear from the panel or the system to lock up\n"
+"STEPS:\n"
+" 1. Log in to desktop\n"
+" 2. Press wifi hotkey at a rate of 1 press per second and slowly increase "
+"the speed of the tap, until you are tapping as fast as possible\n"
+"VERIFICATION:\n"
+" Verify the system is not frozen and the wifi and bluetooth applets are "
+"still visible and functional"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:6 ../units/dock.pxu:479
+msgid "Record the current network before suspending."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:23
+msgid "Record the current resolution before suspending."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:33 ../units/dock.pxu:489
+msgid "Record mixer settings before suspending."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:40
+msgid "Verify that all the CPUs are online before suspending"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:47
+msgid ""
+"Dumps memory info to a file for comparison after suspend test has been run"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:58
+msgid ""
+"This test disconnects all connections and then connects to the wireless "
+"interface. It then checks the connection to confirm it's working as expected."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:93
+msgid ""
+"This test executes iperf connection performance/stability against device "
+"{__index__} ({interface}) before suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:121
+msgid ""
+"This test executes iperf connection performance/stability against the "
+"broadband device found on the system before suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:225
+msgid ""
+"PURPOSE:\n"
+" This test will check suspend and resume\n"
+"STEPS:\n"
+" 1. Click \"Test\" and your system will suspend for about 30 - 60 "
+"seconds\n"
+" 2. Observe the Power LED to see if it blinks or changes color during "
+"suspend\n"
+" 3. If your system does not wake itself up after 60 seconds, please press "
+"the power button momentarily to wake the system manually\n"
+" 4. If your system fails to wake at all and must be rebooted, restart "
+"System Testing after reboot and mark this test as Failed\n"
+"VERIFICATION:\n"
+" Did your system suspend and resume correctly?\n"
+" (NOTE: Please only consider whether the system successfully suspended "
+"and resumed. Power/Suspend LED verification will occur after this test is "
+"completed.)"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:257
+msgid "Test suspend/resume after switching to {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:258
+msgid ""
+"PURPOSE:\n"
+" This test will check suspend and resume after switching to {vendor} "
+"{product} graphics card.\n"
+"STEPS:\n"
+" 1. Ensure you have switched to {vendor} {product} graphics card.\n"
+" 2. Click \"Test\" and your system will suspend for about 30 - 60 "
+"seconds\n"
+" 3. Observe the Power LED to see if it blinks or changes color during "
+"suspend\n"
+" 4. If your system does not wake itself up after 60 seconds, please press "
+"the power button momentarily to wake the system manually\n"
+" 5. If your system fails to wake at all and must be rebooted, restart "
+"System Testing after reboot and mark this test as Failed\n"
+"VERIFICATION:\n"
+" Did your system suspend and resume correctly after switching to {vendor} "
+"{product} graphics card?\n"
+" (NOTE: Please only consider whether the system successfully suspended "
+"and resumed. Power/Suspend LED verification will occur after this test is "
+"completed.)"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:277
+msgid "This is the automated version of suspend/suspend_advanced."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:293
+msgid ""
+"PURPOSE:\n"
+" This test will check hybrid sleep and resume\n"
+"STEPS:\n"
+" 1. Click \"Test\" and your system will go into hybrid sleep mode for "
+"about 30 - 60 seconds\n"
+" 2. Observe the Power LED to see if it blinks or changes color during "
+"suspend\n"
+" 3. If your system does not wake itself up after 60 seconds, please press "
+"the power button momentarily to wake the system manually\n"
+" 4. If your system fails to wake at all and must be rebooted, restart "
+"System Testing after reboot and mark this test as Failed\n"
+"VERIFICATION:\n"
+" Did your system enter hybrid sleep and then resume correctly?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:309
+msgid ""
+"Automated check of the suspend log to look for errors reported by fwts"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:337
+msgid ""
+"Automated check of the hybrid sleep log to look for errors reported by fwts"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:347
+msgid ""
+"Attaches the log from the single hybrid sleep/resume test to the results"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:375
+msgid ""
+"PURPOSE:\n"
+" Wake up by USB keyboard\n"
+"STEPS:\n"
+" 1. Enable \"Wake by USB KB/Mouse\" item in BIOS\n"
+" 2. Press \"Test\" to enter suspend (S3) mode\n"
+" 3. Press any key of USB keyboard to wake system up\n"
+"VERIFICATION:\n"
+" Did the system wake up from suspend mode when you pressed a keyboard key?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:392
+msgid ""
+"PURPOSE:\n"
+" Wake up by USB mouse\n"
+"STEPS:\n"
+" 1. Enable \"Wake by USB KB/Mouse\" item in BIOS\n"
+" 2. Press \"Test\" to enter suspend (S3) mode\n"
+" 3. Press any button of USB mouse to wake system up\n"
+"VERIFICATION:\n"
+" Did the system wake up from suspend mode when you pressed the mouse "
+"button?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:407
+msgid "Test the network after resuming."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:425
+msgid ""
+"Test to see that we have the same resolution after resuming as before."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:449 ../units/dock.pxu:838
+msgid ""
+"Verify that mixer settings after suspend are the same as before suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:463
+msgid ""
+"PURPOSE:\n"
+" Check that system detects speakers or headphones being plugged in after "
+"suspend\n"
+"STEPS:\n"
+" 1. Prepare a pair of headphones or speakers with a standard 3.5mm jack\n"
+" 2. Locate the speaker / headphone jack on the device under test\n"
+" 3. Run the test (you have 30 seconds from now on)\n"
+" 4. Plug headphones or speakers into the appropriate jack\n"
+" 5. Unplug the device for subsequent tests.\n"
+"VERIFICATION:\n"
+" Verification is automatic, no action is required.\n"
+" The test times out after 30 seconds (and fails in that case)."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:485
+msgid ""
+"PURPOSE:\n"
+" Check that system detects a microphone being plugged in after suspend\n"
+"STEPS:\n"
+" 1. Prepare a microphone with a standard 3.5mm jack\n"
+" 2. Locate the microphone jack on the device under test.\n"
+" Keep in mind that it may be shared with the headphone jack.\n"
+" 3. Run the test (you have 30 seconds from now on)\n"
+" 4. Plug the microphone into the appropriate jack\n"
+" 5. Unplug the device for subsequent tests.\n"
+"VERIFICATION:\n"
+" Verification is automatic, no action is required.\n"
+" The test times out after 30 seconds (and fails in that case)."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:516
+msgid ""
+"PURPOSE:\n"
+" This test will check that headphones connector works correctly after "
+"suspend\n"
+"STEPS:\n"
+" 1. Connect a pair of headphones to your audio device\n"
+" 2. Commence the test to play a sound to your audio device\n"
+"VERIFICATION:\n"
+" Did you hear a sound through the headphones and did the sound play "
+"without any distortion, clicks or other strange noises from your headphones?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:542
+msgid ""
+"PURPOSE:\n"
+" This test will check that recording sound using an external microphone "
+"works correctly after suspend\n"
+"STEPS:\n"
+" 1. Connect a microphone to your microphone port\n"
+" 2. Click \"Test\", then speak into the external microphone\n"
+" 3. After a few seconds, your speech will be played back to you\n"
+"VERIFICATION:\n"
+" Did you hear your speech played back?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:565
+msgid "Verify that all CPUs are online after resuming."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:582
+msgid "Verify that all memory is available after resuming from suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:591
+msgid ""
+"PURPOSE:\n"
+" This test will check that the display is correct after suspend and "
+"resume\n"
+"STEPS:\n"
+" 1. Check that your display does not show up visual artifacts after "
+"resuming.\n"
+"VERIFICATION:\n"
+" Does the display work normally after resuming from suspend?"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:605
+msgid "Test display function after suspend for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:606
+msgid ""
+"PURPOSE:\n"
+" This test will check that the display is correct after suspend and "
+"resume on the {vendor} {product} graphics card.\n"
+"STEPS:\n"
+" 1. Check that your display does not show up visual artifacts after "
+"resuming.\n"
+"VERIFICATION:\n"
+" Does the display work normally after resuming from suspend using the "
+"{vendor} {product} graphics card?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:622
+msgid ""
+"This test checks that the wireless interface is working after suspending the "
+"system. It disconnects all interfaces and then connects to the wireless "
+"interface and checks that the connection is working as expected."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:842 ../units/dock.pxu:709
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using WPA "
+"security and the 802.11b/g protocols after the system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:873 ../units/dock.pxu:732
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using no "
+"security and the 802.11b/g protocols after the system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:904 ../units/dock.pxu:755
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using WPA "
+"security and the 802.11n protocol after the system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:935 ../units/dock.pxu:778
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using no "
+"security and the 802.11n protocol after the system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:967 ../units/dock.pxu:802
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using WPA "
+"security and the 802.11ac protocol after the system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:999 ../units/dock.pxu:826
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using no "
+"security and the 802.11ac protocol after the system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1034
+msgid ""
+"This test executes iperf connection performance/stability against device "
+"{__index__} ({interface}) after suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1062
+msgid ""
+"This test executes iperf connection performance/stability against the "
+"broadband device found on the system after suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1092
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using "
+"WPA\n"
+" security and the 802.11b/g protocols.\n"
+"STEPS:\n"
+" 1. Open your routers configuration tool\n"
+" 2. Change the settings to only accept connections on the B and G "
+"wireless bands\n"
+" 3. Make sure the SSID is set to ROUTER_SSID\n"
+" 4. Change the security settings to use WPA2 and ensure the PSK matches "
+"that set in ROUTER_PSK\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1132
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using\n"
+" no security and the 802.11b/g protocols.\n"
+"STEPS:\n"
+" 1. Open your routers configuration tool\n"
+" 2. Change the settings to only accept connections on the B and G "
+"wireless bands\n"
+" 3. Make sure the SSID is set to ROUTER_SSID\n"
+" 4. Change the security settings to use no security\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1172
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using "
+"WPA\n"
+" security and the 802.11n protocols.\n"
+"STEPS:\n"
+" 1. Open your routers configuration tool\n"
+" 2. Change the settings to only accept connections on the N wireless "
+"band\n"
+" 3. Make sure the SSID is set to ROUTER_SSID\n"
+" 4. Change the security settings to use WPA2 and ensure the PSK matches "
+"that set in ROUTER_PSK\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1212
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using\n"
+" no security and the 802.11n protocol.\n"
+"STEPS:\n"
+" 1. Open your routers configuration tool\n"
+" 2. Change the settings to only accept connections on the N wireless "
+"band\n"
+" 3. Make sure the SSID is set to ROUTER_SSID\n"
+" 4. Change the security settings to use no security\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1252
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using "
+"WPA\n"
+" security and the 802.11ac protocol.\n"
+"STEPS:\n"
+" 1. Open your routers configuration tool\n"
+" 2. Change the settings to only accept connections on the 802.11ac "
+"protocol.\n"
+" 3. Make sure the SSID is set to ROUTER_SSID\n"
+" 4. Change the security settings to use WPA2 and ensure the PSK matches "
+"that set in ROUTER_PSK\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1292
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using\n"
+" no security and the 802.11ac protocol.\n"
+"STEPS:\n"
+" 1. Open your routers configuration tool\n"
+" 2. Change the settings to only accept connections on the 802.11ac "
+"protocol.\n"
+" 3. Make sure the SSID is set to ROUTER_SSID\n"
+" 4. Change the security settings to use no security\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1328
+msgid ""
+"This test grabs the hardware address of the bluetooth adapter after suspend "
+"and compares it to the address grabbed before suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1386
+msgid ""
+"This is an automated Bluetooth file transfer test. It sends an image to the "
+"device specified by the BTDEVADDR environment variable."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1444
+msgid ""
+"This is an automated Bluetooth test. It emulates browsing on a remote device "
+"specified by the BTDEVADDR environment variable."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1502
+msgid ""
+"This is an automated Bluetooth test. It receives the given file from a "
+"remote host specified by the BTDEVADDR environment variable"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1529
+msgid ""
+"PURPOSE:\n"
+" This test will cycle through the detected display modes\n"
+"STEPS:\n"
+" 1. Click \"Test\" and the display will cycle trough the display modes\n"
+"VERIFICATION:\n"
+" Did your display look fine in the detected mode?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1543
+msgid ""
+"This test will check to make sure supported video modes work after a suspend "
+"and resume. This is done automatically by taking screenshots and uploading "
+"them as an attachment."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1562
+msgid ""
+"This attaches screenshots from the suspend/cycle_resolutions_after_suspend "
+"test to the results submission."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1595 ../units/dock.pxu:857
+msgid ""
+"This will check to make sure that your audio device works properly after a "
+"suspend and resume. This may work fine with speakers and onboard "
+"microphone, however, it works best if used with a cable connecting the audio-"
+"out jack to the audio-in jack."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1602
+msgid "Attaches the log from the single suspend/resume test to the results"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1612
+msgid ""
+"PURPOSE:\n"
+" Take a screengrab of the current screen after suspend (logged on Unity "
+"desktop)\n"
+"STEPS:\n"
+" 1. Take picture using USB webcam\n"
+"VERIFICATION:\n"
+" Review attachment manually later"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1625
+msgid "Attaches the screenshot captured in graphics/screenshot."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1637
+msgid ""
+"PURPOSE:\n"
+" Do some challenging operations then check for lockup on the GPU\n"
+"STEPS:\n"
+" 1. Create 2 glxgears windows and move them quickly\n"
+" 2. Switch workspaces with wmctrl\n"
+" 3. Launch an HTML5 video playback in firefox\n"
+"VERIFICATION:\n"
+" After a 60s workload, check kern.log for reported GPU errors"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1667
+msgid ""
+"Checks the length of time it takes to reconnect an existing wifi connection "
+"after a suspend/resume cycle."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1691
+msgid ""
+"Checks the length of time it takes to reconnect an existing wired "
+"connection\n"
+" after a suspend/resume cycle."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1700
+msgid ""
+"PURPOSE:\n"
+" Validate that the power LED operated the same after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Power LED should be on while device is switched on\n"
+"VERIFICATION:\n"
+" Does the power LED remain on after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1713
+msgid ""
+"PURPOSE:\n"
+" Validate that the battery light shows charging status after resuming "
+"from suspend\n"
+"STEPS:\n"
+" 1. Let system run on battery for a while\n"
+" 2. Plug in AC plug\n"
+"VERIFICATION:\n"
+" Did the battery indicator LED still turn orange after resuming from "
+"suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1727
+msgid ""
+"PURPOSE:\n"
+" Validate that the battery LED properly displays charged status after "
+"resuming from suspend\n"
+"STEPS:\n"
+" 1. Let system run on battery for a short time\n"
+" 2. Plug in AC\n"
+" 3. Let system run on AC\n"
+"VERIFICATION:\n"
+" Does the orange battery LED still shut off when system is fully charged "
+"after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1742
+msgid ""
+"PURPOSE:\n"
+" Validate that the battery LED indicated low power after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Let system run on battery for several hours\n"
+" 2. Monitor battery LED carefully\n"
+"VERIFICATION:\n"
+" Does the LED light orange when battery is low after resuming from "
+"suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1757
+msgid ""
+"PURPOSE:\n"
+" Validate that the HDD LED still operates as expected after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Select \"Test\" to write and read a temporary file for a few seconds\n"
+" 2. HDD LED should blink when writing to/reading from HDD\n"
+"VERIFICATION:\n"
+" Did the HDD LED still blink with HDD activity after resuming from "
+"suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1772
+msgid ""
+"PURPOSE:\n"
+" Validate that the numeric keypad LED operates the same before and after "
+"resuming from suspend\n"
+"STEPS:\n"
+" 1. Press \"Block Num\" key to toggle numeric keypad LED\n"
+" 2. Click on the \"Test\" button to open a window to verify your typing\n"
+" 3. Type using the numeric keypad both when the LED is on and off\n"
+"VERIFICATION:\n"
+" 1. Numeric keypad LED status should toggle everytime the \"Block Num\" "
+"key is pressed\n"
+" 2. Numbers should only be entered in the keyboard verification window "
+"when the LED is on"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1788
+msgid ""
+"PURPOSE:\n"
+" Validate that the Caps Lock key operates the same before and after "
+"resuming from suspend\n"
+"STEPS:\n"
+" 1. Press \"Block Cap Keys\" to activate/deactivate cap keys blocking\n"
+" 2. Cap Keys LED should be switched on/off every time the key is pressed\n"
+"VERIFICATION:\n"
+" Did the Cap Keys LED light as expected after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1802
+msgid ""
+"PURPOSE:\n"
+" WLAN LED verification after resuming from suspend\n"
+"STEPS:\n"
+" 1. Make sure WLAN connection is established\n"
+" 2. WLAN LED should light\n"
+"VERIFICATION:\n"
+" Did the WLAN LED light as expected after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1816
+msgid ""
+"PURPOSE:\n"
+" Validate that WLAN LED shuts off when disabled after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Connect to AP\n"
+" 2. Use Physical switch to disable WLAN\n"
+" 3. Re-enable\n"
+" 4. Use Network-Manager to disable WLAN\n"
+"VERIFICATION:\n"
+" Did the LED turn off then WLAN is disabled after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1832
+msgid ""
+"PURPOSE:\n"
+" Validate that the Bluetooth LED turns on and off when BT is "
+"enabled/disabled after resuming from suspend\n"
+"STEPS:\n"
+" 1. Switch bluetooth off from a hardware switch (if present)\n"
+" 2. Switch bluetooth back on\n"
+" 3. Switch bluetooth off from the panel applet\n"
+" 4. Switch bluetooth back on\n"
+"VERIFICATION:\n"
+" Did the bluetooth LED turn off and on twice after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1851
+msgid ""
+"PURPOSE:\n"
+" Validate that the camera LED still works as expected after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Select Test to activate camera\n"
+" 2. Camera LED should light for a few seconds\n"
+"VERIFICATION:\n"
+" Did the camera LED still turn on and off after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1865
+msgid ""
+"PURPOSE:\n"
+" Touchpad LED verification after resuming from suspend\n"
+"STEPS:\n"
+" 1. Click on the touchpad button or press key combination to "
+"enable/disable touchpad button\n"
+" 2. Slide your finger on the touchpad\n"
+"VERIFICATION:\n"
+" 1. Touchpad LED status should toggle everytime the button is clicked or "
+"the key combination is pressed\n"
+" 2. When the LED is on, the mouse pointer should move on touchpad usage\n"
+" 3. When the LED is off, the mouse pointer should not move on touchpad "
+"usage"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1881
+msgid ""
+"PURPOSE:\n"
+" Validate Wireless (WLAN + Bluetooth) LED operated the same after "
+"resuming from suspend\n"
+"STEPS:\n"
+" 1. Make sure WLAN connection is established and Bluetooth is enabled.\n"
+" 2. WLAN/Bluetooth LED should light\n"
+" 3. Switch WLAN and Bluetooth off from a hardware switch (if present)\n"
+" 4. Switch them back on\n"
+" 5. Switch WLAN and Bluetooth off from the panel applet\n"
+" 6. Switch them back on\n"
+"VERIFICATION:\n"
+" Did the WLAN/Bluetooth LED light as expected after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1900
+msgid ""
+"PURPOSE:\n"
+" This test will test the brightness key after resuming from suspend\n"
+"STEPS:\n"
+" 1. Press the brightness buttons on the keyboard\n"
+"VERIFICATION:\n"
+" Did the brightness change following to your key presses after resuming "
+"from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1917
+msgid ""
+"PURPOSE:\n"
+" This test will test the volume keys of your keyboard after resuming from "
+"suspend\n"
+"STEPS:\n"
+" Skip this test if your computer has no volume keys.\n"
+" 1. Click test to open a window on which to test the volume keys.\n"
+" 2. If all the keys work, the test will be marked as passed.\n"
+"VERIFICATION:\n"
+" Did the volume change following to your key presses?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1936
+msgid ""
+"PURPOSE:\n"
+" This test will test the mute key of your keyboard after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Click test to open a window on which to test the mute key.\n"
+" 2. If the key works, the test will pass and the window will close.\n"
+"VERIFICATION:\n"
+" Did the volume mute following your key presses?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1952
+msgid ""
+"PURPOSE:\n"
+" This test will test the sleep key after resuming from suspend\n"
+"STEPS:\n"
+" 1. Press the sleep key on the keyboard\n"
+" 2. Wake your system up by pressing the power button\n"
+"VERIFICATION:\n"
+" Did the system go to sleep after pressing the sleep key after resuming "
+"from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1969
+msgid ""
+"PURPOSE:\n"
+" This test will test the battery information key after resuming from "
+"suspend\n"
+"STEPS:\n"
+" Skip this test if you do not have a Battery Button.\n"
+" 1. Click Test to begin\n"
+" 2. Press the Battery Info button (or combo like Fn+F3)\n"
+" 3: Close the Power Statistics tool if it opens\n"
+"VERIFICATION:\n"
+" Did the Battery Info key work as expected after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:1986
+msgid ""
+"PURPOSE:\n"
+" This test will test the wireless key after resuming from suspend\n"
+"STEPS:\n"
+" 1. Press the wireless key on the keyboard\n"
+" 2. Press the same key again\n"
+"VERIFICATION:\n"
+" Did the wireless go off on the first press and on again on the second "
+"after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2004
+msgid ""
+"PURPOSE:\n"
+" This test will test the media keys of your keyboard after resuming from "
+"suspend\n"
+"STEPS:\n"
+" Skip this test if your computer has no media keys.\n"
+" 1. Click test to open a window on which to test the media keys.\n"
+" 2. If all the keys work, the test will be marked as passed.\n"
+"VERIFICATION:\n"
+" Do the keys work as expected after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2023
+msgid ""
+"PURPOSE:\n"
+" This test will test the super key of your keyboard after resuming from "
+"suspend\n"
+"STEPS:\n"
+" 1. Click test to open a window on which to test the super key.\n"
+" 2. If the key works, the test will pass and the window will close.\n"
+"VERIFICATION:\n"
+" Does the super key work as expected after resuming from suspend?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2038
+msgid ""
+"PURPOSE:\n"
+" Validate that the External Video hot key is working as expected after "
+"resuming from suspend\n"
+"STEPS:\n"
+" 1. Plug in an external monitor\n"
+" 2. Press the display hot key to change the monitors configuration\n"
+"VERIFICATION:\n"
+" Check that the video signal can be mirrored, extended, displayed on "
+"external or onboard only, after resuming from suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2053
+msgid ""
+"PURPOSE:\n"
+" Verify touchpad hotkey toggles touchpad functionality on and off after "
+"resuming from suspend\n"
+"STEPS:\n"
+" 1. Verify the touchpad is functional\n"
+" 2. Tap the touchpad toggle hotkey\n"
+" 3. Tap the touchpad toggle hotkey again\n"
+"VERIFICATION:\n"
+" Verify the touchpad has been disabled and re-enabled."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2070
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the insertion of\n"
+" a USB storage device after suspend and resume.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a USB storage device (pen-drive/HDD).\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not unplug the device after the test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2091
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the insertion of\n"
+" a USB 3.0 storage device after suspend and resume.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a USB 3.0 storage device (pen-drive/HDD) "
+"in\n"
+" a USB 3.0 port. (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not unplug the device after the test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2110
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal of\n"
+" a USB storage device after suspend.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the USB device.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2130
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal of\n"
+" a USB 3.0 storage device after suspend\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the USB 3.0 device.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2148
+msgid ""
+"This test is automated and executes after the "
+"suspend/usb_insert_after_suspend test is run."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2161
+msgid ""
+"This test is automated and executes after the "
+"suspend/usb3_insert_after_suspend test is run."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2172
+msgid ""
+"This is an automated version of usb/storage-automated and assumes that the "
+"server has usb storage devices plugged in prior to checkbox execution. It is "
+"intended for servers and SRU automated testing."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2186
+msgid ""
+"This is an automated version of usb3/storage-automated and assumes that the "
+"server has usb 3.0 storage devices plugged in prior to checkbox execution. "
+"It is intended for servers and SRU automated testing."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2198 ../jobs/usb.txt.in:219
+msgid ""
+"This test will check that your USB 2.0 port transfers data at a minimum "
+"expected speed."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2211
+msgid ""
+"This test will check that your USB 3.0 port could be recognized as "
+"SuperSpeed USB device using xhci_hcd driver and transfers data correctly."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2221
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of an MMC card after the system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert an MMC card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2241
+msgid ""
+"This test is automated and executes after the mediacard/mmc-insert-after-"
+"suspend test is run. It tests reading and writing to the MMC card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2251
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of an MMC card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the MMC card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2268
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of an UNLOCKED SD card after the system\n"
+" has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert an UNLOCKED SD card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2289
+msgid ""
+"This test is automated and executes after the mediacard/sd-insert-after-"
+"suspend test is run. It tests reading and writing to the SD card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2299
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects\n"
+" the removal of an SD card from the systems card reader\n"
+" after the system has been suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the SD card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2317
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of an UNLOCKED SDHC media card after the\n"
+" system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert an UNLOCKED SDHC card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2338
+msgid ""
+"This test is automated and executes after the mediacard/sdhc-insert-after-"
+"suspend test is run. It tests reading and writing to the SDHC card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2348
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of an SDHC card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the SDHC card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2365
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a CF card after the system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a CF card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2385
+msgid ""
+"This test is automated and executes after the mediacard/cf-insert-after-"
+"suspend test is run. It tests reading and writing to the CF card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2395
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of a CF card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the CF card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2412
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a SDXC card after the system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a SDXC card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2432
+msgid ""
+"This test is automated and executes after the mediacard/sdxc-insert-after-"
+"suspend test is run. It tests reading and writing to the SDXC card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2442
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of a SDXC card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the SDXC card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2459
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a MS card after the system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a MS card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2479
+msgid ""
+"This test is automated and executes after the mediacard/ms-insert-after-"
+"suspend test is run. It tests reading and writing to the MS card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2489
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of a MS card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the MS card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2506
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a MSP card after the system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a MSP card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2526
+msgid ""
+"This test is automated and executes after the mediacard/msp-insert-after-"
+"suspend test is run. It tests reading and writing to the MSP card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2536
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of a MSP card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the MSP card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2553
+msgid ""
+"PURPOSE:\n"
+" This test will check that the systems media card reader can\n"
+" detect the insertion of a xD card after the system has been suspended\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a xD card into the reader.\n"
+" If a file browser opens up, you can safely close it.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not remove the device after this test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2573
+msgid ""
+"This test is automated and executes after the mediacard/xd-insert-after-"
+"suspend test is run. It tests reading and writing to the xD card after the "
+"system has been suspended."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2583
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal\n"
+" of a xD card from the systems card reader after the system has been "
+"suspended.\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the xD card from the reader.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2603
+msgid "Determine if the touchpad is still functioning after suspend/resume."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2613 ../jobs/touchscreen.txt.in:45
+msgid ""
+"PURPOSE:\n"
+" Check touchscreen tap recognition\n"
+"STEPS:\n"
+" 1. Tap an object on the screen with finger. The cursor should jump to "
+"location tapped and object should highlight\n"
+"VERIFICATION:\n"
+" Does tap recognition work?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2629
+msgid ""
+"PURPOSE:\n"
+" This test will check that the built-in camera works after suspend\n"
+"STEPS:\n"
+" 1. Click on Test to display a video capture from the camera for ten "
+"seconds.\n"
+"VERIFICATION:\n"
+" Did you see the video capture?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2648
+msgid ""
+"PURPOSE:\n"
+" This test will check that the built-in camera works after suspend\n"
+"STEPS:\n"
+" 1. Click on Test to display a still image from the camera for ten "
+"seconds.\n"
+"VERIFICATION:\n"
+" Did you see the image?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2665
+msgid ""
+" Takes multiple pictures based on the resolutions supported by the camera "
+"and\n"
+" validates their size and that they are of a valid format after suspend"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2677
+msgid ""
+"PURPOSE:\n"
+" This will test your {product} device after suspend.\n"
+"STEPS:\n"
+" 1. Move the cursor with your {product}.\n"
+"VERIFICATION:\n"
+" Did the cursor move?"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2694
+msgid "Check post suspend button functionality for {product}"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2695
+msgid ""
+"PURPOSE:\n"
+" This will test the buttons of your {product} device after suspend\n"
+"STEPS:\n"
+" 1. Click the left button with your {product}.\n"
+" 2. Click the right button with your {product}.\n"
+" 3. Click the middle button with your {product} (if available).\n"
+" 4. Double-click the left button with your {product}.\n"
+"VERIFICATION:\n"
+" Did these buttons work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2715
+msgid "Check that {product} hardware is able to run compiz after suspend"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2716
+msgid "Test Compiz support for {product} after suspend"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2725
+msgid "Check that the hardware is able to run compiz after suspend"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2726
+msgid "Test Compiz support after suspend"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2736
+msgid "Test that glxgears works for {vendor} {product} after suspend"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2737
+msgid ""
+"PURPOSE:\n"
+" This test tests the basic 3D capabilities of your {vendor} {product} "
+"video card after suspend\n"
+"STEPS:\n"
+" 1. Click \"Test\" to execute an OpenGL demo. Press ESC at any time to "
+"close.\n"
+" 2. Verify that the animation is not jerky or slow.\n"
+"VERIFICATION:\n"
+" 1. Did the 3d animation appear?\n"
+" 2. Was the animation free from slowness/jerkiness?"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2755
+msgid "Test that glxgears works after suspend"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2756
+msgid ""
+"PURPOSE:\n"
+" This test tests the basic 3D capabilities of your $product video card "
+"after suspend\n"
+"STEPS:\n"
+" 1. Click \"Test\" to execute an OpenGL demo. Press ESC at any time to "
+"close.\n"
+" 2. Verify that the animation is not jerky or slow.\n"
+"VERIFICATION:\n"
+" 1. Did the 3d animation appear?\n"
+" 2. Was the animation free from slowness/jerkiness?"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2776
+msgid ""
+"Test that video can be displayed after suspend with {vendor} {product}"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2794
+msgid "Test that video can be displayed after suspend"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2795
+msgid ""
+"PURPOSE:\n"
+" This test will test the default display after suspend with a sample "
+"video\n"
+"STEPS:\n"
+" 1. Click \"Test\" to display a video test.\n"
+"VERIFICATION:\n"
+" Do you see color bars and static?"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2811
+msgid ""
+"Parses Xorg.0.Log and discovers the running X driver and version after "
+"suspend for the {vendor} {product} graphics card"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2812
+msgid "Test X driver/version after suspend for {vendor} {product}"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2821
+msgid ""
+"Parses Xorg.0.Log and discovers the running X driver and version after "
+"suspend"
+msgstr ""
+
+#. summary
+#: ../jobs/suspend.txt.in:2822
+msgid "Test X driver/version after suspend"
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2831
+msgid "Run Firmware Test Suite (fwts) oops tests after suspend."
+msgstr ""
+
+#. description
+#: ../jobs/suspend.txt.in:2843
+msgid "Attaches the FWTS oops results log to the submission after suspend"
+msgstr ""
+
+#. name
+#: ../jobs/thunderbolt.pxu:3
+msgid "Thunderbolt Support "
+msgstr ""
+
+#. summary
+#: ../jobs/thunderbolt.pxu:13
+msgid "Storage insert detection on Thunderbolt"
+msgstr ""
+
+#. description
+#: ../jobs/thunderbolt.pxu:14
+msgid ""
+"PURPOSE:\n"
+" This test will check if the insertion of a Thunderbolt HDD could be "
+"detected\n"
+"STEPS:\n"
+" 1. Click 'Test' to begin the test. This test will\n"
+" timeout and fail if the insertion has not been detected within 40 "
+"seconds.\n"
+" 2. Plug a Thunderbolt HDD into an available Thunderbolt port, if it's "
+"not\n"
+" mounted automatically, please click the HDD icon to mount it.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. summary
+#: ../jobs/thunderbolt.pxu:35
+msgid "Storage test on Thunderbolt"
+msgstr ""
+
+#. description
+#: ../jobs/thunderbolt.pxu:36 ../units/dock.pxu:1016
+msgid ""
+"This is an automated test which performs read/write operations on an "
+"attached Thunderbolt HDD"
+msgstr ""
+
+#. summary
+#: ../jobs/thunderbolt.pxu:48
+msgid "Storage removal detection on Thunderbolt"
+msgstr ""
+
+#. description
+#: ../jobs/thunderbolt.pxu:49
+msgid ""
+"PURPOSE:\n"
+" This test will check the system can detect the removal of a Thunderbolt "
+"HDD\n"
+"STEPS:\n"
+" 1. Click 'Test' to begin the test. This test will timeout and fail if\n"
+" the removal has not been detected within 20 seconds.\n"
+" 2. Remove the previously attached Thunderbolt HDD from the Thunderbolt "
+"port.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. summary
+#: ../jobs/thunderbolt.pxu:67
+msgid "Daisy-chain testing for Thunderbolt storage and display device"
+msgstr ""
+
+#. description
+#: ../jobs/thunderbolt.pxu:68
+msgid ""
+"PURPOSE:\n"
+" This test will check if your system can support daisy-chaining of a "
+"storage\n"
+" and a monitor over Thunderbolt port\n"
+"STEPS:\n"
+" 1. Connect your Thunderbolt monitor to your systems\n"
+" 2. Connect and mount your Thunderbolt HDD to another Thunderbolt port of "
+"the\n"
+" monitor (you can do this with HDD first as well)\n"
+" 3. Click 'Test' to perform the storage test on the Thunderbolt HDD\n"
+"VERIFICATION:\n"
+" 1. The verification for storage is automated, please select the result "
+"combine\n"
+" with the result for the display.\n"
+" 2. Was the desktop displayed correctly on the Thunderbolt-connected "
+"screen?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:6
+msgid ""
+"PURPOSE:\n"
+" Touchpad manual verification\n"
+"STEPS:\n"
+" 1. Make sure that touchpad is enabled.\n"
+" 2. Move cursor using the touchpad.\n"
+"VERIFICATION:\n"
+" Did the cursor move?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:23
+msgid ""
+"PURPOSE:\n"
+" Touchpad horizontal scroll verification\n"
+"STEPS:\n"
+" 1. Select \"Test\" when ready and place your cursor within the borders "
+"of the displayed test window.\n"
+" 2. Verify that you can move the horizontal slider by moving your finger "
+"right and left in the lower part of the touchpad.\n"
+"VERIFICATION:\n"
+" Could you scroll right and left?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:40
+msgid ""
+"PURPOSE:\n"
+" Touchpad vertical scroll verification\n"
+"STEPS:\n"
+" 1. Select \"Test\" when ready and place your cursor within the borders "
+"of the displayed test window.\n"
+" 2. Verify that you can move the vertical slider by moving your finger up "
+"and down in the right part of the touchpad.\n"
+"VERIFICATION:\n"
+" Could you scroll up and down?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:57
+msgid ""
+"Determine whether the touchpad is detected as a singletouch device "
+"automatically."
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:68
+msgid ""
+"Determine whether the touchpad is detected as a multitouch device "
+"automatically."
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:77
+msgid ""
+"PURPOSE:\n"
+" Touchpad manual detection of multitouch.\n"
+"STEPS:\n"
+" 1. Look at the specifications for your system.\n"
+"VERIFICATION:\n"
+" Is the touchpad supposed to be multitouch?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:90
+msgid ""
+"PURPOSE:\n"
+" Determine that the hot corner feature is working as expected\n"
+"STEPS:\n"
+" 1. Launch a browser.\n"
+" 2. Go to a website, and hover the cursor over a link.\n"
+" 3. Tap the upper right corner on the touchpad.\n"
+"VERIFICATION:\n"
+" Did the tap trigger a new tab to be opened?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:105
+msgid ""
+"PURPOSE:\n"
+" Determine that the selection window function is working as expected.\n"
+"STEPS:\n"
+" 1. Open a file folder\n"
+" 2. Double tap and drag the cursor across several file.\n"
+"VERIFICATION:\n"
+" Did a selection window open and were several files selected?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:120
+msgid ""
+"PURPOSE:\n"
+" Determine that the right click function is working as expected.\n"
+"STEPS:\n"
+" 1. Open a file folder\n"
+" 2. Hover cursor over file in folder\n"
+" 3. 2-touch tap.\n"
+"VERIFICATION:\n"
+" Did the right click pop up menu appear?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:136
+msgid ""
+"PURPOSE:\n"
+" Touchpad 2-touch horizontal scroll verification\n"
+"STEPS:\n"
+" 1. Select \"Test\" when ready and place your cursor within the borders "
+"of the displayed test window.\n"
+" 2. Verify that you can move the horizontal slider by moving 2 fingers "
+"right and left along the touchpad.\n"
+"VERIFICATION:\n"
+" Could you scroll right and left?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:151
+msgid ""
+"PURPOSE:\n"
+" Touchpad 2-touch vertical scroll verification\n"
+"STEPS:\n"
+" 1. Select \"Test\" when ready and place your cursor within the borders "
+"of the displayed test window.\n"
+" 2. Verify that you can move the vertical slider by moving 2 fingers up "
+"and down along the touchpad.\n"
+"VERIFICATION:\n"
+" Could you scroll up and down?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:165
+msgid ""
+"PURPOSE:\n"
+" Determine that the drag and drop function is working as expected.\n"
+"STEPS:\n"
+" 1. Browse to the examples folder in the current user's home directory\n"
+" 2. Double tap and hold to select the \"Ubuntu_Free_Culture_Showcase\" "
+"folder\n"
+" 2. Drag the selected folder to the desktop and remove finger from "
+"touchpad.\n"
+"VERIFICATION:\n"
+" Did a selected folder move to the desktop?"
+msgstr ""
+
+#. summary
+#: ../jobs/touchpad.txt.in:181
+msgid "Check touchpad pinch-to-zoom gesture"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:182
+msgid ""
+"PURPOSE:\n"
+" Check touchpad pinch gesture for zoom\n"
+"STEPS:\n"
+" 1. Open gallery-app with an image\n"
+" 2. Place two fingers on the touchpad and pinch them together\n"
+" 3. Place two fingers on the touchpad and move them apart\n"
+"VERIFICATION:\n"
+" Does the image zoom in and out?"
+msgstr ""
+
+#. summary
+#: ../jobs/touchpad.txt.in:198
+msgid "Check 4-finger tap gesture"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:199
+msgid ""
+"PURPOSE:\n"
+" Validate that 4-touch tap is operating as expected\n"
+"STEPS:\n"
+" 1. 4-touch tap (tap with 4 fingers) anywhere on the touchpad\n"
+"VERIFICATION:\n"
+" Did the tap open the Dash?"
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:220
+msgid "This test will check if your touchpad was detected as a mouse."
+msgstr ""
+
+#. description
+#: ../jobs/touchpad.txt.in:229
+msgid ""
+"PURPOSE:\n"
+" Touchpad continuous move verification\n"
+"STEPS:\n"
+" 1. Select \"Test\" when ready and continuously move your cursor within "
+"the borders of the displayed test window.\n"
+" You'll need to keep moving your finger on the touchpad for 10 seconds.\n"
+"VERIFICATION:\n"
+" Did the mouse cursor move without interruption?"
+msgstr ""
+
+#. name
+#: ../jobs/touchscreen.txt.in:3
+msgid "Touchscreen"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:13
+msgid ""
+"Determine whether the screen is detected as a non-touch device automatically."
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:23
+msgid ""
+"Determine whether the screen is detected as a multitouch device "
+"automatically."
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:31
+msgid ""
+"PURPOSE:\n"
+" Touchscreen capability manual detection.\n"
+"STEPS:\n"
+" 1. Look at the specifications for your system.\n"
+"VERIFICATION:\n"
+" Your screen was detected as a non touch screen. Select PASS if this is "
+"correct."
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:59
+msgid ""
+"PURPOSE:\n"
+" Check touchscreen drag & drop\n"
+"STEPS:\n"
+" 1. Tap and hold an object on the desktop\n"
+" 2. Drag and drop the object in a different location\n"
+"VERIFICATION:\n"
+" Does drag and drop work?"
+msgstr ""
+
+#. summary
+#: ../jobs/touchscreen.txt.in:71
+msgid "Check touchscreen pinch gesture for zoom"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:76
+msgid ""
+"PURPOSE:\n"
+" Check touchscreen pinch gesture for zoom\n"
+"STEPS:\n"
+" 1. Commence the test\n"
+" 2. Using 2 fingers, resize the blue square until it turns green, then "
+"release it.\n"
+"VERIFICATION:\n"
+" Did the blue square change size following the gesture?"
+msgstr ""
+
+#. summary
+#: ../jobs/touchscreen.txt.in:88
+msgid "Check touchscreen pinch gesture for rotate"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:93
+msgid ""
+"PURPOSE:\n"
+" Check touchscreen pinch gesture for rotate\n"
+"STEPS:\n"
+" 1. Commence the test\n"
+" 2. Using 2 fingers, rotate the blue square until it turns green, then "
+"release it.\n"
+"VERIFICATION:\n"
+" Did the blue square rotate following the gesture?"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:108
+msgid ""
+"PURPOSE:\n"
+" Validate that 3-touch drag is operating as expected\n"
+"STEPS:\n"
+" 1. Open a windows and bring it to the foreground\n"
+" 2. 3-touch the window and drag\n"
+"VERIFICATION:\n"
+" Did the window move along with the drag?"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:123
+msgid ""
+"PURPOSE:\n"
+" Validate that 4-touch tap is operating as expected\n"
+"STEPS:\n"
+" 1. 4-touch tap anywhere on the touchscreen\n"
+"VERIFICATION:\n"
+" Did the tap open the Dash?"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:137
+msgid ""
+"PURPOSE:\n"
+" Validate that 3-touch tap is operating as expected\n"
+"STEPS:\n"
+" 1. Commence the test\n"
+" 2. Tap the screen within the test area with 3 fingers simultaneously.\n"
+" 3. Once 3 fingers are on the screen you should see the indicator they "
+"are recognized.\n"
+"VERIFICATION:\n"
+" Did you see the green circles around the three fingers?"
+msgstr ""
+
+#. description
+#: ../jobs/touchscreen.txt.in:160
+msgid ""
+"PURPOSE:\n"
+" Validate that 4-touch tap is operating as expected\n"
+"STEPS:\n"
+" 1. Commence the test\n"
+" 2. Tap the screen within the test area with 4 fingers simultaneously.\n"
+" 3. Once 4 fingers are on the screen you should see the indicator they "
+"are recognized.\n"
+"VERIFICATION:\n"
+" Did you see the green circles around the four fingers?"
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:6
+msgid "Detects and shows USB devices attached to this system."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:14
+msgid ""
+"PURPOSE:\n"
+" This test will check that your system detects USB storage devices.\n"
+"STEPS:\n"
+" 1. Plug in one or more USB keys or hard drives.\n"
+" 2. Click on \"Test\".\n"
+"VERIFICATION:\n"
+" Were the drives detected?"
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:29
+msgid ""
+"PURPOSE:\n"
+" This test will check that you can use a USB HID device\n"
+"STEPS:\n"
+" 1. Enable either a USB mouse or keyboard\n"
+" 2. For mice, perform actions such as moving the pointer, right and left "
+"button clicks and double clicks\n"
+" 3. For keyboards, commence the test to launch a small tool. Type some "
+"text and close the tool.\n"
+"VERIFICATION:\n"
+" Did the device work as expected?"
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:45
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the insertion of\n"
+" a USB storage device\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a USB storage device\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not unplug the device after the test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:64
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the insertion of\n"
+" a USB 3.0 storage device\n"
+"STEPS:\n"
+" 1. Click \"Test\" and insert a USB 3.0 storage device in a USB 3.0 "
+"port.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not unplug the device after the test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:82
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal of\n"
+" a USB storage device\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the USB device.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:101
+msgid ""
+"PURPOSE:\n"
+" This test will check that the system correctly detects the removal of\n"
+" a USB 3.0 storage device\n"
+"STEPS:\n"
+" 1. Click \"Test\" and remove the USB 3.0 device.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:119
+msgid ""
+"PURPOSE:\n"
+" This test will check your USB connection.\n"
+"STEPS:\n"
+" 1. Plug a USB HDD or thumbdrive into the computer.\n"
+" 2. An icon should appear on the Launcher.\n"
+" 3. Click \"Test\" to begin the test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:139
+msgid ""
+"PURPOSE:\n"
+" This test will check your USB 3.0 connection.\n"
+"STEPS:\n"
+" 1. Plug a USB 3.0 HDD or thumbdrive into a USB 3.0 port in the "
+"computer.\n"
+" 2. An icon should appear on the Launcher.\n"
+" 3. Click \"Test\" to begin the test.\n"
+"VERIFICATION:\n"
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:157
+msgid "This test is automated and executes after the usb/insert test is run."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:169
+msgid ""
+"This test is automated and executes after the usb3/insert test is run."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:178
+msgid ""
+"Tests USB 2.0 or 1.1 ports on a system by doing write/read/compare tests on "
+"randomly created data. It requires that a USB stick is plugged into an "
+"available USB port before running the certification suite."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:191
+msgid ""
+"Tests USB 3.0 ports on a system by doing write/read/compare tests on "
+"randomly created data. It requires that a USB stick is plugged into an "
+"available USB port before running the certification suite. Additionally, it "
+"will only work with USB sticks and ports rated for USB 3.0 speeds or faster."
+msgstr ""
+
+#. description
+#: ../jobs/usb.txt.in:200
+msgid ""
+"PURPOSE:\n"
+" This test will check your USB connection.\n"
+"STEPS:\n"
+" 1. Connect a USB storage device to an external USB slot on this "
+"computer.\n"
+" 2. An icon should appear on the Launcher.\n"
+" 3. Confirm that the icon appears.\n"
+" 4. Eject the device.\n"
+" 5. Repeat with each external USB slot.\n"
+"VERIFICATION:\n"
+" Do all USB slots work with the device?"
+msgstr ""
+
+#. description
+#: ../jobs/virtualization.txt.in:12
+msgid ""
+"Verifies that a KVM guest can be created and booted using an Ubuntu Server "
+"cloud image."
+msgstr ""
+
+#. summary
+#: ../jobs/virtualization.txt.in:15
+msgid "Verify KVM VM boots"
+msgstr ""
+
+#. description
+#: ../jobs/virtualization.txt.in:25
+msgid "Test to verify that the Xen Hypervisor is running."
+msgstr ""
+
+#. summary
+#: ../jobs/virtualization.txt.in:27
+msgid "Verify Xen is running"
+msgstr ""
+
+#. description
+#: ../jobs/virtualization.txt.in:37
+msgid "Test to check that a Xen domU image can boot and run on Xen on Ubuntu"
+msgstr ""
+
+#. summary
+#: ../jobs/virtualization.txt.in:39
+msgid "Verify Xen domU can boot"
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:22
+msgid "Wireless scanning test. It scans and reports on discovered APs."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:32
+msgid ""
+"This is an automated test to gather some info on the current state of your "
+"wireless devices. If no devices are found, the test will exit with an error."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:41
+msgid ""
+"PURPOSE:\n"
+" This test will check your wireless connection.\n"
+"STEPS:\n"
+" 1. Click on the Network icon in the panel.\n"
+" 2. Select a network below the 'Wireless networks' section.\n"
+" 3. Click \"Test\" to verify that it's possible to establish an HTTP "
+"connection.\n"
+"VERIFICATION:\n"
+" Did a notification show and was the connection correctly established?"
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:77
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using WPA "
+"security and the 802.11b/g protocols."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:107
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using no "
+"security and the 802.11b/g protocols."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:137
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using WPA "
+"security and the 802.11n protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:167
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using no "
+"security and the 802.11n protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:198
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using WPA "
+"security and the 802.11ac protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:229
+msgid ""
+"Tests that the systems wireless hardware can connect to a router using no "
+"security and the 802.11ac protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:259
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using "
+"WPA\n"
+" security and the 802.11b/g protocols.\n"
+"STEPS:\n"
+" 1. Open your router's configuration tool\n"
+" 2. Change the settings to only accept connections on the B and G "
+"wireless bands\n"
+" 3. Make sure the SSID is set to the contents of the ROUTER_SSID "
+"environment variable\n"
+" 4. Change the security settings to use WPA2 and ensure the PSK matches "
+"what is set in the ROUTER_PSK environment variable\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:298
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using\n"
+" no security and the 802.11b/g protocols.\n"
+"STEPS:\n"
+" 1. Open your router's configuration tool\n"
+" 2. Change the settings to only accept connections on the B and G "
+"wireless bands\n"
+" 3. Make sure the SSID is set to the contents of the ROUTER_SSID "
+"environment variable\n"
+" 4. Change the security settings to use no security\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:338
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using "
+"WPA\n"
+" security and the 802.11n protocols.\n"
+"STEPS:\n"
+" 1. Open your router's configuration tool\n"
+" 2. Change the settings to only accept connections on the N wireless "
+"band\n"
+" 3. Make sure the SSID is set to the contents of the ROUTER_SSID "
+"environment variable\n"
+" 4. Change the security settings to use WPA2 and ensure the PSK matches "
+"what is set in the ROUTER_PSK environment variable\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:378
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using\n"
+" no security and the 802.11n protocol.\n"
+"STEPS:\n"
+" 1. Open your router's configuration tool\n"
+" 2. Change the settings to only accept connections on the N wireless "
+"band\n"
+" 3. Make sure the SSID is set to the contents of the ROUTER_SSID "
+"environment variable\n"
+" 4. Change the security settings to use no security\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:418
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using "
+"WPA\n"
+" security and the 802.11ac protocol.\n"
+"STEPS:\n"
+" 1. Open your router's configuration tool\n"
+" 2. Change the settings to only accept connections with the 802.11ac "
+"protocol.\n"
+" 3. Make sure the SSID is set to the contents of the ROUTER_SSID "
+"environment variable\n"
+" 4. Change the security settings to use WPA2 and ensure the PSK matches "
+"what is set in the ROUTER_PSK environment variable\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:458
+msgid ""
+"PURPOSE:\n"
+" Tests that the systems wireless hardware can connect to a router using\n"
+" no security and the 802.11ac protocol.\n"
+"STEPS:\n"
+" 1. Open your router's configuration tool\n"
+" 2. Change the settings to only accept connections with the 802.11ac "
+"protocol.\n"
+" 3. Make sure the SSID is set to the contents of the ROUTER_SSID "
+"environment variable\n"
+" 4. Change the security settings to use no security\n"
+" 5. Commence the test to create a connection to the router and test the "
+"connection\n"
+"VERIFICATION:\n"
+" Verification is automated, do not change the automatically selected "
+"result."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:497
+msgid ""
+"Tests the performance of a system's wireless connection through the iperf "
+"tool."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:526
+msgid ""
+"Tests the performance of a system's wireless connection through the iperf "
+"tool, using UDP packets."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:555
+msgid ""
+" Test that the system's wireless hardware can connect to a router using the\n"
+" 802.11a protocol. This requires that you have a router pre-configured to "
+"only\n"
+" respond to requests on the 802.11a protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:585
+msgid ""
+" Test that the system's wireless hardware can connect to a router using the\n"
+" 802.11b protocol. This requires that you have a router pre-configured to "
+"only\n"
+" respond to requests on the 802.11b protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:604
+msgid ""
+"This test executes iperf to generate a load on the network device "
+"{__index__} ({interface}) and then performs a ping test to watch for dropped "
+"packets and very large latency periods."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:632
+msgid ""
+" Test that the system's wireless hardware can connect to a router using the\n"
+" 802.11g protocol. This requires that you have a router pre-configured to "
+"only\n"
+" respond to requests on the 802.11g protocol."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:643
+msgid ""
+"Test that the MAC80211 modules are loaded and wireless extensions are "
+"working."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:655
+msgid ""
+"This test executes iwconfig requests against wireless device {__index__} "
+"({interface})."
+msgstr ""
+
+#. description
+#: ../jobs/wireless.txt.in:664
+msgid ""
+"PURPOSE:\n"
+" This test will check whether or not your driver responds to rfkill "
+"commands.\n"
+"STEPS:\n"
+" 1. Use the hardware switch on the side of your device to switch off "
+"wireless.\n"
+" 2. If you do not have a hardware switch disable wireless from the "
+"network manager icon in the panel\n"
+" 3. Click \"Test\" to verify that the hard or soft blocks are in place.\n"
+"VERIFICATION:\n"
+" Did the hard or soft blocks show on in the dialog?"
+msgstr ""
+
+#. purpose
+#: ../jobs/wireless.txt.in:688
+msgid ""
+"User verification of whether the observed transfer throughput is acceptable "
+"for the type and maximum speed of wireless device {__index__} ({interface})."
+msgstr ""
+
+#. name
+#: ../units/autotesting.pxu:2
+msgid "Automated Tests"
+msgstr ""
+
+#. description
+#: ../units/autotesting.pxu:4
+msgid ""
+" This test plan is used for automated testing of the test cases "
+"themselves.\n"
+" The resources jobs are needed for a valid submission, so they are "
+"included\n"
+" explicitly, even if they are usually run implicitly by jobs requiring "
+"them."
+msgstr ""
+
+#. name
+#: ../units/default.pxu:2
+msgid "Default Tests"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:4
+msgid "Docking test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:5
+msgid " This test will check the device can be used after docking."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:7
+msgid " 1. Dock the device to the docking unit."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:9
+msgid " Is the device working as expected after being docked?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:15
+msgid "DisplayPort test on the dock"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:17
+msgid " This test will check the DisplayPort(s) on the dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:29
+msgid "DVI port test on the dock"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:31
+msgid " This test will check the DVI port(s) on the dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:43
+msgid "HDMI port test on the dock"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:45
+msgid " This test will check the HDMI port(s) on the dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:57
+msgid "VGA port test on the dock"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:59
+msgid " This test will check the VGA port(s) on the dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:71
+msgid "Multiple monitors test while docked"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:73
+msgid ""
+" This test verifies that multi-monitor output works using the dock. You "
+"will need at least two external monitors to perform this test."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:75
+msgid ""
+" Skip this test if your video card or the dock do not support multiple "
+"monitors.\n"
+" 1. If your dock provides more than one monitor outputs, connect two "
+"monitors\n"
+" 2. Open the \"Displays\" tool (open the dash and search for "
+"\"Displays\")\n"
+" 3. Configure your output to provide one desktop across all the monitors\n"
+" 4. Open any application and drag its window from one monitor to the next."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:81
+msgid ""
+" Was the stretched desktop displayed correctly across all the screens?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:87
+msgid "Video Out hotkey test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:89
+msgid " Validate that the External Video hotkey is working as expected"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:91
+msgid ""
+" 1. Plug in an external monitor\n"
+" 2. Press the display hotkey to change the monitors configuration"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:94
+msgid ""
+" Check that the video signal can be mirrored, extended, displayed on "
+"external or onboard only."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:102
+msgid "List audio devices"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:117
+msgid "HDMI audio test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:127
+msgid " Dock HDMI audio interface verification"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:129
+msgid ""
+" 1. Plug an external HDMI device with sound to the dock (use only one "
+"HDMI/DisplayPort/Thunderbolt interface at a time for this test)\n"
+" 2. Go to the Sound settings and make sure the correct Output is selected\n"
+" 3. Click the Test button"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:143
+msgid "DisplayPort audio test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:153
+msgid " Dock DisplayPort audio interface verification"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:155
+msgid ""
+" 1. Plug an external DisplayPort device with sound to the dock (use only "
+"one HDMI/DisplayPort/Thunderbolt interface at a time for this test)\n"
+" 2. Go to the Sound settings and make sure the correct Output is selected\n"
+" 3. Click the Test button"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:165
+msgid "Headphones output test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:179
+msgid ""
+" This test will check that headphones connector works correctly.\n"
+" (Skip this test if there is no headphone connector on the dock)"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:182
+msgid ""
+" 1. Connect a pair of headphones to the dock\n"
+" 2. Click the Test button to play a sound to your audio device"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:185
+msgid ""
+" Did you hear a sound through the headphones and did the sound play "
+"without any distortion, clicks or other strange noises from your headphones?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:191
+msgid "External microphone plugged to the dock to record sound test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:205
+msgid ""
+" This test will check that recording sound using an external microphone "
+"works correctly\n"
+" (Skip this test if the dock does not have a microphone connector)"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:208
+msgid ""
+" 1. Connect a microphone to the dock's microphone port\n"
+" 2. Click \"Test\", then speak into the external microphone\n"
+" 3. After a few seconds, your speech will be played back to you"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:212
+msgid " Did you hear your speech played back?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:218
+msgid "Collect audio-related system information"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:230
+msgid "Attach audio hardware data log to results"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:239
+msgid "Line-out connection test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:240
+msgid ""
+" Check that external line-out connection works correctly\n"
+" (Skip this test if dock does not have a line out connector)"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:243
+msgid ""
+" 1. Insert cable to speakers (with built-in amplifiers) on the dock's "
+"line-out port\n"
+" 2. Open system sound preferences, 'Output' tab, select 'Line-out' on the "
+"connector list. Click the Test button\n"
+" 3. On the system sound preferences, select 'Internal Audio' on the "
+"device list and click 'Test Speakers' to check left and right channel"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:247
+msgid ""
+" 1. Do you hear a sound in the speakers? The internal speakers should "
+"*not* be muted automatically\n"
+" 2. Do you hear the sound coming out on the corresponding channel?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:255
+msgid "Line-in connection test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:268
+msgid ""
+" Check that external line-in connection works correctly\n"
+" (Skip this test if the dock does not have a line in connector)"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:271
+msgid ""
+" 1. Use a cable to connect the dock's line-in port to an external line-out "
+"source.\n"
+" 2. Open system sound preferences, 'Input' tab, select 'Line-in' on the "
+"connector list. Click the Test button\n"
+" 3. After a few seconds, your recording will be played back to you."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:275
+msgid " Did you hear your recording?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:282
+msgid "Headphones recognized when plugged to the dock test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:287
+msgid ""
+" Check that system detects speakers or headphones being plugged in\n"
+" (Skip this test if the dock does not have headphones connector)"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:290
+msgid ""
+" 1. Prepare a pair of headphones or speakers with a standard 3.5mm jack\n"
+" 2. Locate the speaker / headphone jack on the dock under test\n"
+" 3. Run the test (you have 30 seconds from now on)\n"
+" 4. Plug headphones or speakers into the appropriate jack\n"
+" 5. Unplug the device for subsequent tests."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:304
+msgid "Microphone recognized when plugged to the dock test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:309
+msgid ""
+" Check that system detects a microphone being plugged in\n"
+" (Skip this test if the dock does not have a microphone connector)"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:312
+msgid ""
+" 1. Prepare a microphone with a standard 3.5mm jack\n"
+" 2. Locate the microphone jack on the dock under test.\n"
+" Keep in mind that it may be shared with the headphone jack.\n"
+" 3. Run the test (you have 30 seconds from now on)\n"
+" 4. Plug the microphone into the appropriate jack\n"
+" 5. Unplug the device for subsequent tests."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:319
+msgid ""
+" Verification is automatic, no action is required.\n"
+" The test times out after 30 seconds (and fails in that case)."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:330
+msgid "Ping test using dock's Ethernet connectivity"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:331
+msgid " Tests whether the system has a working Internet connection."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:337
+msgid ""
+" Was the test able to ping the network using the Ethernet connection?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:347
+msgid "NTP sync test using dock's Ethernet connectivity"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:348
+msgid " Test to see if we can sync local clock to an NTP server"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:350
+msgid ""
+" 1. Make sure the dock is connected to network using an Ethernet cable\n"
+" 2. Make sure the laptop itself is not connected to any Ethernet cable\n"
+" 3. Launch the test"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:354
+msgid ""
+" Was the test able to synchronize system time using the Ethernet "
+"connection?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:362
+msgid "USB HID device test"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:376
+msgid "USB drive insertion test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:378
+msgid ""
+" This test will check that the system correctly detects the insertion of\n"
+" a USB storage device plugged on the dock"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:395
+msgid "USB3 drive insertion test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:397
+msgid ""
+" This test will check that the system correctly detects the insertion of\n"
+" a USB 3.0 storage device"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:414
+msgid "USB drive removal test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:416
+msgid ""
+" This test will check that the system correctly detects the removal of\n"
+" a USB storage device"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:430
+msgid "USB3 drive removal test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:432
+msgid ""
+" This test will check that the system correctly detects the removal of\n"
+" a USB 3.0 storage device"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:447
+msgid "USB drive storage test"
+msgstr ""
+
+#. description
+#: ../units/dock.pxu:449
+msgid ""
+"This test is automated and executes after the dock/usb_insert test is run."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:457
+msgid "USB3 drive storage test"
+msgstr ""
+
+#. description
+#: ../units/dock.pxu:459
+msgid ""
+"This test is automated and executes after the dock/usb3_insert test is run."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:465
+msgid "Battery charging when docked test"
+msgstr ""
+
+#. description
+#: ../units/dock.pxu:471
+msgid ""
+"This test will make sure the laptop is being charged while connected to the "
+"dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:478
+msgid "Network status before suspend"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:485
+msgid "Audio status before suspend"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:495
+msgid "Suspend the device, dock it and resume it"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:496
+msgid ""
+" This test will check the device can be suspended, docked and resumed "
+"properly"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:498
+msgid ""
+" 1. If the laptop is currently docked, undock it now\n"
+" 2. Suspend the laptop (e.g. by closing its lid)\n"
+" 3. Dock the laptop\n"
+" 4. Resume the laptop (e.g. by pressing the Power button on the dock)"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:503
+msgid " Is the device working as expected after being docked and resumed?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:511
+msgid "Network gateway ping after suspend"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:518
+msgid "USB drive insertion after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:520
+msgid ""
+" This test will check that the system correctly detects the insertion of\n"
+" a USB storage device plugged on the dock after suspend"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:523
+msgid ""
+" 1. Click \"Test\" and insert a USB storage device, preferably a HDD,\n"
+" in one of the dock's port.\n"
+" Although a USB pen drive may be used it might cause performance\n"
+" related tests to fail. (Note: this test will time-out after 20\n"
+" seconds.)\n"
+" 2. Do not unplug the device after the test."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:538
+msgid "USB3 drive insertion after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:540
+msgid ""
+" This test will check that the system correctly detects the insertion of\n"
+" a USB 3.0 storage device after suspend"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:543
+msgid ""
+" 1. Click \"Test\" and insert a USB 3.0 storage device, preferably a HDD,\n"
+" in one of the dock's USB 3.0 port. Although a USB 3.0 pen drive may\n"
+" be used it might cause performance related tests to fail.\n"
+" (Note: this test will time-out after 20 seconds.)\n"
+" 2. Do not unplug the device after the test."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:557
+msgid "USB drive removal after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:559
+msgid ""
+" This test will check that the system correctly detects the removal of\n"
+" a USB storage device after suspend"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:562
+msgid ""
+" 1. Click \"Test\" and remove the USB device from the dock.\n"
+" (Note: this test will time-out after 20 seconds.)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:573
+msgid "USB3 drive removal after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:575
+msgid ""
+" This test will check that the system correctly detects the removal of\n"
+" a USB 3.0 storage device after suspend"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:578
+msgid ""
+" 1. Click \"Test\" and remove the USB 3.0 device from the dock.\n"
+" (Note: this test will time-out after 20 seconds.)"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:581
+msgid ""
+" The verification of this test is automated. Do not change the\n"
+" automatically selected result."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:590
+msgid "USB drive storage test after resuming"
+msgstr ""
+
+#. description
+#: ../units/dock.pxu:592
+msgid ""
+"This test is automated and executes after the dock/usb-insert test is run."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:600
+msgid "USB3 drive storage test after resuming"
+msgstr ""
+
+#. description
+#: ../units/dock.pxu:602
+msgid ""
+"This test is automated and executes after the dock/usb3-insert test is run."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:609
+msgid "USB HID device test after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:611
+msgid " This test will check that you can use a USB HID device"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:613
+msgid ""
+" 1. Enable either a USB mouse or keyboard\n"
+" 2. For mice, perform actions such as moving the pointer, right and left "
+"button clicks and double clicks\n"
+" 3. For keyboards, click the Test button to lauch a small tool. Type some "
+"text and close the tool."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:617
+msgid " Did the device work as expected?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:623
+msgid "DisplayPort test on the dock after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:625
+msgid ""
+" This test will check the DisplayPort(s) on the dock after resuming."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:627
+msgid ""
+" Skip this test if the dock does not have a DisplayPort.\n"
+" 1. Connect a display (if not already connected) to the DisplayPort on the "
+"dock\n"
+" 2. Repeat step 1 for each additional DisplayPorts, if any"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:637
+msgid "DVI port test on the dock after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:639
+msgid " This test will check the DVI port(s) on the dock after resuming."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:641
+msgid ""
+" Skip this test if the dock does not have a DVI port.\n"
+" 1. Connect a display (if not already connected) to the DVI port on the "
+"dock\n"
+" 2. Repeat step 1 for each additional DVI port, if any"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:651
+msgid "HDMI port test on the dock after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:653
+msgid " This test will check the HDMI port(s) on the dock after resuming."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:655
+msgid ""
+" Skip this test if the dock does not have a HDMI port.\n"
+" 1. Connect a display (if not already connected) to the HDMI port on the "
+"dock\n"
+" 2. Repeat step 1 for each additional HDMI port, if any"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:665
+msgid "VGA port test on the dock after resuming"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:667
+msgid " This test will check the VGA port(s) on the dock after resuming."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:669
+msgid ""
+" Skip this test if the dock does not have a VGA port.\n"
+" 1. Connect a display (if not already connected) to the VGA port on the "
+"dock\n"
+" 2. Repeat step 1 for each additional VGA port, if any"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:679
+msgid "Suspend the device, undock it and resume it"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:680
+msgid ""
+" This test will check the device can be suspended, undocked and resumed "
+"properly"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:682
+msgid ""
+" 1. If the laptop is currently undocked, dock it now\n"
+" 2. Suspend the laptop (e.g. by closing its lid)\n"
+" 3. Undock the laptop\n"
+" 4. Resume the laptop (e.g. by pressing its Power button)"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:687
+msgid ""
+" Is the device working as expected after being undocked and resumed?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:694
+msgid "Wireless connection after suspend (WPA BG)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:717
+msgid "Wireless connection after suspend (Open BG)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:740
+msgid "Wireless connection after suspend (WPA N)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:763
+msgid "Wireless connection after suspend (Open N)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:786
+msgid "Wireless connection after suspend (WPA AC)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:810
+msgid "Wireless connection after suspend (Open AC)"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:833
+msgid "Audio after resuming test"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:846
+msgid "Record playback after resuming"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:863
+msgid "ExpressCard slot verification"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:865
+msgid ""
+" This will verify that an ExpressCard slot on the dock can detect inserted "
+"devices."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:867
+msgid ""
+" Skip this test if you do not have an ExpressCard slot on the dock.\n"
+" 1. Plug an ExpressCard device into the ExpressCard slot"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:870
+msgid " Was the device correctly detected?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:876
+msgid "FireWire HDD insertion test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:879
+msgid ""
+" This test will check the system can detect the insertion of a FireWire "
+"HDD on the dock"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:881
+msgid ""
+" (Skip this test id there is no FireWire connector on the dock)\n"
+" 1. Click 'Test' to begin the test. This test will\n"
+" timeout and fail if the insertion has not been detected within 20 "
+"seconds.\n"
+" 2. Plug a FireWire HDD into an available FireWire port."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:893
+msgid "FireWire HDD storage test"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:904
+msgid "FireWire HDD removal test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:907
+msgid ""
+" This test will check the system can detect the removal of a FireWire HDD"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:909
+msgid ""
+" 1. Click 'Test' to begin the test. This test will timeout and fail if\n"
+" the removal has not been detected within 20 seconds.\n"
+" 2. Remove the previously attached FireWire HDD from the FireWire port on\n"
+" the dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:921
+msgid "eSATA HDD insertion test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:924
+msgid ""
+" This test will check the system can detect the insertion of an eSATA HDD "
+"on the dock"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:926
+msgid ""
+" (Skip this test if there are no eSATA connectors on the dock)\n"
+" 1. Click 'Test' to begin the test. This test will\n"
+" timeout and fail if the insertion has not been detected within 20 "
+"seconds.\n"
+" 2. Plug an eSATA HDD into an available eSATA port on the dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:938
+msgid "eSATA HDD storage test"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:949
+msgid "eSATA HDD removal test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:952
+msgid ""
+" This test will check the system can detect the removal of an eSATA HDD "
+"from the dock"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:954
+msgid ""
+" 1. Click 'Test' to begin the test. This test will timeout and fail if\n"
+" the removal has not been detected within 20 seconds.\n"
+" 2. Remove the previously attached eSATA HDD from the eSATA port on the "
+"dock."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:966
+msgid "Optical media (CD) read test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:967
+msgid " This test will check the dock's ability to read CD media"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:969
+msgid ""
+" (Skip this test if the dock does not have an optical reader)\n"
+" 1. Insert appropriate non-blank media into your optical drive(s). Movie "
+"and Audio Disks may not work. Self-created data disks have the greatest "
+"chance of working.\n"
+" 2. Try to copy a few files from the optical media to the computer."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:973
+msgid " Are the files properly copied to the computer?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:980
+msgid "Optical media (CD-RW, DVD-RW) writing test"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:981
+msgid ""
+" This test will check the dock's ability to write CD/DVD media.\n"
+" Depending on what the dock's optical drive support, you will need\n"
+" a blank CD-R, CD-RW, DVD-R and/or DVD-RW."
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:985
+msgid ""
+" 1. Insert a blank CD-R into the dock's drive\n"
+" 2. Open Brasero Disc Burner and write some files on the CD-R\n"
+" 3. Repeat steps 1-2 for other compatible media (CD-RW, DVD-R, DVD-RW)"
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:989
+msgid " Are all kinds of discs properly written?"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:997
+msgid "Thunderbolt storage insertion detection"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:998
+msgid ""
+" This test will check if the connection of a Thunderbolt HDD to the dock "
+"could be detected"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:1000
+msgid ""
+" 1. Click 'Test' to begin the test. This test will\n"
+" timeout and fail if the insertion has not been detected within 40 "
+"seconds.\n"
+" 2. Plug a Thunderbolt HDD into an available Thunderbolt port on the "
+"dock;\n"
+" if it's not mounted automatically, please click the HDD icon to mount "
+"it."
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:1015
+msgid "Thunderbolt storage test"
+msgstr ""
+
+#. summary
+#: ../units/dock.pxu:1025
+msgid "Thunderbolt storage removal detection"
+msgstr ""
+
+#. purpose
+#: ../units/dock.pxu:1026
+msgid ""
+" This test will check the system can detect the removal of a Thunderbolt "
+"HDD"
+msgstr ""
+
+#. steps
+#: ../units/dock.pxu:1028
+msgid ""
+" 1. Click 'Test' to begin the test. This test will timeout and fail if\n"
+" the removal has not been detected within 20 seconds.\n"
+" 2. Remove the previously attached Thunderbolt HDD from the Thunderbolt "
+"port."
+msgstr ""
+
+#. verification
+#: ../units/dock.pxu:1032
+msgid ""
+" The verification of this test is automated. Do not change the "
+"automatically\n"
+" selected result"
+msgstr ""
+
+#. name
+#: ../units/hwsubmit.pxu:2
+msgid "All HW Information Submit Tests"
+msgstr ""
+
+#. name
+#: ../units/smoke.pxu:2
+msgid "All Smoke Tests"
+msgstr ""
+
+#. description
+#: ../units/smoke.pxu:4
+msgid ""
+" This is an example test plan to start from.\n"
+" To use, copy this file and add the jobs you want to run to the copy. "
+"Delete\n"
+" these comments. DO NOT delete the first 9 jobs in tis file.\n"
+" They are resource gathering jobs and are necessary to do any testing at "
+"all."
+msgstr ""