Update documentation for uni tests to use the new tests directory
This commit is contained in:
parent
a5b9337fc8
commit
bf5d6fc37e
1 changed files with 3 additions and 6 deletions
|
@ -279,14 +279,11 @@ functionality. Most of the tests for cryptographic algorithms are
|
||||||
using standard test vectors to validate functionality. These tests can
|
using standard test vectors to validate functionality. These tests can
|
||||||
be useful especially when verifying port to a new CPU target.
|
be useful especially when verifying port to a new CPU target.
|
||||||
|
|
||||||
In most cases, these tests are implemented in the end of the same file
|
The test programs are collected in the tests subdirectory. All
|
||||||
with functions that are normally commented out, but ca be included by
|
automated unit tests can be run with
|
||||||
defining a pre-processor variable when building the file separately.
|
|
||||||
The details of the needed build options are included in the Makefile
|
|
||||||
(test-* targets). All automated unit tests can be run with
|
|
||||||
|
|
||||||
\verbatim
|
\verbatim
|
||||||
make tests
|
make run-tests
|
||||||
\endverbatim
|
\endverbatim
|
||||||
|
|
||||||
This make target builds and runs each test and terminates with zero
|
This make target builds and runs each test and terminates with zero
|
||||||
|
|
Loading…
Reference in a new issue