PSP needs unit tests

[skliper]

This project has no unit tests that can be run as part of an automatic build-and-test cycle to assure that a change has not broken fundamental behaviors.

We need central portable unit tests that can be run against any PSP that check the basic behaviors required of every PSP, and a way for individual PSPs to provide additional unit tests that verify any PSP-specific required behaviors.

[skliper]

Imported from trac issue 8. Created by glimes on 2015-01-30T11:37:37, last modified: 2015-04-13T14:05:23

[skliper]

Trac comment by sduran on 2015-02-24 19:01:43:

JSC has developed PSP unit tests, used for the Class A ARINC cert. These tests have not been included in the main release yet. The tests run on linux and ARINC653 OSs. Currently, the tests are being updated to run under VxWorks (being tested on a SPARC LEON3 development board) for a Class A cert of CFS on VxWorks 6.7/SPARC LEON3.

The tests currently do not tests all functions (many were not relevant in the ARINC653 environment), but more are being added since more of them are relevant in VxWorks.

The PSP unit tests can be made to run automatically easy enough, however, most of the tests do not provide a simple PASS/FAIL output. Many of the tests get hardware info (memory addresses, buffer sizes, etc) and have to be manually compared to the kernel config or cfe_platform.h config to verify.

[skliper]

Trac comment by glimes on 2015-04-13 14:05:23:

Will close this ticket as a duplicate of #14
used to track the integration of new tests
from JSC into the tree.

I suspect we will end up with one Trac ticket
for each PSP to get its tests running, and
probably a ticket for support code that is common
across all PSPs.