curl 7.88.1源码下载

<!-- Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al. SPDX-License-Identifier: curl --> # The curl Test Suite # Running ## Requires to run - perl (and a unix-style shell) - python (and a unix-style shell, for SMB and TELNET tests) - python-impacket (for SMB tests) - diff (when a test fails, a diff is shown) - stunnel (for HTTPS and FTPS tests) - OpenSSH or SunSSH (for SCP, SFTP and SOCKS4/5 tests) - nghttpx (for HTTP/2 and HTTP/3 tests) - nroff (for --manual tests) - An available `en_US.UTF-8` locale ### Installation of python-impacket The Python-based test servers support both recent Python 2 and 3. You can figure out your default Python interpreter with python -V Please install python-impacket in the correct Python environment. You can use pip or your OS' package manager to install 'impacket'. On Debian/Ubuntu the package names are: - Python 2: 'python-impacket' - Python 3: 'python3-impacket' On FreeBSD the package names are: - Python 2: 'py27-impacket' - Python 3: 'py37-impacket' On any system where pip is available: - Python 2: 'pip2 install impacket' - Python 3: 'pip3 install impacket' You may also need to manually install the Python package 'six' as that may be a missing requirement for impacket on Python 3. ### Port numbers used by test servers All test servers run on "random" port numbers. All tests should be written to use suitable variables instead of fixed port numbers so that test cases continue to work independent on what port numbers the test servers actually use. See [`FILEFORMAT`](FILEFORMAT.md) for the port number variables. ### Test servers The test suite runs stand-alone servers on random ports to which it makes requests. For SSL tests, it runs stunnel to handle encryption to the regular servers. For SSH, it runs a standard OpenSSH server. For SOCKS4/5 tests SSH is used to perform the SOCKS functionality and requires a SSH client and server. The listen port numbers for the test servers are picked randomly to allow users to run multiple test cases concurrently and to not collide with other existing services that might listen to ports on the machine. The HTTP server supports listening on a Unix domain socket, the default location is 'http.sock'. For HTTP/2 and HTTP/3 testing an installed `nghttpx` is used. HTTP/3 tests check if nghttpx supports the protocol. To override the nghttpx used, set the environment variable `NGHTTPX`. The default can also be changed by specifying `--with-test-nghttpx=<path>` as argument to `configure`. ### Run `./configure && make && make test`. This builds the test suite support code and invokes the 'runtests.pl' perl script to run all the tests. Edit the top variables of that script in case you have some specific needs, or run the script manually (after the support code has been built). The script breaks on the first test that doesn't do OK. Use `-a` to prevent the script from aborting 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. Specifying `-k` keeps all the log files generated by the test intact. 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.pl 3 to 9` which runs the seven tests from 3 to 9. Any test numbers starting with ! are disabled, as are any test numbers found in the files `data/DISABLED` or `data/DISABLED.local` (one per line). The latter is meant for local temporary disables and will be ignored by git. Test cases mentioned in `DISABLED` can still be run if `-f` is provided. When `-s` is not present, each successful test will display on one line the test number and description and on the next line a set of flags, the test result, current test sequence, total number of tests to be run and an estimated amount of time to complete the test run. The flags consist of these letters describing what is checked in this test: s stdout d data u upload p protocol o output e exit code m memory v valgrind ### Shell startup scripts Tests which use the ssh test server, SCP/SFTP/SOCKS tests, might be badly influenced by the output of system wide or user specific shell startup scripts, .bashrc, .profile, /etc/csh.cshrc, .login, /etc/bashrc, etc. which output text messages or escape sequences on user login. When these shell startup messages or escape sequences are output they might corrupt the expected stream of data which flows to the sftp-server or from the ssh client which can result in bad test behavior or even prevent the test server from running. If the test suite ssh or sftp server fails to start up and logs the message 'Received message too long' then you are certainly suffering the unwanted output of a shell startup script. Locate, cleanup or adjust the shell script. ### Memory test 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.pl` script to analyze the memory debugging output. Also, if you run tests on a machine where valgrind is found, the script will use valgrind to run the test with (unless you use `-n`) to further verify correctness. The `runtests.pl` `-t` option enables torture testing mode. It runs each test many times and makes each different memory allocation fail on each successive run. This tests the out of memory error handling code to ensure that memory leaks do not occur even in those situations. It can help to compile curl with `CPPFLAGS=-DMEMDEBUG_LOG_SYNC` when using this option, to ensure that the memory log file is properly written even if curl crashes. ### 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 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. ### Logs All logs are generated in the log/ subdirectory (it is emptied first in the runtests.pl script). They remain in there after a test run. ### Log Verbosity A curl build with `--enable-debug` offers more verbose output in the logs. This applies not only for test cases, but also when running it standalone with `curl -v`. While a curl debug built is ***not suitable for production***, it is often helpful in tracking down problems. Sometimes, one needs detailed logging of operations, but does not want to drown in output. The newly introduced *connection filters* allows one to dynamically increase log verbosity for a particular *filter type*. Example: CURL_DEBUG=ssl curl -v https://curl.se will make the `ssl` connection filter log more details. One may do that for every filter type and also use a combination of names, separated by `,` or space. CURL_DEBUG=ssl,http/2 curl -v https://curl.se The order of filter type names is not relevant. Names used here are case insensitive. Note that these names are implementation internals and subject to change. Some, likely stable names are `tcp`, `ssl`, `http/2`. For a current list, one may search the sources for `struct Curl_cftype` definitions and find the names there. Also, some filters are only available with certain build options, of course. ### Test input files All test cases are put in the `data/` subdirectory. Each test is stored in the file named according to the test number. See [`FILEFORMAT`](FILEFORMAT.md) for a description of the test case file format. ### Code coverage gcc provides a tool that can determine the code coverage