From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 0/2] packet capture: update automation testing script/test plan *. new feature upload
Date: Wed, 4 Jan 2017 11:56:56 +0800 [thread overview]
Message-ID: <1483502218-25662-1-git-send-email-yufengx.mo@intel.com> (raw)
yufengmx (2):
Packet capture: upload automation test plan
Packet capture: upload automation testing script
test_plans/packet_capture_test_plan.rst | 376 ++++++++++++++++
tests/TestSuite_packet_capture.py | 730 ++++++++++++++++++++++++++++++++
2 files changed, 1106 insertions(+)
create mode 100644 test_plans/packet_capture_test_plan.rst
create mode 100644 tests/TestSuite_packet_capture.py
--
1.9.3
next reply other threads:[~2017-01-04 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 3:56 yufengmx [this message]
2017-01-04 3:56 ` [dts] [PATCH V1 1/2] Packet capture: upload automation test plan yufengmx
2017-01-04 3:56 ` [dts] [PATCH V1 2/2] Packet capture: upload automation testing script yufengmx
2017-01-16 2:48 [dts] [PATCH V1 0/2] packet capture: update automation testing script/test plan *. new feature upload 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=1483502218-25662-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).