Juan Carrano 3b8deac3e9 sys/ubjson: deprecate module.
Summary for Users
=================

 Deprecation is scheduled for 2020.01.
 Users which depend on this module and cannot switch libraries may copy
 the code into to their own application.

As expressed in PR #11724, the UBJSON module has issues which are not easy
or worth fixing.

Before removing the module, it should be marked as deprecated to give users
time to either migrate to another library, or copy the code to their own
private repo.

The deprecation warning has been supressed from the unit tests. This has the
ugly side-effect of supressing deprecation warning in other unit tests too,
but that should not last long, only until the module is finally deleted.
2019-06-28 18:28:16 +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
2019-06-28 18:28:16 +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