From: Paolo Bonzini <pbonzini@redhat.com>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Pierrick Bouvier" <pierrick.bouvier@linaro.org>
Subject: Re: [PATCH 3/3] tests/functional: add -k TEST_NAME_PATTERN CLI arg
Date: Fri, 18 Jul 2025 11:37:05 +0200 [thread overview]
Message-ID: <1c805fa1-09c2-417a-9529-6ee9122d37dd@redhat.com> (raw)
In-Reply-To: <20250718-functional_tests_args-v1-3-54d4c6207690@linaro.org>
On 7/18/25 11:12, Manos Pitsidianakis wrote:
> Add a CLI argument that takes fnmatch(3)-style patterns as value and can
> be specified many times. Only tests that match the pattern will be
> executed. This argument is passed to unittest.main which takes the same
> argument.
>
> Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
> ---
> tests/functional/qemu_test/testcase.py | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/tests/functional/qemu_test/testcase.py b/tests/functional/qemu_test/testcase.py
> index 4455fcc38016c14db04019bbd64eaae9b47363c1..b7a660fd729afe39ff8cf7a0be97c2fc2f2f573f 100644
> --- a/tests/functional/qemu_test/testcase.py
> +++ b/tests/functional/qemu_test/testcase.py
> @@ -55,6 +55,14 @@ def parse_args(test_name: str) -> argparse.Namespace:
> action="store_true",
> help="List all tests that would be executed and exit.",
> )
> + parser.add_argument(
> + "-k",
> + dest="test_name_patterns",
> + action="append",
> + type=str,
> + help="Only run tests which match the given substring. "
> + "This argument is passed to unittest.main verbatim.",
> + )
> return parser.parse_args()
>
>
> @@ -301,8 +309,12 @@ def main():
>
> tr = pycotap.TAPTestRunner(message_log = pycotap.LogMode.LogToError,
> test_output_log = pycotap.LogMode.LogToError)
> + argv = ["__dummy__", path] + (
> + (["-k"] + args.test_name_patterns)
> + if args.test_name_patterns else []
> + )
This does not work for >1 occurrences of -k. Maybe something like:
argv = list(itertools.chain(
["__dummy__", "path"],
*[["-k", x] for x in args.test_name_patterns]))
Paolo
> res = unittest.main(module = None, testRunner = tr, exit = False,
> - argv=["__dummy__", path])
> + argv=argv)
> for (test, message) in res.result.errors + res.result.failures:
>
> if hasattr(test, "log_filename"):
>
next prev parent reply other threads:[~2025-07-18 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 9:12 [PATCH 0/3] tests/functional: add more CLI args Manos Pitsidianakis
2025-07-18 9:12 ` [PATCH 1/3] tests/functional: add --keep-scratch CLI arg Manos Pitsidianakis
2025-07-18 9:12 ` [PATCH 2/3] tests/functional: add --list-tests " Manos Pitsidianakis
2025-07-18 9:12 ` [PATCH 3/3] tests/functional: add -k TEST_NAME_PATTERN " Manos Pitsidianakis
2025-07-18 9:37 ` Paolo Bonzini [this message]
2025-07-18 9:44 ` Manos Pitsidianakis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c805fa1-09c2-417a-9529-6ee9122d37dd@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).