DPDK patches and discussions
 help / color / mirror / Atom feed
From: jspewock@iol.unh.edu
To: npratte@iol.unh.edu, thomas@monjalon.net, alex.chapman@arm.com,
	probb@iol.unh.edu, wathsala.vithanage@arm.com,
	Luca.Vizzarro@arm.com, Honnappa.Nagarahalli@arm.com,
	yoan.picchi@foss.arm.com, paul.szczepanek@arm.com,
	juraj.linkes@pantheon.tech
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v1 0/3] dts: port vf_smoke to new DTS
Date: Fri,  6 Sep 2024 13:37:06 -0400	[thread overview]
Message-ID: <20240906173709.17487-1-jspewock@iol.unh.edu> (raw)

From: Jeremy Spewock <jspewock@iol.unh.edu>

The VF smoke testing suite in the old DTS framework had the same test
cases as the PF smoke testing suite and, therefore, it makes sense to
have the two test suites use the same testing functions. In this series
the easiest way to do this was to simply parameterize what ports are
used for sending and receiving packets in the pf_smoke_tests suite and
then have the vf_smoke_testing suite extend from this class. This makes
it so that the two will always have the same test cases.

It was desirable to separate the testing into two different test suites
since, while their testing methods are the same, the two test suites
are testing disjoint functionality.

Depends-on: series-32935 ("dts: pf_smoke port")
Depends-on: series-32814 ("dts: add VFs to the framework")

Jeremy Spewock (3):
  dts: allow specifying ingress port in send_packets
  dts: parameterize ports used in pf_smoke suite
  dts: add vf_smoke tests suite

 dts/framework/config/conf_yaml_schema.json |  3 ++-
 dts/framework/test_suite.py                |  7 +++++-
 dts/tests/TestSuite_pf_smoke_tests.py      | 22 ++++++++++++++---
 dts/tests/TestSuite_vf_smoke_tests.py      | 28 ++++++++++++++++++++++
 4 files changed, 55 insertions(+), 5 deletions(-)
 create mode 100644 dts/tests/TestSuite_vf_smoke_tests.py

-- 
2.46.0


             reply	other threads:[~2024-09-06 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 17:37 jspewock [this message]
2024-09-06 17:37 ` [PATCH v1 1/3] dts: allow specifying ingress port in send_packets jspewock
2024-09-06 17:37 ` [PATCH v1 2/3] dts: parameterize ports used in pf_smoke suite jspewock
2024-09-06 17:37 ` [PATCH v1 3/3] dts: add vf_smoke tests suite jspewock

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=20240906173709.17487-1-jspewock@iol.unh.edu \
    --to=jspewock@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Luca.Vizzarro@arm.com \
    --cc=alex.chapman@arm.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=npratte@iol.unh.edu \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@arm.com \
    --cc=yoan.picchi@foss.arm.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).