From: "Peng, Yuan" <yuan.peng@intel.com>
To: "Sun, QinX" <qinx.sun@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Sun, QinX" <qinx.sun@intel.com>
Subject: Re: [dts] [PATCH V1 0/3] add test suite cvl_limit_value_test
Date: Wed, 4 Nov 2020 05:37:39 +0000 [thread overview]
Message-ID: <MWHPR11MB18565FF5D31F775EAF32E43EFEEF0@MWHPR11MB1856.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201104102528.6880-1-qinx.sun@intel.com>
Acked-by Peng, Yuan <yuan.peng@intel.com>
-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of sunqin
Sent: Wednesday, November 4, 2020 6:25 PM
To: dts@dpdk.org
Cc: Sun, QinX <qinx.sun@intel.com>
Subject: [dts] [PATCH V1 0/3] add test suite cvl_limit_value_test
These 8 cases take a long time to run, so split them from 3 already existed
suites (iavf_fdir, cvl_fdir, cvl_dcf_switch_filter) and make them as a new test suite
sunqin (3):
test_plans/cvl_limit_value_test: add test plan
tests/cvl_limit_value_test: add cvl_limit test suite
conf/cvl_limit_value_test: add config file for new test suite
conf/cvl_limit_value_test.cfg | 5 +
test_plans/cvl_limit_value_test_test_plan.rst | 594 ++++++++++++
tests/TestSuite_cvl_limit_value_test.py | 917 ++++++++++++++++++
3 files changed, 1516 insertions(+)
create mode 100644 conf/cvl_limit_value_test.cfg create mode 100644 test_plans/cvl_limit_value_test_test_plan.rst
create mode 100644 tests/TestSuite_cvl_limit_value_test.py
--
2.17.1
next prev parent reply other threads:[~2020-11-04 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 10:25 sunqin
2020-11-04 5:37 ` Peng, Yuan [this message]
2020-11-04 7:14 ` Sun, QinX
2020-11-04 10:25 ` [dts] [PATCH V1 1/3] test_plans/cvl_limit_value_test sunqin
2020-11-04 10:25 ` [dts] [PATCH V1 2/3] tests/cvl_limit_value_test add test suite sunqin
2020-11-04 10:25 ` [dts] [PATCH V1 3/3] conf/cvl_limit_value_test add config file sunqin
2020-11-11 3:18 ` [dts] [PATCH V1 0/3] add test suite cvl_limit_value_test Tu, Lijuan
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=MWHPR11MB18565FF5D31F775EAF32E43EFEEF0@MWHPR11MB1856.namprd11.prod.outlook.com \
--to=yuan.peng@intel.com \
--cc=dts@dpdk.org \
--cc=qinx.sun@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).