test suite reviews and discussions
 help / color / mirror / Atom feed
From: TangHaifeng <haifengx.tang@intel.com>
To: dts@dpdk.org
Cc: jingguox.fu@intel.com
Subject: [dts] [dts 12/28] add unit_test_ring rst file into dts
Date: Tue, 26 May 2015 15:35:39 +0800	[thread overview]
Message-ID: <1432625755-19403-6-git-send-email-haifengx.tang@intel.com> (raw)
In-Reply-To: <1432625755-19403-1-git-send-email-haifengx.tang@intel.com>

---
 test_plans/unit_tests_ring_test_plan.rst |  123 ++++++++++++++++++++++++++++++
 1 files changed, 123 insertions(+), 0 deletions(-)
 create mode 100644 test_plans/unit_tests_ring_test_plan.rst

diff --git a/test_plans/unit_tests_ring_test_plan.rst b/test_plans/unit_tests_ring_test_plan.rst
new file mode 100644
index 0000000..9a0b2ed
--- /dev/null
+++ b/test_plans/unit_tests_ring_test_plan.rst
@@ -0,0 +1,123 @@
+.. 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.
+
+==============
+Ring Autotests
+==============
+
+This is the test plan for the Intel® DPDK ring library.
+
+Description
+===========
+
+#. Basic tests (done on one core)
+
+   - Using single producer/single consumer functions:
+
+     - Enqueue one object, two objects, MAX_BULK objects
+     - Dequeue one object, two objects, MAX_BULK objects
+     - Check that dequeued pointers are correct
+
+   - Using multi producers/multi consumers functions:
+
+     - Enqueue one object, two objects, MAX_BULK objects
+     - Dequeue one object, two objects, MAX_BULK objects
+     - Check that dequeued pointers are correct
+
+   - Test watermark and default bulk enqueue/dequeue:
+
+     - Set watermark
+     - Set default bulk value
+     - Enqueue objects, check that -EDQUOT is returned when
+       watermark is exceeded
+     - Check that dequeued pointers are correct
+
+#. Check quota and watermark
+
+   - Start a loop on another lcore that will enqueue and dequeue
+     objects in a ring. It will monitor the value of quota (default
+     bulk count) and watermark.
+   - At the same time, change the quota and the watermark on the
+     master lcore.
+   - The slave lcore will check that bulk count changes from 4 to
+     8, and watermark changes from 16 to 32.
+
+#. Performance tests
+
+   This test is done on the following configurations:
+
+   - One core enqueuing, one core dequeuing
+   - One core enqueuing, other cores dequeuing
+   - One core dequeuing, other cores enqueuing
+   - Half of the cores enqueuing, the other half dequeuing
+
+   When only one core enqueues/dequeues, the test is done with the
+   SP/SC functions in addition to the MP/MC functions.
+
+   The test is done with different bulk size.
+
+   On each core, the test enqueues or dequeues objects during
+   TIME_S seconds. The number of successes and failures are stored on
+   each core, then summed and displayed.
+
+   The test checks that the number of enqueues is equal to the
+   number of dequeues.
+
+#. Change watermark and quota
+
+   Use the command line to change the value of quota and
+   watermark. Then dump the status of ring to check that the values
+   are correctly updated in the ring structure.
+   
+=========================
+Ring Performance Autotest
+=========================
+
+This is the test plan for the Intel®  DPDK LPM Method in IPv6.
+
+This section explains how to run the unit tests for LPM in IPv6.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>> ring_perf_autotest
+
+
+The final output of the test has to be "Test OK"
-- 
1.7.4.4

  parent reply	other threads:[~2015-05-26  7:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  7:35 [dts] [dts 07/28] add unit_test_mbuf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 08/28] add unit_test_mempool " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 09/28] add unit_tests_pmd_perf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 10/28] add unit_test_power " TangHaifeng
2015-05-26  9:01   ` Liu, Yong
2015-05-26  7:35 ` [dts] [dts 11/28] add unit_test_qos " TangHaifeng
2015-05-26  7:35 ` TangHaifeng [this message]
2015-05-26  7:35 ` [dts] [dts 13/28] add unit_test_ringpmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 14/28] add unit_test_timer " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 15/28] add unit_test_cmdline testcase " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 16/28] add unit_test_dump " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 17/28] add unit_test_eal " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 18/28] add unit_test_ivshmem " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 19/28] add unit_test_kni " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 20/28] add unit_test_lpm " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 21/28] add unit_test_mbuf " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 22/28] add unit_test_mempool " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 23/28] add unit_test_pmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 24/28] add unit_test_power " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 25/28] add unit_test_qos " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 26/28] add unit_test_ring " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 27/28] add unit_test_ringpmd " TangHaifeng
2015-05-26  7:35 ` [dts] [dts 28/28] add unit_tests_timer " TangHaifeng

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=1432625755-19403-6-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).