From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Khangar, Churchill" <churchill.khangar@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"P, Venkata Suresh Kumar" <venkata.suresh.kumar.p@intel.com>,
"Khangar, Churchill" <churchill.khangar@intel.com>,
"Jangra, Yogesh" <yogesh.jangra@intel.com>
Subject: Re: [dts] [PATCH v2 0/4] add pipeline suite
Date: Wed, 18 Nov 2020 03:29:14 +0000 [thread overview]
Message-ID: <5c289aa6679442fea67ec45ac7ec983a@intel.com> (raw)
In-Reply-To: <1605254605-31556-1-git-send-email-churchill.khangar@intel.com>
> This patch series adds a new test suite for pipeline application.
> Pipeline example is an application for improved Software Switch (SWX)
> pipeline type that supports dynamically-defined packet headers, meta-data,
> actions and pipelines.
> Actions and pipelines are defined through instructions.
>
> New pipeline test suites aims to verify the all supported instructions by
> using required input, spec and cli files which are part of dependences
> directory(dep/pipeline.tar.gz).
>
> Patch details
> 1. Patch1 adds the pipeline dependencies archive and compressed file
> pipeline.tar.gz
> 2. Patch2 adds the details of pipeline test plan details
> pipeline_test_plan.rst
> 3. Patch3 adds the pipeline new test suite implementation file
> TestSuite_pipeline.py
> 4. Patch4 adds new pipeline application configuration in app_name.cfg
> file
>
> Churchill Khangar (4):
> dep: add pipeline test suite dependencies
> test_plans: add pipeline test plan document
> tests: add pipeline test suite
> conf/app_name: add pipeline app name config
>
> conf/app_name.cfg | 2 +
> dep/pipeline.tar.gz | Bin 0 -> 119666 bytes
> test_plans/pipeline_test_plan.rst | 122 +
> tests/TestSuite_pipeline.py | 5833
> +++++++++++++++++++++++++++++++++++++
> 4 files changed, 5957 insertions(+)
> create mode 100644 dep/pipeline.tar.gz
> create mode 100644 test_plans/pipeline_test_plan.rst create mode 100644
> tests/TestSuite_pipeline.py
>
> --
> 1.8.3.1
Applied
prev parent reply other threads:[~2020-11-18 3:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 8:03 Churchill Khangar
2020-11-13 8:03 ` [dts] [PATCH v2 1/4] dep: add pipeline test suite dependencies Churchill Khangar
2020-11-13 8:03 ` [dts] [PATCH v2 2/4] test_plans: add pipeline test plan document Churchill Khangar
2020-11-13 8:03 ` [dts] [PATCH v2 3/4] tests: add pipeline test suite Churchill Khangar
2020-11-13 8:03 ` [dts] [PATCH v2 4/4] conf/app_name: add pipeline app name config Churchill Khangar
2020-11-18 3:29 ` Tu, Lijuan [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=5c289aa6679442fea67ec45ac7ec983a@intel.com \
--to=lijuan.tu@intel.com \
--cc=churchill.khangar@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dts@dpdk.org \
--cc=venkata.suresh.kumar.p@intel.com \
--cc=yogesh.jangra@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).