Lines Matching refs:test
14 runtests.pl - run one or more test cases
22 *runtests.pl* runs one, several or all the existing test cases in curl's
23 test suite. It is often called from the root Makefile of the curl package with
24 'make test'.
28 Specify which test(s) to run by specifying test numbers or keywords.
30 If no test number or keyword is given, all existing tests that the script can
31 find are considered for running. You can specify single test cases to run by
32 specifying test numbers space-separated, like `1 3 5 7 11`, and you can
38 Prefix a test number with a tilde (~) to still run it, but ignore the results.
40 It is also possible to specify tests based on a keyword describing the test(s)
53 runtests.pl directly rather than via make, each test emits a pair of lines
59 the first line contains the test number and a description. On the second line,
61 behavior were checked by the test:
73 E the test was run event-based
75 The remainder of the second line contains the test result, current test sequence,
77 test run.
83 Continue running the rest of the test cases even if one test fails. By
84 default, the test script stops as soon as an error is detected.
88 Provide a path to a curl binary to talk to APIs (currently only CI test APIs).
92 Display test results in automake style output (`PASS/FAIL: [number] [name]`).
96 Run tests via bundled test binaries. Bundled test binaries contain all tests,
97 and the test name passed as the first argument selects which test run.
108 the specific test being run.
119 *keyword*, *test*, and *tool*.
121 ## `-e` or `--test-event`
123 Run the test event-based (if possible). This makes runtests invoke curl with
124 --test-event option. This option only works if both curl and libcurl were
129 Force the test to run even if mentioned in DISABLED.
133 Run the given test(s) with gdb. This is best used on a single test case and
135 run the specified test case. Simply (set a break-point and) type 'run' to
140 Run the given test(s) with lldb. This is best used on a single test case and
142 run the specified test case. Simply (set a break-point and) type 'run' to
147 Run the given test(s) with gdb as a windowed application.
157 multiple tests to run in parallel, speeding up a test run. The optimum number
165 Keep output and log files in log/ after a test run, even if no error was
173 regression test suite.
177 Lists all test case names.
197 themselves do not specify a proxy. This option allows one to test external
198 proxies using curl's regression test suite.
202 Prints out all files in the log directory to stdout when a test case fails.
229 This repeats the given set of test numbers this many times. If no test numbers
234 extended the test sequence.
250 mode to no more than **num** per test case. If this reduces the amount, the
258 Selects a **torture** test for the given tests. This makes runtests.pl first
260 reruns the test that number of times, each time forcing one of the allocations
266 ## `--test-duphandle`
268 Passes the `--test-duphandle` option to curl when invoked. This command line
276 HSTS data is not. A specific test case can be set to avoid using
277 `--test-duphandle` by disabling it on a per test basis.
287 test being run.
292 running are indeed our test servers. Default is the curl executable in the
297 Many tests have conditions that must be met before the test case can run fine.
302 The test script checks most of these by itself to determine when it is safe to
303 attempt to run each test. Those which cannot be run due to failed requirements
304 are simply skipped and listed at the completion of all test cases. In some
305 unusual configurations, the test script cannot make the correct determination
311 The simplest way to write test cases is to start with a similar existing test,
313 document the test case file format in **tests/FILEFORMAT.md**.
