From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id E28799A92 for ; Tue, 26 May 2015 08:57:43 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP; 25 May 2015 23:57:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,496,1427785200"; d="scan'208";a="576764520" Received: from shvmail01.sh.intel.com ([10.239.29.42]) by orsmga003.jf.intel.com with ESMTP; 25 May 2015 23:57:41 -0700 Received: from shecgisg003.sh.intel.com (shecgisg003.sh.intel.com [10.239.29.90]) by shvmail01.sh.intel.com with ESMTP id t4Q6vcEU019493; Tue, 26 May 2015 14:57:38 +0800 Received: from shecgisg003.sh.intel.com (localhost [127.0.0.1]) by shecgisg003.sh.intel.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id t4Q6vaX7019188; Tue, 26 May 2015 14:57:38 +0800 Received: (from jingguox@localhost) by shecgisg003.sh.intel.com (8.13.6/8.13.6/Submit) id t4Q6vZvv019184; Tue, 26 May 2015 14:57:35 +0800 From: TangHaifeng To: dts@dpdk.org Date: Tue, 26 May 2015 14:57:24 +0800 Message-Id: <1432623448-19146-2-git-send-email-haifengx.tang@intel.com> X-Mailer: git-send-email 1.7.4.1 In-Reply-To: <1432623448-19146-1-git-send-email-haifengx.tang@intel.com> References: <1432623448-19146-1-git-send-email-haifengx.tang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: jingguox.fu@intel.com Subject: [dts] =?utf-8?q?=5Bdts_02/28=5D_add_unit=5Ftest=5Fdump_rst_file_i?= =?utf-8?q?nto_dts?= X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2015 06:57:44 -0000 --- test_plans/unit_tests_dump_test_plan.rst | 169 ++++++++++++++++++++++++++++++ 1 files changed, 169 insertions(+), 0 deletions(-) create mode 100644 test_plans/unit_tests_dump_test_plan.rst diff --git a/test_plans/unit_tests_dump_test_plan.rst b/test_plans/unit_tests_dump_test_plan.rst new file mode 100644 index 0000000..23dd993 --- /dev/null +++ b/test_plans/unit_tests_dump_test_plan.rst @@ -0,0 +1,169 @@ +.. Copyright (c) <2014>, 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. + +========================= +Dump log history Autotest +========================= + +This is the test plan for dump history log of Intel® DPDK . + +This section explains how to run the unit tests for dump history log. 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/ + # ./app/test/test -n 1 -c ffff + RTE>> dump_log_history + +The final output of the test will be the initial log of DPDK. + +================== +Dump ring Autotest +================== + +This is the test plan for dump the elements of Intel® DPDK ring. + +This section explains how to run the unit tests for dump elements of ring. +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/ + # ./app/test/test -n 1 -c ffff + RTE>> dump_ring + +The final output of the test will be detail elements of DPDK ring. + +===================== +Dump mempool Autotest +===================== + +This is the test plan for dump the elements of Intel® DPDK mempool. + +This section explains how to run the unit tests for dump elements of mempool. +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/ + # ./app/test/test -n 1 -c ffff + RTE>> dump_mempool + +The final output of the test will be detail elements of DPDK mempool. + +============================= +Dump Physical memory Autotest +============================= + +This is the test plan for dump the elements of Intel® DPDK physical memory. + +This section explains how to run the unit tests for dump elements of memory. +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/ + # ./app/test/test -n 1 -c ffff + RTE>> dump_physmem + +The final output of the test will be detail elements of DPDK physical memory. + +===================== +Dump Memzone Autotest +===================== + +This is the test plan for dump the elements of Intel® DPDK memzone. + +This section explains how to run the unit tests for dump elements of memzone. +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/ + # ./app/test/test -n 1 -c ffff + RTE>> dump_memzone + +The final output of the test will be detail elements of DPDK memzone. + +================ +Dump Struct size +================ + +This is the test plan for dump the size of Intel® DPDK structure. + +This section explains how to run the unit tests for dump structure size. +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/ + # ./app/test/test -n 1 -c ffff + RTE>> dump_struct_sizes + +The final output of the test will be the size of DPDK structure. -- 1.7.4.4