Lines Matching +refs:run +refs:many +refs:tests

14 runtests.pl - run one or more test cases
18 **runtests.pl [options] [tests]**
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
33 specify a range of tests like `45 to 67`.
35 Specify tests to not run with a leading exclamation point, like `!66`, which
36 runs all available tests except number 66.
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)
41 to run, like `FTPS`. The keywords are strings used in the individual tests.
44 or phrase, like "!HTTP NTLM auth" to run all tests **except** those using this
46 somehow when entered at many command shells.
48 Prefix a keyword with a tilde (~) to still run it, but ignore the results.
73     E the test was run event-based
76 total number of tests to be run and an estimated amount of time to complete the
77 test run.
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.
101 Provide a path to a custom curl binary to run the tests with. Default is the
108 the specific test being run.
112 Load the **exclude_file** with additional reasons why certain tests should be
114 the tests are not appropriate.
118 the reason why matching tests should be skipped. The exclusion types are
129 Force the test to run even if mentioned in DISABLED.
135 run the specified test case. Simply (set a break-point and) type 'run' to
142 run the specified test case. Simply (set a break-point and) type 'run' to
155 Spawn the given number of processes to run tests in. This defaults to 0 to run
156 tests serially within a single process. Using a number greater than one allows
157 multiple tests to run in parallel, speeding up a test run. The optimum number
158 is dependent on the system and set of tests to run, but 7 times the number of
160 or 5 times for torture tests. Enabling parallel tests is not recommended in
165 Keep output and log files in log/ after a test run, even if no error was
196 Use the specified HTTP proxy when executing tests, even if the tests
203 Practical when used in the automated and distributed tests since then the
209 Run the tests in a scrambled, or randomized, order instead of sequentially.
216 Display run time statistics. (Requires the `Perl Time::HiRes` module)
220 Display full run time statistics. (Requires the `Perl Time::HiRes` module)
229 This repeats the given set of test numbers this many times. If no test numbers
230 are given, it repeats ALL tests this many times. It adds the new repeated
249 Used together with **-t**. This limits the number of tests to fail in torture
258 Selects a **torture** test for the given tests. This makes runtests.pl first
259 run the tests once and count the number of memory allocations made. It then
274 test being run.
278 Provide a path to a custom curl binary to run when verifying that the servers
284 Many tests have conditions that must be met before the test case can run fine.
290 attempt to run each test. Those which cannot be run due to failed requirements
293 for all tests. In these cases, the problematic tests can be skipped using the
300 document the test case file format in **tests/FILEFORMAT.md**.