Ways to test individual application #507
Replies: 1 comment 2 replies
-
We use UtAssert for coverage (stubbed) testing and test application based functional/api testing. See the sample-app unit test directory as an example of coverage testing (https://github.com/nasa/sample_app/tree/main/unit-test), or any of the coverage testing in cFE, OSAL, or many of the open source GSFC apps. The test application for functional/api testing of cFE is here: https://github.com/nasa/cFE/tree/main/modules/cfe_testcase. We've recently started using CTF (https://github.com/nasa/ctf) along with CCDD (https://github.com/nasa/ccdd) for what you describe above. We do plan to eventually release those tests, but we haven't generalized them for open source yet (they are still project specific). |
Beta Was this translation helpful? Give feedback.
-
We are writing individual monitoring apps for cFS, and we'd like to test them.
The way we are doing it now is by adding some applications that can replay a complete run, but that means we'd be running many applications in the system even if we just want to test one. It also means that I have to inspect a log/terminal manually to see that my application is doing the right thing, but the output contains also data from other applications running simultaneously.
The kinds of properties I envision testing are of the following shape:
and so on.
What is the best way to test an individual app?
I see that there is this discussion, but it never reached a conclusion and it doesn't answer this question, as far as I can see.
Beta Was this translation helpful? Give feedback.
All reactions