1 The file format of the test suite is a very simple and extendable format. All
2 data for a single test case resides in a single ASCII file. Labels mark the
3 beginning and the end of all sections. Each label must be written in its own
4 line and is resembling XML/HTML.
6 Each file is split up in three main sections: reply, client and verify. The
7 reply section is used for the server to know what to send as a reply for the
8 requests curl sends, the client section defines how the client should behave
9 while the verify section defines how to verify that the data stored after a
10 command has been run ended up correctly.
12 Each main section has a number of available subsections that can be
13 specified, that will be checked/used if specified. This document includes all
14 the subsections currently supported.
18 data to sent to the client on its request and later verified that it arrived
19 safely. Set the nocheck=1 to prevent the test script to verify the arrival
23 Send back this contents instead of the <data> one. The num is set by:
24 A) The test number in the request line is >10000 and this is the remainder
25 of [test case number]%10000.
26 B) The request was HTTP and included digest details, which sets NUM to 1000.
27 C) If a HTTP request is NTLM type-1, it sets num to 1001
28 D) If a HTTP request is NTLM type-3, it sets num to 1002
30 <datacheck [nonewline=yes]>
31 if the data is sent but this is what should be checked afterwards. If
32 'nonewline' is set, we will cut off the trailing newline of this given data
33 before comparing with the one actually received by the client
36 number to return on a ftp SIZE command (set to -1 to make this command fail)
39 what to send back if the client sends a (FTP) MDTM command, set to -1 to
40 have it return that the file doesn't exist
43 special purpose server-command to control its behavior *before* the
47 special purpose server-command to control its behavior *after* the
55 protocols as in 'http' 'ftp' etc. Give only one per line. Used for test cases
56 500+ (at this point) to specify which servers the test case requires. In the
57 future all test cases should use this. Makes us independent of the test
62 A list of features that must be present in the client/library for this test
63 to be able to run. Features testable here are:
69 Using the same syntax as in <server> but when mentioned here these servers
70 are explicitly KILLED when this test case is completed. Only use this if there
71 is no other alternatives. Using this of course requires subsequent tests to
76 Name of tool to use instead of "curl". This tool must be built and exist
77 in the libtest/ directory.
88 Set the given environment variables to the specified value before the actual
89 command is run, they are clear again after the command has been run.
92 <command [option=no-output]>
93 command line to run, there's a bunch of %variables that get replaced
94 accordingly. more about them elsewhere
96 Set 'option=no-output' to prevent the test script to slap on the --output
97 argument that directs the output to a file. The --output is also not added if
98 the client/stdout section is used.
100 Available substitute variables include:
101 %HOSTIP - IP address of the host running this test
102 %HOSTPORT - Port number of the HTTP server
103 %HTTPSPORT - Port number of the HTTPS server
104 %FTPPORT - Port number of the FTP server
105 %FTPSPORT - Port number of the FTPS server
106 %SRCDIR - Full path to the source dir
107 %PWD - Current directory
110 <file name="log/filename">
111 this creates the named file with this content before the test case is run
112 which is useful if the test case needs a file to act on.
119 numerical error code curl is supposed to return
122 One regex per line that is removed from the protocol dumps before the
123 comparison is made. This is very useful to remove dependencies on dynamicly
124 changing protocol data such as port numbers or user-agent strings.
126 <protocol [nonewline=yes]>
127 the protocol dump curl should transmit, if 'nonewline' is set, we will cut
128 off the trailing newline of this given data before comparing with the one
129 actually sent by the client
132 This verfies that this data was passed to stdout.
134 <file name="log/filename">
135 the file's contents must be identical to this
138 the contents of the upload data curl should have sent