On 05/08/2016 13:59, Neil Horman wrote:
> On Fri, Aug 05, 2016 at 10:11:56AM +0100, Remy Horton wrote:
[..]
>> Cmocka's mocking relies on Gnu ld's --wrap feature, which has problems if
>> the function being mocked is defined in the same compilation unit that it is
>> used. Pity really as otherwise
On 03.08.2016 15:57, Doherty, Declan wrote:
> Some of the things I've come across include:
> No standard output format to integrated with continuous regression systems
> No ability to specify specific unit tests or groups of tests to run from the
> command line
> No standard set of test assertion
On 05/08/2016 08:41, Yerden Zhumabekov wrote:
[..]
> We use cmocka.org for tests. Written in C. It has support for:
> * mocking;
> * setup/teardown;
> * asserts;
> * test groups.
>
> Output is nicely formatted.
Cmocka's mocking relies on Gnu ld's --wrap feature, which has problems
if the functio
2016-08-04 19:55, Wiles, Keith:
>
> > On Aug 4, 2016, at 2:47 PM, Jim Murphy wrote:
> >
> > Hi,
> >
> > We are looking at using our existing test environment for our DPDK
> > applications that will run on our build servers. Hughpages therefore is an
> > issue. What is involved in running DPDK w
On Fri, Aug 05, 2016 at 10:11:56AM +0100, Remy Horton wrote:
>
> On 05/08/2016 08:41, Yerden Zhumabekov wrote:
> [..]
> > We use cmocka.org for tests. Written in C. It has support for:
> > * mocking;
> > * setup/teardown;
> > * asserts;
> > * test groups.
> >
> > Output is nicely formatted.
>
>
> On Aug 4, 2016, at 2:47 PM, Jim Murphy wrote:
>
> Hi,
>
> We are looking at using our existing test environment for our DPDK
> applications that will run on our build servers. Hughpages therefore is an
> issue. What is involved in running DPDK without huge pages?
Command line option ?no-hug
Hi,
We are looking at using our existing test environment for our DPDK
applications that will run on our build servers. Hughpages therefore is an
issue. What is involved in running DPDK without hugepages?
Thanks,
Jim
On Wed, Aug 3, 2016 at 1:46 PM, Ming Zhao(??)
wrote:
> googletest is a very
googletest is a very nice test framework and we use it very
extensively in our company(Luminate Wireless), together with gmock.
I understand the resistance from the maintainers that are concerned
about introducing a C++ dependency to a pure C code base. The approach
we take doesn't require any cha
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 princip
> -Original Message-
...
> 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.
I know where you are coming from on this point, and I general
On Wed, Aug 03, 2016 at 09:57:39AM +, Doherty, Declan wrote:
>
>
> > -Original Message-
> ...
> > 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
On Tue, Aug 02, 2016 at 11:52:24PM +0200, Thomas Monjalon wrote:
> 2016-08-02 21:37, Declan Doherty:
> > I've been trying out using google test as a possible replacement for our
> > unit
> > test framework and have put to together this series of patches with help
> > from
> > Anatoly as RFC to ge
2016-08-02 21:37, Declan Doherty:
> I've been trying out using google test as a possible replacement for our unit
> test framework and have put to together this series of patches with help from
> Anatoly as RFC to get peoples thoughts on migrating to google test.
Thanks for exploring new possibili
I've been trying out using google test as a possible replacement for our unit
test framework and have put to together this series of patches with help from
Anatoly as RFC to get peoples thoughts on migrating to google test.
To facilitate google test this rfc patch set contains build system changes
14 matches
Mail list logo
