DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
	Honnappa.Nagarahalli@arm.com, ohilyard@iol.unh.edu,
	lijuan.tu@intel.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [RFC PATCH v1 0/2] merge DTS testcase files to DPDK
Date: Wed,  6 Apr 2022 15:26:46 +0000	[thread overview]
Message-ID: <20220406152648.2916866-1-juraj.linkes@pantheon.tech> (raw)

DTS testcases with their testplans and configuration.

Outstanding items:
Create util and data subdirectories under tests/ and move
testsuite related files into them to better organize DTS:
Python libraries from framework/ which are only used by testcases.
Files from dep/ which are used only by testcases.

Starting out with just one testsuite and planning on adding more.

Juraj Linkeš (2):
  dts: merge DTS test_plans/pf_smoke_test_plan.rst to DPDK
  dts: merge DTS tests/TestSuite_pf_smoke.py to DPDK

 dts/test_plans/pf_smoke_test_plan.rst | 165 +++++++++++++++++++++++++
 dts/tests/TestSuite_pf_smoke.py       | 170 ++++++++++++++++++++++++++
 2 files changed, 335 insertions(+)
 create mode 100644 dts/test_plans/pf_smoke_test_plan.rst
 create mode 100644 dts/tests/TestSuite_pf_smoke.py

-- 
2.20.1


             reply	other threads:[~2022-04-06 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 15:26 Juraj Linkeš [this message]
2022-04-06 15:26 ` [RFC PATCH v1 1/2] dts: merge DTS test_plans/pf_smoke_test_plan.rst " Juraj Linkeš
2022-04-06 15:26 ` [RFC PATCH v1 2/2] dts: merge DTS tests/TestSuite_pf_smoke.py " Juraj Linkeš

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=20220406152648.2916866-1-juraj.linkes@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).