test suite reviews and discussions
 help / color / mirror / Atom feed
From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V1 1/2] test_plans/cvl_dcf_flow_priority: modify rule priority
Date: Mon,  6 Sep 2021 16:13:50 +0800	[thread overview]
Message-ID: <1630916031-119082-1-git-send-email-songx.jiale@intel.com> (raw)

because the priority of the dpdk rule is changed from 0<1<2... to 0>1>2..., 
modify the testplan

Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
 test_plans/cvl_dcf_flow_priority_test_plan.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/test_plans/cvl_dcf_flow_priority_test_plan.rst b/test_plans/cvl_dcf_flow_priority_test_plan.rst
index 8ae6052..b73f438 100644
--- a/test_plans/cvl_dcf_flow_priority_test_plan.rst
+++ b/test_plans/cvl_dcf_flow_priority_test_plan.rst
@@ -118,16 +118,16 @@ test steps for supported pattern
 ================================
 1. validate rules: two rules have same pattern, input set but different priority and action(priority 0 -> to vf 1, priority 1 -> to vf 2).
 2. create rules and list rules.
-3. send matched packets, check vf 2 receive the packets for hiting the priority 1.
+3. send matched packets, check vf 1 receive the packets for hiting the priority 0.
 4. send mismatched packets, check the packets are not received by vf 1 or 2.
-5. destroy rule with priority 1, list rules.
-6. send matched packets, check vf 1 receive the packets for hiting the priority 0.
+5. destroy rule with priority 0, list rules.
+6. send matched packets, check vf 2 receive the packets for hiting the priority 1.
 7. send mismatched packets, check the packets are not received by vf 1 or 2.
-8. recreate rules which priority is 1, list rule.
-9. destroy rule with priority 0, list rules.
-10. send matched packets, check vf 2 receive the packets for hiting the priority 1.
+8. recreate rules which priority is 0, list rule.
+9. destroy rule with priority 1, list rules.
+10. send matched packets, check vf 1 receive the packets for hiting the priority 0.
 11. send mismatched packets, check the packets are not received by vf 1 or 2.
-12. destroy rule with priority 1, list rules.
+12. destroy rule with priority 0, list rules.
 13. send matched packets, check the packets are not received by vf 1 or 2.
 
 
-- 
1.8.3.1


             reply	other threads:[~2021-09-06  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  8:13 Jiale Song [this message]
2021-09-06  8:13 ` [dts] [PATCH V1 2/2] tests/cvl_dcf_flow_priority: modify the script according to the testplan Jiale Song
2021-09-13  7:47 [dts] [PATCH V1 1/2] test_plans/cvl_dcf_flow_priority: modify rule priority Jiale Song

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=1630916031-119082-1-git-send-email-songx.jiale@intel.com \
    --to=songx.jiale@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).