From: "Liu, Yong" <yong.liu@intel.com>
To: Lijuan Tu <lijuanx.a.tu@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH V1 1/2] add unit_tests_distributor_test_plan
Date: Wed, 03 Aug 2016 09:36:37 +0800 [thread overview]
Message-ID: <57A14AA5.9040703@intel.com> (raw)
In-Reply-To: <1470026999-7300-1-git-send-email-lijuanx.a.tu@intel.com>
Lijuan, please add description for each case.
On 08/01/2016 12:49 PM, Lijuan Tu wrote:
> Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
> ---
> test_plans/unit_tests_distributor_test_plan.rst | 59 +++++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
> create mode 100644 test_plans/unit_tests_distributor_test_plan.rst
>
> diff --git a/test_plans/unit_tests_distributor_test_plan.rst b/test_plans/unit_tests_distributor_test_plan.rst
> new file mode 100644
> index 0000000..6a2ede0
> --- /dev/null
> +++ b/test_plans/unit_tests_distributor_test_plan.rst
> @@ -0,0 +1,59 @@
> +.. 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.
> +
> +Prerequisites
> +=============
> +One 10Gb Ethernet port of the DUT is directly connected and link is up.
> +
> +===========================
> +Packet Distributor
> +===========================
> +
> +This is the test plan for Packet Distributor
> +
> +This section explains how to run the unit tests for distributor.
> +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 final output of the test will be average cycles of IO used per packet.
> +
> +The steps to run the unit test manually are as follow::
> +
> + # make -C ./app/test/
> + # ./app/test/test -n 1 -c ffff
> + RTE>> distributor_autotest
> +
next prev parent reply other threads:[~2016-08-03 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 4:41 [dts] [PATCH V1 0/2] Add packet distributor unit test plan and test script Lijuan Tu
2016-08-01 4:49 ` [dts] [PATCH V1 1/2] add unit_tests_distributor_test_plan Lijuan Tu
2016-08-03 1:36 ` Liu, Yong [this message]
2016-08-01 4:51 ` [dts] [PATCH V1 2/2] add unit_tests_distributor test script Lijuan Tu
2016-08-03 1:47 ` 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=57A14AA5.9040703@intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuanx.a.tu@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).