Allows to run functional tests like:
test/functional/test_runner.py --filter wallet
Allows to run functional tests like:
test/functional/test_runner.py --filter wallet
233 | @@ -234,6 +234,7 @@ def main(): 234 | parser.add_argument('--quiet', '-q', action='store_true', help='only print dots, results summary and failure logs') 235 | parser.add_argument('--tmpdirprefix', '-t', default=tempfile.gettempdir(), help="Root directory for datadirs") 236 | parser.add_argument('--failfast', action='store_true', help='stop execution after the first test failure') 237 | + parser.add_argument('--filter', help='regular expression to filter scripts to run')
Perhaps place it alphabetically, e.g. between extended and help. The failfast placement looks like an anomaly.
Suggested help: "filter tests to run by regular expression", or possibly "filter scripts to run by regular expression", in the format of verb + subject + details.
Argument --ci is also misplaced. Note that test/functional/test_runner.py --help already has the output sorted.
Updated message.
When I run test/functional/test_runner.py --help on Linux Debian, the output is not sorted (it's a bit of a mess TBH and am writing a PR to improve that and a few other things with the test runner output).
Concept ACK / tested ACK
ACK 1a6242526093424947eb49f3416dc0c6bc9fc3a8
Just saw this. What's wrong with ./test_runner.py wallet*?
Nothing wrong, you have to cd test/functional/ or something like that. This is also similar to bench_bitcoin -filter.
See the IRC discussion:
Currently, passing wildcard testname args to the test runner from outside the test/functional/ directory does not work. See these recent IRC discussions for more background: http://www.erisian.com.au/bitcoin-core-dev/log-2019-07-10.html#l-262 (lines 262 to 323) and http://www.erisian.com.au/bitcoin-core-dev/log-2019-07-11.html#l-134.
From #16374#issue-296813072