From: Zhimin Huang <zhiminx.huang@intel.com>
To: dts@dpdk.org
Cc: Zhimin Huang <zhiminx.huang@intel.com>
Subject: [dts] [PATCH V1 2/4] test_plans/stats_checks_test_plan:rich test point in plan
Date: Wed, 8 Sep 2021 03:13:17 +0800 [thread overview]
Message-ID: <20210907191319.15494-3-zhiminx.huang@intel.com> (raw)
In-Reply-To: <20210907191319.15494-1-zhiminx.huang@intel.com>
add some new test points in plan:
stats_checks:
add clear stats test.
Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
---
test_plans/stats_checks_test_plan.rst | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/test_plans/stats_checks_test_plan.rst b/test_plans/stats_checks_test_plan.rst
index 51ec36d..327aaf2 100644
--- a/test_plans/stats_checks_test_plan.rst
+++ b/test_plans/stats_checks_test_plan.rst
@@ -264,6 +264,21 @@ FVL does not support hardware per queue stats,
so rx_qx_packets and rx_qx_bytes are both 0.
tx_qx_packets and tx_qx_bytes are both 0 too.
+6. Clear stats::
+
+ testpmd> clear port stats all
+
+7. Check stats and xstats, verify rx_good_packets, RX-packets of port 0 and tx_good_packets, TX-packets of port 1 are both 0.
+
+8. Repeat above 4 and 5 steps.
+
+9. Clear xstats::
+
+ testpmd> clear port xstats all
+
+10. Check stats and xstats, verify rx_good_packets, RX-packets of port 0 and tx_good_packets, TX-packets of port 1 are both 0.
+
+
Test Case: VF xstats Checks
============================
1. Create one VF port on a kernel PF, then bind the VF to pmd driver::
--
2.17.1
next prev parent reply other threads:[~2021-09-07 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 19:13 [dts] [PATCH V1 0/4] add plan and case Zhimin Huang
2021-09-07 19:13 ` [dts] [PATCH V1 1/4] test_plans/kernelpf_iavf_test_plan:rich test point in plan Zhimin Huang
2021-09-07 19:13 ` Zhimin Huang [this message]
2021-09-07 19:13 ` [dts] [PATCH V1 3/4] tests/kernelpf_iavf:rich test point in case Zhimin Huang
2021-09-07 19:13 ` [dts] [PATCH V1 4/4] tests/stats_checks:rich " Zhimin Huang
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=20210907191319.15494-3-zhiminx.huang@intel.com \
--to=zhiminx.huang@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).