To ensure that everything works properly once the library is compiled, there will be also a test suite in the NASPRO core package.

Such tests will cover more or less the whole library code and, apart from checking that everything runs fine in normal conditions, they will try to break the library as well in various ways (illegal input, stress tests, etc.)

Tests don't have to be documented like the rest of the code, but have to be well written and understandable, since they are the most immediate way to know exactly about problems on users' machines.

An header file (tests/tests.h) is there as well to help in writing such tests; it is documented and contains some convenience macros and functions to save test writers a lot of typewriting.

In the end, tests serve another purpose as well: they are examples of code using the library and focusing on a single aspect each time; so they are a good point to start learning about programming with this library.