From: Jaehee Park <jhpark1013@gmail.com>
To: outreachy@lists.linux.dev, Julia Denham <jdenham@redhat.com>,
Roopa Prabhu <roopa.prabhu@gmail.com>,
Stefano Brivio <sbrivio@redhat.com>,
netdev@vger.kernel.org, jhpark1013@gmail.com
Subject: [PATCH] [net-next] selftests: net: vrf_strict_mode_test: add support to select a test to run
Date: Wed, 20 Apr 2022 00:46:47 -0400 [thread overview]
Message-ID: <20220420044647.GA1288137@jaehee-ThinkPad-X1-Extreme> (raw)
Add a boilerplate test loop to run all tests in
vrf_strict_mode_test.sh.
Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
---
.../testing/selftests/net/vrf_strict_mode_test.sh | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/net/vrf_strict_mode_test.sh b/tools/testing/selftests/net/vrf_strict_mode_test.sh
index 865d53c1781c..116ca43381b5 100755
--- a/tools/testing/selftests/net/vrf_strict_mode_test.sh
+++ b/tools/testing/selftests/net/vrf_strict_mode_test.sh
@@ -14,6 +14,8 @@ INIT_NETNS_NAME="init"
PAUSE_ON_FAIL=${PAUSE_ON_FAIL:=no}
+TESTS="vrf_strict_mode_tests_init vrf_strict_mode_tests_testns vrf_strict_mode_tests_mix"
+
log_test()
{
local rc=$1
@@ -391,7 +393,17 @@ fi
cleanup &> /dev/null
setup
-vrf_strict_mode_tests
+for t in $TESTS
+do
+ case $t in
+ vrf_strict_mode_tests_init|vrf_strict_mode_init) vrf_strict_mode_tests_init;;
+ vrf_strict_mode_tests_testns|vrf_strict_mode_testns) vrf_strict_mode_tests_testns;;
+ vrf_strict_mode_tests_mix|vrf_strict_mode_mix) vrf_strict_mode_tests_mix;;
+
+ help) echo "Test names: $TESTS"; exit 0;;
+
+ esac
+done
cleanup
print_log_test_results
--
2.25.1
next reply other threads:[~2022-04-20 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 4:46 Jaehee Park [this message]
2022-04-21 14:53 ` [PATCH] [net-next] selftests: net: vrf_strict_mode_test: add support to select a test to run Roopa Prabhu
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 4:55 [PATCH net-next] " Jaehee Park
2022-04-20 5:01 ` Jaehee
2022-04-21 14:52 ` Roopa Prabhu
2022-04-21 16:47 ` Jaehee Park
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=20220420044647.GA1288137@jaehee-ThinkPad-X1-Extreme \
--to=jhpark1013@gmail.com \
--cc=jdenham@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=roopa.prabhu@gmail.com \
--cc=sbrivio@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