test suite reviews and discussions
 help / color / mirror / Atom feed
From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V1 6/6] add xstats_test_plan code
Date: Mon, 15 Aug 2016 12:46:55 +0800	[thread overview]
Message-ID: <1471236415-13011-6-git-send-email-gangx.xu@intel.com> (raw)
In-Reply-To: <1471236415-13011-1-git-send-email-gangx.xu@intel.com>

Signed-off-by: xu,gang <gangx.xu@intel.com>
---
 test_plans/xstats_test_plan.rst | 40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 test_plans/xstats_test_plan.rst

diff --git a/test_plans/xstats_test_plan.rst b/test_plans/xstats_test_plan.rst
new file mode 100644
index 0000000..bfcc747
--- /dev/null
+++ b/test_plans/xstats_test_plan.rst
@@ -0,0 +1,40 @@
+..  BSD LICENSE
+        Copyright(c) 2010-2016 Intel Corporation. All rights reserved.
+    All rights reserved.
+
+    Redistribution and use in source and binary forms, with or without
+    modification, are permitted provided that the following conditions
+    are met:
+
+    * Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in
+    the documentation and/or other materials provided with the
+    distribution.
+    * Neither the name of Intel Corporation nor the names of its
+    contributors may be used to endorse or promote products derived
+    from this software without specific prior written permission.
+
+    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+Test Case:test_xstats
+=======================================
+Run this case ::
+        ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x1e -n 4 -- -i
+then::
+       start
+show port xstats info::
+       show port xstats 0
+in scapy to send packets and check port xstats info ::
+       show port xstats 0
+if received package is correct the case pass.
-- 
1.9.3

      parent reply	other threads:[~2016-08-15  4:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15  4:46 [dts] [PATCH V1 1/6] add hotplug test code xu,gang
2016-08-15  4:46 ` [dts] [PATCH V1 2/6] add hotplug_test_plan code xu,gang
2016-08-15  4:46 ` [dts] [PATCH V1 3/6] add l2fwd-jobstats test code xu,gang
2016-08-15  4:46 ` [dts] [PATCH V1 4/6] add l2fwd-jobstats_test_plan code xu,gang
2016-08-15  4:46 ` [dts] [PATCH V1 5/6] add xstats test code xu,gang
2016-09-06  6:28   ` Liu, Yong
2016-08-15  4:46 ` xu,gang [this message]

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=1471236415-13011-6-git-send-email-gangx.xu@intel.com \
    --to=gangx.xu@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).