ACATS 3.1 User's Guide
5.6.3 Expected Results for Class L Tests
Class L tests are expected to be rejected before
execution begins. They must be submitted to the compiler and to the linker/binder.
If an executable is generated, then it must be submitted for execution.
Unless otherwise documented, the test is graded as "failed"
if it begins execution, regardless of whether any output is produced..
(Twenty-eight L tests contain documentation indicating that they may
execute. See below.)
In general, an L test is expected to be rejected
at link/bind time. Some tests contain -- ERROR: indications;
an implementation that reports an error associated with one of these
lines is judged to have passed the test (provided, of course, that the
link attempt fails).
The following tests
are exceptions to the general rule that an L test must not execute:
Test LXE3002, for
the Distributed Systems Annex, is a test that has two partitions, each
of which may execute. As documented in the source code, this test is
graded "failed" if both partitions report "TENTATIVELY
PASSED". Other outcomes are graded as appropriate for Class L tests.
and LA20002 (twenty-seven core language tests), as documented in the
source code, may execute if automatic recompilation is supported. These
tests are graded as "passed" if they execute and report "PASSED".
Other outcomes are graded as appropriate for Class L tests.