curl/tests
Daniel Stenberg debbcf81bb ignore more 2004-02-17 07:57:31 +00:00
..
data stop doing the weirdo symlinks 2004-02-12 14:39:28 +00:00
libtest ignore more 2004-02-17 07:57:31 +00:00
server make the path const 2004-02-13 07:05:15 +00:00
.cvsignore ignore the .pid files 2003-08-14 13:01:07 +00:00
FILEFORMAT added the missing stdin section 2004-02-05 21:51:45 +00:00
Makefile.am no need to run make test in the data dir anymore 2004-02-12 14:43:13 +00:00
README modified the TODO, we already do persistant tests 2004-01-13 07:39:42 +00:00
ftpserver.pl removed unused stuff 2004-01-16 06:50:41 +00:00
ftpsserver.pl Stop using stunnel.pm, we pass in the path from the main script instead. 2003-10-29 16:27:43 +00:00
getpart.pm provide a source path to the servers to make them find the tests when run 2004-02-12 14:40:08 +00:00
httpserver.pl provide a source path to the servers to make them find the tests when run 2004-02-12 14:40:08 +00:00
httpsserver.pl Stop using stunnel.pm, we pass in the path from the main script instead. 2003-10-29 16:27:43 +00:00
memanalyze.pl supports -l now to display the actual line that was prevented by memlimit 2003-10-24 12:59:58 +00:00
runtests.pl provide a source path to the servers to make them find the tests when run 2004-02-12 14:40:08 +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

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)

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 emtpied first
  in the runtests.pl script). Use runtests.pl -k to make the temporary files
  to be kept 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.

  The test case file format is simply a way to store different sections within
  the same physical file. The different sections are to be described here
  within shortly.


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, GOPHER, LDAP, DICT...