This section describes the suite of tests in HTS. These tests are selected by HTS according to features available in the hardware.
checks for playback and recording capability in full duplex. This test requires user to connect a speaker to the test machine if there is not already a speaker present.
This is a stress test, to test the system's functionality under load. The core test also check for problems with system clock(s).
The cdrom test performs the highest capability test of every cdrom device on test machine. Typically the test reads files and writes files on disk media, and compares the results.
So, the scheme for this test is:
For CD-read-only drives, the test performs a file read test.
CD-recordable drives, the test performs a write test, then reads the file from the media for comparison.
For Combo drives the test performs the CD-recordable test, then does a read test on the DVD-ROM.
DVD-recordable drives, the test performs a write test, then reads the file from the media for comparison.
The floppy test tests reading and writing to the floppy disk drive
This test captures system configuration information for review.
The memory test performs stress and bandwidth testing of memory.
The network test checks bandwidth and latency for ICMP, TCP and UDP protocols over ethernet interfaces. It checks ICMP by "pinging" the Network Test Server. TCP and UDP are tested using lmbench bandwidth and latency test tools. UDP is also tested via copying files over NFS to the Network Test Server and comparing the results.
Notes:
The Network Test server Hostname or IP address must be supplied via the --server HTS parameter
Each interface will be tested seperately,, so if there are multiple NICs on your test machine, please make sure all NICs are connected.
The firewall on both the system under test, and the Network Test Server must be disabled to allow testing.
This test walks the total number of sockets turning each off and then on, ensuring a configuration is selected at power-on.
The storage test performs read and write tests of all storage devices.
Notes:
To be able to properly test disk storage, Red Hat Enterprise Linux5 must be installed on a single disk. There may be any number of extra, unused disks present in the machine. But the entire install of the operating system must be confined to a single disk. If Red Hat Enterprise Linux5 is installed using more than one disk, some of the disks used for installation will be unusable for testing. This applies to hardware RAID storage as well as conventional disks. When installing to a hardware RAID-enabled system, be sure to put all operating system partitions on the same RAID volume.
The storage test will check every disk storage device on the test machine. The test run time may be very long, depending on the amount of storage.
If using LVM while installing the Red Hat Enterprise Linux5 operating system, must make sure that the volume which will store Red Hat Enterprise Linux5 files only uses one physical device (one disk or one RAID volume).
The tape test uses "mt" and "tar" to backup all files under /usr to a tape and then verify all files.
The USB asks the user to plug in, and then remove a USB device from each unused USB socket, verifying the device is present.
The "x11perf" is used to check that the display is functional.
The virtualization test is specifically designed to check the new virtualization capabilities in Red Hat Enterprise Linux5.
The test will first create an Red Hat Enterprise Linux5 FV(Full-Virtualized) guest OS and then run a subset of HTS tests in the guest. When the guest finishes running, it powers itself off. Then host OS checks the results and removes the guest OS.
Notes:
This test requires 8GB disk space under host's /tmp directory.
Make sure the NFS server is functional on the test machine. Guest OS and host OS exchange files through NFS. Please check that the firewall is set properly.
It's better to set host OS get its IP address by DHCP, as the guest OS gets its IP address by DHCP. Connect all test machine network interfaces directly to a switch.
When this test is started, the guest OS's screen will not prompt out automatically, you can use such tools like "virt-manager" to open it's window to monitor the test.
This test is only applicable for IBM's s390x machines.