From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 7F9FCC2DC for ; Tue, 26 May 2015 09:36:19 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 26 May 2015 00:36:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,496,1427785200"; d="scan'208";a="715562386" Received: from shvmail01.sh.intel.com ([10.239.29.42]) by fmsmga001.fm.intel.com with ESMTP; 26 May 2015 00:36:18 -0700 Received: from shecgisg003.sh.intel.com (shecgisg003.sh.intel.com [10.239.29.90]) by shvmail01.sh.intel.com with ESMTP id t4Q7aGgr027789; Tue, 26 May 2015 15:36:16 +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 t4Q7aEgj019465; Tue, 26 May 2015 15:36:16 +0800 Received: (from jingguox@localhost) by shecgisg003.sh.intel.com (8.13.6/8.13.6/Submit) id t4Q7aDci019461; Tue, 26 May 2015 15:36:13 +0800 From: TangHaifeng To: dts@dpdk.org Date: Tue, 26 May 2015 15:35:38 +0800 Message-Id: <1432625755-19403-5-git-send-email-haifengx.tang@intel.com> X-Mailer: git-send-email 1.7.4.1 In-Reply-To: <1432625755-19403-1-git-send-email-haifengx.tang@intel.com> References: <1432625755-19403-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_11/28=5D_add_unit=5Ftest=5Fqos_rst_file_in?= =?utf-8?q?to_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 07:36:20 -0000 --- test_plans/unit_tests_qos_test_plan.rst | 100 +++++++++++++++++++++++++++++++ 1 files changed, 100 insertions(+), 0 deletions(-) create mode 100644 test_plans/unit_tests_qos_test_plan.rst diff --git a/test_plans/unit_tests_qos_test_plan.rst b/test_plans/unit_tests_qos_test_plan.rst new file mode 100644 index 0000000..397c06a --- /dev/null +++ b/test_plans/unit_tests_qos_test_plan.rst @@ -0,0 +1,100 @@ +.. 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. + +============ +RED Autotest +============ + +This is the test plan for the Intel® DPDK Random Early Detection feature. + +This section explains how to run the unit tests for RED. 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>> red_autotest + +The final output of the test has to be "Test OK" + +============== +Meter Autotest +============== + +This is the test plan for the Intel® DPDK Metering feature. + +This section explains how to run the unit tests for Meter. 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>> meter_autotest + +The final output of the test has to be "Test OK" + +================== +Scheduler Autotest +================== + +This is the test plan for the Intel® DPDK Scheduler feature. + +This section explains how to run the unit tests for Scheduler. 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>> sched_autotest + +The final output of the test has to be "Test OK" \ No newline at end of file -- 1.7.4.4