curl/tests
Yang Tse c54a4301ee Abort test if it seems that it would have run forever. This is just to prevent
test hanging and actually is an indication that there's a condition that is
not being properly handled at some point in the library.

Remove a pair of braces and adjust indentation appropriately.
2006-10-24 15:51:42 +00:00
..
data Armel Asselin separated CA cert verification problems from problems with 2006-10-21 11:32:05 +00:00
libtest Abort test if it seems that it would have run forever. This is just to prevent 2006-10-24 15:51:42 +00:00
server Avoid trying to compare more than strlen bytes. 2006-10-23 19:16:19 +00:00
.cvsignore ignore more generated files 2005-04-28 11:22:18 +00:00
FILEFORMAT filled in some docs for the FTP server control commands 2006-09-23 20:39:34 +00:00
Makefile.am removed ftpsserver.pl 2005-04-28 13:55:16 +00:00
README David Shaw finally removed all traces of Gopher and we are now officially 2006-01-16 22:14:37 +00:00
ftp.pm added function for individual ftp slave kills 2005-05-25 12:26:38 +00:00
ftpserver.pl Fix a "sockfilt" leak. When a new 'data' connection sockfilt server is started, 2006-10-08 08:43:32 +00:00
getpart.pm fixed the attribute parser to better handle multiple ones, with or without 2005-04-28 21:05:40 +00:00
httpserver.pl support --fork and pass that on to sws 2006-04-10 13:09:56 +00:00
httpsserver.pl Use /usr/bin/env to invoke perl like the other test scripts. 2006-08-23 21:20:00 +00:00
keywords.pl sum up 2005-05-20 11:14:44 +00:00
memanalyze.pl Support realloc() on a NULL pointer properly (printf(%p) on a NULL pointer 2005-08-04 23:05:36 +00:00
runtests.1 format mistake 2005-03-21 07:45:18 +00:00
runtests.pl catch silly mistakes better 2006-10-06 21:19:40 +00:00
stunnel.pem Peter Sylvester brought code that now allows a callback to modified the URL 2004-01-12 15:26:32 +00:00
testcurl.1 added -nobuildconf 2005-05-20 11:24:55 +00:00
testcurl.pl buildconf already runs ares/buildconf by itself if there is an ares subdir 2006-10-17 11:46:42 +00:00
valgrind.pm Moved out the valgrind report parser to valgrind.pm, to make it easier to 2005-02-10 08:50:33 +00:00

README

                                  _   _ ____  _     
                              ___| | | |  _ \| |    
                             / __| | | | |_) | |    
                            | (__| |_| |  _ <| |___ 
                             \___|\___/|_| \_\_____|

The cURL Test Suite

Requires:
  perl (and a unix-style shell)
  diff (when a test fail, a diff is shown)
  stunnel (for HTTPS and FTPS tests)

TCP ports used:

  - 8999 on localhost for HTTP tests
  - 8433 on localhost for HTTPS tests
  - 8921 on localhost for FTP tests
  - 8821 on localhost for FTPS tests (currently disabled)

  The test suite runs simple FTP and HTTP servers on these ports to which
  it makes requests.

Run:
  'make test'. This invokes the 'runtests.pl' perl script. Edit the top
  variables of that script in case you have some specific needs.

  The script breaks on the first test that doesn't do OK. Use -a to prevent
  the script to abort on the first error. Run the script with -v for more
  verbose output. Use -d to run the test servers with debug output enabled as
  well.

  Use -s for shorter output, or pass test numbers to run specific tests only
  (like "./runtests.pl 3 4" to test 3 and 4 only). It also supports test case
  ranges with 'to'. As in "./runtests 3 to 9" which runs the seven tests from
  3 to 9.

Memory:
  The test script will check that all allocated memory is freed properly IF
  curl has been built with the CURLDEBUG define set. The script will
  automatically detect if that is the case, and it will use the ../memanalyze
  script to analyze the memory debugging output.

Debug:
  If a test case fails, you can conveniently get the script to invoke the
  debugger (gdb) for you with the server running and the exact same command
  line parameters that failed. Just invoke 'runtests.pl <test number> -g' and
  then just type 'run' in the debugger to perform the command through the
  debugger.

  If a test case causes a core dump, analyze it by running gdb like:

          # gdb ../curl/src core

  ... and get a stack trace with the gdb command:

          (gdb) where

Logs:
  All logs are generated in the logs/ subdirctory (it is emptied first
  in the runtests.pl script). Use runtests.pl -k to keep the temporary files
  after the test run.

Data:
  All test cases are put in the data/ subdirctory. Each test is stored in the
  file named according to the test number.

  See FILEFORMAT for the description of the test case files.


TEST CASE NUMBERS

 So far, I've used this system:

 1   -  99   HTTP
 100 - 199   FTP
 200 - 299   FILE
 300 - 399   HTTPS
 400 - 499   FTPS
 500 - 599   libcurl source code tests, not using the curl command tool

 Since 30-apr-2003, there's nothing in the system that requires us to keep
 within these number series. Each test case now specifies its own server
 requirements, independent of test number.

TODO:

  * Add tests for TELNET, LDAP, DICT...