-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSAL coverage test should be part of normal build #362
Milestone
Comments
jphickey
added a commit
to jphickey/osal
that referenced
this issue
Feb 26, 2020
Build the full suite of OSAL coverage tests as part of the normal build when ENABLE_UNIT_TESTS is true. This will use the same target OSAL BSP to execute the tests as is used for the FSW.
jphickey
added a commit
to jphickey/osal
that referenced
this issue
Mar 10, 2020
Build the full suite of OSAL coverage tests as part of the normal build when ENABLE_UNIT_TESTS is true. This will use the same target OSAL BSP to execute the tests as is used for the FSW.
jphickey
added a commit
to jphickey/osal
that referenced
this issue
Apr 2, 2020
Build the full suite of OSAL coverage tests as part of the normal build when ENABLE_UNIT_TESTS is true. This will use the same target OSAL BSP to execute the tests as is used for the FSW.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently the
src/unit-test-coverage
directory is an entirely separate build which needs to be invoked separately by the user.As per CFE request nasa/cFE#386 it is desired to integrate the OSAL coverage tests as part of the normal unit test builds, so these do not need to be built separately.
Describe the solution you'd like
The tentatively agreed-upon approach is to build all coverage targets by default, and use the target BSP to run them.
Additional context
The side effect is that this may build coverage targets which are not relevant to the deployed platform (e.g. building and running a VxWorks coverage test for a platform that does not use VxWorks).
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: