Adding a Custom Test

Developers can add their own custom tests to the SunVTS environment. This book does not describe custom test development, but does list the tasks necessary to add a custom test into the SunVTS environment.

To Add a Custom Test

1. Copy your custom test binary to the SunVTS bin directory based on the 32-bit or 64-bit functionality of your binary test:

   • 32-bit: /opt/SUNWvts/bin

   • 64-bit: /opt/SUNWvts/bin/sparcv9

2. Modify one of the following .customtest files based on the 32-bit or 64-bit functionality of your binary test:

   • 32-bit: /opt/SUNWvts/bin/.customtest

   • 64-bit: /opt/SUNWvts/bin/sparcv9/.customtest

   The format of the .customtest file is described in "The .customtest File Format".

3. Restart SunVTS or reprobe the system.

When invoked, SunVTS displays the custom test in the SunVTS user interface.

The .customtest File Format

The .customtest file defines the test options and the default option values for your custom test. The tester can change these options using the option dialog boxes through the SunVTS user interface. However, the Reset button returns the options to the default settings as defined in the .customtest file.

Each line in this file is made up of two or more fields that are separated by a semicolon where:

• The first field is the label or device name (mandatory field).

• The second field is the test name (mandatory field).

• The third field is an option line (optional field). If used, this field must be in the format specified.

• The fourth field is used if the test is scalable. If used, append the keyword SCA to this field.

Examples:

• To add a test with no options:

  % your_label_name;your_test_name

• To add the scalability option, append the keyword SCA:

  % your_label_name;your_test_name;SCA

• To custom build an option menu, add an option specification:

  % Option_Name<Option_Type|Value|Default_Value|Command_Line_Option>

• To specify more than one option, separate each option by a comma:

  % label_name;test_name;Numeric<NUMERIC|0,100|50|numeric>, Exc_Choice<EXC_CHOICE|Top,Middle,Bottom|Middle|exc_choice>, Inc_Choice <INC_CHOICE|Left,Center,Right|Left+Center+Right|inc_choice>, Toggle<TOGGLE|This,That|This|toggle>, Text<TEXT|20|Type_Here|text>, Slidebar<SLIDEBAR|0,10|5|slidebar>, Errors<CYCLE|Yes,No|No|errors>, Cycle<CYCLE|First,Second,Third|First|cycle>;SCA

SunVTS invokes the above test as follows:

% ./test_name -s[vq..] [-i n] 

-o dev=user[0,1..],Command_Line_Option=Value...

You cannot use the .customtest file when a test has a probe attached. You must ensure that the binaries are compatible with the version of the Solaris kernel on which SunVTS is currently running.

If .customtest is renamed as .customtest-group, all of the associated tests will appear under the specified group.