diff mbox series

[V1] test_plans/coremask: modify test case name

Message ID 20220608044918.350522-1-yaqi.tang@intel.com (mailing list archive)
State Accepted
Headers
Series [V1] test_plans/coremask: modify test case name |

Checks

Context Check Description
ci/Intel-dts-format-test success Testing OK
ci/Intel-dts-pylama-test success Testing OK
ci/Intel-dts-doc-test success Testing OK
ci/Intel-dts-suite-test warning SKIPPED

Commit Message

Yaqi Tang June 8, 2022, 4:49 a.m. UTC 
  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(-)

Comments

Tu, Lijuan June 15, 2022, 9:05 a.m. UTC | #1 
On Wed,  8 Jun 2022 04:49:18 +0000, Yaqi Tang <yaqi.tang@intel.com> wrote:
> 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>


Applied, thanks
diff mbox series

Patch

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``.