1RESULT CODES
2============
3
4POSIX Test Suite tests all return standard result codes for ease in
5interpreting the output.  The result code terms are taken from
6IEEE Test Methods for Measuring Conformance to POSIX (IEEE 1003.3-1991).
7These result codes are a subset of the LSB result codes and, for
8consistency with LSB, are given the same number.
9
10Initial Contributors:
11	ajosey REMOVE-THIS AT rdg DOT opengroup DOT org
12	julie.n.fleischer REMOVE-THIS AT intel DOT com
13	geoffrey.r.gustafson REMOVE-THIS AT intel DOT com
14
15The PTS result codes are:
16
17#define PTS_PASS        0
18#define PTS_FAIL        1
19#define PTS_UNRESOLVED  2
20#define PTS_UNSUPPORTED 4
21#define PTS_UNTESTED    5
22
23A brief discussion of each of these follows:
24
25PTP_PASS	Used when the test executes fully with no problems and passes.
26PTP_FAIL	Used when the test executes fully, but fails.
27PTP_UNRESOLVED	Used when the test was blocked from fully completing and
28		the pass/failure results cannot be determined.
29PTP_UNSUPPORTED	Used if the test is for a conditional feature that is
30		not implemented.
31PTP_UNTESTED	Used when a feature does not have a test associated
32		with it because:
33		- The test is just a stub and doesn't do anything
34		- The test is only partially complete and can't really
35		  finish the test
36		- The test is complete in some cases, but certain things
37		  can happen that leave the test incomplete.  When these
38		  happen, it's PTP_UNTESTED.
39
40These result codes are contained in the header file posixtest.h, located
41in the include/ directory.
42
43This header file should be included in each test suite created.
44