aboutsummaryrefslogtreecommitdiff
path: root/tests/runtests.1
AgeCommit message (Collapse)Author
2020-03-04runtests.1: rephrase how to specify what tests to runDaniel Stenberg
Also mention the new tilde-prefixed way to ignore test results. Reviewed-By: Marc Hoersken Closes #5033
2020-01-09runtests: make random seed fixed for a monthDaniel Stenberg
When using randomized features of runtests (-R and --shallow) it is useful to have a fixed random seed to make sure for example extra commits in a branch or a rebase won't change the seed that would make repeated runs work differently. As it is also useful to change seed sometimes, the default seed is now determined based on the current month (and first line curl -V output). When the month changes, so will the random seed. The specific seed is also shown in the standard test suite top header and it can be set explictly with the new --seed=[num] option so that the exact order of a previous run can be achieved. Closes #4734
2019-12-15runtests: --repeat=[num] to repeat testsDaniel Stenberg
Closes #4715
2019-12-11runtests: introduce --shallow to reduce huge torture testsDaniel Stenberg
When set, shallow mode limits runtests -t to make no more than NUM fails per test case. If more are found, it will randomly discard entries until the number is right. The random seed can also be set. This is particularly useful when running MANY tests as then most torture failures will already fail the same functions over and over and make the total operation painfully tedious. Closes #4699
2017-05-05runtests: use -R for random orderDaniel Stenberg
Suggested-by: Dan Fandrich
2017-05-04runtests: add -o to run test cases in scrambled orderDaniel Stenberg
... instead of numerical order. Closes #1466
2016-02-03URLs: change all http:// URLs to https://Daniel Stenberg
2013-08-26runtests.pl: allow -vc point to a separate curl binary to verify withDaniel Stenberg
The specified curl binary will then be used to verify the running server(s) instead of the development version. This is very useful in some cases when the development version fails to verify correctly as then the test case may not run at all. The actual test will still be run with the "normal" curl executable (unless the test case specifies something differently).
2013-08-20curl_easy_perform_ev: debug/test functionDaniel Stenberg
This function is meant to work *exactly* as curl_easy_perform() but will use the event-based libcurl API internally instead of curl_multi_perform(). To avoid relying on an actual event-based library and to not use non-portable functions (like epoll or similar), there's a rather inefficient emulation layer implemented on top of Curl_poll() instead. There's currently some convenience logging done in curl_easy_perform_ev which helps when tracking down problems. They may be suitable to remove or change once things seem to be fine enough. curl has a new --test-event option when built with debug enabled that then uses curl_easy_perform_ev() instead of curl_easy_perform(). If built without debug, using --test-event will only output a warning message. NOTE: curl_easy_perform_ev() is not part if the public API on purpose. It is only present in debug builds of libcurl and MUST NOT be considered stable even then. Use it for libcurl-testing purposes only. runtests.pl now features an -e command line option that makes it use --test-event for all curl command line tests. The man page is updated.
2010-03-24remove the CVSish $Id$ linesDaniel Stenberg
2010-02-02mention run time statistics optionsYang Tse
2008-07-27Added feature in runtests.pl to select tests based on key word.Dan Fandrich
2008-07-23Mention that the test harness can't check every possible feature.Dan Fandrich
2007-10-11Fixed the -l option of runtests.plDan Fandrich
Added support for skipping tests based on key words.
2005-03-21format mistakeDaniel Stenberg
2005-03-17added descriptionsDaniel Stenberg
2005-03-17its a startDaniel Stenberg