RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
2b91605f58
RIOT/tests/unittests/Makefile

49 lines
1.2 KiB
Makefile
Raw Normal View History

make: don't use export on example makefiles
2014-05-05 21:54:10 +02:00
APPLICATION = unittests
Create unittest application
2014-04-07 15:15:25 +02:00
include ../Makefile.tests_common
USEMODULE += embunit
INCLUDES += -I$(RIOTBASE)/tests/unittests/embunit
ifeq ($(OUTPUT),XML)
CFLAGS += -DOUTPUT=OUTPUT_XML
USEMODULE += embunit_textui
else ifeq ($(OUTPUT),TEXT)
CFLAGS += -DOUTPUT=OUTPUT_TEXT
USEMODULE += embunit_textui
else ifeq ($(OUTPUT),COMPILER)
CFLAGS += -DOUTPUT=OUTPUT_COMPILER
USEMODULE += embunit_textui
endif
unittests: use subfolders for different tests Unittests for e.g. different libraries can be put into `tests/unittests/tests-XXX`, where `XXX` is your test suite. If `unittests` is made with `make all` (or any explicit argument), then all test suites get built. If you use `make tests-XXX tests-YYY …` then only the test suites `XXX` and `YYY` get built.
2014-05-14 11:13:53 +02:00
ifeq (, $(filter tests-%, $(MAKECMDGOALS)))
UNIT_TESTS := $(shell find -mindepth 1 -maxdepth 1 -type d -name 'tests-*' -printf '%f ')
else
UNIT_TESTS := $(filter tests-%, $(MAKECMDGOALS))
endif
Create unittest application
2014-04-07 15:15:25 +02:00
unittests: support Makefile.include in test suites This change will pull in the `Makefile.include` for every test suite that is compiled in. Fixes #1205.
2014-05-18 16:17:02 +02:00
# Pull in `Makefile.include`s from the test suites:
-include $(UNIT_TESTS:%=$(RIOTBASE)/tests/unittests/%/Makefile.include)
make: make DIRS usable for applications
2014-06-18 11:21:05 +02:00
DIRS += $(UNIT_TESTS)
BASELIBS += $(UNIT_TESTS:%=$(BINDIR)%.a)
unittests: use subfolders for different tests Unittests for e.g. different libraries can be put into `tests/unittests/tests-XXX`, where `XXX` is your test suite. If `unittests` is made with `make all` (or any explicit argument), then all test suites get built. If you use `make tests-XXX tests-YYY …` then only the test suites `XXX` and `YYY` get built.
2014-05-14 11:13:53 +02:00
make: make DIRS usable for applications
2014-06-18 11:21:05 +02:00
include $(RIOTBASE)/Makefile.include
unittests: use subfolders for different tests Unittests for e.g. different libraries can be put into `tests/unittests/tests-XXX`, where `XXX` is your test suite. If `unittests` is made with `make all` (or any explicit argument), then all test suites get built. If you use `make tests-XXX tests-YYY …` then only the test suites `XXX` and `YYY` get built.
2014-05-14 11:13:53 +02:00
$(UNIT_TESTS): all
unittests: separate test suites from main.c This change removes the need to patch the main.c if you add or remove a test suite. A test suite in `tests/unittests/tests-XXX` needs to export the function `void tests_XXX(void)`, which gets called by `main()`. The `tests-XXX/Makefile` looks like your average module: ``` MODULE = tests-XXX include $(RIOTBASE)/Makefile.base ```
2014-05-14 12:21:20 +02:00
charCOMMA := ,
ifeq (, $(UNIT_TESTS))
CFLAGS += -DNO_TEST_SUITES
$(warning There was no test suite specified!)
else
make: make DIRS usable for applications
2014-06-18 11:21:05 +02:00
CFLAGS += -DTEST_SUITES='$(subst $() $(),$(charCOMMA),$(UNIT_TESTS:tests-%=%))'
unittests: separate test suites from main.c This change removes the need to patch the main.c if you add or remove a test suite. A test suite in `tests/unittests/tests-XXX` needs to export the function `void tests_XXX(void)`, which gets called by `main()`. The `tests-XXX/Makefile` looks like your average module: ``` MODULE = tests-XXX include $(RIOTBASE)/Makefile.base ```
2014-05-14 12:21:20 +02:00
endif
tests/Travis: run unittests on x86, too
2014-05-29 04:40:43 +02:00
test: SHELL=bash
test:
@exec 5>&1 && \
LOG=$$("$(MAKE)" -s term | tee >(cat - >&5)) && \
grep 'OK ([1-9][0-9]* tests)' <<< $${LOG} > /dev/null
Copy Permalink