test suite reviews and discussions
 help / color / mirror / Atom feed
From: yufengx.mo@intel.com
To: dts@dpdk.org
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 0/4] ipfix_flow_classify: upload test plan
Date: Wed,  6 Jun 2018 13:34:42 +0800	[thread overview]
Message-ID: <1528263286-23120-1-git-send-email-yufengx.mo@intel.com> (raw)

From: yufengmx <yufengx.mo@intel.com>

*. ixia multiple streams to do burst traffic 
*. ipfix_flow_classify test plan 
*. ipfix_flow_classify automation script 

yufengmx (4):
  ipfix_flow_classify: upload test plan
  ipfix_flow_classify: upload automation script
  ipfix_flow_classify: framework etgen/ixia function exetend
  ipfix_flow_classify: framework setting

 framework/etgen.py                           | 184 ++++++-
 framework/settings.py                        |   3 +-
 framework/tester.py                          |  53 +-
 test_plans/ipfix_flow_classify_test_plan.rst | 246 +++++++++
 tests/TestSuite_ipfix_flow_classify.py       | 714 +++++++++++++++++++++++++++
 5 files changed, 1193 insertions(+), 7 deletions(-)
 mode change 100755 => 100644 framework/tester.py
 create mode 100644 test_plans/ipfix_flow_classify_test_plan.rst
 create mode 100644 tests/TestSuite_ipfix_flow_classify.py

-- 
1.9.3

             reply	other threads:[~2018-06-06  5:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06  5:34 yufengx.mo [this message]
2018-06-06  5:34 ` [dts] [PATCH V1 1/4] " yufengx.mo
2018-06-06  5:34 ` [dts] [PATCH V1 2/4] ipfix_flow_classify: upload automation script yufengx.mo
2018-06-06  5:34 ` [dts] [PATCH V1 3/4] ipfix_flow_classify: framework etgen/ixia function exetend yufengx.mo
2018-06-06  5:34 ` [dts] [PATCH V1 4/4] ipfix_flow_classify: framework setting yufengx.mo

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=1528263286-23120-1-git-send-email-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    /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).