The unittest folder contains the Makefile-FSFW-Tests which needs to be copied into project main directory. It is assumed that the FSFW is included there as a submodule.
Then the unittests can be built (right now only on Linux)
with
make -f Makefile-FSFW-Tests -j
which generates a binary which can be run (run with --success for success messages).
README still needs to be updated. This propably makes fsfw_tests repo obsolete
The unittest folder contains the Makefile-FSFW-Tests which needs to be copied into project main directory. It is assumed that the FSFW is included there as a submodule.
Then the unittests can be built (right now only on Linux)
with
```sh
make -f Makefile-FSFW-Tests -j
```
which generates a binary which can be run (run with --success for success messages).
README still needs to be updated. This propably makes fsfw_tests repo obsolete
Ok, I have thought about this request. If we integrate catch2, we have to updated the licence and notice.
As this packet is publicly avaiable and not mandatory for the functionallity of the fsfw itself, we shouldn't integrate catch2 here.
Ok, I have thought about this request. If we integrate catch2, we have to updated the licence and notice.
As this packet is publicly avaiable and not mandatory for the functionallity of the fsfw itself, we shouldn't integrate catch2 here.
gaisser
added this to the Release Apollo-Sojus-Test-Project (ASTP) 0.0.1 milestone 2020-10-27 13:53:09 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The unittest folder contains the Makefile-FSFW-Tests which needs to be copied into project main directory. It is assumed that the FSFW is included there as a submodule.
Then the unittests can be built (right now only on Linux)
with
which generates a binary which can be run (run with --success for success messages).
README still needs to be updated. This propably makes fsfw_tests repo obsolete
Ok, I have thought about this request. If we integrate catch2, we have to updated the licence and notice.
As this packet is publicly avaiable and not mandatory for the functionallity of the fsfw itself, we shouldn't integrate catch2 here.
Okay, we can do it like that but then we would keep fsfw_test I guess.