DPDK patches and discussions
 help / color / mirror / Atom feed
From: jspewock@iol.unh.edu
To: dev@dpdk.org
Cc: Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [RFC PATCH 0/1] add DTS smoke tests
Date: Thu, 13 Apr 2023 13:54:14 -0400	[thread overview]
Message-ID: <20230413175415.7683-2-jspewock@iol.unh.edu> (raw)

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

This patch series adds a set of smoke tests to be run at
the beginning of DTS execution. The point is to validate
the user’s setup before running “real” tests. This helps
save time by bailing out of DTS early when the setup is
not valid, and also prevents DTS displaying “false failures”
associated with an incorrect DTS setup.

More specificially, these tests will verify the following:
* DPDK fast-tests suite
* DPDK driver-test suite
* Devices are bound to the correct driver
* General information about the SUT (kernel version, compiler version,
etc.)
* DPDK testpmd starts, stops, and receives packets

Jeremy Spewock (1):
  dts: add smoke tests

 dts/conf.yaml                              |  7 ++-
 dts/framework/config/__init__.py           | 15 ++++++
 dts/framework/config/conf_yaml_schema.json | 16 +++++-
 dts/framework/dts.py                       | 19 ++++++-
 dts/framework/exception.py                 | 11 ++++
 dts/framework/test_result.py               | 13 +++--
 dts/framework/test_suite.py                | 24 ++++++++-
 dts/tests/TestSuite_smoke_tests.py         | 63 ++++++++++++++++++++++
 8 files changed, 159 insertions(+), 9 deletions(-)
 create mode 100644 dts/tests/TestSuite_smoke_tests.py

-- 
2.40.0


             reply	other threads:[~2023-04-13 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 17:54 jspewock [this message]
2023-04-13 17:54 ` [RFC PATCH 1/1] dts: add " 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=20230413175415.7683-2-jspewock@iol.unh.edu \
    --to=jspewock@iol.unh.edu \
    --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).