Translations by Joel Addison
Joel Addison has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
19. |
PURPOSE:
This test will check that a USB audio device works correctly
STEPS:
1. Connect a USB audio device to your system
2. Click "Test", then speak into the microphone
3. After a few seconds, your speech will be played back to you
VERIFICATION:
Did you hear your speech played back through the USB headphones?
|
|
2012-02-11 |
PURPOSE:
This test will check that a USB audio device works correctly
STEPS:
1. Connect a USB audio device to your system
2. Click "Test", then speak into the microphone
3. After a few seconds, your speech will be played back to you
VERIFICATION:
Did you hear your speech played back through the USB headphones?
|
|
20. |
Play back a sound on the default output and listen for it on the default input.
|
|
2012-09-22 |
Play back a sound on the default output and listen for it on the default input.
|
|
21. |
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.
|
|
2012-09-22 |
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.
|
|
22. |
Attaches the audio hardware data collection log to the results.
|
|
2012-09-22 |
Attaches the audio hardware data collection log to the results.
|
|
23. |
PURPOSE:
Check that the various audio channels are working properly
STEPS:
1. Click the Test button
VERIFICATION:
You should clearly hear a voice from the different audio channels
|
|
2012-09-22 |
PURPOSE:
Check that the various audio channels are working properly
STEPS:
1. Click the Test button
VERIFICATION:
You should clearly hear a voice from the different audio channels
|
|
24. |
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.
|
|
2012-09-22 |
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) recognised 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.
|
|
29. |
Benchmark for each disk
|
|
2012-02-17 |
Benchmark for each disk
|
|
31. |
Run Render-Bench XRender/Imlib2 benchmark
|
|
2012-09-22 |
Run Render-Bench XRender/Imlib2 benchmark
|
|
32. |
Run Qgears2 XRender Extension gearsfancy benchmark
|
|
2012-09-22 |
Run Qgears2 XRender Extension gearsfancy benchmark
|
|
33. |
Run Qgears2 XRender Extension image scaling benchmark
|
|
2012-09-22 |
Run Qgears2 XRender Extension image scaling benchmark
|
|
34. |
Run Qgears2 OpenGL gearsfancy benchmark
|
|
2012-09-22 |
Run Qgears2 OpenGL gearsfancy benchmark
|
|
73. |
PURPOSE:
This test will check that the built-in camera works
STEPS:
1. Click on Test to display a video capture from the camera for ten seconds.
VERIFICATION:
Did you see the video capture?
|
|
2012-02-11 |
PURPOSE:
This test will check that the built-in camera works
STEPS:
1. Click on Test to display a video capture from the camera for ten seconds.
VERIFICATION:
Did you see the video capture?
|
|
97. |
Check stats changes for each disk
|
|
2012-02-17 |
Check stats changes for each disk
|
|
110. |
This is an automated test which performs read/write operations on an attached FireWire HDD
|
|
2012-02-11 |
This is an automated test which performs read/write operations on an attached FireWire HDD
|
|
126. |
Check that VESA drivers are not in use
|
|
2012-02-11 |
Check that VESA drivers are not in use
|
|
129. |
Check that hardware is able to run compiz
|
|
2012-02-11 |
Check that hardware is able to run compiz
|
|
130. |
Check that hardware is able to run Unity 3D
|
|
2012-02-11 |
Check that hardware is able to run Unity 3D
|
|
250. |
This test is automated and executes after the mediacard/mmc-insert test is run. It tests reading and writing to the MMC card.
|
|
2012-02-17 |
This test is automated and executes after the mediacard/mmc-insert test is run. It tests reading and writing to the MMC card.
|
|
253. |
This test is automated and executes after the mediacard/sd-insert test is run. It tests reading and writing to the SD card.
|
|
2012-02-11 |
This test is automated and executes after the mediacard/sd-insert test is run. It tests reading and writing to the SD card.
|
|
257. |
This test is automated and executes after the mediacard/sdhc-insert test is run. It tests reading and writing to the SDHC card.
|
|
2012-02-17 |
This test is automated and executes after the mediacard/sdhc-insert test is run. It tests reading and writing to the SDHC card.
|
|
260. |
This test is automated and executes after the mediacard/cf-insert test is run. It tests reading and writing to the CF card.
|
|
2012-02-17 |
This test is automated and executes after the mediacard/cf-insert test is run. It tests reading and writing to the CF card.
|
|
263. |
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.
|
|
2012-02-17 |
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.
|
|
289. |
This test checks the amount of memory which is reporting in meminfo against the size of the memory modules detected by DMI.
|
|
2012-02-11 |
This test checks the amount of memory which is reporting in meminfo against the size of the memory modules detected by DMI.
|
|
296. |
Determine if we need to run tests specific to portable computers that may not apply to desktops.
|
|
2012-02-11 |
Determine if we need to run tests specific to portable computers that may not apply to desktops.
|
|
297. |
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)
|
|
2012-02-17 |
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)
|
|
316. |
This is an automated test to gather some info on the current state of your network devices. If no devices are found, the test will exit with an error.
|
|
2012-02-11 |
This is an automated test to gather some info on the current state of your network devices. If no devices are found, the test will exit with an error.
|
|
330. |
PURPOSE:
This test will check your CD audio playback capabilities
STEPS:
1. Insert an audio CD in your optical drive
2. When prompted, launch the Music Player
3. Locate the CD in the display of the Music Player
4. Select the CD in the Music Player
5. Click the Play button to listen to the music on the CD
6. Stop playing after some time
7. Right click on the CD icon and select "Eject Disc"
8. The CD should be ejected
9. Close the Music Player
VERIFICATION:
Did all the steps work?
|
|
2012-03-22 |
PURPOSE:
This test will check your CD audio playback capabilities
STEPS:
1. Insert an audio CD in your optical drive
2. When prompted, launch the Music Player
3. Locate the CD in the display of the Music Player
4. Select the CD in the Music Player
5. Click the Play button to listen to the music on the CD
6. Stop playing after some time
7. Right click on the CD icon and select "Eject Disc"
8. The CD should be ejected
9. Close the Music Player
VERIFICATION:
Did all the steps work?
|
|
335. |
PURPOSE:
This test will verify that the desktop clock synchronizes with the system clock.
STEPS:
1. Click the "Test" button and verify the clock moves ahead by 1 hour.
Note: It may take a minute or so for the clock to refresh
2. Right click on the clock, then click on "Time & Date Settings..."
3. Ensure that your clock application is set to manual.
4. Change the time 1 hour back
5. Close the window and reboot
VERIFICATION:
Is your system clock displaying the correct date and time for your timezone?
|
|
2012-02-11 |
PURPOSE:
This test will verify that the desktop clock synchronises with the system clock.
STEPS:
1. Click the "Test" button and verify the clock moves ahead by 1 hour.
Note: It may take a minute or so for the clock to refresh
2. Right click on the clock, then click on "Time & Date Settings..."
3. Ensure that your clock application is set to manual.
4. Change the time 1 hour back
5. Close the window and reboot
VERIFICATION:
Is your system clock displaying the correct date and time for your timezone?
|
|
409. |
Record the current network before suspending.
|
|
2012-02-11 |
Record the current network before suspending.
|
|
482. |
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.
|
|
2012-02-17 |
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.
|
|
485. |
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.
|
|
2012-02-11 |
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.
|
|
488. |
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.
|
|
2012-02-17 |
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.
|
|
503. |
PURPOSE:
This test will check that your system detects USB storage devices.
STEPS:
1. Plug in one or more USB keys or hard drives.
2. Click on "Test".
INFO:
$output
VERIFICATION:
Were the drives detected?
|
|
2012-02-11 |
PURPOSE:
This test will check that your system detects USB storage devices.
STEPS:
1. Plug in one or more USB keys or hard drives.
2. Click on "Test".
INFO:
$output
VERIFICATION:
Were the drives detected?
|
|
509. |
PURPOSE:
This test will check your USB connection.
STEPS:
1. Plug a USB HDD or thumbdrive into the computer.
2. An icon should appear on the Launcher.
3. Click "Test" to begin the test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
|
|
2012-02-11 |
PURPOSE:
This test will check your USB connection.
STEPS:
1. Plug a USB HDD or thumbdrive into the computer.
2. An icon should appear on the Launcher.
3. Click "Test" to begin the test.
VERIFICATION:
The verification of this test is automated. Do not change the
automatically selected result.
|
|
511. |
This test is automated and executes after the usb/insert test is run.
|
|
2012-02-11 |
This test is automated and executes after the usb/insert test is run.
|
|
516. |
PURPOSE:
This test will check that the file browser can create a new folder.
STEPS:
1. Click Test to open the File Browser.
2. On the menu bar, click File -> Create Folder.
3. In the name box for the new folder, enter the name Test Folder and hit Enter.
4. Close the File browser.
VERIFICATION:
Do you now have a new folder called Test Folder?
|
|
2012-02-11 |
PURPOSE:
This test will check that the file browser can create a new folder.
STEPS:
1. Click Test to open the File Browser.
2. On the menu bar, click File -> Create Folder.
3. In the name box for the new folder, enter the name Test Folder and hit Enter.
4. Close the File browser.
VERIFICATION:
Do you now have a new folder called Test Folder?
|
|
529. |
PURPOSE:
This test will check that Firefox can play a Quicktime (.mov) video file.
Note: this may require installing additional software to successfully
complete.
STEPS:
1. Select Test to launch Firefox with a sample video.
VERIFICATION:
Did the video play using a plugin?
|
|
2012-02-11 |
PURPOSE:
This test will check that Firefox can play a Quicktime (.mov) video file.
Note: this may require installing additional software to successfully
complete.
STEPS:
1. Select Test to launch Firefox with a sample video.
VERIFICATION:
Did the video play using a plugin?
|
|
545. |
Test to check that virtualization is supported and the test system has at least a minimal amount of RAM to function as an OpenStack Compute Node
|
|
2012-02-17 |
Test to check that virtualisation is supported and the test system has at least a minimal amount of RAM to function as an OpenStack Compute Node
|
|
552. |
Tests that the systems wireless hardware can connect to a router using WPA security and the 802.11b/g protocols.
|
|
2012-02-11 |
Tests that the systems wireless hardware can connect to a router using WPA security and the 802.11b/g protocols.
|
|
553. |
Tests that the systems wireless hardware can connect to a router using no security and the 802.11b/g protocols.
|
|
2012-02-11 |
Tests that the systems wireless hardware can connect to a router using no security and the 802.11b/g protocols.
|
|
554. |
Tests that the systems wireless hardware can connect to a router using WPA security and the 802.11n protocol.
|
|
2012-02-11 |
Tests that the systems wireless hardware can connect to a router using WPA security and the 802.11n protocol.
|
|
555. |
Tests that the systems wireless hardware can connect to a router using no security and the 802.11n protocol.
|
|
2012-02-11 |
Tests that the systems wireless hardware can connect to a router using no security and the 802.11n protocol.
|
|
556. |
Tests the performance of a systems wireless connection through the iperf tool.
|
|
2012-02-11 |
Tests the performance of a systems wireless connection through the iperf tool.
|
|
557. |
Tests the performance of a systems wireless connection through the iperf tool, using UDP packets.
|
|
2012-02-11 |
Tests the performance of a systems wireless connection through the iperf tool, using UDP packets.
|
|
571. |
Command not found.
|
|
2012-02-11 |
Command not found.
|
|
599. |
Space when finished
|
|
2012-02-17 |
Space when finished
|
|
600. |
Combine with character above to expand node
|
|
2012-02-17 |
Combine with character above to expand node
|
|
610. |
Expand All
|
|
2012-02-24 |
Expand All
|
|
611. |
Collapse All
|
|
2012-02-24 |
Collapse All
|
|
619. |
Restart
|
|
2012-02-11 |
Restart
|