User`s manual

Chapter 8 293
IBASIC Controller
The TESTS Subsystem
TESTS Subsystem File Descriptions
Three types of files are used in the TESTS Subsystem to store different
types of information.
Code Files
The first aspect of an automated definition is the code itself. This is just
a standard IBASIC code file that can reside either on the PC card, or in
an internal RAM. The name of this file has a .PGM extension. This
extension identifies the file as program code.
Library Files
A Library indicates all of the available test subroutines in the code, the
set of all parameters that might be entered using the user-interface
screens, and all specifications that might be used by the subroutines in
the code to decide if a test point passes or fails.
Only one Library is defined for each Code file. The name of this file has
a .LIB file extension in the Test Set, indicating that this is a Library
file. Also, both the Library and Code file should have the same base
name to indicate the relationship between them.
A Library is required to use the user-interface screen functions of the
TESTS Subsystem. If the program is simple enough that there is no
need for user-input, or if all the user-input is simple enough to be
accomplished with INPUT statements, a [NO LIB] option is available.
Procedure Files
A Procedure allows the user to define which of the test subroutines,
parameters, and specifications defined in the Library will be used to
test a specific Radio. There may be many Procedures defined that use
the same IBASIC Code and Library, each using a different subset of the
choices available in the Library. These files have a .PRC file extension,
but are not required to have the same base name as either the Library
or the Code. The name of the corresponding Library (if any) is stored in
each Procedure file.