test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, XinfengX" <xinfengx.zhao@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
Subject: Re: [dts] [PATCH V2] test_plans: add test plan for cryptodev unit-tests
Date: Mon, 25 Feb 2019 09:59:05 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA26C34@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1549001114-48291-1-git-send-email-xinfengx.zhao@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xinfeng Zhao
> Sent: Friday, February 1, 2019 2:05 PM
> To: dts@dpdk.org
> Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
> Subject: [dts] [PATCH V2] test_plans: add test plan for cryptodev unit-tests
> 
> add unit-tests_cryptodev_func_test_plan.rst
> 
> Signed-off-by: Xinfeng Zhao <xinfengx.zhao@intel.com>
> ---
>  test_plans/unit_tests_cryptodev_func_test_plan.rst | 79
> ++++++++++++++++++++
>  test_plans/unit_tests_cryptodev_test_plan.rst      | 85 ----------------------
>  2 files changed, 79 insertions(+), 85 deletions(-)  create mode 100644
> test_plans/unit_tests_cryptodev_func_test_plan.rst
>  delete mode 100644 test_plans/unit_tests_cryptodev_test_plan.rst
> 
> diff --git a/test_plans/unit_tests_cryptodev_func_test_plan.rst
> b/test_plans/unit_tests_cryptodev_func_test_plan.rst
> new file mode 100644
> index 0000000..6cb6c5e
> --- /dev/null
> +++ b/test_plans/unit_tests_cryptodev_func_test_plan.rst
> @@ -0,0 +1,79 @@
> +.. Copyright (c) 2016-2017 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.
> +
> +=====================
> +Unit Tests: Cryptodev
> +=====================
> +
> +
> +Description
> +===========
> +
> +This document provides the plan for testing Cryptodev API via Cryptodev unit
> tests.
> +Unit tests include supported Hardware and Software PMD(polling mode device)
> and supported algorithms.
> +Cryptodev API provides ability to do encryption/decryption by
> +integrating QAT(Intel@ QuickAssist
> +Technology) into DPDK. The QAT provides poll mode crypto driver support
> +for Intel@ QuickAssist Adapter 8950 hardware accelerator.
> +
> +The testing of Crytpodev API should be tested under either Intel
> +QuickAssist Technology DH895xxC hardware accelerator or AES-NI library.
> +
> +This test suite will run all cryptodev related unit test cases.
> +Alternatively, you could execute the unit tests manually by app/test DPDK
> application.
> +
> +Unit Test List
> +==============
> +
> +- cryptodev_qat_autotest
> +- cryptodev_aesni_mb_autotest
> +- cryptodev_openssl_autotest
> +- cryptodev_aesni_gcm_autotest
> +- cryptodev_null_autotest
> +- cryptodev_sw_snow3g_autotest
> +- cryptodev_sw_kasumi_autotest
> +- cryptodev_sw_zuc_autotest
> +- cryptodev_scheduler_autotest
> +
> +
> +Test Case Setup
> +===============
> +
> +#. Build DPDK and app/test app
> +#. Bind cryptodev devices to igb_uio driver #. Manually verify the
> +app/test by this command, as example, in your build folder::
> +
> +     ./app/test -c 1 -n 1
> +     RTE>> cryptodev_qat_autotest
> +
> +All Unit Test Cases are listed above.
> +
> +Expected all tests could pass in testing.
> diff --git a/test_plans/unit_tests_cryptodev_test_plan.rst
> b/test_plans/unit_tests_cryptodev_test_plan.rst
> deleted file mode 100644
> index ae2817b..0000000
> --- a/test_plans/unit_tests_cryptodev_test_plan.rst
> +++ /dev/null
> @@ -1,85 +0,0 @@
> -.. Copyright (c) 2016-2017 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.
> -
> -=====================
> -Unit Tests: Cryptodev
> -=====================
> -
> -
> -Description
> -===========
> -
> -This document provides the plan for testing Cryptodev API via Cryptodev unit
> tests.
> -Unit tests include supported Hardware and Software PMD(polling mode device)
> and supported algorithms.
> -Cryptodev API provides ability to do encryption/decryption by integrating
> QAT(Intel@ QuickAssist
> -Technology) into DPDK. The QAT provides poll mode crypto driver support for -
> Intel@ QuickAssist Adapter 8950 hardware accelerator.
> -
> -The testing of Crytpodev API should be tested under either Intel QuickAssist
> Technology DH895xxC hardware -accelerator or AES-NI library.
> -
> -This test suite will run all cryptodev related unit test cases. Alternatively, you
> could execute -the unit tests manually by app/test DPDK application.
> -
> -Unit Test List
> -==============
> -
> -- cryptodev_qat_autotest
> -- cryptodev_qat_perftest
> -- cryptodev_aesni_mb_perftest
> -- cryptodev_sw_snow3g_perftest
> -- cryptodev_qat_snow3g_perftest
> -- cryptodev_aesni_gcm_perftest
> -- cryptodev_openssl_perftest
> -- cryptodev_qat_continual_perftest
> -- cryptodev_aesni_mb_autotest
> -- cryptodev_openssl_autotest
> -- cryptodev_aesni_gcm_autotest
> -- cryptodev_null_autotest
> -- cryptodev_sw_snow3g_autotest
> -- cryptodev_sw_kasumi_autotest
> -- cryptodev_sw_zuc_autotest
> -
> -
> -Test Case Setup
> -===============
> -
> -#. Build DPDK and app/test app
> -#. Bind cryptodev devices to igb_uio driver -#. Manually verify the app/test by
> this command, as example, in your build folder::
> -
> -     ./app/test -c 1 -n 1
> -     RTE>> cryptodev_qat_autotest
> -
> -All Unit Test Cases are listed above.
> -
> -Expected all tests could pass in testing.
> --
> 2.7.4

  parent reply	other threads:[~2019-02-25  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  6:05 Xinfeng Zhao
2019-02-15  6:24 ` Chen, Zhaoyan
2019-02-25  9:59 ` Tu, Lijuan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-01  5:48 Xinfeng Zhao
2019-02-15  6:24 ` Chen, Zhaoyan

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=8CE3E05A3F976642AAB0F4675D0AD20E0BA26C34@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=xinfengx.zhao@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).