From bf5d6fc37eec13aa2f65d39607aec007288f2a82 Mon Sep 17 00:00:00 2001 From: Jouni Malinen Date: Wed, 23 Dec 2009 23:19:22 +0200 Subject: [PATCH] Update documentation for uni tests to use the new tests directory --- doc/testing_tools.doxygen | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/doc/testing_tools.doxygen b/doc/testing_tools.doxygen index a2ae0c250..f14403bcb 100644 --- a/doc/testing_tools.doxygen +++ b/doc/testing_tools.doxygen @@ -279,14 +279,11 @@ functionality. Most of the tests for cryptographic algorithms are using standard test vectors to validate functionality. These tests can 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 -with functions that are normally commented out, but ca be included by -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 +The test programs are collected in the tests subdirectory. All +automated unit tests can be run with \verbatim -make tests +make run-tests \endverbatim This make target builds and runs each test and terminates with zero