From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lijuan.tu@intel.com, xueqin.lin@intel.com,
pingx.yu@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 0/1] [examples/flow_classify]: upload automation test script
Date: Fri, 20 Sep 2019 10:21:50 +0800
Message-ID: <20190920022151.11817-1-yufengx.mo@intel.com> (raw)
upload examples/flow_classify automation test script
v4:
- rebase source code.
-
v3:
- Follow Lin Xueqin suggestion
- refactor source code to run functional test cases.
- rename suite from ipfix_flow_classify to flow_classify.
- rename suite class TestIpfixFlowClassify to TestFlowClassify.
- remove ixia burst traffic source code of framework.
- remove ixia burst traffic source code/comment in suite script.
- remove burst packet type limitation.
- remove flow classify process status check methods.
- remove performance test cases.
- add functional test cases:
- test_udp_valid_rule
- test_udp_invalid_rule
- test_tcp_valid_rule
- test_tcp_invalid_rule
- test_sctp_valid_rule
- test_sctp_invalid_rule
- test_whole_rules
- change core mask from mutiple cores to one core.
- update copy right year.
yufengmx (1):
[examples/flow_classify]: upload automation test script
tests/TestSuite_flow_classify.py | 509 +++++++++++++++++++++++++++++++
1 file changed, 509 insertions(+)
create mode 100644 tests/TestSuite_flow_classify.py
--
2.21.0
next reply other threads:[~2019-09-20 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 2:21 yufengmx [this message]
2019-09-20 2:21 ` [dts] [PATCH V4 1/1] " yufengmx
2019-09-20 3:19 ` Lin, Xueqin
2019-09-20 6:08 ` 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=20190920022151.11817-1-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=pingx.yu@intel.com \
--cc=xueqin.lin@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
test suite reviews and discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.dpdk.org/dts/0 dts/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 dts dts/ http://inbox.dpdk.org/dts \
dts@dpdk.org
public-inbox-index dts
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://inbox.dpdk.org/inbox.dpdk.dts
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git