From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1538] [DTS] [Doc] add section below "How to write a testsuite" for how to do traffic validation and/or testsuite validation
Date: Mon, 09 Sep 2024 17:06:54 +0000 [thread overview]
Message-ID: <bug-1538-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1538
Bug ID: 1538
Summary: [DTS] [Doc] add section below "How to write a
testsuite" for how to do traffic validation and/or
testsuite validation
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Luca's add-pktgen-and-testpmd-changes series is highlighting to me that we are
now providing a few paths for traffic validation through DTS, and testsuite
validation through testpmd queries. In the spirit of the goal of making DTS a
framework where people can start using it from no knowledge, and write a simple
testsuite in a matter of minutes, not hours, it probably makes sense to
organize some common strategies for testsuite validation through traffic
validation and/or testpmd queries, so new users can copy those strategies
easily. Jotting down a few high level notes for this below, but I can write
something more comprehensive for this doc patch.
1. Send and store the returned packet list using send_packets_and_capture(),
build expected returned packet list by mapping the packet list with
get_expected_packet(), then compare the two using
sendtestsuite.match_all_packets()
optional: User can also leverage framework/utils.py
generate_random_packets() to build a list of packets which can be used with the
above process, if desired.
2. Build a packet with a known payload, like:
packet = Ether() / IP() / Raw("XXXXXXXXX")
And then send the packet with testsuite.send_packet_and_capture, iterate
through the returned list, checking for a packet with that Raw layer contents.
3. Can also validate using the info returned by testpmd with show port info,
verbose output, etc.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4156 bytes --]
reply other threads:[~2024-09-09 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1538-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).