A test exercises a software application by supplying it
  with valid and invalid data to determine the integrity
  of the software. You must plan and create the tests.

  You can create three types of tests, depending on the
  needs of the application:

  o  Noninteractive test

  o  Interactive terminal test

  o  DECwindows test

  You must identify each test to DTM in a test
  description. After creating a test description, you
  can place the test into a collection for execution.

1  –  cre_noninter

  A noninteractive test is a test whose template file is
  a DCL command file.

  To create a noninteractive test, perform the following
  steps:

  1. Write the test using a text editor.

  2. Write the template file, which can be the test file
     itself or a OpenVMS command file that executes the
     specified test.

  3. Create the test description.

2  –  cre_inter_term

  To create an interactive terminal test, perform the
  following steps:

  1. Create the test description for the test.

  2. Record the test by running an application and
     generating input and output interactively.

  With interactive terminal tests, you can also run an
  application with a previously created input file.

3  –  rec_inter_term

  To record an interactive terminal test, perform the
  following steps:

  1. Pull down the Testing menu.

  2. Choose the Record menu item and the Terminal...
     submenu item.

  3. Fill in the appropriate fields and press the OK
     button.

  DTM begins the recording session by creating a task
  and displaying the DCL prompt. Every action during the
  session is then recorded until you end the recording
  session by typing CTRL/P twice.

  The Record functions record and place the input into a
  template file (filename.SESSION) and the output into a
  benchmark file (filename.BMK).

3.1  –  rec_commands

  Use the default termination character (CTRL/P) to
  suspend a recording session. You can then issue a
  Record control key sequence.

  The following table contains the Record control key
  sequences.

  Key
  Sequence  Function

  CTRL/P B  Starts an automatic screen comparison and
            ends a manual screen comparison for terminal-
            based tests. This control key sequence does
            not apply to DECwindows tests.
  CTRL/P !  Invokes a text editor so that you can enter
            a comment into the session file. You end
            the comment by pressing CTRL/Z. This control
            key sequence is not available for DECwindows
            testing.
  CTRL/P E  Ends an automatic screen comparison and
            begins a manual screen comparison for
            terminal-based tests. This control key
            sequence does not apply to DECwindows tests.
  CTRL/P    Ends the recording session and returns
  CTRL/P    control to the previous command level. When
            you terminate a recording session this way,
            DTM saves the session and benchmark files.
  CTRL/P ?  Displays the current screen comparison mode
            and lists the available recording functions.
            This control key sequence is not available
            for DECwindows testing.
  CTRL/P I  Inserts an input file into the session file
            you are recording. DTM prompts you for the
            input file specification. Input files are
            available for interactive terminal tests
            only.
  CTRL/P C  Marks a screen for comparison. This is the
            only way to mark screens for DECwindows
            tests. You must mark the specific screen
            that you want to compare for DECwindows
            tests. DTM automatically compares all screens
            for terminal-based tests. This control key
            sequence is used in terminal-based tests when
            automatic comparison is disabled.
  CTRL/P    Terminates an interactive recording session,
  CTRL/Z    saves the session file, creates (or modifies)
            the test description, but does not save the
            benchmark file.
  CTRL/P W  Invokes a prompt for you to specify a wait
            time. You issue this control key sequence
            at the place in a session file that you want
            the wait to occur. When the session file is
            subsequently played or executed, the wait
            time is included in the session file.
  CTRL/P    Aborts an interactive recording session
  CTRL/C    without saving any of the generated files.

3.2  –  cre_inp_fl

  An input file is a text file that you can edit. DTM
  translates and writes all input, commands, and comments
  in a session file to an input file.

  You can use an input file to create a new session
  file from an existing session file for an interactive
  terminal test only.

  To create an input file, perform the following steps:

  1. Pull down the Testing menu.

  2. Choose the Extract... menu item.

  To use the input file to create a new session file,
  perform the following steps:

  1. Pull down the Testing menu.

  2. Choose the Record menu item and the Terminal...
     submenu item.

  The Record dialog box contains an Input file field for
  use with an interactive terminal test.

4  –  cre_decw

  To create an interactive DECwindows test, perform the
  following steps:

  1. Create the test description for the test.

  2. Record the test by running applications and
     generating input and output interactively.

5  –  rec_dw_test

  To record an interactive terminal test, perform the
  following steps:

  1. Pull down the Testing menu.

  2. Choose the Record menu item and the DECwindows...
     submenu item.

  3. Fill in the fields and press the OK button.

  You begin the recording session by pressing Compose/S.
  DTM then starts the specified application and records
  every action during the session until you end the
  session by pressing Compose/P. You mark screen images
  for comparison by pressing Compose/M.

  DTM records and places the input into a template file
  (test_name.SESSION) and the output into a benchmark
  file (test_name.BMK).