From: Yaqi Tang <yaqi.tang@intel.com>
To: dts@dpdk.org
Cc: Yaqi Tang <yaqi.tang@intel.com>
Subject: [dts][PATCH V1] test_plans/coremask: modify test case name
Date: Wed, 8 Jun 2022 04:49:18 +0000 [thread overview]
Message-ID: <20220608044918.350522-1-yaqi.tang@intel.com> (raw)
The case name of test case 3 does not match the test script, so modify the case name of test case 3.
And adjust the format of test plan according to test plan template.
Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
---
test_plans/coremask_test_plan.rst | 52 +++++++++++++++----------------
1 file changed, 25 insertions(+), 27 deletions(-)
diff --git a/test_plans/coremask_test_plan.rst b/test_plans/coremask_test_plan.rst
index b14d561f..074c8191 100644
--- a/test_plans/coremask_test_plan.rst
+++ b/test_plans/coremask_test_plan.rst
@@ -12,54 +12,52 @@ Prerequisites
This test will run in any machine able to run ``test``. No traffic will be sent.
No extra needs for ports.
+Test Case
+=========
-Test Case: individual coremask
-==============================
+Test Case 1: individual coremask
+--------------------------------
-Launch ``test`` once per core, set the core mask for the core::
+1. Launch ``test`` once per core, set the core mask for the core::
./x86_64-default-linuxapp-gcc/app/test/dpdk-test -c <One core mask> -n 4
+2. Verify: every time the application is launched the core is properly detected
+ and used.
-Verify: every time the application is launched the core is properly detected
-and used.
+3. Stop ``test``.
-Stop ``test``.
+Test Case 2: big coremask
+-------------------------
-Test Case: big coremask
-=======================
+1. Launch ``test`` with a mask bigger than the available cores::
-Launch ``test`` with a mask bigger than the available cores::
+ ./x86_64-default-linuxapp-gcte't'sc/app/test/dpdk-test -c <128 bits mask> -n 4
- ./x86_64-default-linuxapp-gcc/app/test/dpdk-test -c <128 bits mask> -n 4
+2. Verify: the application handles the mask properly and all the available cores
+ are detected and used.
+3. Stop ``test``.
-Verify: the application handles the mask properly and all the available cores
-are detected and used.
+Test Case 3: all cores coremask
+-------------------------------
-Stop ``test``.
-
-Test Case: all cores
-====================
-
-Launch ``test`` with all the available cores::
+1. Launch ``test`` with all the available cores::
./x86_64-default-linuxapp-gcc/app/test/dpdk-test -c <All cores mask> -n 4
+2. Verify: all the cores have been detected and used by the application.
-Verify: all the cores have been detected and used by the application.
+3. Stop ``test``.
-Stop ``test``.
+Test Case 4: wrong coremask
+---------------------------
-Test Case: wrong coremask
-=========================
-
-Launch ``test`` with several wrong masks::
+1. Launch ``test`` with several wrong masks::
./x86_64-default-linuxapp-gcc/app/test/dpdk-test -c <Wrong mask> -n 4
+2. Verify: the application complains about the mask and does not start.
-Verify: the application complains about the mask and does not start.
-
-Stop ``test``.
+3. Stop ``test``.
--
2.25.1
next reply other threads:[~2022-06-08 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:49 Yaqi Tang [this message]
2022-06-15 9:05 ` lijuan.tu
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=20220608044918.350522-1-yaqi.tang@intel.com \
--to=yaqi.tang@intel.com \
--cc=dts@dpdk.org \
/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).