Kaspar Schleiser 8370acb2ff tests/riotboot_flashwrite: blacklist some boards
Adding saml1[01]-xpro, nucleo-f302r8|f334r8 to
BOARDS_INSUFFICIENT_MEMORY.

The riotboot build fails because it only offers half the flash size (per
slot), compared to before where the default build would not use riotboot
at all, thus have double the flash (but being useless).
2019-07-08 16:54:43 +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