Updated readme for UnitTests
This commit is contained in:
parent
8ea0c571e4
commit
3264029256
|
@ -88,6 +88,7 @@ This is my personally preferred IDE setup for C/C++ and by no means needed to ac
|
||||||
clangd,
|
clangd,
|
||||||
Clang-Format,
|
Clang-Format,
|
||||||
CodeLLDB,
|
CodeLLDB,
|
||||||
|
C++ TestMate,
|
||||||
Docker and
|
Docker and
|
||||||
Remote Development
|
Remote Development
|
||||||
|
|
||||||
|
@ -151,6 +152,12 @@ You can also set the following variables in the CacheAnalysisPass/CacheAnalysisP
|
||||||
|
|
||||||
Helpful to understand what the program does but not very so much for the actual exercise.
|
Helpful to understand what the program does but not very so much for the actual exercise.
|
||||||
|
|
||||||
|
## UnitTest
|
||||||
|
|
||||||
|
The best way to see what your function does is to use the UnitTest.cpp.
|
||||||
|
With "C++ TestMate" install you can simply run or debug the test from the side panel in VS Code (Flask Icon).
|
||||||
|
The "C++ TestMate" is not installed in the VM as I just added this feature now.
|
||||||
|
Please feel free to add more test cases to your liking in UnitTest.cpp.
|
||||||
## Use the Helper script
|
## Use the Helper script
|
||||||
|
|
||||||
Again if you work on a Pool PC use poolhelper.sh insted of the helper.sh script.
|
Again if you work on a Pool PC use poolhelper.sh insted of the helper.sh script.
|
||||||
|
|
Loading…
Reference in New Issue