From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: [PATCH 3/3] test/argparse: add test for repeated arguments
Date: Mon, 16 Jun 2025 11:49:43 +0100 [thread overview]
Message-ID: <20250616104944.3425929-4-bruce.richardson@intel.com> (raw)
In-Reply-To: <20250616104944.3425929-1-bruce.richardson@intel.com>
Add a test case to check that argparse throws an error when an argument
is repeated on the commandline without the SUPPORT_MULTI flag. Also test
that multiple arguments are correctly handled with the flag.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
app/test/test_argparse.c | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/app/test/test_argparse.c b/app/test/test_argparse.c
index 57b85c4bf0..0a229752fa 100644
--- a/app/test/test_argparse.c
+++ b/app/test/test_argparse.c
@@ -329,6 +329,38 @@ test_argparse_invalid_option(void)
return 0;
}
+static int
+test_argparse_invalid_repeated_option(void)
+{
+ /* test that we allow repeated args only with the MULTI flag */
+ struct rte_argparse *obj;
+ char *argv[3];
+ int ret;
+
+ /* check that we error out with two "-a" flags */
+ obj = test_argparse_init_obj();
+ obj->args[0].val_saver = NULL;
+ obj->args[1].val_saver = NULL;
+ argv[0] = test_strdup(obj->prog_name);
+ argv[1] = test_strdup("-a");
+ argv[2] = test_strdup("-a");
+ ret = rte_argparse_parse(obj, 3, argv);
+ TEST_ASSERT(ret == -EINVAL, "Argparse did not error out with two '-a' flags!");
+
+ obj = test_argparse_init_obj();
+ obj->args[0].val_saver = NULL;
+ obj->args[1].val_saver = NULL;
+ obj->args[0].flags |= RTE_ARGPARSE_FLAG_SUPPORT_MULTI;
+ /* check that we allow two "-a" flags with MULTI flag set */
+ argv[0] = test_strdup(obj->prog_name);
+ argv[1] = test_strdup("-a");
+ argv[2] = test_strdup("-a");
+ ret = rte_argparse_parse(obj, 3, argv);
+ TEST_ASSERT(ret == 3, "Argparse failed to handle duplicate '-a' flags!");
+
+ return 0;
+}
+
static int
test_argparse_opt_autosave_parse_int_of_no_val(void)
{
@@ -864,6 +896,7 @@ static struct unit_test_suite argparse_test_suite = {
TEST_CASE(test_argparse_invalid_arg_flags),
TEST_CASE(test_argparse_invalid_arg_repeat),
TEST_CASE(test_argparse_invalid_option),
+ TEST_CASE(test_argparse_invalid_repeated_option),
TEST_CASE(test_argparse_opt_autosave_parse_int_of_no_val),
TEST_CASE(test_argparse_opt_autosave_parse_int_of_required_val),
TEST_CASE(test_argparse_opt_autosave_parse_int_of_optional_val),
--
2.48.1
prev parent reply other threads:[~2025-06-16 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 10:49 [PATCH 0/3] argparse: improve handling of multi-instance args Bruce Richardson
2025-06-16 10:49 ` [PATCH 1/3] argparse: track parsed arguments internally Bruce Richardson
2025-06-16 10:49 ` [PATCH 2/3] argparse: mark parameter struct as const Bruce Richardson
2025-06-16 10:49 ` Bruce Richardson [this message]
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=20250616104944.3425929-4-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.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).