From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id 5530B4594A;
Mon, 9 Sep 2024 19:06:56 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 37C4A40ED8;
Mon, 9 Sep 2024 19:06:56 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
by mails.dpdk.org (Postfix) with ESMTP id 8910A40ED0
for ; Mon, 9 Sep 2024 19:06:54 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
id 7C1624594B; Mon, 9 Sep 2024 19:06:54 +0200 (CEST)
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
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: DTS
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: probb@iol.unh.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
op_sys bug_status bug_severity priority component assigned_to reporter cc
target_milestone
Message-ID:
Content-Type: multipart/alternative; boundary=17259016140.e6CCDAaE.3523792
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dev-bounces@dpdk.org
--17259016140.e6CCDAaE.3523792
Date: Mon, 9 Sep 2024 19:06:54 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
https://bugs.dpdk.org/show_bug.cgi?id=3D1538
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 si=
mple
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.=20
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.=20
2. Build a packet with a known payload, like:
packet =3D 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 conten=
ts.
3. Can also validate using the info returned by testpmd with show port info,
verbose output, etc.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--17259016140.e6CCDAaE.3523792
Date: Mon, 9 Sep 2024 19:06:54 +0200
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
[DTS] [Doc] add section below "How to write a testsuite&=
quot; 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-chan=
ges 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 si=
mple
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.=20
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.=20
2. Build a packet with a known payload, like:
packet =3D 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 conten=
ts.
3. Can also validate using the info returned by testpmd with show port info,
verbose output, etc.