From: Remy Horton <remy.horton@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Declan Doherty <declan.doherty@intel.com>
Cc: dev@dpdk.org
Subject: Re: [RFC 0/4] Use Google Test as DPDK unit test framework
Date: Wed, 3 Aug 2016 10:16:53 +0100 [thread overview]
Message-ID: <f0dfe7aa-9b83-ecfd-e8a8-ad6d3cb72b78@intel.com> (raw)
In-Reply-To: <5511822.hGlaykcsx3@xps13>
On 02/08/2016 22:52, Thomas Monjalon wrote:
> 2016-08-02 21:37, Declan Doherty:
[..]
> You are not advocating but the unit test must be written in C++.
> I don't think it is a good idea to force people to write and maintain the tests
> in a different language than the code it tests.
In principle I agree, but in practice I don't see any alternative. All
the purely C-based frameworks I've (independently of Declan) tried don't
have the same flexibility as the C++ ones.
> It would be interesting to better describe in details what is missing currently
> and what such a framework can bring.
> (I agree there is a huge room for improvements on unit tests)
From my own perspective, mocking of functions is the main thing that is
missing. When testing KeepAlive this allowed me to reroute rte_malloc()
calls to the OS malloc() rather than having to startup/teardown the
hugepage subsystem.
..Remy
next prev parent reply other threads:[~2016-08-03 9:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 20:37 [RFC 0/4] Use Google Test as DPDK unit test framework Declan Doherty
2016-08-02 20:37 ` [RFC 1/4] mk: Add support for C++ compilation Declan Doherty
2016-08-02 20:37 ` [RFC 2/4] examples: add c++ example application Declan Doherty
2016-08-02 20:37 ` [RFC 3/4] eal: add command line option to log output to stdout Declan Doherty
2016-08-03 11:25 ` Neil Horman
2016-08-02 20:37 ` [RFC 4/4] app/test-gtest: example google test application Declan Doherty
2016-08-02 21:52 ` [RFC 0/4] Use Google Test as DPDK unit test framework Thomas Monjalon
2016-08-03 9:16 ` Remy Horton [this message]
2016-08-03 9:57 ` Doherty, Declan
2016-08-03 12:51 ` Neil Horman
2016-08-03 20:46 ` Ming Zhao(赵明)
2016-08-04 19:47 ` Jim Murphy
2016-08-04 19:55 ` Wiles, Keith
2016-08-05 7:42 ` Thomas Monjalon
2016-08-05 7:41 ` Yerden Zhumabekov
2016-08-05 9:11 ` Remy Horton
2016-08-05 12:59 ` Neil Horman
2016-08-05 14:54 ` Remy Horton
2016-08-03 11:31 ` Neil Horman
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=f0dfe7aa-9b83-ecfd-e8a8-ad6d3cb72b78@intel.com \
--to=remy.horton@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.