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 4750143FB2; Tue, 7 May 2024 16:43:13 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3F6FD433DB; Tue, 7 May 2024 16:43:13 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id BD9D3433B1 for ; Tue, 7 May 2024 16:43:11 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id AACDC43FC9; Tue, 7 May 2024 16:43:11 +0200 (CEST) From: bugzilla@dpdk.org To: dts@dpdk.org Subject: [DTS/framework Bug 1438] Add additional packet checking functionality into DTS TestSuite Date: Tue, 07 May 2024 14:43:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DTS X-Bugzilla-Component: framework X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: npratte@iol.unh.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dts@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 target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17150929910.E04d1eB3.3798446 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: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org --17150929910.E04d1eB3.3798446 Date: Tue, 7 May 2024 16:43:11 +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=3D1438 Bug ID: 1438 Summary: Add additional packet checking functionality into DTS TestSuite Product: DTS Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: Normal Component: framework Assignee: dts@dpdk.org Reporter: npratte@iol.unh.edu Target Milestone: --- I think a discussion should be made around introducing extra functionality = into the TestSuite object within DTS. Old DTS, in numerous test suites, will explicitly insert a payload into a frame; some test suites may even analyse= the contents within the frame to ensure that the specified payload was received properly. A good example of this being the case in new DTS is the jumbofram= es suite I am working on. Implementation of packet verification can be done in= two way: Assessing both layers two and three in all received packets to verify = the expected packet was received, or alternatively, dissecting and inspecting t= he payload of each received packet and validating the user's previously defined payload in within one of these received packets. For those that prefer the latter, it might make sense to introduce a method that automatically does t= his and introduce some kind of "default" payload in each packet if the user lea= ves it unspecified. A potential benefit of this might be that we could create s= ome sort of "filter" method that, when called by the user, will return a list of packets that contain a defined payload as a parameter, effectively getting = rid of all the the junk packets the test suite doesn't care about. In any case,= I think a good concern could be raised about why this sort of filtering is not currently implemented in the framework currently. --=20 You are receiving this mail because: You are the assignee for the bug.= --17150929910.E04d1eB3.3798446 Date: Tue, 7 May 2024 16:43:11 +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
Bug ID 1438
Summary Add additional packet checking functionality into DTS TestSui= te
Product DTS
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity minor
Priority Normal
Component framework
Assignee dts@dpdk.org
Reporter npratte@iol.unh.edu
Target Milestone --- 

I think a discussion should be mad=
e around introducing extra functionality into
the TestSuite object within DTS. Old DTS, in numerous test suites, will
explicitly insert a payload into a frame; some test suites may even analyse=
 the
contents within the frame to ensure that the specified payload was received
properly. A good example of this being the case in new DTS is the jumbofram=
es
suite I am working on. Implementation of packet verification can be done in=
 two
way: Assessing both layers two and three in all received packets to verify =
the
expected packet was received, or alternatively, dissecting and inspecting t=
he
payload of each received packet and validating the user's previously defined
payload in within one of these received packets. For those that prefer the
latter, it might make sense to introduce a method that automatically does t=
his
and introduce some kind of "default" payload in each packet if th=
e user leaves
it unspecified. A potential benefit of this might be that we could create s=
ome
sort of "filter" method that, when called by the user, will retur=
n a list of
packets that contain a defined payload as a parameter, effectively getting =
rid
of all the the junk packets the test suite doesn't care about. In any case,=
 I
think a good concern could be raised about why this sort of filtering is not
currently implemented in the framework currently.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17150929910.E04d1eB3.3798446--