3 SSL testcases are configured in the `ssl-tests` directory.
5 Each `ssl_*.conf.in` file contains a number of test configurations. These files
6 are used to generate testcases in the OpenSSL CONF format.
8 The precise test output can be dependent on the library configuration. The test
9 harness generates the output files on the fly.
11 However, for verification, we also include checked-in configuration outputs
12 corresponding to the default configuration. These testcases live in
13 `test/ssl-tests/*.conf` files. Therefore, whenever you're adding or updating a
14 generated test, you should run
19 $ TOP=.. perl -I testlib/ generate_ssl_tests.pl ssl-tests/my.conf.in \
23 where `my.conf.in` is your test input file.
25 For example, to generate the test cases in `ssl-tests/01-simple.conf.in`, do
28 $ TOP=.. perl generate_ssl_tests.pl ssl-tests/01-simple.conf.in > ssl-tests/01-simple.conf
31 For more details, see `ssl-tests/01-simple.conf.in` for an example.
33 ## Configuring the test
35 First, give your test a name. The names do not have to be unique.
37 An example test input looks like this:
41 name => "test-default",
42 server => { "CipherString" => "DEFAULT" },
43 client => { "CipherString" => "DEFAULT" },
44 test => { "ExpectedResult" => "Success" },
48 The test section supports the following options:
50 * ExpectedResult - expected handshake outcome. One of
51 - Success - handshake success
52 - ServerFail - serverside handshake failure
53 - ClientFail - clientside handshake failure
54 - InternalError - some other error
56 * ClientAlert, ServerAlert - expected alert. See `ssl_test_ctx.c` for known
59 * Protocol - expected negotiated protocol. One of
60 SSLv3, TLSv1, TLSv1.1, TLSv1.2.
62 * ClientVerifyCallback - the client's custom certificate verify callback.
63 Used to test callback behaviour. One of
64 - AcceptAll - accepts all certificates.
65 - RejectAll - rejects all certificates.
67 ## Configuring the client and server
69 The client and server configurations can be any valid `SSL_CTX`
70 configurations. For details, see the manpages for `SSL_CONF_cmd`.
72 Give your configurations as a dictionary of CONF commands, e.g.
76 "CipherString" => "DEFAULT",
77 "MinProtocol" => "TLSv1",
81 ### Default server and client configurations
83 The default server certificate and CA files are added to the configurations
84 automatically. Server certificate verification is requested by default.
86 You can override these options by redefining them:
90 "VerifyCAFile" => "/path/to/custom/file"
98 "VerifyCAFile" => undef
102 ## Adding a test to the test harness
104 Add your configuration file to `test/recipes/80-test_ssl_new.t`.
106 ## Running the tests with the test harness
109 HARNESS_VERBOSE=yes make TESTS=test_ssl_new test
112 ## Running a test manually
114 These steps are only needed during development. End users should run `make test`
115 or follow the instructions above to run the SSL test suite.
117 To run an SSL test manually from the command line, the `TEST_CERTS_DIR`
118 environment variable to point to the location of the certs. E.g., from the root
119 OpenSSL directory, do
122 $ TEST_CERTS_DIR=test/certs test/ssl_test test/ssl-tests/01-simple.conf
128 $ TEST_CERTS_DIR=test/certs util/shlib_wrap.sh test/ssl_test \
129 test/ssl-tests/01-simple.conf
132 Note that the test expectations sometimes depend on the Configure settings. For
133 example, the negotiated protocol depends on the set of available (enabled)
134 protocols: a build with `enable-ssl3` has different test expectations than a
135 build with `no-ssl3`.
137 The Perl test harness automatically generates expected outputs, so users who
138 just run `make test` do not need any extra steps.
140 However, when running a test manually, keep in mind that the repository version
141 of the generated `test/ssl-tests/*.conf` correspond to expected outputs in with
142 the default Configure options. To run `ssl_test` manually from the command line
143 in a build with a different configuration, you may need to generate the right
144 `*.conf` file from the `*.conf.in` input first.