ACATS 3.1 User's Guide
4.3.1 Legacy Naming
The name of a legacy
test is composed of seven or eight characters. Each character position
serves a specific purpose as described in the table below. The first
column identifies the character position(s) starting from the left, the
second column gives the kind of character allowed, and the third gives
the corresponding meaning:
class (see Section 4.2)
chapter containing the test objective
within the above AIG chapter
of the above AIG section
of the test objective within the above sub-section
identifier of the sub-objective of the above objective.
– Compilation sequence identifier — indicates the compilation
order of multiple files that make up a single test. This position is
used only if the test comprises multiple files.
The convention is illustrated below.
File Name Convention
In multiple file tests, the intended order of compilation
is indicated by a numeral at position 8. The first file to be compiled
has '0', the second has '1', and so forth.
The chapter and section numbers of the AIG (ACVC
Implementer's Guide) correspond to those in [Ada83]
Note: The use of a ninth character ('m') to indicate
the file containing the main subprogram has been discontinued. The following
table lists the files containing the main subprograms of the legacy multiple
The file name extension
is three characters long. There are four extensions:
A file that contains only Ada code. It does not require any pre-processing
to create a compilable test. It will be submitted directly to the implementation
for determination of test results. All implementations must correctly
process these tests.
A file that has a test involving implementation-dependent features of
the language. These tests may not apply to all implementations.
A file that has "code" that is not quite Ada; it contains "macro"
symbols to be replaced by implementation-dependent values, and it must
be customized (macro expanded) to prepare it for compilation (see Section
). Once customized, the resulting test
must be processed as indicated by its class.
A file that has been modified by the macro processor. It contains only
Ada code and may be submitted to the implementation for results. All
implementations must correctly process these tests. There are no files
in the ACATS distribution with this extension; they are only produced
as the output of the macro processor.
Modern tests use different file name extensions (see
that legacy tests have not been renamed for ACATS 3.1. Since [Ada95]
includes some organizational differences from [Ada83],
this means that the name of a legacy test sometimes will not correspond
to the clause of [Ada95] in which the tested
feature is described.