From: TangHaifeng <haifengx.tang@intel.com>
To: dts@dpdk.org
Cc: jingguox.fu@intel.com
Subject: [dts] [dts 05/28] add unit_test_kni rst file into dts
Date: Tue, 26 May 2015 14:57:27 +0800 [thread overview]
Message-ID: <1432623448-19146-5-git-send-email-haifengx.tang@intel.com> (raw)
In-Reply-To: <1432623448-19146-1-git-send-email-haifengx.tang@intel.com>
---
test_plans/unit_tests_kni_test_plan.rst | 60 +++++++++++++++++++++++++++++++
1 files changed, 60 insertions(+), 0 deletions(-)
create mode 100644 test_plans/unit_tests_kni_test_plan.rst
diff --git a/test_plans/unit_tests_kni_test_plan.rst b/test_plans/unit_tests_kni_test_plan.rst
new file mode 100644
index 0000000..9dec43a
--- /dev/null
+++ b/test_plans/unit_tests_kni_test_plan.rst
@@ -0,0 +1,60 @@
+.. Copyright (c) <2010>, Intel Corporation
+ 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.
+
+=============
+KNI Autotests
+=============
+
+This is the test plan for the Intel® DPDK KNI library.
+
+This section explains how to run the unit tests for KNI. The test can be
+launched independently using the command line interface.
+This test is implemented as a linuxapp environment application.
+
+The complete test suite is launched automatically using a python-expect
+script (launched using ``make test``) that sends commands to
+the application and checks the results. A test report is displayed on
+stdout.
+
+The steps to run the unit test manually are as follow::
+
+ # make -C ./app/test/
+ # insmod ./<TARGET>/kmod/igb_uio.ko
+ # insmod ./<TARGET>/kmod/rte_kni.ko
+ # ./app/test/test -n 1 -c ffff
+ RTE>> kni_autotest
+ RTE>> quit
+ # rmmod rte_kni
+ # rmmod igb_uio
+
+
+The final output of the test has to be "Test OK"
--
1.7.4.4
next prev parent reply other threads:[~2015-05-26 6:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 6:57 [dts] [dts 01/28] add unit_test_cmdline " TangHaifeng
2015-05-26 6:57 ` [dts] [dts 02/28] add unit_test_dump " TangHaifeng
2015-05-26 10:12 ` Fu, JingguoX
2015-05-26 6:57 ` [dts] [dts 03/28] add unit_test_eal " TangHaifeng
2015-05-26 10:13 ` Fu, JingguoX
2015-05-26 6:57 ` [dts] [dts 04/28] add unit_test_ivshmem " TangHaifeng
2015-05-26 10:13 ` Fu, JingguoX
2015-05-26 6:57 ` TangHaifeng [this message]
2015-05-26 10:13 ` [dts] [dts 05/28] add unit_test_kni " Fu, JingguoX
2015-05-26 6:57 ` [dts] [dts 06/28] add unit_test_lpm " TangHaifeng
2015-05-26 10:14 ` Fu, JingguoX
2015-05-26 10:12 ` [dts] [dts 01/28] add unit_test_cmdline " Fu, JingguoX
2015-06-01 9:09 ` Liu, Yong
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=1432623448-19146-5-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).