test suite reviews and discussions
 help / color / mirror / Atom feed
From: TangHaifeng <haifengx.tang@intel.com>
To: dts@dpdk.org
Cc: jingguox.fu@intel.com
Subject: [dts] [dts 26/28] add unit_test_ring testcase into dts
Date: Tue, 26 May 2015 15:35:53 +0800	[thread overview]
Message-ID: <1432625755-19403-20-git-send-email-haifengx.tang@intel.com> (raw)
In-Reply-To: <1432625755-19403-1-git-send-email-haifengx.tang@intel.com>

---
 tests/TestSuite_unit_tests_ring.py |  101 ++++++++++++++++++++++++++++++++++++
 1 files changed, 101 insertions(+), 0 deletions(-)
 create mode 100644 tests/TestSuite_unit_tests_ring.py

diff --git a/tests/TestSuite_unit_tests_ring.py b/tests/TestSuite_unit_tests_ring.py
new file mode 100644
index 0000000..cae07ef
--- /dev/null
+++ b/tests/TestSuite_unit_tests_ring.py
@@ -0,0 +1,101 @@
+# BSD LICENSE
+#
+# Copyright(c) 2010-2014 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.
+
+"""
+DPDK Test suite.
+
+Run all Ring autotests
+"""
+
+
+from test_case import TestCase
+
+#
+#
+# Test class.
+#
+
+
+class TestUnitTestsRing(TestCase):
+
+    #
+    #
+    #
+    # Test cases.
+    #
+
+    def set_up_all(self):
+        """
+        Run at the start of each test suite.
+        """
+        out = self.dut.build_dpdk_apps('./app/test/')
+        self.verify('make: Leaving directory' in out, "Compilation failed")
+
+    def set_up(self):
+        """
+        Run before each test case.
+        """
+        pass
+
+    def test_ring(self):
+        """
+        Run ring autotest.
+        """
+
+        self.dut.send_expect("./app/test/test -n 1 -c ffff", "R.*T.*E.*>.*>", 10)
+        out = self.dut.send_expect("ring_autotest", "RTE>>", 36000)
+        self.verify("Test OK" in out, "Test failed")
+        self.dut.send_expect("set_watermark test 100", "RTE>>")
+        out = self.dut.send_expect("dump_ring test", "RTE>>")
+        self.dut.send_expect("quit", "# ")
+        self.verify("watermark=100" in out, "Test failed")
+
+    def test_ring_performance(self):
+        """
+        Run ring performance autotest.
+        """
+
+        self.dut.send_expect("./app/test/test -n 1 -c fffe", "R.*T.*E.*>.*>", 30)
+        out = self.dut.send_expect("ring_perf_autotest", "RTE>>", 210)
+        self.dut.send_expect("quit", "# ")
+        self.verify("Test OK" in out, "Test failed")
+
+    def tear_down(self):
+        """
+        Run after each test case.
+        """
+        pass
+
+    def tear_down_all(self):
+        """
+        Run after each test suite.
+        """
+        pass
-- 
1.7.4.4

  parent reply	other threads:[~2015-05-26  7:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  7:35 [dts] [dts 07/28] add unit_test_mbuf rst file " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 08/28] add unit_test_mempool " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 09/28] add unit_tests_pmd_perf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 10/28] add unit_test_power " TangHaifeng
2015-05-26  9:01   ` Liu, Yong
2015-05-26  7:35 ` [dts] [dts 11/28] add unit_test_qos " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 12/28] add unit_test_ring " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 13/28] add unit_test_ringpmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 14/28] add unit_test_timer " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 15/28] add unit_test_cmdline testcase " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 16/28] add unit_test_dump " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 17/28] add unit_test_eal " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 18/28] add unit_test_ivshmem " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 19/28] add unit_test_kni " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 20/28] add unit_test_lpm " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 21/28] add unit_test_mbuf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 22/28] add unit_test_mempool " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 23/28] add unit_test_pmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 24/28] add unit_test_power " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 25/28] add unit_test_qos " TangHaifeng
2015-05-26  7:35 ` TangHaifeng [this message]
2015-05-26  7:35 ` [dts] [dts 27/28] add unit_test_ringpmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 28/28] add unit_tests_timer " TangHaifeng

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=1432625755-19403-20-git-send-email-haifengx.tang@intel.com \
    --to=haifengx.tang@intel.com \
    --cc=dts@dpdk.org \
    --cc=jingguox.fu@intel.com \
    /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).