From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V2 01/10] add ip_pipeline cfg test code
Date: Thu, 25 Aug 2016 16:24:14 +0800 [thread overview]
Message-ID: <1472113463-4298-1-git-send-email-gangx.xu@intel.com> (raw)
Signed-off-by: xu,gang <gangx.xu@intel.com>
---
tests/TestSuite_ip_pipeline_cfg.py | 100 +++++++++++++++++++++++++++++++++++++
1 file changed, 100 insertions(+)
create mode 100644 tests/TestSuite_ip_pipeline_cfg.py
diff --git a/tests/TestSuite_ip_pipeline_cfg.py b/tests/TestSuite_ip_pipeline_cfg.py
new file mode 100644
index 0000000..bdeda36
--- /dev/null
+++ b/tests/TestSuite_ip_pipeline_cfg.py
@@ -0,0 +1,100 @@
+#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.
+
+
+"""
+DPDK Test suite.
+Test Ip_pipeline_cfg.
+"""
+
+import dts
+import string
+import time
+import re
+import os
+import os.path
+from test_case import TestCase
+
+class TestIpPipelineCfg(TestCase):
+
+ def set_up_all(self):
+ """
+ Run at the start of each test suite.
+ """
+ self.dut_ports = self.dut.get_ports(self.nic)
+ self.verify(len(self.dut_ports) >= 2, "Insufficient ports")
+ cores = self.dut.get_core_list("1S/4C/1T")
+ self.coremask = dts.create_mask(cores)
+
+ self.path = "./examples/ip_pipeline/build/ip_pipeline"
+
+ self.dut.session.copy_file_to("dep/ip_pipeline.tar.gz")
+ self.dut.send_expect("tar -zxvf ~/ip_pipeline.tar.gz -C ~","# ",50)
+ # build sample app
+ out = self.dut.build_dpdk_apps("./examples/ip_pipeline")
+ self.verify("Error" not in out, "compilation error 1")
+ self.verify("No such file" not in out, "compilation error 2")
+
+ def set_up(self):
+ """
+ Run before each test case.
+ """
+ pass
+
+ def test_postive(self):
+ rootdir = "dep/ip_pipeline/ip_pipeline_cfg/postive/"
+ for parent,dirnames,filenames in os.walk(rootdir):
+ for filename in filenames:
+ cmd = self.path + " -p 0x3 -f ~/ip_pipeline/ip_pipeline_cfg/postive/%s" % filename
+ self.dut.send_expect(cmd,"[PIPELINE1]",50)
+ out = self.dut.send_expect("quit","# ",10)
+ self.verify("Bye!" in out, "Test failed on %s" % filename)
+
+ def test_negative(self):
+ rootdir = "dep/ip_pipeline/ip_pipeline_cfg/negative/"
+ for parent,dirnames,filenames in os.walk(rootdir):
+ for filename in filenames:
+ cmd = self.path + " -p 0x3 -f ~/ip_pipeline/ip_pipeline_cfg/negative/%s" % filename
+ out = self.dut.send_expect(cmd,"# ",50)
+ self.verify("error" in out, "Test failed on %s" % filename)
+
+ def tear_down(self):
+ """
+ Run after each test case.
+ """
+ self.dut.kill_all()
+ time.sleep(2)
+
+ def tear_down_all(self):
+ """
+ Run after each test suite.
+ """
+ pass
--
1.9.3
next reply other threads:[~2016-08-25 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 8:24 xu,gang [this message]
2016-08-25 8:24 ` [dts] [PATCH V2 02/10] add ip_pipeline cfg test plan xu,gang
2016-08-26 1:28 ` Liu, Yong
2016-08-25 8:24 ` [dts] [PATCH V2 03/10] add ip_pipeline cpu utilization test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 04/10] add ip_pipeline cpu utilization test plan xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 05/10] add ip_pipeline link_identification test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 06/10] add ip_pipeline link_identification test plan xu,gang
2016-08-26 2:19 ` Liu, Yong
2016-08-25 8:24 ` [dts] [dst][PATCH V2 07/10] add ip_pipeline parser_cleanup test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 08/10] add ip_pipeline parser_cleanup test plan xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 09/10] add ip_pipeline source_sink test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 10/10] add ip_pipeline source_sink test plan xu,gang
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=1472113463-4298-1-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).