Skip to content

Latest commit

 

History

History
 
 

unit_tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
googletest @ 542e057
googletest @ 542e057
 
 
test_basic_math
test_basic_math
 
 
tests
tests
 
 
.cproject
.cproject
 
 
.gitignore
.gitignore
 
 
.project
.project
 
 
Makefile
Makefile
 
 
adc_inputs.h
adc_inputs.h
 
 
afm2mapConverter.cpp
afm2mapConverter.cpp
 
 
afm2mapConverter.h
afm2mapConverter.h
 
 
boards.cpp
boards.cpp
 
 
boards.h
boards.h
 
 
compile.bat
compile.bat
 
 
efifeatures.h
efifeatures.h
 
 
engine_test_helper.cpp
engine_test_helper.cpp
 
 
engine_test_helper.h
engine_test_helper.h
 
 
global.h
global.h
 
 
global_execution_queue.cpp
global_execution_queue.cpp
 
 
gtest-all.cpp
gtest-all.cpp
 
 
jenkins.sh
jenkins.sh
 
 
main.cpp
main.cpp
 
 
map_resize.cpp
map_resize.cpp
 
 
map_resize.h
map_resize.h
 
 
readme.txt
readme.txt
 
 
rules.mk
rules.mk
 
 
settings.h
settings.h
 
 
test.mk
test.mk
 
 
triggers.txt
triggers.txt
 
 
unit_test_framework.cpp
unit_test_framework.cpp
 
 
unit_test_framework.h
unit_test_framework.h
 
 

readme.txt

In this folder we have a naive test suite.

I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:

Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU.

Run 'make' to build desktop binary & run it on your PC/Mac, it's expected to say SUCCESS and not fail :)