test suite reviews and discussions
 help / color / mirror / Atom feed
From: changqingxwu <changqingx.wu@intel.com>
To: dts@dpdk.org
Cc: changqingxwu <changqingx.wu@intel.com>
Subject: [dts] [PATCH V1] tests:add testsuite about example build
Date: Wed, 30 Jan 2019 15:39:05 +0800	[thread overview]
Message-ID: <1548833945-44963-1-git-send-email-changqingx.wu@intel.com> (raw)

Signed-off-by: changqingxwu <changqingx.wu@intel.com>
---
 tests/TestSuite_example_build.py | 76 ++++++++++++++++++++++++++++++++
 1 file changed, 76 insertions(+)
 create mode 100644 tests/TestSuite_example_build.py

diff --git a/tests/TestSuite_example_build.py b/tests/TestSuite_example_build.py
new file mode 100644
index 0000000..d49a3d8
--- /dev/null
+++ b/tests/TestSuite_example_build.py
@@ -0,0 +1,76 @@
+#BSD LICENSE
+#
+# Copyright(c) 2010-2017 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 example_build.
+"""
+
+import time
+import re
+from test_case import TestCase
+
+class TestExamplebuild(TestCase):
+
+    def set_up_all(self):
+        """
+        Run at the start of each test suite.
+        """
+        pass
+
+    def set_up(self):
+        """
+        Run before each test case.
+        """
+        pass
+
+    def test_example_build(self):
+        """
+        Verify example applications compile successfully
+        """
+        self.dut.send_expect('export PQOS_INSTALL_PATH=/root/intel-cmt-cat-master/lib', '#')
+        out = self.dut.build_dpdk_apps("./examples", '#')
+        verify_info = ['error','Error','Stop','terminate','failed','No such file','no input files','not found','No rule']
+        for failed_info in verify_info:
+            self.verify(failed_info not 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
-- 
2.17.2

             reply	other threads:[~2019-01-30  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  7:39 changqingxwu [this message]
2019-01-31  2:03 ` Tu, Lijuan
2019-02-01  1:24 ` Zhu, WenhuiX

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=1548833945-44963-1-git-send-email-changqingx.wu@intel.com \
    --to=changqingx.wu@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).