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
88349beb89
RIOT/tests/unittests/Makefile

57 lines
1.4 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
unittests: add spark-core to BOARD_INSUFFICIENT_RAM
2015-03-19 12:04:49 +01:00
BOARD_INSUFFICIENT_RAM := chronos msb-430 msb-430h redbee-econotag spark-core \
stm32f0discovery telosb wsn430-v1_3b wsn430-v1_4 z1 \
nucleo-f334
cbor: CBOR implementation for RIOT-OS This is a malloc-free implementation of the Concise Binary Object Representation (CBOR) data format for the RIOT-OS. This implementation mostly stand-alone, and it should be pretty easy to port to other platforms. We're only using the C STL and some custom network-related functionaliy which could be easily replaced by depending on arpa/inet.h. The CBOR API is straight-forward to use and provides encoding/decoding functionality for all major C types, such as: - int - uint64_t - int64_t - float - double - char* - struct tm - time_t It is possible to conditionally compile this module via CFLAGS: - CBOR_NO_SEMANTIC_TAGGING: All semantic-tagging features removed - CBOR_NO_CTIME: All ctime related features removed - CBOR_NO_FLOAT: All floating-point related features removed - CBOR_NO_PRINT: All features depending on printf removed
2014-07-14 21:40:04 +02:00
Create unittest application
2014-04-07 15:15:25 +02:00
USEMODULE += embunit
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)))
unittests: make: Fix unittests for branch changes Changing between branches in git typically leaves directories empty and does not remove them. If you have different unittests in different branches this leads to an error in building them, since the current configuration expects a Makefile in all `tests-*` directory. This change configures Make to search for a Makefile in `tests-*` rather than just assuming that there is one.
2014-09-08 11:56:01 +02:00
UNIT_TESTS := $(foreach d,$(wildcard tests-*/Makefile),$(shell dirname $(d)))
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
else
UNIT_TESTS := $(filter tests-%, $(MAKECMDGOALS))
endif
Create unittest application
2014-04-07 15:15:25 +02:00
unittests: do not use auto_init
2014-08-21 20:45:36 +02:00
DISABLE_MODULE += auto_init
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)
unittests: add test network device The reasoning behind this commit is twofold: 1. test the "lower" part (the device part) of netdev 2. provide a well defined testing infrastructure for modules that utilise netdev The actual tests that represent 1. are provided in the following commit
2014-08-08 13:48:14 +02:00
ifneq (,$(filter netdev_dummy,$(USEMODULE)))
USEMODULE += netdev_base
DIRS += netdev_dummy
INCLUDES += -I$(RIOTBASE)/tests/unittests/netdev_dummy/include
endif
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
unittests: move test data to common header
2015-03-20 19:57:08 +01:00
INCLUDES += -I$(RIOTBASE)/tests/unittests/common
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
unittests: move test data to common header
2015-03-20 19:57:08 +01:00
include $(RIOTBASE)/Makefile.include
unittests: Provide unittests for net_dev_dummy * tests if net_dev_dummy is correct and if driver part of net_dev is correct
2014-08-08 19:21:03 +02:00
unittests: Simplify module-wise rebuild
2014-08-27 14:04:22 +02:00
.PHONY: FORCE $(UNIT_TESTS)
FORCE:
touch $(CURDIR)/main.c
all: FORCE
$(UNIT_TESTS): FORCE all
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
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