Accessing SunVTS

You can access SunVTS from various interfaces: CDE, OL, or the TTY interface. SunVTS tests can be run from a shell command line, using the command line syntax for each test. The SunVTS kernel probes for hardware devices installed on your system.

Graphical User Interfaces (GUIs) SunVTS GUIs let you select tests and test options by pointing and clicking with a mouse button. You can use the CDE or OL interface.

TTY Interface Using the TTY interface, you can run SunVTS from a terminal or modem attached to a serial port. This feature requires that you use the keyboard instead of using the mouse, and it displays one screen of information at a time. However, it emulates the window system whenever possible.

Command Line Interface You can also run each of the SunVTS tests individually from a shell command line using the command line syntax. Each test description contains the corresponding command line syntax.

For more information about running individual tests from the command line, refer to the specific test description in this manual.

Standard Command Line Arguments Different types of command arguments can be applied to a test: generic command arguments (common to all tests), and test-specific command arguments. Because the code for each test defines test-specific arguments, this section only addresses generic command parameters.

The standard usage for all SunVTS tests is:

Usage: testname [-scruvdtelnf] [-p number][-i number] [-w number] [-o test specific arguments]

The following table defines the standard SunVTS command Line arguments:

Table 1-1

Argument	Definition
-s	Runs a test in SunVTS mode.
-c	Enables a core dump; the test creates a core file if a system crash occurs.
-r	Runs on Error; if an error occurs, the test continues the next test sequence instead of exiting.
-u	Displays the Usage statement.
-v	Runs the test in Verbose mode; the test displays VERBOSE messages that tell more about the testing process.

Table 1-1 (Continued)

Argument	Definition
-d	Runs the test in Debug mode; the test displays DEBUG messages to help programmers debug their test code.
-t	Runs the test in test function trace mode; the test displays TRACE messages that track down function calls and sequences currently being used by the test code.
-e	Runs in stress mode; the test runs under increased system load.
-l	Runs in online mode.
-n	Runs in connectivity mode.
-f	Runs in offline mode.
-i number	Defines the number of instances for scalable tests.
-p number	Defines the number of passes.
-w number	For scalable tests, defines which instance the test is assigned.

Test-Specific Arguments Test-specific arguments should follow the format specified in the getsubopt(3c) man page. There should be at least one test-specific argument, as described in Table 1-2.

Table 1-2

Argument	Definition
-o	Separate each test-specific argument by commas, with no space after the each comma. For example: # ./sample -v -o dev=/dev/audio,volume=78 The test option format is specified by the man page getsubopt(3C).

Test Modes SunVTS has several test modes that you can select during testing. The modes are Connectivity, Online, Offline, and Stress. The following table lists the various tests by group, and indicates the test modes available for each test.

Table 1-3

Test Name	Connectivity	Online	Offline	Stress
System Board
audiotest	Yes	Yes	Yes	Yes
fputest	Yes	Yes	Yes	No
mptest	Yes	Yes	Yes	No
pmem	Yes	Yes	Yes	No
systest	No	No	Yes	No
vmem Devices	No	No	Yes	No
cdtest	Yes	Yes	Yes	Yes
disktest	Yes	Yes	Yes	No
tapetest Parallel Ports	Yes	Yes	Yes	No
bpptest	Yes	Yes	Yes	No
ecpptest	Yes	Yes	Yes	No
lpvitest	No	No	Yes	No
spdtest Comm Ports	No	No	Yes	No
spiftest	No	No	Yes	No
sptest	Yes	Yes	Yes	No
sunlink Networks	No	No	Yes	No
isdntest	Yes	Yes	Yes	No
nettest	Yes	Yes	Yes	No

Table 1-3

Test Name	Connectivity	Online	Offline	Stress
Controllers
plntest	Yes	Yes	Yes	No
pstest Frame Buffers	No	No	Yes	Yes
cg6test	No	No	Yes	Yes
cg14test	No	No	Yes	Yes
fbtest	No	No	Yes	No
ffbtest	No	No	Yes	No
leotest	No	No	Yes	No
sxtest	No	No	Yes	No
tcxtest Miscellaneous	No	No	Yes	Yes
pcsertest	No	No	Yes	No
rtvctest	No	No	Yes	No
sundials	No	No	Yes	No
sunbuttons	No	No	Yes	No
xbtest	No	No	Yes	No

Hardware Verification The SunVTS kernel automatically probes the system kernel for installed hardware devices. Those devices are then displayed on the SunVTS control panel with the appropriate tests and test options. This provides a quick check of your hardware setup.

Hardware and Software Requirements

The SunVTS Version 2.0 software runs on any system with the Solaris 2.5 (or later) operating environment installed. The operating system kernel must be configured to support all peripherals that are to be tested.

OPEN LOOK Software Requirements

You must meet the following requirements to run SunVTS with OPEN LOOK:

• Run Solaris 2.5 operating environment, or later
• Run OPEN LOOK Version 3.3 or later
• Set the correct library path

You may have to set the LD_LIBRARY_PATH variable, depending on the location of the OPEN LOOK directory in your system.

• If you installed or mounted OPEN LOOK files in the default location, /usr/openwin, you can ignore this step.
• If OPEN LOOK is installed in a different location, you must specify the location of the OPEN LOOK libraries. Use the following command and substitute the pathname variable for the actual path where you installed the OPEN LOOK software:

# setenv LD_LIBRARY_PATH pathname

* Check the existing LD_LIBRARY_PATH by typing env.

Testing Multiple Frame Buffers

These rules apply when you test multiple frame buffers (displays) simultaneously:

• You can test multiple frame buffers on a system at the same time, but only one frame buffer can run the OPEN LOOK software.
• To avoid incorrect test failures, the frame buffer that runs the OPEN LOOK software must have window locking enabled. Any other frame buffers must have window locking disabled.

---

Caution - If window locking is disabled (unlocked) on frame buffers that are running OPEN LOOK software, the SunVTS tests can return spurious error messages if you move the mouse during testing. Even a slight mouse movement can cause a test to fail.

---

• By default, SunVTS enables window locking on the console monitor (frame buffers that are pointed by /dev/fb).
• If you are running a frame buffer test from a command line, you can disable window locking by specifying a command line argument (see the test command line descriptions in this manual). For example, when running the generic frame buffer test (fbtest), use the lock=e/d option to disable or enable frame buffer locking. Frame buffer locking is being enabled in the example below.:

#./fbtest -o dev=cgthree0,lock=e

Remote Testing

The frame buffer locking option does not work when you start sunvts or vtsk remotely. In this case, set the frame buffer locking option to disable. Do not run any graphic programs (including vtsui) on that frame buffer during graphic testing.