Gaëtan Harter 7286a99e55
tests/unittests: enable boards with enough memory
Now that tests with packages have been moved out of `unittests`
re-enable boards with enough memory.

The removed boards list matches the boards that now compiled locally
with `BUILD_IN_DOCKER=1 make buildtest` and also the output of murdock
for boards that were able to link despite being in the list:

    avsextrem:gnu
    cc2538dk:gnu
    firefly:gnu
    mbed_lpc1768:gnu
    msba2:gnu
    openmote-b:gnu
    openmote-cc2538:gnu
    remote-pa:gnu
    remote-reva:gnu
    remote-revb:gnu
    seeeduino_arch-pro:gnu
2019-05-28 21:54:33 +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