4 For any test that you want to perform, you write a script located in
5 test/recipes/, named {nn}-test_{name}.t, where {nn} is a two digit number and
6 {name} is a unique name of your choice.
8 Please note that if a test involves a new testing executable, you will need to
9 do some additions in test/Makefile. More on this later.
15 A test executable is named test/{name}test.c
17 A test recipe is named test/recipes/{nn}-test_{name}.t, where {nn} is a two
18 digit number and {name} is a unique name of your choice.
20 The number {nn} is (somewhat loosely) grouped as follows:
22 00-04 sanity, internal and essential API tests
23 05-09 individual symmetric cipher algorithms
25 15-19 individual asymmetric cipher algorithms
26 20-24 openssl commands (some otherwise not tested)
27 25-29 certificate forms, generation and verification
31 80-89 "larger" protocols (CA, CMS, OCSP, SSL, TSA)
33 99 most time consuming tests [such as test_fuzz]
36 A recipe that just runs a test executable
37 =========================================
39 A script that just runs a program looks like this:
43 use OpenSSL::Test::Simple;
45 simple_test("test_{name}", "{name}test", "{name}");
47 {name} is the unique name you have chosen for your test.
49 The second argument to `simple_test' is the test executable, and `simple_test'
50 expects it to be located in test/
52 For documentation on OpenSSL::Test::Simple, do
53 `perldoc test/testlib/OpenSSL/Test/Simple.pm'.
56 A recipe that runs a more complex test
57 ======================================
59 For more complex tests, you will need to read up on Test::More and
60 OpenSSL::Test. Test::More is normally preinstalled, do `man Test::More' for
61 documentation. For OpenSSL::Test, do `perldoc test/testlib/OpenSSL/Test.pm'.
63 A script to start from could be this:
73 plan tests => 2; # The number of tests being performed
89 Changes to test/Makefile
90 ========================
92 Whenever a new test involves a new test executable you need to do the
93 following (at all times, replace {NAME} and {name} with the name of your
96 * among the variables for test executables at the beginning, add a line like
99 {NAME}TEST= {name}test
101 * add `$({NAME}TEST)$(EXE_EXT)' to the assignment of EXE:
103 * add `$({NAME}TEST).o' to the assignment of OBJ:
105 * add `$({NAME}TEST).c' to the assignment of SRC:
107 * add the following lines for building the executable:
109 $({NAME}TEST)$(EXE_EXT): $({NAME}TEST).o $(DLIBCRYPTO)
110 @target=$({NAME}TEST); $(BUILD_CMD)