1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2025-12-28 16:01:18 +01:00
Gaëtan Harter 381382b61a
tests/rng: take into account stack buffers and printf
Take into account stack buffers and printf for allocating the default
stack size.

This solves stack size issues with `wsn430-v1_3b` and `z1`.
It now have a main stack usage of 514 bytes out of 768 on `wsn430-v1_3b`.
2019-05-28 15:43:15 +02:00
..
2018-06-11 19:12:02 +02:00
2019-05-24 17:56:42 +02:00
2018-06-11 19:12:02 +02:00
2019-05-24 17:56:42 +02:00
2019-05-24 17:56:42 +02:00
2019-05-24 17:56:42 +02:00
2019-05-24 17:56:42 +02:00
2019-05-24 17:56:42 +02:00
2019-05-24 17:56:42 +02:00
2018-12-04 00:01:42 +01:00
2019-05-24 17:56:42 +02:00

Running and creating tests

There are a number of tests included in RIOT. They are located in the tests folder. These tests allow basic functionality to be verified as well as provide an example of usage.

Running automated tests

Some tests can be performed automatically. The test automation scripts are defined in the <test_application>/tests/ folder. They are written in python and interact through the uart with the test application code running on a board to do the validation. It is recommended to flash the board with the test just before running it because some platforms cannot be reset while testing.

From the test application directory run:

BOARD=<board_of_your_choice> make flash test

An automated way of knowing if a test is available is to execute the 'test/available' target from the test application directory. It executes without error if tests run by 'make test' are present.

make test/available