5 \___|\___/|_| \_\_____|
11 1.2 Port numbers used by test servers
14 1.5 Shell startup scripts
23 2.1 Test case numbering
35 ==============================================================================
41 perl (and a unix-style shell)
42 python (and a unix-style shell)
43 diff (when a test fails, a diff is shown)
44 stunnel (for HTTPS and FTPS tests)
45 OpenSSH or SunSSH (for SCP, SFTP and SOCKS4/5 tests)
47 1.2 Port numbers used by test servers
53 - TCP/8994 for HTTP IPv6
54 - TCP/8995 for FTP (2)
55 - TCP/8996 for FTP IPv6
57 - UDP/8998 for TFTP IPv6
58 - TCP/8999 for SCP/SFTP
63 - TCP/9004 for SMTP IPv6
65 - TCP/9006 for RTSP IPv6
67 - TCP/9008 for GOPHER IPv6
68 - TCP/9008 for HTTPS server with TLS-SRP support
72 The test suite runs simple FTP, POP3, IMAP, SMTP, HTTP and TFTP stand-alone
73 servers on the ports listed above to which it makes requests. For SSL tests,
74 it runs stunnel to handle encryption to the regular servers. For SSH, it
75 runs a standard OpenSSH server. For SOCKS4/5 tests SSH is used to perform
76 the SOCKS functionality and requires a SSH client and server.
78 The base port number (8990), which all the individual port numbers are
79 indexed from, can be set explicitly using runtests.pl' -b option to allow
80 running more than one instance of the test suite simultaneously on one
81 machine, or just move the servers in case you have local services on any of
84 The HTTP server supports listening on a Unix domain socket, the default
85 location is 'http.sock'.
89 'make test'. This builds the test suite support code and invokes the
90 'runtests.pl' perl script to run all the tests. Edit the top variables
91 of that script in case you have some specific needs, or run the script
92 manually (after the support code has been built).
94 The script breaks on the first test that doesn't do OK. Use -a to prevent
95 the script from aborting on the first error. Run the script with -v for more
96 verbose output. Use -d to run the test servers with debug output enabled as
97 well. Specifying -k keeps all the log files generated by the test intact.
99 Use -s for shorter output, or pass test numbers to run specific tests only
100 (like "./runtests.pl 3 4" to test 3 and 4 only). It also supports test case
101 ranges with 'to', as in "./runtests 3 to 9" which runs the seven tests from
102 3 to 9. Any test numbers starting with ! are disabled, as are any test
103 numbers found in the files data/DISABLED or data/DISABLED.local (one per
104 line). The latter is meant for local temporary disables and will be ignored
107 When -s is not present, each successful test will display on one line the
108 test number and description and on the next line a set of flags, the test
109 result, current test sequence, total number of tests to be run and an
110 estimated amount of time to complete the test run. The flags consist of
111 these letters describing what is checked in this test:
122 1.5 Shell startup scripts
124 Tests which use the ssh test server, SCP/SFTP/SOCKS tests, might be badly
125 influenced by the output of system wide or user specific shell startup
126 scripts, .bashrc, .profile, /etc/csh.cshrc, .login, /etc/bashrc, etc. which
127 output text messages or escape sequences on user login. When these shell
128 startup messages or escape sequences are output they might corrupt the
129 expected stream of data which flows to the sftp-server or from the ssh
130 client which can result in bad test behaviour or even prevent the test
133 If the test suite ssh or sftp server fails to start up and logs the message
134 'Received message too long' then you are certainly suffering the unwanted
135 output of a shell startup script. Locate, cleanup or adjust the shell
140 The test script will check that all allocated memory is freed properly IF
141 curl has been built with the CURLDEBUG define set. The script will
142 automatically detect if that is the case, and it will use the
143 'memanalyze.pl' script to analyze the memory debugging output.
145 Also, if you run tests on a machine where valgrind is found, the script will
146 use valgrind to run the test with (unless you use -n) to further verify
149 runtests.pl's -t option will enable torture testing mode, which runs each
150 test many times and makes each different memory allocation fail on each
151 successive run. This tests the out of memory error handling code to ensure
152 that memory leaks do not occur even in those situations. It can help to
153 compile curl with CPPFLAGS=-DMEMDEBUG_LOG_SYNC when using this option, to
154 ensure that the memory log file is properly written even if curl crashes.
158 If a test case fails, you can conveniently get the script to invoke the
159 debugger (gdb) for you with the server running and the exact same command
160 line parameters that failed. Just invoke 'runtests.pl <test number> -g' and
161 then just type 'run' in the debugger to perform the command through the
166 All logs are generated in the logs/ subdirectory (it is emptied first in the
167 runtests.pl script). Use runtests.pl -k to force it to keep the temporary
168 files after the test run since successful runs will clean it up otherwise.
172 All test cases are put in the data/ subdirectory. Each test is stored in the
173 file named according to the test number.
175 See FILEFORMAT for the description of the test case files.
179 gcc provides a tool that can determine the code coverage figures for
180 the test suite. To use it, configure curl with
181 CFLAGS='-fprofile-arcs -ftest-coverage -g -O0'. Make sure you run the normal
182 and torture tests to get more full coverage, i.e. do:
187 The graphical tool ggcov can be used to browse the source and create
188 coverage reports on *NIX hosts:
192 The text mode tool gcov may also be used, but it doesn't handle object files
193 in more than one directory very well.
197 The runtests.pl script provides some hooks to allow curl to be tested on a
198 machine where perl can not be run. The test framework in this case runs on
199 a workstation where perl is available, while curl itself is run on a remote
200 system using ssh or some other remote execution method. See the comments at
201 the beginning of runtests.pl for details.
205 2.1 Test case numbering
212 500 - 599 libcurl source code tests, not using the curl command tool
214 700 - 799 SOCKS4 (even numbers) and SOCK5 (odd numbers)
218 1000 - 1299 miscellaneous
219 1300 - 1399 unit tests
220 1400 - 1499 miscellaneous
221 1500 - 1599 libcurl source code tests, not using the curl command tool
223 1600 - 1699 unit tests
224 2000 - x multiple sequential protocols per test case
226 There's nothing in the system that *requires* us to keep within these number
231 Here's a quick description on writing test cases. We basically have three
232 kinds of tests: the ones that test the curl tool, the ones that build small
233 applications and test libcurl directly and the unit tests that test
234 individual (possibly internal) functions.
238 Each test has a master file that controls all the test data. What to read,
239 what the protocol exchange should look like, what exit code to expect and
240 what command line arguments to use etc.
242 These files are tests/data/test[num] where [num] is described in section 2
243 of this document, and the XML-like file format of them is described in the
244 separate tests/FILEFORMAT document.
248 A test case that runs the curl tool and verifies that it gets the correct
249 data, it sends the correct data, it uses the correct protocol primitives
254 The libcurl tests are identical to the curl ones, except that they use a
255 specific and dedicated custom-built program to run instead of "curl". This
256 tool is built from source code placed in tests/libtest and if you want to
257 make a new libcurl test that is where you add your code.
261 Unit tests are tests in the 13xx sequence and they are placed in tests/unit.
262 There's a tests/unit/README describing the specific set of checks and macros
263 that may be used when writing tests that verify behaviors of specific
264 individual functions.
266 The unit tests depend on curl being built with debug enabled.
272 Add tests for TELNET, LDAP, DICT...
276 SOCKS4/5 test deficiencies - no proxy authentication tests as SSH (the
277 test mechanism) doesn't support them