From: "Coyle, David" <david.coyle@intel.com>
To: "Troy, Rebecca" <rebecca.troy@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Power, Ciara" <ciara.power@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Akhil Goyal <gakhil@marvell.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: refactor docsis to show hidden cases
Date: Thu, 28 Oct 2021 10:34:29 +0000 [thread overview]
Message-ID: <DM8PR11MB5575CCEBF1219E9A98C1AF40E3869@DM8PR11MB5575.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211022105302.3652-1-rebecca.troy@intel.com>
Hi Rebecca, see below
> -----Original Message-----
> From: Troy, Rebecca <rebecca.troy@intel.com>
>
> In the current implementation, the docsis test cases are running and being
> reported as one test, despite the fact that multiple test cases are hidden
> inside i.e. "test_DOCSIS_PROTO_all" runs
> 52 test cases. Each docsis test case should be reported individually instead.
[DC] Should make "docsis" all uppercase in the commit message - "DOCSIS"
>
> This commit achieves this by removing the use of the
> test_DOCSIS_PROTO_all function and statically listing the test cases to run
> when building the test suite, which are then reported to the user by
> description.
>
> Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> ---
> app/test/test_cryptodev.c | 265 +++++++-----------
> ...t_cryptodev_security_docsis_test_vectors.h | 159 +++++++++--
> 2 files changed, 241 insertions(+), 183 deletions(-)
>
>
<snip>
> +
> static struct unit_test_suite docsis_proto_testsuite = {
> .suite_name = "Docsis Proto Unit Test Suite",
[DC] Outside the specific changes of this patch, but "Docsis" should be all uppercase in the
suite name too - "DOCSIS"... could take this opportunity to fix up this minor one
> .setup = docsis_proto_testsuite_setup,
> .unit_test_cases = {
> - TEST_CASE_ST(ut_setup_security, ut_teardown,
> - test_DOCSIS_PROTO_all),
> + /* Uplink */
> + ADD_UPLINK_TESTCASE(docsis_test_case_1)
> + ADD_UPLINK_TESTCASE(docsis_test_case_2)
> + ADD_UPLINK_TESTCASE(docsis_test_case_3)
> + ADD_UPLINK_TESTCASE(docsis_test_case_4)
<snip>
>
> -struct docsis_test_data docsis_test_case_1 = {
> +const struct docsis_test_data docsis_test_case_1 = {
> + .test_descr_uplink = {"AES-DOCSIS-BPI-128 and CRC Verify (24-byte "
> + "frame, Small offset and runt block encryption)"},
> + .test_descr_downlink = {"CRC Generate and AES-DOCSIS-BPI-128
> (24-byte "
> + "frame, Small offset and runt block encryption)"},
[DC] This one is my fault when I supplied the descriptions, so apologies about this,
but all the uplink descriptions should say "decryption" instead of "encryption"
Also I think all the descriptions should say "Uplink" or "Downlink" at the start.
This can be inferred from the order of AES-DOCSIS-BPI and CRC in the description, but
when I ran the test cases, I still had to think are these Uplink or Downlink tests.
It would be much clearer if it's stated explicitly
Regards,
David
next prev parent reply other threads:[~2021-10-28 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 10:53 Rebecca Troy
2021-10-28 10:34 ` Coyle, David [this message]
2021-10-28 10:41 ` Troy, Rebecca
2021-10-29 9:04 ` [dpdk-dev] [PATCH v2] test/crypto: refactor DOCSIS " Rebecca Troy
2021-11-02 10:40 ` Power, Ciara
2021-11-03 18:56 ` Akhil Goyal
2021-11-02 10:46 ` Coyle, David
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=DM8PR11MB5575CCEBF1219E9A98C1AF40E3869@DM8PR11MB5575.namprd11.prod.outlook.com \
--to=david.coyle@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=rebecca.troy@intel.com \
--cc=roy.fan.zhang@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).