From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: qi.fu@intel.com, lijuan.tu@intel.com, Ke Xu <ke1.xu@intel.com>
Subject: [DTS][PATCH V1 0/4] update existing cases and add new sub-cases to validate port representor action and represented port action
Date: Fri, 30 Sep 2022 05:46:43 +0000 [thread overview]
Message-ID: <20220930054647.545932-1-ke1.xu@intel.com> (raw)
Deprecated TO_VF action contains a 'vf original' action which is not covered in
previous tests. This commit applys equivilant 'vf original' rule to previous
cases for 'vf id' action to cover 'vf original' action.
This patch adds the following subcases to cover the negative scenario of 'port
representor' action and 'represented port' action replacing 'vf original' action
and 'vf id' action.
1. Add second PF with VFs for following cases
2. Add a subcase to validate creating 'represented port' action on a representor
3. Add a subcase to validate creating 'represented port' action on a VF
4. Add a subcase to validate creating 'represented port' action to a VF
5. Add two subcases to validate creating 'represented port' action to DCFs
6. Add a subcase to validate creating 'represented port' action to a representor of another DCF
7. Add a subcase to validate creating 'port representor' action on a representor
8. Add a subcase to validate creating 'port representor' action on a VF
9. Add a subcase to validate creating 'port representor' action to a VF
10. Add a subcase to validate creating 'port representor' action to a representor
11. Add a subcase to validate creating 'port representor' action to another DCF
12. Add a subcase to validate deprecated action
13. Add a subcase to validate using an invalid port id
Ke Xu (4):
test_plans/ice_dcf_switch_filter: update existing TO_VF action cases to
cover port representor action from not covered vf original action
test_plans/ice_dcf_switch_filter: update existing negative cases to
validate represented port action and port representor action
tests/ice_dcf_switch_filter: update existing TO_VF action cases to
cover port representor action from not covered vf original action
tests/ice_dcf_switch_filter: update existing negative cases to
validate represented port action and port representor action
.../ice_dcf_switch_filter_test_plan.rst | 1060 +++++++++++++----
tests/TestSuite_ice_dcf_switch_filter.py | 662 ++++++----
2 files changed, 1268 insertions(+), 454 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-30 5:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 5:46 Ke Xu [this message]
2022-09-30 5:46 ` [DTS][PATCH V1 1/4] test_plans/ice_dcf_switch_filter: update existing TO_VF action cases to cover port representor action from not covered vf original action Ke Xu
2022-09-30 5:46 ` [DTS][PATCH V1 2/4] test_plans/ice_dcf_switch_filter: update existing negative cases to validate represented port action and port representor action Ke Xu
2022-09-30 5:46 ` [DTS][PATCH V1 3/4] tests/ice_dcf_switch_filter: update existing TO_VF action cases to cover port representor action from not covered vf original action Ke Xu
2022-09-30 5:46 ` [DTS][PATCH V1 4/4] tests/ice_dcf_switch_filter: update existing negative cases to validate represented port action and port representor action Ke Xu
2022-12-13 7:14 [DTS][PATCH V1 0/4] update existing cases and add new sub-cases to validate port representor action and represented port action Ke Xu
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=20220930054647.545932-1-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qi.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).