3.2. Test Execution

For each test case (single "c" source file) there are three ways the test will be used.

• compile test run: Each test case will be compiled, with a successful compile registered as a successful test run. The intent to verify the correctness of the header files used by the HPI implementation.

• link test run: Each test case object file will be linked, with a successful link registered as a successful test run. The intent of this type of test is to verify the implementation contains the specified symbols.

• binary execution test run: Each test binary executable will be executed by a shell, with a zero returned by the shell registered as a successful test run. The intent of this type of test is to verify the run-time behavior of the HPI implementation compiles with the HPI specification. A 70h (N/A) for Not Applicable will be returned when a test does not meet pre-requisite requirements to be valid.

All test cases for a specific HPI version can be executed using the "hpitest" script located in root test directory, or by changing to the specific MAJOR/MINOR directory and using the "run-test" script.