I18N: Fix protocol recorded for a multi-SMTPUTF8-message connection. Bug 2287

[users/heiko/exim.git] / test / README

diff --git a/test/README b/test/README
index 8164cb2c8cd43dac26b49f497b23ad9a108f9e9e..f9ee5d0a9d6f57a93ae68803526abb2cd2213ff1 100644 (file)
--- a/test/README
+++ b/test/README
@@ -146,10 +146,10 @@ the extra functionality, except for a few special cases such as the databases
 RUNNING THE TEST SUITE
 ----------------------
 
-(1) Download the tarball exim-testsuite-x.xx.tar.bz2 and unpack it, preferably
-    in a directory alongside an Exim source directory (see below).
+(1) Clone the git tree for Exim.  This include both the Exim source and the
+    testsuite.
 
-(2) cd into the exim-testsuite-x.xx directory.
+(2) cd into the test/ subdirectory (where this README lives).
 
 (3) Run "./configure" and then "make". This builds a few auxiliary programs that
     are written in C.
@@ -1030,11 +1030,16 @@ Lines in client scripts are of two kinds:
     line is input to be sent to the server.  Backslash escaping is done as
     described below, but no trailing "\r\n" is sent.
 
-(4) Otherwise, the line is an input line line that is sent to the server. Any
+(4) If a line begin with three '<' characters and a space, the rest of the
+    line is a filename; the content of the file is inserted intto the script
+    at this point.
+
+(5) Otherwise, the line is an input line line that is sent to the server. Any
     occurrences of \r and \n in the line are turned into carriage return and
     linefeed, respectively. This is used for testing PIPELINING.
     Any sequences of \x followed by two hex digits are converted to the equvalent
     byte value.  Any other character following a \ is sent verbatim.
+    The line is sent with a trailing "\r\n".
 
 Here is a simple example: