X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/c9a55f6ac1c48adf32a02b21d628c0deb71b3e6f..7eb6c37c5084760c1d1469bd4be652b479a8df55:/test/README?ds=sidebyside diff --git a/test/README b/test/README index f51217537..653cf951f 100644 --- a/test/README +++ b/test/README @@ -91,9 +91,10 @@ In order to run this test suite, the following requirements must be met: (5) Exim must be built with its user and group specified at build time, and with certain minimum facilities, namely: - Routers: accept, dnslookup, manualroute, redirect - Transports: appendfile, autoreply, pipe, smtp - Lookups: lsearch + Routers: accept, dnslookup, manualroute, redirect + Transports: appendfile, autoreply, pipe, smtp + Lookups: lsearch + Authenticators: plaintext Most Exim binaries will have these included. @@ -237,6 +238,11 @@ is as follows: There are some options for the ./runtest script itself: + -CONTINUE This will allow the script to move past some failing tests. It will + write a simple failure line with the test number in a temporary + logfile test/failed-summary.log. Unexpected exit codes will still + stall the test execution and require interaction. + -DEBUG This option is for debugging the test script. It causes some tracing information to be output. @@ -434,6 +440,10 @@ OTHER ISSUES with an extra log line saying the hostname doesn't resolve. You must use a FQDN for the hostname for proper test functionality. +. If you change your hostname to a FQDN, you must delete the test/dnszones + subdirectory. When you next run the runtest script, it will rebuild the + content to use the new hostname. + . If your hostname has an uppercase characters in it, expect that some tests will fail, for example, 0036, because some log lines will have the hostname in all lowercase. The regex which extracts the hostname from the log lines @@ -448,6 +458,9 @@ OTHER ISSUES be on by default and you'll see this problem, so make sure your umask is 022 and re-checkout the test/ subdirectory. +. Some tests will fail if the username and group name are different. It does + not have to be the primary group, a secondary group is sufficient. + OTHER SCRIPTS AND PROGRAMS -------------------------- @@ -664,7 +677,7 @@ only when DBM support is available in Exim, and typically follows the use of a "write" command (see below) that creates the input file. - dumpdb + dump This command runs the exim_dumpdb utility on the testing spool directory, using the database name given, for example: "dumpdb retry". @@ -718,7 +731,7 @@ to the screen. munge This command requests custom munging of the test outputs. The munge names -used are coded in the runtest script. +used are coded in the runtest script (look for 'name of munge'). need_ipv4 @@ -823,7 +836,7 @@ This command runs the auxiliary "client" program that simulates an SMTP client. It is controlled by a script read from its standard input, details of which are given below. There are two options. One is -t, which must be followed directly by a number, to specify the command timeout in seconds (e.g. -t5). The default -timeout is 1 second. The other option is -tls-on-connect, which causes the +timeout is 5 seconds. The other option is -tls-on-connect, which causes the client to try to start up a TLS session as soon as it has connected, without using the STARTTLS command. The client program connects to the given IP address and port, using the specified interface, if one is given. @@ -834,9 +847,11 @@ and port, using the specified interface, if one is given. When OpenSSL is available on the host, an alternative version of the client program is compiled, one that supports TLS using OpenSSL. The additional -arguments specify a certificate and key file when required. There is one -additional option, -tls-on-connect, that causes the client to initiate TLS -negotiation immediately on connection. +arguments specify a certificate and key file when required for the connection. +There are two additional options: -tls-on-connect, that causes the client to +initiate TLS negociation immediately on connection; -ocsp that causes the TLS +negotiation to include a certificate-status request. The latter takes a +filename argument, the CA info for verifying the stapled response. client-gnutls [] [] \ @@ -882,13 +897,15 @@ input, details of which are given below. A number of options are implemented: -d causes the server to output debugging information - -t sets a timeout in seconds (default 5) for when the server is + -t sets a timeout (default 5) for when the server is awaiting an incoming connection -noipv4 causes the server not to set up an IPv4 socket -noipv6 causes the server not to set up an IPv6 socket + -i sets an initial pause, to delay before creating the listen sockets + By default, in an IPv6 environment, both kinds of socket are set up. However, the test script knows which interfaces actually exist on the host, and it adds -noipv4 or -noipv6 to the server command as required. An error occurs if both @@ -1004,7 +1021,10 @@ are of the following kinds: (d) If the line starts with ">*eof", nothing is sent and the connection is closed. - The data that is sent starts after the initial '>' sequence. + The data that is sent starts after the initial '>' sequence. Within + each line the sequence '\x' followed by two hex digits can be used + to specify an arbitrary byte value. The sequence '\\' specifies a + single backslash. (2) A line that starts with "*sleep" specifies a number of seconds to wait before proceeding. @@ -1018,7 +1038,10 @@ are of the following kinds: (5) Otherwise, the line defines the start of an input line that the client is expected to send. To allow for lines that start with digits, the line may start with '<', which is not taken as part of the input data. If the - input does not match, the server bombs out with an error message. + lines starts with '<<' then only the characters are expected; no return- + linefeed terminator. If the input does not match, the server bombs out + with an error message. Backslash-escape sequences may be used in the + line content as for output lines. Here is a simple example of server use in a test script: