-
Notifications
You must be signed in to change notification settings - Fork 229
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
Examples for application testing #4
Comments
Yes, this is a problem. I'm working on getting the GSFC cFS apps fully migrated to cFE 6.6/Cmake. Hopefully I will have an example to release soon. |
Cool, thanks for the confirmation. |
CCB 20191001 - Plan to incorporate in sample_app and app developer's guide also |
See nasa/sample_app#26 and nasa/sample_lib#11 as a work in progress. |
What was the duplicate issue #? |
nasa/sample_lib#9 and nasa/sample_app#8, both linked to the pull requests. |
Since the release of cFE 6.6, there hasn't been apps that give an example of the way tests should be defined in the CMakeLists file. Previously, when UTAssert was part of the tools directory rather than being part of the OSAL, this definition would exist inside of the fsw/for_build/Makefile but this doesn't cleanly translate to cFE 6.6's cmake build system.
The arch_build.cmake file located in the cmake directory seems to have a function add_unit_test_exe but I couldn't get this to work when calling it from the simple app's CMakeList.txt. An explanation of what needs to be done in either the target.cmake or CMakeLists file for an app or an example of an app using UT for it's testing would be appreciated.
The text was updated successfully, but these errors were encountered: