From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: ke1.xu@intel.com, tarcadia@qq.com
Subject: [DTS][Patch V1 0/2] Rewrite test suite for checksum_offload
Date: Wed, 12 Jul 2023 20:33:32 +0000 [thread overview]
Message-ID: <20230712203334.2032445-1-ke1.xu@intel.com> (raw)
Checksum offload cases were in bad situation. Cases are not well organized
in structure. Cases were added one by one along with the development of
features.
The very beginning cases are designed to verifying RX Checksum Offload
enabling / disabling. The followed cases are to verify the TX Offload, and
found a gap when TX introduces differences to IP and L4. Then IP and L4 RX
cases are added again. There were also a gap found on the flag verifying
and a seperate ol_flag case was added.
To better organizing the checksum offload cases. I introduced the scenario
based common cases and specific cases named with sufix to cover specific
scenarios of special requirements. And we placed all available test scopes
introduced in any existing cases to each of our common test execution to
ensure no leakage to our test scopes.
For scenarios, we introduce the very commonly used configurations for
checksum as our test scenarios. These scenarios cover combined usage of HW
checksum Offload, SW checksum and differently configured tunneling scenario,
w/wo VLAN. These cases formed a organized web for future cases that if a new
configuration is introduced, cases of new configuration combinations are to
be added but existing configurations for different scopes are not to be added.
For test scopes, we introduce verifying ol_flag, fwd stats, other verbose lines,
and forwarded packet capturing and analyzing. All these scopes are recorder for
verifying in each common checksum offload execution. This ensures no scope would
be missed in this rewrite and in future case updating.
The newly organized cases also helps better covering our existing test
requirements. A common packet sending and recording helps cut down the repeating
time cost of different executions for scope based redundant cases.
This rewrite also helps formating a data-process-seperated suite structure. The
test parameters and required packets are listed in front and cases are referring
to the configured parameters. This helps better reading the suite code.
In the test plan, new cases are added and old ones are merged with the new cases.
Packets, ol_flags, stats and related test scopes are listed in table to show where
the expected result is from.
Generally speaking, this case rewrite helps formating the case structure and helps
better maintaining the cases in future.
Ke Xu (2):
test_plans/checksum_offload: Refactor checksum_offload case.
tests/checksum_offload: Refactor checksum_offload case.
test_plans/checksum_offload_test_plan.rst | 1478 +++++++----------
tests/TestSuite_checksum_offload.py | 1766 +++++++++++----------
2 files changed, 1549 insertions(+), 1695 deletions(-)
--
2.34.1
next reply other threads:[~2023-07-12 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 20:33 Ke Xu [this message]
2023-07-12 20:33 ` [DTS][Patch V1 1/2] test_plans/checksum_offload: Refactor checksum_offload case Ke Xu
2023-07-12 20:33 ` [DTS][Patch V1 2/2] tests/checksum_offload: " Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 0/6] Rewrite test suite for checksum_offload, tso and vf_offload Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 1/6] test_plans/checksum_offload: Refactor checksum_offload case Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 2/6] tests/checksum_offload: " Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 3/6] test_plans/tso: Refactor TSO case Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 4/6] tests/tso: Refactor TSO cases Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 5/6] test_plans/vf_offload: Refactor checksum_offload case Ke Xu
2023-07-18 1:26 ` [DTS][Patch V2 6/6] tests/vf_offload: Refactor vf_offload cases Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 0/6] Rewrite test suite for checksum_offload, tso and vf_offload Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 1/6] test_plans/checksum_offload: Refactor checksum_offload case Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 2/6] tests/checksum_offload: " Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 3/6] test_plans/tso: Refactor TSO case Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 4/6] tests/tso: Refactor TSO cases Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 5/6] test_plans/vf_offload: Refactor checksum_offload case Ke Xu
2023-07-18 2:33 ` [DTS][Patch V3 6/6] tests/vf_offload: Refactor vf_offload cases 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=20230712203334.2032445-1-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=tarcadia@qq.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).