With trac ticket #29 (and related #30) now implemented, the OSAL tests can be used as one piece of a build verification tool suite.

However, the implementation is currently very basic - it does not use any real testing framework, it simply counts errors using a global integer added to each test.

CFE has a more sophisticated UT framework consisting of the following functions:

• UT_Text() - informational / log file text printing function;
• UT_Report() - provides a common method to check for a condition, along with code to log PASSED/FAILED in a consistent manner;
• UT_SetRtnCode() - ability to tailor the response code of stub functions in order to exercise error paths;
• UT_ReportFailures() - test summary generator

OSAL could benefit from using the same framework to run its tests. Most importantly, using the common "UT_Report()" API ensures that any errors that occur will be counted and logged in a consistent way. This is particularly important for automated tests, as a simple "grep" command can reliably find failures within log files containing thousands of test cases.