{name} is a unique name of your choice.
Please note that if a test involves a new testing executable, you will need to
-do some additions in test/Makefile. More on this later.
+do some additions in test/build.info. Please refer to the section "Changes to
+test/build.info" below.
Naming conventions
20-24 openssl commands (some otherwise not tested)
25-29 certificate forms, generation and verification
30-35 engine and evp
-60-79 APIs
+60-79 APIs:
+ 60 X509 subsystem
+ 61 BIO subsystem
+ 65 CMP subsystem
70 PACKET layer
80-89 "larger" protocols (CA, CMS, OCSP, SSL, TSA)
90-98 misc
expects it to be located in test/
For documentation on OpenSSL::Test::Simple, do
-`perldoc test/testlib/OpenSSL/Test/Simple.pm'.
+`perldoc util/perl/OpenSSL/Test/Simple.pm'.
A recipe that runs a more complex test
For more complex tests, you will need to read up on Test::More and
OpenSSL::Test. Test::More is normally preinstalled, do `man Test::More' for
-documentation. For OpenSSL::Test, do `perldoc test/testlib/OpenSSL/Test.pm'.
+documentation. For OpenSSL::Test, do `perldoc util/perl/OpenSSL/Test.pm'.
A script to start from could be this:
basic test framework:
SOURCE[{name}]={name}.c
- INCLUDE[{name}]=.. ../include
+ INCLUDE[{name}]=.. ../include ../apps/include
DEPEND[{name}]=../libcrypto libtestutil.a
Generic form of C test executables
int observed;
observed = function(); /* Call the code under test */
- if (!TEST_int_equal(observed, 2)) /* Check the result is correct */
+ if (!TEST_int_eq(observed, 2)) /* Check the result is correct */
goto end; /* Exit on failure - optional */
testresult = 1; /* Mark the test case a success */
return testresult;
}
- void register_tests(void)
+ int setup_tests(void)
{
ADD_TEST(my_test); /* Add each test separately */
+ return 1; /* Indicate success */
}
You should use the TEST_xxx macros provided by testutil.h to test all failure