[dts] [dts 11/28] add unit_test_qos rst file into dts

[TangHaifeng <haifengx.tang@intel.com>]

---
 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