From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47])
 by dpdk.org (Postfix) with ESMTP id 298A0214A
 for <dev@dpdk.org>; Tue,  2 Aug 2016 23:52:26 +0200 (CEST)
Received: by mail-wm0-f47.google.com with SMTP id i5so309371482wmg.0
 for <dev@dpdk.org>; Tue, 02 Aug 2016 14:52:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=6wind-com.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id:user-agent:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=3e8/CTgJm8pSLix8aS+F+nNN4zP9bqaeMnI3PWkZ3TY=;
 b=Q1O9A3me42r+EY4+YVAOk2mYnzACPLa/Ht72mlTYiS9ZJP0frKgSd2vIjzpT7rWzgg
 w0nOlPwrGQb7IRXv6wH5QmcrWPWbVnr4X0D/fRRvLkMUXCJXO0HcO7kQN+9cKXb4Tvb/
 zYmy8BqvjPbqrvN+FPB7mA7syXX2VnXAorcNvu9keLLBPbkSl71lsKCc9LBCYOx9WZmN
 zAJTbNtaT3Q4e0wb9QUFmr7SV4XOCLZcPbOvfIFLz3u8iOxZIzZbe7TO2qPXvBNMu33p
 gUOC3z46MuKTsI09+gGa7RJmHZsKxPvgUoEDUpFjGrccvgqTKY2wQJtFJqtm1UCtemRa
 fKow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent
 :in-reply-to:references:mime-version:content-transfer-encoding;
 bh=3e8/CTgJm8pSLix8aS+F+nNN4zP9bqaeMnI3PWkZ3TY=;
 b=V+wsDV5YmC/JJ/snMt+T5IvAPuViSqmJdz4uOvOo1pPy0ViJaOe7KAWiFkl69KztKm
 Z35kdBGKoJaYhb/dzi8koZ2sIMIAtIY1MRaYUC4ruIU/uAlFLG1ihh0oapQieE8835yD
 D30p0ratbR7V6hK91Luge6jxcKfaiOhYPDqsquKfty+9BuIBWm00V5XuCq3umtzYXkU9
 jWl03g4dOBW5FOIYe9EHQCY60rfeWLtxng+1FHRUlev58+f0C4twNS5j1VEy0WN1QOD7
 dHAYrdYp10bx5l2afpBWPz+FSoLP5F87l97vvJT+wye1SR9FXv/lcEyrJuRVTQgtDmEH
 Y1Vg==
X-Gm-Message-State: AEkoouvNuOjf4Dm1MfMEVudvA6EhcqbBSWE8SzKb/YqaBR4GGbKcNnqdeufB6oKEUT+OYjCd
X-Received: by 10.28.35.86 with SMTP id j83mr60628318wmj.18.1470174745864;
 Tue, 02 Aug 2016 14:52:25 -0700 (PDT)
Received: from xps13.localnet (86.114.118.80.rev.sfr.net. [80.118.114.86])
 by smtp.gmail.com with ESMTPSA id f4sm23869710wmf.8.2016.08.02.14.52.25
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 02 Aug 2016 14:52:25 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Declan Doherty <declan.doherty@intel.com>
Cc: dev@dpdk.org
Date: Tue, 02 Aug 2016 23:52:24 +0200
Message-ID: <5511822.hGlaykcsx3@xps13>
User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <1470170269-20721-1-git-send-email-declan.doherty@intel.com>
References: <1470170269-20721-1-git-send-email-declan.doherty@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [RFC 0/4] Use Google Test as DPDK unit test framework
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 21:52:26 -0000

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 possibilities.

> To facilitate google test this rfc patch set contains build system changes to
> allow C++ to built within the DPDK framework, this intended for unit test code
> only, and to support google test which is a C++ framework. Don't worry, I'm not
> advocating making DPDK a C++ project :) 

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.

> Some of the major advantages of google test that I see over continuing to use the
> current test include giving a consist feel to all tests, a powerful test
> execution framework which allow individual test suites or tests to be specified
> from the command line, support for a standard xunit output which can be integrated
> into a continuous build systems, and a very powerful mocking library
> which allows much more control over testing failure conditions.

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)