X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/03755744c9c07af50c92f44d287f1c4ea0db71be..9bf74b9c298f6968417fe88a68ccdf2179db1403:/test/README diff --git a/test/README b/test/README index 6c9a2d8da..67df47453 100644 --- a/test/README +++ b/test/README @@ -301,6 +301,11 @@ There are some options for the ./runtest script itself: -SLOW For very slow hosts that appear to have Heisenbugs, delay before comparing output files from a testcase + -TLS For cross-library testing. Specify 'openssl" or 'gnutls' + as the client; the other is used as the server (assumes that + both have been built: set up Local/Makefile for OpenSSL and + "make exim_openssl", then for GnuTLS and "make exim_gnutls") + The options for ./runtest must be given first (but after the name of the binary, if present). Any further options, that is, items on the command line that start with a hyphen, are passed to the Exim binary when it is run as part @@ -676,7 +681,12 @@ script. For example: # -bS Use of HELO/RSET A line consisting just of digits is interpreted as the expected return code -for the command that follows. The default expectation when no such line exists +for the command that follows. + +A line consisting of a tilde (~) followed by digits indicates a non-expected +return code for the command that follows. + +The default expectation when neither such line exists is a zero return code. For example, here is a complete test script, containing just one command: @@ -1145,7 +1155,7 @@ are of the following kinds: before proceeding. (3) A line containing "*data" and a number specifies that the client is - expected to send that many byte; the server discards them + expected to send that many bytes; the server discards them (4) A line containing "*eof" specifies that the client is expected to close the connection at this point.