Lines Matching refs:test
6 Each `ssl_*.cnf.in` file contains a number of test configurations. These files
9 The precise test output can be dependent on the library configuration. The test
14 `test/ssl-tests/*.cnf` files.
18 Configuring the test
21 First, give your test a name. The names do not have to be unique.
23 An example test input looks like this:
26 name => "test-default",
29 test => { "ExpectedResult" => "Success" },
32 The test section supports the following options
36 * Method - the method to test. One of DTLS or TLS.
38 * HandshakeMode - which handshake flavour to test:
40 - Resume - test resumption
41 - RenegotiateServer - test server initiated renegotiation
42 - RenegotiateClient - test client initiated renegotiation
45 to succeed. All configured test expectations are verified against the second
70 `test/helpers/ssl_test_ctx.c` for known values. Note: the expected alert is currently
130 ServerName test option. This context is used whenever a ServerNameCallback is
158 Used to test callback behaviour. One of
181 * BrokenSessionTicket - a special test case where the session ticket callback
212 Adding a test to the test harness
215 1. Add a new test configuration to `test/ssl-tests`, following the examples of
218 2. Generate the generated `*.cnf` test input file. You can do so by running
222 $ cd test
226 where `my.cnf.in` is your test input file and `default` is the provider to use.
227 For all the pre-generated test files you should use the default provider.
229 For example, to generate the test cases in `ssl-tests/01-simple.cnf.in`, do
238 in `test/recipes/80-test_ssl_new.t` and run
240 $ make TESTS=test_ssl_new test
244 3. Update the number of tests planned in `test/recipes/80-test_ssl_new.t`. If
245 the test suite has any skip conditions, update those too (see
246 `test/recipes/80-test_ssl_new.t` for details).
248 Running the tests with the test harness
251 HARNESS_VERBOSE=yes make TESTS=test_ssl_new test
253 Running a test manually
256 These steps are only needed during development. End users should run `make test`
257 or follow the instructions above to run the SSL test suite.
259 To run an SSL test manually from the command line, the `TEST_CERTS_DIR`
263 $ CTLOG_FILE=test/ct/log_list.cnf TEST_CERTS_DIR=test/certs test/ssl_test \
264 test/ssl-tests/01-simple.cnf default
268 $ CTLOG_FILE=test/ct/log_list.cnf TEST_CERTS_DIR=test/certs \
269 util/wrap.pl test/ssl_test test/ssl-tests/01-simple.cnf default
273 Note that the test expectations sometimes depend on the Configure settings. For
275 protocols: a build with `enable-ssl3` has different test expectations than a
278 The Perl test harness automatically generates expected outputs, so users who
279 just run `make test` do not need any extra steps.
281 However, when running a test manually, keep in mind that the repository version
282 of the generated `test/ssl-tests/*.cnf` correspond to expected outputs in with
287 Running a test manually via make
294 $ make test TESTS=test_ssl_new SSL_TESTS="0*.cnf.in"
296 $ make test TESTS=test_ssl_new SSL_TESTS="01-simple.cnf.in 05-sni.cnf.in"
