1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Commit Graph

9 Commits

Author SHA1 Message Date
René Kijewski
b17028bb46 tests/Travis: run unittests on x86, too 2014-06-24 21:07:20 +02:00
René Kijewski
d19fc447ed make: make DIRS usable for applications 2014-06-23 15:50:10 +02:00
Martin Lenders
f201ceed99 unittests: Force execution of $(UNITTEST_LIBS) build target 2014-05-27 10:41:28 +02:00
Martine Lenders
62139bd0d2 Merge pull request #1207 from Kijewski/unittests-makefile.include
unittests: support Makefile.include in test suites
2014-05-26 14:51:12 +02:00
Thomas Eichinger
1e983c9670 s/PROJECT/APPLICATION/g
fixes #548
2014-05-26 13:21:09 +02:00
René Kijewski
4df2f4b4da 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:20:35 +02:00
René Kijewski
0246329050 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:57:52 +02:00
René Kijewski
297bc52062 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 12:48:56 +02:00
Martin Lenders
9ce8ab2275 Create unittest application 2014-04-10 15:33:10 +02:00