From: Yogesh Jangra <yogesh.jangra@intel.com>
To: dts@dpdk.org
Cc: cristian.dumitrescu@intel.com, kamalakannan.r@intel.com,
harshad.suresh.narayane@intel.com, Suresh@dpdk.org,
Narayane@dpdk.org, R@dpdk.org
Subject: [PATCH 3/3] test_plan/pipeline: updated test suite documentation
Date: Wed, 16 Nov 2022 22:29:43 +0530 [thread overview]
Message-ID: <20221116165943.2700919-4-yogesh.jangra@intel.com> (raw)
In-Reply-To: <20221116165943.2700919-1-yogesh.jangra@intel.com>
Updated the testsuite documentation to explain the changes. In this
patch series we have updated the folder structure of the test suite.
So, updated the documentation as per that.
Signed-off-by: Yogesh Jangra <yogesh.jangra@intel.com>
Signed-off-by: Suresh Narayane, Harshad <harshad.suresh.narayane@intel.com>
Signed-off-by: R, Kamalakannan <kamalakannan.r@intel.com>
---
test_plans/pipeline_test_plan.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/test_plans/pipeline_test_plan.rst b/test_plans/pipeline_test_plan.rst
index 416e92a0..ee7a2af5 100644
--- a/test_plans/pipeline_test_plan.rst
+++ b/test_plans/pipeline_test_plan.rst
@@ -33,12 +33,12 @@ Bind them to dpdk igb_uio driver::
Supporting Files
================
-All the supporting files for this test suite are maintained in a tar file named "pipeline.tar.gz"
+All the supporting files for this test suite are maintained in the folder named "pipeline"
present in the {DTS_SRC_DIR}/dep directory.
Directory Structure of Each Test Case
=====================================
-Within {DTS_SRC_DIR}/dep/pipeline.tar.gz, all files related to a particular test case are maintained
+Within {DTS_SRC_DIR}/dep/pipeline folder, all files related to a particular test case are maintained
in a separate directory of which the directory structure is shown below::
test_case_name [directory]
--
2.25.1
prev parent reply other threads:[~2022-11-16 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:59 [PATCH 0/3] pipeline test suite dependency updated Yogesh Jangra
2022-11-16 16:59 ` [PATCH 1/3] dep: removed pipeline test suite tarball dependency Yogesh Jangra
2022-11-16 16:59 ` [PATCH 2/3] tests/pipeline: updated pipeline test suite Yogesh Jangra
2022-11-16 16:59 ` Yogesh Jangra [this message]
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=20221116165943.2700919-4-yogesh.jangra@intel.com \
--to=yogesh.jangra@intel.com \
--cc=Narayane@dpdk.org \
--cc=R@dpdk.org \
--cc=Suresh@dpdk.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dts@dpdk.org \
--cc=harshad.suresh.narayane@intel.com \
--cc=kamalakannan.r@intel.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).