Lines Matching +full:protocol +full:- +full:tests
21 .\" * SPDX-License-Identifier: curl
27 runtests.pl \- run one or more test cases
29 .B runtests.pl [options] [tests]
34 .SH "TESTS"
37 If no test number or keyword is given, all existing tests that the script can
39 by specifying test numbers space-separated, like "1 3 5 7 11", and you can
40 specify a range of tests like "45 to 67".
42 Specify tests to not run with a leading exclamation point, like "!66", which
43 runs all available tests except number 66.
47 It is also possible to specify tests based on a keyword describing the test(s)
48 to run, like "FTPS". The keywords are strings used in the individual tests.
51 or phrase, like "!HTTP NTLM auth" to run all tests \fBexcept\fP those using
59 When running without -s (short output), for instance when running runtests.pl
62 Test 0045...[simple HTTP Location: without protocol in initial URL]
63 --pd---e-v- OK (45 out of 1427, remaining: 16:08, took 6.188s, duration: 00:31)
71 p protocol
79 E the test was run event-based
82 total number of tests to be run and an estimated amount of time to complete the
86 .IP "-a"
89 .IP "-ac <curl>"
91 .IP "-am"
93 .IP "-c <curl>"
94 Provide a path to a custom curl binary to run the tests with. Default is the
96 .IP "-d"
97 Enable protocol debug: have the servers display protocol output. If used in
100 .IP "-E <exclude_file>"
101 Load the \fBexclude_file\fP with additional reasons why certain tests
103 which case some of the tests aren't appropriate.
104 The file contains colon-delimited lines. The first field contains the
106 field contains the reason why matching tests should be skipped.
108 .IP "-e"
109 Run the test event-based (if possible). This will make runtests invoke curl
110 with --test-event option. This option only works if both curl and libcurl were
111 built debug-enabled.
112 .IP "-f"
114 .IP "-g"
116 curl built --disable-shared. This then fires up gdb with command line set to
117 run the specified test case. Simply (set a break-point and) type 'run' to
119 .IP "-gl"
121 curl built --disable-shared. This then fires up lldb with command line set to
122 run the specified test case. Simply (set a break-point and) type 'run' to
124 .IP "-gw"
126 .IP "-h, --help"
128 .IP "-j[num]"
129 Spawn num processes to run tests. This defaults to 0 to run tests serially
130 within a single process. Using a number greater than one allows multiple tests
132 the system and set of tests to run, but 7*number of CPU cores is a good figure
134 parallel tests is not recommended in conjunction with the \-g option.
135 .IP "-k"
138 .IP "-L <file>"
143 .IP "-l"
145 .IP "-n"
147 .IP "--no-debuginfod"
150 .IP "-o <variablename=value>"
154 .IP "-P <proxy>"
155 Use the specified HTTP proxy when executing tests, even if the tests
158 .IP "-p"
160 practical when used in the automated and distributed tests since then the
163 .IP "-R"
164 Run the tests in a scrambled, or randomized, order instead of sequentially.
167 \fI--seed\fP.
168 .IP "-r"
170 .IP "-rf"
172 .IP "-rm"
175 .IP "--repeat=[num]"
177 numbers are given, it will repeat ALL tests this many times. It iteratively
180 If \fB-R\fP is also used, the scrambling is done after the repeats have
182 .IP "-s"
184 .IP "--seed=[num]"
185 When using \fI--shallow\fP or \fI-R\fP that randomize certain aspects of the
188 of the "curl -V" output.
189 .IP "--shallow=[num]"
190 Used together with \fB-t\fP. This limits the number of tests to fail in
195 \fI--seed\fP.
196 .IP "-t[num]"
197 Selects a \fBtorture\fP test for the given tests. This makes runtests.pl first
198 run the tests once and count the number of memory allocations made. It then
203 combination with \fI-g\fP.
204 .IP "-u"
206 .IP "-v"
210 .IP "-vc <curl>"
214 .SH "RUNNING TESTS"
215 Many tests have conditions that must be met before the test case can run
216 fine. They could depend on built-in features in libcurl or features present in
217 the operating system or even in third-party libraries that curl may or may not
224 cannot make the correct determination for all tests. In these cases,
225 the problematic tests can be skipped using the "!keyword" skip feature
227 .SH "WRITING TESTS"
230 document the test case file format in the tests/FILEFORMAT.md.