riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix typo

Browse Source
This commit is contained in:
Lotte Steenbrink 2016-07-20 12:20:50 +02:00 committed by GitHub
parent cbd1fa4bc0
commit fef429e16b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/unittests/README.md
View File

@ -92,7 +92,7 @@ make term
## Writing unit tests ## Writing unit tests
### File struture ### File struture
RIOT uses [*embUnit*](http://embunit.sourceforge.net/) for unit testing. RIOT uses [*embUnit*](http://embunit.sourceforge.net/) for unit testing.
All unit tests are organized in ``tests/unittests`` and can be build module-wise, if needed. All unit tests are organized in ``tests/unittests`` and can be built module-wise, if needed.
For each module there exists a ``tests-<modulename>/tests-<modulename>.h`` file, at least one C file in ``tests-<modulename>/`` and a ``tests-<modulename>/Makefile``. For each module there exists a ``tests-<modulename>/tests-<modulename>.h`` file, at least one C file in ``tests-<modulename>/`` and a ``tests-<modulename>/Makefile``.
It is recommended to add a C file named ``tests-<modulename>/tests-<modulename>-<headername>.c`` for every header file that defines functions (or macros) implemented in the module. It is recommended to add a C file named ``tests-<modulename>/tests-<modulename>-<headername>.c`` for every header file that defines functions (or macros) implemented in the module.
If there is only one such header file ``tests-<modulename>/tests-<modulename>.c`` should suffice. If there is only one such header file ``tests-<modulename>/tests-<modulename>.c`` should suffice.