nt

Purpose:

Process a new gp_test specification.

Enter:

nt <test_procedure_file> [t=gp_test_name] [mode=start_mode_number] [time=timeout_value] [+r] [+i]

Where:

procedure_file

Specify the name of the test specification file to activate
or
if specifying the +i option, specify the label of  the string variable that contains the procedure_file name.

mode=start_mode_number

Optional. Specify a start_mode_number to override the start mode of the procedure.

time=time_out_value

Optional. Specify a mode time_out_value to override the mode timeout of the first mode.

t=gp_test_name

Optional. Specify the name assigned to the gp_test to process the new test procedure. The default name is ‘test’.

+r

Optional. Specify this flag to restart the test without reading the specification file.

+i

Optional. Specify this flag to change the meaning of the procedure_file argument. Instead of the filename, the label of a string variable which contains the filename specified with the procedure_file argument will be used.

Example:

nt gp_hotshut
The above command activates the gp_test procedure that runs a hot-shutdown cycle.

nt hotshut mode=22 +r
The above command jumps to mode 22 without reading the specification file.

nt Testfile +i
The above command jumps to the test procedure contained in the string variable Testfile.

Notes:

The nt command causes gp_test to read and start a new test specification file. If the +r option is used, the test procedure execution is modified without reading the specification file.

Use the ck command to check that there are no errors identified in the syntax of a gp_test spec file before running the spec file with the nt command.

See Also:

ck, hold, idle, release, gp_test, Test Manager User Guide