1
0
mirror of https://github.com/moparisthebest/curl synced 2024-10-31 15:45:12 -04:00
curl/tests
Daniel Stenberg 9e037431b4 When staring a HTTP server, use the pidfile preferably since it turns out
sometimes the server can start but curl cannot speak to it, and then we must
remember the server (in order to kill it properly) anyway.

Also, make sure to kill all servers on exit everywhere.
2005-04-28 13:54:48 +00:00
..
data keyword update 2005-04-27 09:59:47 +00:00
libtest Olivier reported that even though he used CURLOPT_PORT, libcurl clearly still 2005-04-18 19:41:04 +00:00
server listen(..., 1) as 0 doesn't work on Tru64! 2005-04-27 12:28:04 +00:00
.cvsignore ignore more generated files 2005-04-28 11:22:18 +00:00
FILEFORMAT started adding "keywords" for each test, to better allow us to sum up what 2005-04-15 23:48:31 +00:00
ftp.pm Modified the FTP server to use the new 'sockfilt' program to do all the socket 2005-04-18 06:57:44 +00:00
ftpserver.pl kill slave processes when they fail 2005-04-28 07:36:55 +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 if diff -u makes zero output, try diff -c instead 2005-04-28 08:20:33 +00:00
httpserver.pl make sure the ipv6 http server gets its pid stored in a separate file 2004-12-14 21:52:16 +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
keywords.pl show what error codes we test for too, and show 10 test case numbers 2005-04-27 10:12:41 +00:00
Makefile.am Modified the FTP server to use the new 'sockfilt' program to do all the socket 2005-04-18 06:57:44 +00:00
memanalyze.pl James Bursa's fix to make this deal with malloc(0) as OK to free() 2004-05-07 18:54:09 +00:00
README mention what ports the test suite uses 2004-02-20 07:05:10 +00:00
runtests.1 format mistake 2005-03-21 07:45:18 +00:00
runtests.pl When staring a HTTP server, use the pidfile preferably since it turns out 2005-04-28 13:54:48 +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 Fixed spelling of --runtestopts 2005-03-18 18:41:50 +00:00
testcurl.pl Modified to not mix ordinary print to STDOUT with a system() that prints to 2005-04-18 05:46:10 +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

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

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