As each test is set up, the actual test will be added into a folder called in the pane. The tests will be started at the same time and run together, overnight, to stress the overall system more efficiently and reduce testing time. The final test is the Serial Port Test and it is run after the other Overnight Stress Tests have run. The overnight Stress tests do not include the serial port test. However we recommend queuing up the serial port test at the time when the overnight stress tests are started.
Test Overview: This test is required for systems with floppy disk drives. If the SUT does not have a floppy disk drive, go to the next test.
Test Objective: Verifies the Floppy Disk functions correctly with the other devices in the system.
Place a blank floppy disk into the SUT floppy drive.
WARNING:The contents of the floppy disk you insert will be erased.
If testing a USB floppy drive, attach the USB floppy drive to SUT.
Double-click in the TestConsole project for the SUT.
Test Overview: This test is required for systems with CD or DVD drives. If the SUT does not have a CD or DVD drive, go to the next test.
Test Objective: Verifies the CD or DVD drive functions correctly with the other devices in the system.
Certification requires that one optical drive test be run per installed optical device; only test the most capable functionality of each drive.
Table 2-2 CD-ROM/DVD Test Matrix
NOTE:Please verify that the write speed of the CD or DVD writeable media matches the optical drive write speed. If the write speed of the media is slower that the write speed of the drive, the test may fail.
Configure the CDR/DVD test suite.
Double-click in the TestConsole project for the SUT.
Place the CD/DVD media in the drive.
NOTE:The media must contain at least 600 MB (for a CDR drive) or 3 GB (for a DVD-ROM drive) of data, otherwise the test will fail.
If a SUSE Hardware Detection pop up appears, place a check mark next to and click to not open the application.
Repeat the above steps for each CDR or DVD drive (e.g., CDR/DVD 2 Test) or perform CDW or DVDW test for each additional drive (see Table 2-2).
Test Overview: This test is required for systems with CDW drives. If the SUT does not have a CDW drive, go to the next test.
Test Objective: Verifies the CD-rewriteable drive functions correctly with the other devices in the system.
Determine if the CD/DVD-RW supports auto-trayclose.
Enter “eject” at the command line to eject the CD/DVD.
Enter “eject --trayclose” at the command line to close the tray. If the tray closes and the command does not return an error, then it is supported.
IMPORTANT:If the CD/DVD-RW does not support auto-tray close, then the tester will need to manually close the tray during testing.
Configure the CDW test suite.
Double-click in the TestConsole project for the SUT.
Place a blank writable (or rewriteable) CD that supports the maximum write speed of the drive into the CDW drive.
If a SUSE Hardware Detection pop up appears, place a check mark next to “Do not ask again” and click to not open the application.
Repeat the above steps for each CDW drive (e.g., CDW 2 Test) or perform CDW or DVDW test for each additional drive (see Table 2-2).
Test Objective: Verifies the DVD-rewriteable drive functions correctly with the other devices in the system.
Determine if the CD/DVD-RW supports auto-trayclose.
Enter “eject” at the command line to eject the CD/DVD.
Enter “eject --trayclose” at the command line to close the tray. If the tray closes and the command does not return an error, then it is supported.
IMPORTANT:If the CD/DVD-RW does not support auto-tray close, then the tester will need to manually close the tray during testing.
Configure the DVDW test suite.
Double-click in the TestConsole project for the SUT.
Place a blank writable (or rewriteable) DVD that supports the maximum write speed of the drive into the DVDW drive.
If a SUSE Hardware Detection pop up appears, place a check mark next to and click No to not open the application.
Repeat above steps for each DVDW drive (e.g., DVDW 2 Test) or perform CDW or DVDW test for each additional drive (see Table 2-2).
This test is intended for exercising 2 USB ports. We require the use of PS2 keyboards and mice to ensure that 2 USB ports are available for testing. If a system has only 2 USB ports and requires the use of a USB keyboard, then only one USB Hard drive test is required for certification.
Test Objective: Verifies the USB port functions correctly with the other devices in the system.
Connect a USB hard drive to the SUT. If there are two or more USB ports, two should be tested. If there are USB ports on the front and back of the system, plug one hard drive into a front port and the other hard drive into a back port.
If prompted to open a new hard disk, click .
If a USB hard drive needs to be partitioned for Linux, open the System Partitioner to configure the USB hard disk drive.
At a terminal prompt, type yast2 disk<Enter>.
Click at the warning.
Highlight the new device (e.g., sdb or sdc).
Remove existing partitions on the USB hard dive.
Click .
Click to really delete the partition.
Click if prompted to unmount the drive.
Create a new partition on the USB drive.
Click .
Click the radio button next to the new device and click .
Click to create a primary partition.
Click .
Repeat step 5a - 5d for the 2nd USB hard drive.
Click .
Click and continue to format the drive.
Double-click in the TestConsole project for the SUT.
Double-click in the TestConsole project for the SUT.
Test Objective: Verify the Hard Disk/RAID and driver functions with the system.
Double-click in the TestConsole project for the SUT.
Repeat the above steps for each Hard Disk/RAID (e.g., Hard Disk/RAID 2 Test).
Test Overview: The NIC Test tests the LAN I/O.
Test Objective: Verifies the LAN driver functions with the LAN in the system.
The NIC 1 Test and NIC 2 Test are already enabled for SLES 9 and 10 in the top yellow portion of the screen. The NIC 1 Test is already enabled for NLD 9 and SLED 10. If you have additional NICs, they should be listed in the test project. Ensure that the IP address for each adapter is correct.
NIC 1: 10.1.1.2 (the IP address of TC)
NIC 2: 10.2.1.2 (the IP address of FS4)
NIC 3: 10.3.1.2 (a virtual interface or alias of TC)
NIC 4: 10.4.1.2 (a virtual interface or alias of FS4)
And so on
Test Objective: Verifies that the driver routes correctly with the other devices in the system. All servers require this test. The embedded NICs are required to be used during the router testing. Workstations require this test if the workstation being tested has two or more LAN cards. If you are testing a laptop with one wireless card and one Ethernet card, do not run this test.
Test Objective: Verifies the CPUs and memory function correctly under stress for an extended amount of time. This test does not require setup.
Test Objective: Verifies that all system devices function correctly together in a high load situation for an extended period of time.
Double-click the folder.
Click “Continue” in response to the “Verify run” pop-up window. This will start all the tests that were set up.
If RAID are being tested:
Disable or remove one disk of the array if you are testing a RAID 1 or higher.
Wait 10 minutes.
Enable or insert the disk again.
Wait 15 minutes and check see if any of the tests have failed.
If any tests have failed:
Correct the problem (see Section A.0, Troubleshooting.
Restart the test as soon as possible by double clicking on the failed test and then go back to step 4.
We recommend running the Serial Port Test Setup (Section 2.22, Serial Port Test Setup) at this time.
NOTE:The serial port test is not part of the Overnight Stress tests and will not run at the same time, but will be placed in the queue to run immediately after the Overnight Stress tests have completed.