3.1. Test results

The results from all the tests encountered by runtest are reported in the log file and counted, for reporting on completion. The results are triggered by calling the appropriate result procedure, which takes a string to identify the test concerned. The possible results are as follows:

FAIL

Indicates that a test has failed. Triggered by calling the fail procedure.

PASS

Indicates that a test has passed. Triggered by calling the pass procedure.

XFAIL

Indicates that a test has failed as expected. Triggered by calling the xfail procedure.

	Note
	POSIX 1003.3 does not recognize the concept of expected failure (tests either fail or pass), so compliant tests should not generate this result.

XPASS

Indicates that a test which was expected to fail has passed. Triggered by calling the xpass procedure.

	Note
	POSIX 1003.3 does not recognize the concept of expected failure (tests either fail or pass), so compliant tests should not generate this result.

UNTESTED

Indicates that a feature was not tested. Triggered by calling the untested procedure. This is a good way to mark tests that need to be completed.

UNRESOLVED

Indicates that the output from a test needs manual inspection. Triggered by calling the unresolved procedure. Commonly used when tests timeout.

	Note
	Any test which calls `perror` or calls `warning` more than `warning_threshold` times will cause the next call to any result function in this list to behave as though `unresolved` was called.

UNSUPPORTED

Indicates that a test is not supported. Triggered by calling the unsupported procedure. Used for tests which depend on some conditionally available feature. For example for tests which cannot run on a particular target board.