In some cases it may be more convenient to run a single SunVTS test from the command line rather than through a SunVTS user interface. The following information describes how to do this.
Unless specified, the test runs without the SunVTS kernel (vtsk). All events and errors are sent to stdout or stderr, and are not logged in the log files.
When you run a test in this way, you must specify all test options in the form of command line arguments.
Standard arguments--common to all tests. Refer to Table 1-3 for details.
Test specific arguments--unique to a specific test. Refer to the test specific chapters in this book for details.
testname [-scruvdtelnf] [-p number ][-i number ] [-w number] [-o test specific arguments]
64-bit tests are located in the sparcv9 subdirectory: /opt/SUNWvts/bin/sparcv9/testname. If a test is not present in this directory, then it may only be available as a 32-bit test. For more information refer to "32-Bit and 64-Bit Tests".
The following table defines the standard SunVTS command line arguments:Table 1-3 Standard Command-line Arguments
|-s||Run a test as though it were invoked from the SunVTS kernel (vtsk). This causes the test to send output to an RPC port that the SunVTS kernel is using. The default is to send the output to stdout or stderr.|
|-c||Enables a core image of the test process to be created in the current working directory upon receipt of certain signals, otherwise those signals are caught and handled to prevent a core from being generated. The default is to disable the creation of a core image.|
|-r||Enables run on error so that when an error occurs, the test continues with the next test sequence instead of exiting. The default is false.|
|-u||Displays command line usage information.|
|-v||Runs the test in Verbose mode and displays messages with more detailed information about the testing process. The default is false.|
|-d||Runs the test in debug mode and displays messages to help programmers debug their test code. The default is false.|
|-t||Runs the test in test Trace mode and displays messages that track function calls and sequences currently in use by the test code. The default is false.|
|-e||Runs the test in Stress Mode by increasing the system load. The default is false.|
|-l||Runs the test in Online Functional mode. This is the same mode that tests run in when executed through SyMON. It is a non-intrusive version that will not significantly affect other applications. See the note below. The default is true.|
|-n||Runs the test in Connection Mode. See the note below.The default is false.|
|-f||Runs the test in full Functional test mode. This mode assumes that the test has complete control of the device under test. See the note below. The default is false.|
|-i number||Defines the number of instances for scalable tests.|
|-p number||Defines the number of passes.|
|-w number||For scalable tests, defines to which instance the test is assigned.|
|-o||Used to indicate that the options and arguments that follow are test specific. Note - separate each test specific argument by commas, with no space after each comma.|
If you choose to specify a test mode with the l, n, or f option, specify only one option at a time because only one test mode can be selected at a time.
There are test-specific arguments, as described in Table 1-4 Test-specific arguments follow the format specified in the getsubopt(3c) man page. For information about test-specific arguments refer to the specific test chapter in this book.Table 1-4 SunVTS Test-Specific Arguments
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).