Use "UtTest_Setup" as name of entry point for unit tests #435
Labels
Milestone
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Dec 18, 2019
Use "UtTest_Setup" instead of "OS_Application_Startup" This needs to be merged in coordination with a related change in OSAL/UT Assert. This also updates the UT application final link to use "ut_assert" rather than "ut_bsp", as the separate bsp for unit test is also getting phased out.
This was referenced Dec 18, 2019
skliper
added a commit
that referenced
this issue
Jan 10, 2020
skliper
added a commit
that referenced
this issue
Jan 14, 2020
Fix #435: Update UT entry point Resolve merge conflicts in fsw/cfe-core/unit-test/CMakeLists.txt
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.
In nasa/osal#294, The UT assert library is being modified to use a different entry point function name for unit test code, not
OS_Application_Startup()as is used for a normal application.Describe the solution you'd like
The CFE unit tests need to use
UtTest_Setupinstead.Describe alternatives you've considered
Any name could work for test setup, but the issue is that it has to be different than that of a normal application. This is so the normal entry point can be provided by UT assert here, allowing better layering.
Additional context
Changing the name of the Test entry point makes more sense because these only use the OSAL BSP but run with the stub library for OSAL itself. It is therefore not really accurate to name the entry point as
OS_Application_Startupbecause this is not an OSAL application at all, it is a unit test.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: